PEERING POLICY
Guidelines for interconnection and route-server participation
SELECTIVE OPEN PEERING POLICY
We follow a selective, open peering strategy designed to balance performance and cost-efficiency. The main goal is to reduce transit dependency while delivering stable and low-latency connectivity for our users.
Peering is generally preferred when a network:
- is expected to exchange meaningful traffic volume,
- improves latency, resilience, and routing efficiency,
- adds strategic value through interconnection reach.
We additionally prioritize peers that:
- run services within our infrastructure,
- operate as customers, resellers, or partners with their own ASN,
- use BYOIP or comparable integration models in our network.
These scenarios typically benefit from shorter paths and stronger internal traffic exchange.
ROUTE SERVER PEERING
On shared interconnection platforms, we maintain an open policy via route servers and usually accept all available peers.
Requirements include:
- compliance with common routing best practices,
- valid IRR and RPKI data,
- stable and clean BGP announcements.
Individual peers may be filtered or suspended in case of operational issues or when mutual value is no longer present.
TRAFFIC MANAGEMENT & ABUSE PREVENTION
We reserve the right to temporarily rate-limit or restrict traffic in cases of abusive behavior, security incidents, or to preserve platform stability, especially during unusual or unexpected traffic patterns.
GENERAL REQUIREMENTS
- no known harmful routing behavior,
- valid IRR and RPKI records,
- clear technical or economic upside for both sides.
Peering is established over shared interconnection platforms (Internet Exchanges and/or private interconnects) where it is technically and economically reasonable.
We may reject new requests or terminate existing sessions when no sustainable mutual benefit can be identified.