Peering Policy

Our peering policy is built on transparency and flexibility, catering to both public and private peering needs. We ensure our network information is accurate and accessible, supporting the formation of effective and mutually advantageous peering partnerships.

Find our peering information at Peering DB

For route automation please use AS-NETROUTING as our AS-SET (source RIPE).

Peering Policy

Netrouting, with network ASN 6206, outlines its peering policy to establish effective and mutually beneficial peering relationships. Our approach emphasizes equitable exchanges, aligning with our global presence as detailed on our PeeringDB page.

Please note that this policy serves as a guideline and is subject to change.

Netrouting reserves the right to accept or decline peering requests at our discretion, and may terminate existing peering agreements without notice. We review peering applications via peering [at], and aim to respond within five working days.

General Guidelines

  • Peering partners must hold a valid Autonomous System Number (ASN) and utilize BGP4 for peering sessions.
  • Partners are prohibited from abusing the peering relationship. This includes pointing default routes, resetting next hops, or unauthorized sharing of next hops, unless explicitly permitted by Netrouting.
  • A 24/7 Network Operations Centre must be maintained by the peering partner.
  • Consistent route announcements across all peering points are required for both IPv4 and IPv6 sessions.
  • Any implemented filtering (AS, routes, prefix-limits) by the peering partner must be disclosed to Netrouting, along with any subsequent changes.
  • Announced prefixes should not exceed a /24 mask.
  • Peering partners must ensure their PeeringDB entries are current.
  • Traffic exchanged should not permanently exceed 75% of the physical interconnection capacity.

Public Peering Policy

This policy is valid for both IPv4 and IPv6 address families.

Netrouting, with network ASN 6206, will announce all its routes: our own network and all customers. We do not require our peering partners to maintain a specific inbound to outbound ratio, but a certain traffic level must be met to accept the peering. We require peering in both IPv4 and IPv6.

Public National Peering Locations

Netrouting encourages peering partners operating solely in The Netherlands to peer at least in two of the following Internet Exchange Points:

  • AMS-IX - Amsterdam, NL
  • LSIX - Amsterdam, NL

Public International Peering Locations

For international peering partners, Netrouting requires peering at a minimum of one European Internet Exchange Points from the list below:

  • AMS-IX - Amsterdam, NL
  • LSIX - Amsterdam, NL
  • DATAIX - Amsterdam, NL
  • Frys-IX - Amsterdam, NL
  • DE-CIX - Frankfurt, DE
  • LINX - London, UK
  • IXManchester - Manchester, UK
  • Netnod - Stockholm, SE
  • FL-IX - Miami, FL

Traffic Levels for Public Peering

No traffic levels are required for public peering. Netrouting reserves the right to decline any requests at its own discretion.

Private Peering Policy

Netrouting offers private interconnection at the following locations:

  • Netrouting Datacenter (Data Facilities The Hague) - The Hague, NL
  • Equinix AM1&2/AM3/AM5/AM6/AM7/AM11 - Amsterdam, NL
  • Nikhef - Amsterdam, NL
  • Bytesnet - Rotterdam, NL
  • SmartDC - Rotterdam, NL
  • Bytesnet - Groningen, NL
  • Interxion FRA1-16 - Frankfurt, DE
  • M247 Europe - Bucharest, RO
  • Colohouse - Miami, FL
  • Equinix HK2 - Hong Kong

Traffic Levels for Private Peering

For private peering, the aggregated traffic volume must be 500 Mbit/s or more at each interconnection. Netrouting requires that partners support both IPv4 and IPv6 peering.

Need help?

Check out our status page for current information on our infrastructure.

Network Status