Action 1: Prevent propagation of incorrect routing information
We enforce that prefix information must have an RPKI record value to be passed by our network infrastructure through the.
Action 3: Facilitate global operational communication and coordination
We will update the RIR/PeeringDB database as soon as any information changes.
Action 4: Facilitate validation of routing information on a global scale
We only allow IP prefixes that are recorded in the RIR database and have the correct RPKI record value to propagate through our network infrastructure.