Peering Policy AS 214481
Policy Overview
Our peering policy is OPEN, promoting the interconnection of networks to support efficient traffic exchange.
Requirements for Private Network Interconnect (PNI)
- Traffic Volume: We require a minimum of 250 Mbps of sustained, exchanged traffic (either over transit or IX) to establish PNI.
- On-net POP Location: Peering partners must have a presence at a common on-net POP. For details, please refer to our PeeringDB page.
- Costs and Cross Connects (XCs):
- If peering through an Internet Exchange (IX) incurs additional costs, please contact us to discuss arrangements.
- At POPs where XCs are free, we offer Remote Hands (RH) services for FREE to facilitate cross-connects for mutual benefit.
Peering Requirements
- AS Number and Addressing: Only public AS numbers and public IP prefixes are allowed. We do not accept RFC 1918 (private) address space.
- Routing Policy: No static or default routes should be pointed towards our ASN. We expect appropriate prefix announcements in line with BGP best practices.
- Network Operations Center (NOC): Your NOC should be reachable 24/7, with an escalation path in place for troubleshooting peering issues.
- Maximum Prefix Limits: Peering sessions must be configured with appropriate maximum prefix limits to prevent route leaks and other routing issues.
- Consistent Announcements: Announced prefixes must remain consistent and stable, with no frequent or unnecessary prefix withdrawals or additions.
- Filtering: You must ensure appropriate filtering to prevent route leaks, bogons, and other erroneous announcements.
Technical Requirements
We support both IPv4 and IPv6 peering sessions. For specific configuration details and session initiation, please reach out to our network team. Peering connections are generally established using BGP with MD5 authentication as an option if required by the peer.
Additional Information
Our peering policy is designed to support robust and secure interconnections. For further information, or if you have specific requests not covered here, please contact our peering team.
