Action 1: Prevent propagation of incorrect routing information
We validate the prefixes that the customer sends us before implement then.
Action 2: Prevent traffic with spoofed source IP addresses
We use URPF and Source Address validation.
Action 3: Facilitate global operational communication and coordination
We have dedicated emails for NOC, SOC, Peering and other contacts.
Action 4: Facilitate validation of routing information on a global scale
We use IRR and signed our routes with RPKI.
Also have updated data at PeeringDB.