Peering Policy

  • Peers must maintain a publicly routable ASN.
  • Peers must only send traffic from their own and downstream networks to us.
  • Peers must Only send us traffic destined for the routes we announce.
  • Peers must operate a Network Operations Center (NOC) reachable by email.
  • Peers must keep their IRR and registry data up to date at all times.
  • Peers must have a complete and current PeeringDB.
  • Peers shall enforce a strict routing policy to avoid route leaks.
  • Peers shall aggregate their routes to avoid routing table inflation.
  • Peers shall only export their own and downstream network routes to us.
  • Peers are encouraged to employ RPKI signing of their routes.
  • Prefixes with private or other invalid ASNs in AS_PATH will be filtered.
  • Prefixes pointing to well-known bogon addresses will be filtered.
  • Prefixes shorter than a /24 (IPv4) or /64 (IPv6) will be filtered.
  • Prefixes with invalid RPKI status will be filtered.
  • AS paths longer than 100 entries will be filtered.
  • We support usage of the GRACEFUL_SHUTDOWN community.
  • No guarantees are provided for availability or correctness; peer at your own risk.
  • Problematic or abusive peers will be disabled/removed immediately.
  • Policy and peering availability is subject to change without notice.