AS268047 (Masterinfo) WHOIS Information

Whois

as-block:       AS219548 - AS396075
descr:          ASN block not managed by the RIPE NCC
remarks:        ------------------------------------------------------
remarks:
remarks:        aut-num objects within this block represent routing
remarks:        policy published in the RIPE Database
remarks:
remarks:        For registration information,
remarks:        you can find the whois server to query, or the
remarks:        IANA registry to query on this web page:
remarks:        http://www.iana.org/assignments/ipv4-address-space
remarks:
remarks:        You can access databases of other RIR's at:
remarks:
remarks:        AFRINIC (Africa)
remarks:        http://www.afrinic.net/ whois.afrinic.net
remarks:
remarks:        APNIC (Asia Pacific)
remarks:        http://www.apnic.net/ whois.apnic.net
remarks:
remarks:        ARIN (Northern America)
remarks:        http://www.arin.net/ whois.arin.net
remarks:
remarks:        LACNIC (Latin America and the Carribean)
remarks:        http://www.lacnic.net/ whois.lacnic.net
remarks:
remarks:        ------------------------------------------------------
mnt-by:         RIPE-DBM-MNT
created:        2026-06-02T14:29:24Z
last-modified:  2026-06-02T14:29:24Z
source:         RIPE
remarks:        ****************************
remarks:        * THIS OBJECT IS MODIFIED
remarks:        * Please note that all data that is generally regarded as personal
remarks:        * data has been removed from this object.
remarks:        * To view the original object, please query the RIPE Database at:
remarks:        * http://www.ripe.net/whois
remarks:        ****************************

aut-num:        AS268047
as-name:        MASTERINFO
descr:          MASTERINFO INTERNET
import:         from AS268829   accept ANY
import:         from AS28343   accept ANY
import:         from AS263998   accept ANY
mp-import:      afi ipv6.unicast from AS268829   accept ANY
mp-import:      afi ipv6.unicast from AS28343   accept ANY
mp-import:      afi ipv6.unicast from AS263998   accept ANY
export:         to AS268829   announce AS268047:AS-MASTERINFO-ALL
export:         to AS28343   announce AS268047:AS-MASTERINFO-ALL
export:         to AS263998   announce AS268047:AS-MASTERINFO-ALL
mp-export:      afi ipv6.unicast to AS268829   announce AS268047:AS-MASTERINFO-ALL
mp-export:      afi ipv6.unicast to AS28343   announce AS268047:AS-MASTERINFO-ALL
mp-export:      afi ipv6.unicast to AS263998   announce AS268047:AS-MASTERINFO-ALL
admin-c:        Philipe Alves
tech-c:         Rudson Costa
remarks:        ===============================================
24 x 7 technical support regarding our BGP routing
policies or any inquiries concerning AS268047's
security and routing policies please reach out to us
at the following channels:
remarks:        ============================================================
AS268047 Basic Interconnection Requirements
============================================================
remarks:        ============================================================
The following is required from your organization in order to
establish a BGP session with MASTERINFO at ASN 268047:
- The customer must use a RIR assigned ASN.
- The customer must have a route/route6 object for each prefix
it intends to announce to us, which might include its own
prefixes and, if desired, its customers' prefixes as well (customer cone).
- Each route/route6 object corresponding to a customer prefix
(yours or a prefix from your customer cone) must inform the
correct ASN in its 'origin' field.
- The ASN mentioned in the 'origin' field of each route and route6
object must have its proper and corresponding aut-num object.
- The aforementioned aut-num objects must have a clear routing
policy stating what as-sets are to be announced to us.
- This as-set MUST be informed on PeeringDB ("IRR as-set/route-set")
remarks:        MASTERINFO strongly encourages you to use two simultaneous methods to
validate the origin of the prefixes you announce to us: IRR and ROA
(published in your RPKI regime). This is highly recommended because
some of our direct upstreams and also indirect upstreams may reject
any routes where there is a failure in the origin validation process.
remarks:        You can start this process by "cleaning up your own house first", then
working directly with your customers so they can do their homework too,
and, by doing that, we can all prevent route leaks and prefix hijacking
from happening. :-)
remarks:        Last but not least, please feel free to contact us if you have any questions
or need our assistance in working these best practices with you!
We will definitely make ourselves available to increase the security of the
Internet, your experience as our customer/partner, and in the best
interest of our mutual agreement!
============================================================
mnt-by:         MAINT-AS268829
changed:        rudsoncosta@3rsolution.com.br 20231102  #15:14:31Z
source:         RADB
last-modified:  2024-10-23T14:00:11Z