Peering Policy

Summary

Our policy is selectively open. We will peer with any network that meets the technical requirements below, operates a professionally run NOC, and is present at a common exchange or facility. We do not require traffic ratios for public peering, and we do not charge for settlement-free interconnection.

Technical requirements

A publicly registered ASN and a current PeeringDB record.
A fully staffed NOC reachable at all hours, with a role address per RFC 2142.
Consistent announcement of the same prefixes at every point where we interconnect.
Registered route objects in an IRR, and RPKI ROAs covering announced space.
No announcement of default, and no pointing of default at us.
No announcement of prefixes you are not authorized to originate or transit.
MD5 authentication on sessions is supported and available on request.
Prefixes longer than /24 for IPv4 or /48 for IPv6 are filtered, other than blackhole announcements.

What we announce

At public exchanges we announce our own space and the space of our transit customers. We do not announce routes learned from other peers, so peering with us provides reachability to our customer cone rather than to the whole table.

Announcements are consistent across all interconnection points unless you request otherwise. We honor standard traffic-engineering communities from peers where they are documented.

Private interconnection

Where sustained traffic between our networks justifies it, we will move the relationship onto private interconnection within the same facility. We fund our own side of the cross-connect. Private interconnection is generally worth discussing once traffic exceeds a few gigabits per second at peak.

Operational expectations

Planned maintenance is announced to the other party's NOC address in advance.
Sessions that remain down for an extended period without explanation may be removed.
We expect reasonable cooperation on tracing packet loss and routing anomalies.
Either party may terminate the arrangement on reasonable notice.

Requesting a session

Send your ASN, PeeringDB record, the exchanges or facilities where you would like to interconnect, and approximate traffic volumes to [email protected]. We aim to respond within two business days.

Requests to interconnect with a specific customer of ours, rather than with our network as a whole, should go to [email protected] instead, as that is a transit conversation rather than a peering one.