We have an open peering policy subject to the following requirements:

Requirements

• A publicly routable, unique ASN allocated by a registry (ARIN, RIPE, etc)
• Complete, updated, and accurate PeeringDB profile containing:
  • NOC email address
  • Prefix limits for IPv4/IPv6
  • IRR as-set (we filter peer routes based on valid IRR objects)
• Network router capable of running BGP
• Only send traffic destined for prefixes announced by AS1050 or downstreams of AS1050
• Only advertise prefixes originated or originated by downstreams
• No default route or the use static routes that are not authorized in writing
• Peering partner must adhere to the requirements of any applicable Internet Exchange

We encourage peering wherever reasonable as it contributes to our experimentation. Please contact us for coordination.

Route Policy

We currently support and/or filter the following:

• BGP Graceful Shutdown (RFC8326)
• Blackhole Community (RFC7999)
• Bogon prefixes
• Route Leak Prevention and Detection Using Roles (RFC9234)
• RPKI invalid route rejection (Valid and Unknown permitted)
• Small prefix rejection (>/24 IPv4, >/48 IPv6)
• Well-known Communities (RFC1997)

See communities for additional information