Action 1: Prevent propagation of incorrect routing information
We perform route origin validation on all BGP sessions.
Action 2: Prevent traffic with spoofed source IP addresses
We have packet filters on all eBGP links to reject packets not using our IP prefixes.
Action 3: Facilitate global operational communication and coordination
We keep our RIPEDB and PeeringDB records updated.
Action 4: Facilitate validation of routing information on a global scale
Our prefixes are covered by IRR route objects (RIPE) and RPKI ROAs. Our aut-num object contains our intended upstreams.