Open Peering Policy

01   Simple requirements

• No minimum traffic requirement.
• No traffic ratio requirement.
• No multi-location requirement: peering at a single mutually available location is welcome.
• No formal peering contract is normally required.

02   Peering options

We support IPv4 and IPv6. Both bilateral BGP sessions and peering through Internet Exchange (IX) route servers are accepted. Please see our PeeringDB entry for interconnection details.

03   Routing & security

Peers must announce only prefixes they are authorized to originate or propagate. Maintain accurate Internet Routing Registry (IRR) records and, where applicable, valid RPKI Route Origin Authorizations (ROAs). We may apply prefix, AS-path and RPKI-based filtering to protect routing security and stability.

04   Technical feasibility

Peering is subject to technical feasibility, available capacity and a mutually suitable interconnection. Our open policy does not guarantee that every request can be accommodated. We may decline or discontinue a session where necessary to protect network security or stability.