Peering Policy | Knowledge Base

Inter.link is the sustainable Network as a Service (NaaS) company, providing certified carbon neutral IP Transit, IP Access, Ethernet connectivity and DDoS protection services, on-demand in minutes.

Inter.link’s pan-European backbone network AS5405 features 2600+ peers and low latency reach to Internet audiences. Inter.link is a certified B Corporation and has received PAS 2060 Carbon Neutral Certification.

Our customers love us because we deliver:

In-depth performance engineering
Transit with tightly integrated DDoS protection
100% uptime SLA
Direct access to expert support and engineering via SlackConnect
On-demand provisioning via portal or API
Fully protected, redundant service that always favors the lowest latency paths

Network

Currently, Inter.link operates more than 40 Point of Presence in over 15 countries with at least 1 Point of Presence per country. We are present in well known data center facilities and maintain an acurate PeeringDB record [1]. All of our location are connected to at least 2 other locations. The Inter.link networks is fully 400GE enabled and Private Network Interconnects are possible with 10/25/100/400GE.

Peering Principles

Inter.link operates globally using AS5405. We’re present at various Internet Exchange Points in multiple regions, please see our PeeringDB record for more details. Please filter routes using our AS-SET RIPE::AS5405:INTERDOTLINK which is populated automatically and always up to date.

Our general peering policy is selective. Inter.link needs a rationale to enter into a peering relationship, which means it will only do so where this is to the mutual benefit of it and the potential peering partner. Therefore, Inter.link will only establish peering when this has the potential to improve the quality and service experience of its customers.

Inter.link peers to actively cooperate in achieving a balanced benefit and investment contribution to ensure that the relationship is and continues to be in the mutual interests of the parties.

While we are open for settlement free peerings, we prefer to setup direct peering sessions with peers, where we have substantial traffic only. (see Peering at Internet Exchanges)

Inter.link's overall traffic ratio is balanced. Inter.link downstream customers include large cloud service providers, major eyeballs, and other content providers.

We might accept, decline, or suspend peerings or PNIs for network, quality, or commercial reasons at any time. Our peering policy may change over time without further notice.

Contact and Information

Inter.link relies on PeeringDB to manage peerings. Therefore, our own record [1] is always kept up to date and should be consulted before contacting Inter.link's peering team.

New peering requests should be sent to peering-policy@inter.link only.

Existing peering partners should use noc@inter.link for implementation or technical matters.

Inter.link PeeringDB record: https://as5405.peeringdb.com/

Inter.link operates a public Looking Glass service: https://lg.as5405.net/

BGP Communities and other routing information can be found here.

Peering at Internet Exchanges

If feasible, we peer with IXPs route-servers in all regions. We announce all our prefixes via public route servers. However, we might announce certain prefixes in specific regions only from the purpose of traffic engineering.

For traffic levels above 1 Gbps 95/5 percentile, we are open for direct peering sessions.

Certain IXPs filter using the 'server via route server' flag from PeeringDB. Some of our customers use that flag for specific reasons. If you do not receive desired prefixes via route- servers, please apply for a direct peering session.

We prefer being connected to local IXPs and discourage remote peering or wide-area exchanges. Please refer to our PeeringDB record [1] for the closest available IXP. Inter.link may decide to join, upgrade, or leave IXPs at any time to ensure the quality of our network.

Currently, Inter.link does not have a ratio requirement for Peerings.

Private Network Interconnects (PNI)

For traffic levels above 10 Gbps 95/5 percentile, we are open to establish PNIs. PNIs will be evaluated on a per request basis. We do support PNIs with using the following interfaces:

10G-LR

25G-LR

100G-LR1

100G-LR4

400G-LR4

If you require a PNI with Inter.link, the first cross-connect order is paid for by you. Subsequent ports will be cost shared, e.g. the next is order is paid by us, etc. We prefer 25G/100G PNIs. If traffic exceeds 20G, we require multiple redundant connections, in different locations and regions if possible.

Currently, Inter.link does not have a ratio requirement for PNIs.

Peering Requirements

Peering sessions must always be set up using IPv4 and IPv6 or IPv6 only.
All prefixes announced to Inter.link must have valid IRR data or RPKI ROA.
BGP sessions must operate on non RFC1918/RFC5014 IPs only.
Peers must have a PeeringDB entry with accurate data
The peer will set next-hop-self on all advertised routes.
The peer must not point default or static routes to Inter.link routers.
The peer should operate a looking-glass tool or RIPE probes/anchors for debugging purposes.
The peer must cooperate with Inter.link in preventing DDoS attacks and any other network abuse/misconfiguration (e.g. prefix hijacking, etc).
The peer must maintain a network flow data collection system for debugging purposes.
The peer must run a NOC and must allow settlement free access to the NOC for operational issues.
We do support MP-BGP
We do support LACP with single or multiple members
We do support but do not prefer BGP MD5 configured sessions

General Information

A periodic review of this statement of principles will be conducted by Inter.link to ensure that the eligibility requirements are consistent with Inter.link’s business needs. Inter.link may amend this document at any time.

These Peering Principles take effect from September 1st, 2024 onwards. We seek to apply these principles to all new peering relationships established after that date and, to the extent reasonable, to changes to existing peering relationships.

Peering Policy - KnowledgeBase