Action 1: Prevent propagation of incorrect routing information
Route filters restrict announcements based on prefix lists.
Action 3: Facilitate global operational communication and coordination
Contact information is kept up-to-date in both the RIPE IRR DB and on PeeringDB.
Action 4: Facilitate validation of routing information on a global scale
All our routes are correctly documented in the RIPE IRR DB and associated RPKI objects have been created for these routes.