Areas Served: Global
Implementation of MANRS Actions
Action 1: Prevent propagation of incorrect routing informationEvery time a customer needs to propagate a prefix or add an ASN to their account, we email the correspondent RIR POC to validate the request. If not validated then it is not added into our systems. If validated, then it is added to our system that automatically creates a prefix list to filter customer inbound announcements.
Action 2: Prevent traffic with spoofed source IP addressesWe strictly enforce uRPF on all of our interfaces, including those between internal devices.
Action 3: Facilitate global operational communication and coordinationYou can find our information on https://www.peeringdb.com/net/813
Action 4: Facilitate validation of routing information on a global scaleAll of our prefixes have their correspondent ROA at ARIN and RIPE. Also, we have the route set AS-CHOOPA registered in RADb (https://www.radb.net/query?keywords=AS-CHOOPA)
Action 5: Encourage MANRS adoptionWe encourage our customers to create their own ROAs for their prefixes, explain the benefits of RPKI, and promote MANRS adoption in different fora.
Why Vultr Supports MANRS
Tomas Lynch Senior Network Architect, Vultr