Action 1: Prevent propagation of incorrect routing information
We filter at the edge based on a networks:
- IRR Status
- RPKI Status
- Max Prefix count
Action 2: Prevent traffic with spoofed source IP addresses
We use static firewall rules to only allow traffic generated from our own prefixes onto the internet.
Action 3: Facilitate global operational communication and coordination
Our website, peeringdb, and whois all contain updated and active contact emails.
Action 4: Facilitate validation of routing information on a global scale
In addition to our AS-Set's we have information available on peeringdb and our own website about max prefix counts and what prefixes are announced.