Action 1: Prevent propagation of incorrect routing information
Customer BGP sessions are filtered to accept only authorized prefixes. Announcements to peers and transit providers are controlled via BGP communities.
Action 2: Prevent traffic with spoofed source IP addresses
GPC implements data plane filtering with various methods to prevent routing traffic with a spoofed source address to the rest of the internet.
Action 3: Facilitate global operational communication and coordination
All relevant contact information is listed in ARIN, or on our PeeringDB page @ https://www.peeringdb.com/asn/13807
Action 4: Facilitate validation of routing information on a global scale
GPC allocations have route(6) objects in the RADB IRR database. GPC ensures that transit customer prefixes have matching route(6) objects in an IRR database from the following list: AFRINIC, APNIC, ARIN, LACNIC, RIPE, RADB, LEVEL3, NTTCOM. GPC RIR allocations have signed ROAs.