Peering Policy
We peer openly with networks that can improve the quality or resilience of our routes, at any of our points of presence.
- peering policy
- Open
- minimum traffic
- None
- points of presence
- All
- minimum for a PNI
- 5G
Before you ask
What we expect from a peer
Nothing unusual: a clean registry footprint and a session that protects both sides.
Requirements
- A registered ASN with valid contact details in an RIR database
- A published route object and, where available, an ROA/RPKI record for announced prefixes
- A public or private peering capability at a shared point of presence
- Support for BGP4 with 4-byte ASN support
Technical requirements
- IPv4 and/or IPv6 sessions, dual stack preferred
- Max-prefix limit set on both sides of the session
- No transit of routes learned from other peers
- RPKI origin validation applied on announced prefixes
Private interconnect
PNI from 5G of traffic
From 5G of traffic between our networks, a private interconnect in a shared facility makes more sense than the exchange.
Supported port types
- 10G-LRSingle-mode fibre
- 40G-LR4Single-mode fibre
- 100G-LR4Single-mode fibre
How it works
Requesting a session
- 1
Check a shared location
Find a facility or exchange we have in common on our points of presence page or PeeringDB.
- 2
Send your request
Your ASN, the location you want and your IPv4 and IPv6 endpoints.
- 3
We bring it up
We answer within a few business days and configure our side.
Ready to peer?
Send your ASN, requested location and IPv4/IPv6 endpoints to our peering team.