AS53062

We have an open peering policy, and we welcome the opportunity to establish peering connections with any BGP operator, in an effort to improve the experience of our users.

Requests for BGP sessions or prefix releases must be made via email, following the templates at the link below:

BGP Requests

We keep our aut-num, as-set, route, and route6 objects updated in the IRR ALTDB database through MAINT-AS53062

#aut-num
whois -h whois.radb.net AS53062
#as-set
whois -h whois.radb.net AS-53062
#route
whois -h whois.radb.net -i origin AS53062 -T route
#route6
whois -h whois.radb.net -i origin AS53062 -T route6

https://irrexplorer.nlnog.net/asn/AS53062

• LOCAL_PREF is standard for each session type and cannot be changed through communities.
• All sessions with the same neighboring AS will be adjusted for the same type of session. (e.g.: a customer cannot be peering and transit at the same time, it is either one or the other).

Customers with multiple eBGP sessions with us may use the MED (Multi-Exit Discriminator) attribute to indicate their preferred ingress path between different circuits. This allows traffic entering our network to be directed to the desired circuit according to the MED values advertised by the customer. By default, lower MED values are preferred.

Notes:

• Invalid prefixes are rejected

Notes:

• We only accept /32 prefixes in Blackhole.
• The customer must tag the /32 prefix with community 53062:666

• The service works by monitoring potential traffic anomalies. When an anomaly is identified, primary triggers are activated to specifically filter the anomalous flow.
• Secondary triggers may take blackhole action.
• No community tagging is required for the mitigation service.
• The service is not standard. It must be contracted.

We tag all internal routes, from our customers, our upstreams, traffic exchange points, and private peerings using communities, allowing the customer to prioritize route selection:

Some customers (depending on the contract) can control the propagation of their announcements by tagging their prefixes with the following communities:

• Use our LG to check the effectiveness of community tagging.

Attention: It is important to understand that “no_export_to_xxx” communities will prevent the prefix from being exported to “xxx” on our direct BGP session(s). This will not prevent the prefix from reaching “xxx” via other connections. Example: if applying no_export_to_twitchpni, the prefix will not reach Twitch through our direct connection, but it may reach there via another upstream.

This tool allows routing (BGP protocol) queries and reachability and response time tests.

Our team can be reached through the iNOC-DBA project

Hotline Phone: 53062*100

http://inoc.nic.br/sobre/ http://inoc.nic.br/participantes/

https://manrs.org/ https://manrs.org/participant/1638/

— NOC Version: 2024062601 — Author: Marcelo Balbinot