Participant Info

  • Areas ServedBR
  • ASNs52999

Implementation of MANRS Actions

  • Action 1: Prevent propagation of incorrect routing information 1 - We validate all information submitted by our customers, for that we use whois and IRR. 2 - If there is no ROUTE-SET for the prefix then it will be created as Proxy Object. 3 - We add: AS-STARTNET-ALL Customer ASN. 4 - Create Filters and Prefix-List, release peering, validate again and finally release ad to 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 do have peering dB updated and can view it at: http://as52999.peeringdb.com And our information is updated at the RIR (RADB). Our "AS-SET" / "ROUTE-SET" IRR is AS-STARTNET All our customers and routing policies can be found there.