Open, transparent peering at major Internet Exchanges across Europe, the US and Asia.
Our peering policy is built on transparency and flexibility, catering to both public and private peering needs. We keep our network information accurate and accessible to support effective, mutually advantageous partnerships.
Find our full, up-to-date peering information including facilities and exchange points.
as6206.peeringdb.com →For route automation and IRR filtering, use our AS-SET.
AS-NETROUTING · source RIPENetrouting, 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] netrouting.com and aim to respond within five working days.
Peering partners must hold a valid ASN and use BGP4 for peering sessions.
No abuse of the peering relationship — no default routes, next-hop resets or unauthorized next-hop sharing unless explicitly permitted.
A 24/7 Network Operations Centre must be maintained.
Consistent route announcements across all peering points for both IPv4 and IPv6.
Any filtering (AS, routes, prefix-limits) must be disclosed to Netrouting, along with changes.
Announced prefixes should not exceed a /24 mask.
PeeringDB entries must be kept current.
Exchanged traffic should not permanently exceed 75% of the interconnection capacity.
Valid for both IPv4 and IPv6 address families.
Netrouting announces all its routes — our own network and all customers. We don't require a specific inbound/outbound ratio, but a certain traffic level must be met. We require peering in both IPv4 and IPv6.
Partners operating solely in The Netherlands are encouraged to peer at least at two of:
AMS-IX — Amsterdam, NL
LSIX — Amsterdam, NL
International partners must peer at a minimum of one European Internet Exchange 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
No traffic levels are required for public peering. Netrouting reserves the right to decline any request at its own discretion.
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
For private peering, aggregated traffic volume must be 500 Mbit/s or more at each interconnection. Partners must support both IPv4 and IPv6 peering.