Peering with fibranode.

The following criteria must be met for a peering relationship with fibranode Deutschland GmbH to be established:

• At least one shared Internet Exchange Point (IXP) with fibranode — two or more shared IXPs are preferred.
• Regular traffic volume of at least 200 Mbit/s.
• A complete and up-to-date PeeringDB entry.
• All technical parameters (ASNs, IPs, IX presence, contact details, peering policy) are taken directly from PeeringDB and must be accurate for session setup and ongoing operation.

The following rules apply to traffic exchange:

• Only IPv4 and IPv6 unicast traffic is accepted.
• Multicast traffic is not accepted.
• Traffic is restricted to the peer's own prefixes and the prefixes of the peer's direct customers.

We reserve the right to apply traffic filters and protective mechanisms to ensure the security and stability of our network.

• Only prefixes registered in a public Internet Routing Registry (IRR) such as RIPE, RADB or equivalent are accepted.
• Default routes are not accepted.
• Routes must be announced with correct and consistent origin AS information.
• We reserve the right to reject routes that negatively affect routing stability or network performance.

If traffic between a peer and fibranode consistently exceeds 5 Gbit/s, we are happy to discuss establishing a Private Network Interconnect (PNI).

Depending on traffic volume and requirements, we offer PNIs in the following capacities:

• 10 GbE
• 40 GbE
• 100 GbE

PNI locations and technical details are agreed upon by mutual arrangement. Once traffic volume justifies the operational and performance benefits, a PNI is generally the preferred solution over public IX peering.

Peering is possible at any of our PoPs — a full overview is available on our network map ↗. Please note that PNI capacities greater than 100 GbE are not available at every location.

• Peers operate a stable, professionally managed network.
• Maintenance work affecting peering sessions will be communicated in advance wherever possible.
• Up-to-date and responsive technical contacts are maintained in PeeringDB.

fibranode Deutschland GmbH reserves the right to suspend or terminate a peering session if:

• this policy is violated,
• PeeringDB information is outdated or incorrect,
• traffic patterns or routing behaviour negatively affect our network, or
• the peering relationship no longer provides mutual benefit.

Peering requests can be sent informally to our peering team. Please include your ASN, desired locations and — if known — expected traffic volume.