Peering policy.

We do not require a signed agreement, but are happy to do so where the agreement is reasonable.

We use PeeringDB as a single authoritative source of truth. This means peering partners must have an up-to-date PeeringDB entry before a bilateral peering session can be established. Both parties must have an up-to-date NOC contact email, which is responsive to raised issues and concerns.

Guidelines

• Hot-potato routing is implied. MEDs are not honoured.
• Settlement free peering.
• Neither party should ever establish a gateway of last resort configured towards the other party's network.
• A minimum of 5 Mbit/s is generally recommended but not required.
• We reserve the right to refuse peering with any party.

Private interconnection (PNI) requirements

If the network exchanges more than 1Gbps (95th) of traffic in a specific mutual location, either party can request a PNI. We accept single or multiples of 1/10/40/100G connections.

Information

To ensure quality of operations, we reserve the following rights under our peering policy:

• To alter our peering policy and peering requirements at any time.
• To accept or decline a peering request at any time for any reason.
• To suspend, without notice, peering connectivity in the event of severe QoS issues such as high latency, packet loss or jitter, and to take appropriate traffic engineering steps to maintain service quality.
• To selectively withdraw prefixes from public IXP fabrics as needed to protect service quality.
• To terminate any peering connection at any time without notice.