Action 1: Prevent propagation of incorrect routing information
We are Filtering Downstream-Prefixes via IRR and RPKI Validation. The prefix-lists used to validate the IRR information are updated every night and pushed to all our routers automatically. We are working on only accepting RPKI valid prefixes from our Downstream customers.
During the setup of new customers and subnets we are in close contact with the global IRRs to make sure the customer owns the specific subnets. Most of our customers currently announce PI space that is sponsored by us.
Action 3: Facilitate global operational communication and coordination
We‘re using the PeeringDB and the RIPE DB to publish the relevant contact information. Furthermore we are in close contact with other ISPs to be able to react quickly upon incidents.
Action 4: Facilitate validation of routing information on a global scale
These information are published in the RIPE DB and via RPKI. All the prefixes we announce are secured via RPKI and we drop RPKI Invalid prefixes (inbound).