We follow an open peering policy while requiring compliance with certain technical, business, and legal standards.
We build prefix and AS filtering based on the AS-SET listed in PeeringDB (if available) and validate routes using RPKI. Participation in the MANRS is encouraged to enhance the resilience and security of the global routing infrastructure.
Operational Requirements
Prioritize exchanging traffic on all available IXPs to ensure optimal traffic distribution and redundancy.
Ability to respond promptly to operational issues and security incidents.
Provide escalation paths for timely resolution of operational or security issues.
Technical Requirements
Hold a publicly routable ASN.
Possess publicly routable address space (at least one IPv6 /48).
Do not announce IPv6 prefixes with a mask length longer than /48.
Do not route default traffic to our network or use static routing to send traffic to our ASN unless otherwise agreed.
We announce only local prefixes at each PoP unless otherwise agreed.
Register prefixes in an appropriate Internet Routing Registry (IRR) as route/route6 objects and maintain accurate information on PeeringDB. This data will be used to build BGP prefix lists.
Currently, there is no minimum traffic requirement for establishing bilateral BGP sessions on public IXPs.