Participant Info

  • Areas ServedBR
  • ASNs52999

Implementation of MANRS Actions

  • Action 1: Prevent propagation of incorrect routing information 1- We validate all information sent by our customers through Whois and IRR. 2 - If there is no ROUTE-SET for DownStream prefixes, then it will be created as a Proxy Object. 3 - We add: The Customer ASN to Object AS52999:AS-CUSTOMERS. 4 - We create Filters with AS-PATH and Prefix-List, release peering, validate again and finally launch advertisement for our UpStream.
  • Action 2: Prevent traffic with spoofed source IP addresses We use: uRPF – Loose Mode (Router EBGP) uRPF – Strict Mode (Router IBGP)
  • Action 3: Facilitate global operational communication and coordination We are updated on whois and always looking at the abuse and NOC email.
  • Action 4: Facilitate validation of routing information on a global scale We have the updated peeringdb which can be viewed at: And our information is up to date in the IRR (RADB). Our IRR has the following Objects: "AUT-NUM" --> AS52999 "AS-SET" --> AS52999:AS-START. (main) "AS-SET" --> AS52999:AS-CONE. (Has member: AS52999:as-customers.) "AS-SET" --> AS52999:AS-CUSTOMERS. (Owns member: all of our downstream customers.) All of our customer and routing policies can be found there.