AS268047

// Masterinfo Internet //

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 

MM AS-53062-CUSTOMERSMM AS-OPENX-CUSTOMERSMM AS-MMTELECOMMM AS-UFINET-LATAM-BRASILMM AS-ITXBRMM AS-CTBC-CUSTOMERS236MM AS-ULTRATELECOM-BRMM AS-267613MM AS-CTBC-TOOLS

MM AS-53062-CUSTOMERS
MM AS-OPENX-CUSTOMERS
MM AS-MMTELECOM
MM AS-UFINET-LATAM-BRASIL
MM AS-ITXBR
MM AS-CTBC-CUSTOMERS236
MM AS-ULTRATELECOM-BR
MM AS-267613
MM AS-CTBC-TOOLS
#0 1
members: 0
members: 1
M AS268047