AS266003

aut-num: AS266003
as-name: JACSON-BOMFIM
descr: BRASILEIRO TELECOM
import: from AS14840 accept ANY
export: to AS14840 announce AS-266003
import: from AS35280 accept ANY
export: to AS35280 announce AS-266003
admin-c: BRTEL30
tech-c: BRTEL30
mnt-by: MAINT-AS266003
changed: matheus@routerx.net.br 20230530
source: ALTDB 
aut-num: AS266003
as-name: BRASILEIRO-TELECOM
descr: BRASILEIRO TELECOM (AS266003) aut-num
import: from AS61618 accept ANY
import: from AS14840 accept ANY
mp-import: afi ipv6.unicast from AS61618 accept ANY
mp-import: afi ipv6.unicast from AS14840 accept ANY
export: to AS61618 announce AS266003:AS-BRASILEIRO-TELECOM-ALL
export: to AS14840 announce AS266003:AS-BRASILEIRO-TELECOM-ALL
mp-export: afi ipv6.unicast to AS61618 announce AS266003:AS-BRASILEIRO-TELECOM-ALL
mp-export: afi ipv6.unicast to AS14840 announce AS266003:AS-BRASILEIRO-TELECOM-ALL
admin-c: RUDSON-COSTA-3R
tech-c: RUDSON-COSTA-3R
remarks: ========================================================== Abuse/UCE: abuse@brasileirotelecom.com.br Network: noc@brasileirotelecom.com.br Peering: peering@brasileirotelecom.com.br Website: https://www.brasileirotelecom.com.br/ Looking Glass: http://lg.brasileirotelecom.net.br/ Peering and Routing Policy: http://as266003.peeringdb.com/ ==========================================================
remarks: =============================================== 24 x 7 technical support regarding our BGP routing policies or any inquiries concerning AS266003's security and routing policies please reach out to us at the following channels:
remarks: Network issues / requests: noc@brasileirotelecom.com.br Peering issues / requests: peering@brasileirotelecom.com.br Abuse and SPAM : abuse@brasileirotelecom.com.br Or dial +55 (71) 3625-6479 ===============================================
remarks: ============================================================ AS266003 Basic Interconnection Requirements ============================================================
remarks: The following is required from your organization in order to establish a BGP session with Brasileiro at ASN 266003: - 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: Brasileiro 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-AS266003
changed: rudsoncosta@3rsolution.com.br 20250219 # 16:16 GMT
source: RADB
last-modified: 2025-02-19T16:16:21Z