Action 1: Prevent propagation of incorrect routing information
On our router filters we denied wrong prefixes by customer prefix-set and as-path using RADB as common database.
Action 2: Prevent traffic with spoofed source IP addresses
We as good practices using URPF to prevent customers to send spoofed packets beyond our network.
Action 3: Facilitate global operational communication and coordination
We updated weekly our PeeringDB with most recent contacts on our network.
Action 4: Facilitate validation of routing information on a global scale
Yes