Action 1: Prevent propagation of incorrect routing information
We strictly check the ownership of the networks we announce and carry traffic from.
When a customer requests a new announcement from our side, we verify the RIR objects and contact the indicated person to validate the request.
Routes are filtered both incoming and outgoing.
Action 2: Prevent traffic with spoofed source IP addresses
We implement several measures here.
At the edge, we rely on filters and external services like Team CYMRU's bogon service, discarding unallocated, invalid, and martian addresses.
Internal and customer machines are tied to their IP assignments, discarding traffic from non-assigned IP addresses.
Action 3: Facilitate global operational communication and coordination
Everyone can reach us about our network at [email protected] and other contact points in PeeringDB.
Humans constantly monitor those contact points.
Action 4: Facilitate validation of routing information on a global scale
All of our prefixes have their corresponding ROA at RIPE.
The community can use AS203099:AS-LOADFRONT for their filters.
Action 5: Encourage MANRS adoption
We encourage customers with IP space to have ROAs in place and follow MANRS practices, growing the community and following best practices for the good of all of the Internet.