- Areas ServedUS
Implementation of MANRS Actions
- Action 1: Prevent propagation of incorrect routing information All external BGP peer sessions have policies that only allow route updates containing a specific set of BGP communities. From our list of community-based policies (here: https://as14525.net/routing/bgp-communities/), only route updates tagged with 14525:50.* (internally originated) or 14525:54.* (downstream customers) are advertised to peers or transits. At the customer level, IRR data is used to only permit registered announcements from customer peers, all other announcements are dropped.
- Action 2: Prevent traffic with spoofed source IP addresses All transit, peer, and IX interfaces have uRPF loose mode enabled. Customer interfaces have uRPF strict mode, as well as source address validation via ACLs/filters to only allow traffic from their assigned address space to ingress the network.
- Action 3: Facilitate global operational communication and coordination Our PeeringDB entry is kept up to date immediately following any changes. We also maintain a separate site containing our routing and peering policies (as14525.net).
- Action 4: Facilitate validation of routing information on a global scale We maintain the as-set AS-AS14525 in the ARIN database, and request that all our peers and upstream transits use this information when filtering our announcements.
Why Stellar Technologies Inc. Supports MANRS
At Stellar, we place a high value on our responsibility to the internet community. MANRS compliance is something we've implemented since day one, and we will continue to ensure that our network meets or exceeds the community's mutually agreed upon routing standards.