de-cix.net No paid content found Multilingual

Interconnection is the physical and logical linking of two or more networks so they can exchange traffic directly. It is the underlying mechanism that turns thousands of separately operated networks into the internet. A network uses interconnection when it needs to reach destinations outside its own infrastructure — and the choice of how to interconnect (transit, public peering, or private peering) determines its cost, performance, and control over routing.

The three main interconnection options

These are not mutually exclusive. Most networks combine all three: transit for full reach, public peering for broad cost-effective coverage, and private peering for their heaviest traffic relationships.

Interconnection vs. transit vs. peering

The distinction matters because each solves a different problem.

• Transit is a commercial service. You buy a route to the whole internet from an upstream provider. It guarantees reachability but you pay for it, and the provider sits between you and the rest of the world.
• Peering is a settlement-free exchange between two networks that both benefit from the traffic. Each side accepts the other's routes and traffic directly. It reduces reliance on paid transit and can shorten the path traffic takes.
• Interconnection is the umbrella term for both. Transit and peering are two ways of interconnecting; the word describes the link itself, not the commercial arrangement.

A useful way to think about it: interconnection is the what, peering and transit are the how.

Why Internet Exchange Points matter

An Internet Exchange Point (IXP) is a physical location where many networks place equipment and connect to a shared switching fabric. Instead of building a separate link to every network it wants to reach, a network connects once to the IXP and can then peer with any other participant.

DE-CIX, for example, operates neutral Internet Exchanges across Europe, the Middle East, Africa, Asia, and the Americas, and describes its offering as premium interconnection services. "Neutral" here means the exchange itself does not compete with its customers for traffic — it provides the meeting point, not the connectivity.

The practical effect of an IXP:

1. One port, many peers. A single connection can reach dozens or hundreds of networks.
2. Lower latency. Traffic often takes a more direct path than it would through transit providers.
3. Lower cost. Peering at an IXP can replace a meaningful share of paid transit.
4. Resilience. Multiple peering relationships reduce dependence on any single path.

How networks decide where and how to interconnect

There is no single rule, but the decision usually weighs a few concrete factors:

• Traffic volume and direction. If a large share of your traffic goes to a specific network, a direct or private peering link becomes attractive. If traffic is spread across many networks, an IXP gives broader coverage per connection.
• Geography. Interconnecting close to where traffic originates or terminates reduces latency. This is why networks join IXPs in the regions they serve.
• Cost. Compare the price of transit capacity against the cost of a port at an IXP plus the effort of establishing peering relationships.
• Reach and redundancy. Transit provides full reach in one contract; peering requires building relationships network by network but gives more control and often better paths.
• Policy and willingness. Peering only happens when both networks agree. Larger networks are sometimes selective about whom they peer with, which is why transit remains necessary even for well-peered networks.

In practice, a network's interconnection strategy evolves: it may start on transit, add public peering as traffic grows, and establish private peering with its largest counterparts.

What this means if you are evaluating interconnection

If you are choosing how to connect, the question is not "peering or transit" but "which mix." Start by mapping where your traffic goes and where your users are. Then check which IXPs operate in those regions and which networks are present there. Transit covers the gaps that peering cannot. For most networks, the goal is to peer as much high-volume traffic as is practical and use transit for the rest — and an IXP is usually the most efficient place to make those peering connections happen.

A network, in the context of interconnection, is an independently operated system of connected devices and infrastructure that exchanges traffic with other networks. The operator controls its own routing decisions and is identified on the internet by an Autonomous System Number (ASN). Networks connect by exchanging routes and traffic — either directly through peering, through a paid transit provider, or by meeting many other networks at an Internet Exchange Point (IXP). The sections below explain the network types involved, how traffic is addressed between them, and what operators weigh when choosing where and with whom to interconnect.

Networks by role

Interconnection discussions usually distinguish networks by what they carry and whom they serve:

The same organization can operate more than one type. A large carrier may run access, transit, and content infrastructure at once, which changes its peering posture in each role.

How networks are identified and how traffic is routed

Every network that participates in global routing is identified by an Autonomous System Number (ASN). The network announces the IP address ranges it is responsible for, and other networks learn those routes through the Border Gateway Protocol (BGP).

The practical effect:

• A network announces its prefixes to its neighbors.
• Neighbors propagate those routes further, so every network builds a routing table of how to reach every prefix.
• When traffic is sent, each network forwards it to the next hop that its routing table says is best for that destination.
• The path traffic takes is therefore the result of many independent routing decisions, not a single central map.

This is why interconnection choices matter: they change which routes a network can use and how directly traffic reaches its destination.

How networks connect to each other

There are three common ways networks interconnect, and most operators use a mix:

Peering

Two networks agree to exchange traffic directly between themselves, typically without paying each other for the exchange. Peering can be private (a direct physical or virtual link between the two parties) or public (both parties connect to the same exchange fabric). Networks decide where to peer based on factors such as traffic volume, geographic proximity, cost, latency, and how much of their traffic goes to that partner.

Transit

A network buys connectivity from another network to reach the rest of the internet. Transit is the fallback that makes a network reachable even where it has no direct peering relationship. It is usually the paid option, in contrast to settlement-free peering.

Internet Exchange Points (IXPs)

An IXP is a shared physical and logical location where many networks connect to a common switching fabric and peer with each other. Joining one IXP can give a network many peering options through a single connection instead of building a separate link to every partner. DE-CIX operates neutral Internet Exchanges in Europe, the Middle East, Africa, Asia, and the Americas, and describes its services as premium interconnection services.

What networks consider when choosing interconnection partners or locations

The decision is usually a trade-off among measurable and strategic factors:

• Traffic volume and ratio — how much traffic flows each way between the two networks.
• Latency and path quality — whether a direct connection shortens the route to important destinations.
• Cost — port, cross-connect, transport, and any paid arrangement, weighed against the cost of transit.
• Reach — how many relevant networks, content sources, or end users are available at a given location.
• Redundancy — whether a new connection adds diversity or just duplicates an existing path.
• Operational effort — the work of configuring, monitoring, and maintaining each relationship.
• Neutrality and governance — whether the exchange or partner operates neutrally and under terms the network can accept.

Key terms to recognize

• Peering — direct traffic exchange between two networks, often settlement-free.
• Transit — paid connectivity that provides reach to the broader internet.
• IXP — a shared interconnection location where many networks meet.
• AS / ASN — an independently routed network and its identifying number.
• BGP — the routing protocol that exchanges reachability information between networks.
• Prefix — an IP address range a network announces and routes.

Understanding these terms is enough to follow most interconnection discussions and to evaluate why a given network peers where it does.

An Internet Exchange (IX) is a neutral physical and logical hub where separate networks connect directly to exchange traffic with each other. Instead of paying an upstream provider to carry every packet, a network joins an IX, establishes peering sessions with other members, and sends traffic straight to its destination. This matters most when you want lower latency, more control over routing, and reduced dependence on paid transit — but it only pays off if the networks you need to reach are actually present at that exchange.

The core idea: a shared switching fabric

An Internet Exchange Point (IXP) operates a shared network fabric — typically Ethernet switching infrastructure in one or more data centers. Each member connects a port to this fabric and runs BGP (Border Gateway Protocol) sessions with the other members it chooses to peer with.

The IX itself does not route your traffic or sell you reachability. It provides the meeting point. What you do there — which peers you establish, what routes you announce — is up to you and the networks you negotiate with.

DE-CIX, for example, describes itself as operating neutral Internet Exchanges across Europe, the Middle East, Africa, Asia, and the Americas, providing interconnection services to networks of many types. "Neutral" here means the exchange does not compete with its members as a carrier and does not favor one network's traffic over another.

Peering at an IX vs. buying IP transit

These are two different ways to get your traffic to the rest of the internet, and they solve different problems.

The practical takeaway: peering is not a replacement for transit. Most networks use both. Transit guarantees you can reach anyone; peering lets you reach high-volume destinations directly and cheaply, which reduces how much traffic you push through paid transit.

Who connects to an IX, and why

• ISPs and access networks — to exchange traffic with content networks and other ISPs, cutting transit costs and improving the path to popular destinations.
• CDNs and content providers — to deliver content from as close to the end user as possible, which reduces latency and improves delivery quality.
• Enterprises — to connect their own sites and reach cloud or SaaS providers directly rather than backhauling traffic through a transit provider.
• Cloud providers and network operators — to offer or obtain direct interconnection as part of a broader ecosystem.

The common thread is that each participant wants direct, controllable paths to specific other networks rather than routing everything through a third party.

The practical benefits

Lower latency. Traffic takes a more direct path between the two networks instead of traversing one or more transit providers. Fewer hops generally means less delay, though the actual improvement depends on geography and how the peers are connected.

Reduced cost. Once you have a port and peering sessions, you can offload a large share of traffic that would otherwise be billed as transit. The savings depend on how much of your traffic goes to networks present at the IX.

Improved redundancy. Peering with multiple networks across multiple exchanges gives you alternative paths. If one peer or one exchange has a problem, traffic can shift — provided you have configured your routing to allow it.

More control. You choose your peers, your routing policy, and your prefix announcements. That control is also a responsibility: misconfigured BGP can affect your own reachability and, in serious cases, that of others.

What to weigh when choosing an IX

• Location and latency to your users. An exchange near your traffic's origin or destination gives more benefit than a distant one.
• Neutrality and governance. A neutral exchange does not compete with members as a carrier. This affects how fairly the fabric is run and who is willing to join.
• Available networks. The value of an IX is the set of potential peers present. An exchange with the content networks, cloud providers, and ISPs you actually want to reach is worth more to you than a larger one that lacks them.
• Ecosystem and services. Some exchanges offer additional interconnection services beyond basic peering. DE-CIX, for instance, markets "premium interconnection services" alongside its exchanges — check what is included and what is charged separately.
• Resilience and port options. Consider whether you can connect at multiple locations or exchanges for redundancy, and what port speeds and cross-connect arrangements are available.

How peering is actually set up

1. Join the exchange. Arrange a port on the IX fabric and a cross-connect from your equipment in the facility.
2. Configure your router. Assign the IX-provided IP addressing to your interface and prepare BGP.
3. Establish sessions. Peer with the networks you have agreed to interconnect with, using the IX's route servers where available or direct BGP sessions.
4. Announce and filter. Announce your prefixes and apply prefix filters and maximum-prefix limits to protect against route leaks and hijacks.
5. Verify. Confirm sessions are up, routes are being received and advertised as expected, and traffic is flowing over the peering paths.

A common pitfall is skipping filtering. Peering without proper prefix and AS-path filters can expose you to accidental route leaks — a frequent cause of widespread outages. Another is expecting immediate reach: peering only helps with networks that have agreed to peer with you, so the benefit grows as your peering relationships do.

An Internet Exchange Point (IXP) is the physical infrastructure where multiple independent networks meet to exchange traffic directly with one another. In everyday usage, "Internet Exchange Point" and "Internet Exchange (IX)" are often used interchangeably, but the distinction is useful: the IX is the interconnection ecosystem or service, while the IXP is the physical point — the facility, switches, and ports — where that interconnection actually happens. Networks join an IXP when they want to peer with many other networks in one place instead of building a separate private link to each one.

IX vs. IXP: What's the Difference?

In practice, the two terms blur together because an IX is delivered through one or more IXPs. When someone says "connect at the IXP," they mean plugging into the physical switching fabric of that exchange.

The Physical and Operational Components of an IXP

An IXP is built from a small set of core elements:

• Colocation facilities / data centers — the buildings that house the equipment and provide power, cooling, and physical security.
• Switching fabric — the high-capacity switches that carry traffic between connected networks. The fabric is the heart of the IXP.
• Ports — the physical connections (typically Ethernet) that each member network uses to attach to the fabric.
• Route servers — optional but common infrastructure that simplifies peering by letting many networks exchange routes through a single session instead of configuring a session with every other member.
• Peering LAN — the shared network segment over which members exchange traffic.

DE-CIX, for example, describes itself as providing premium interconnection services and operating several neutral Internet Exchanges across Europe, the Middle East, Africa, Asia, and the Americas. "Neutral" matters here: the exchange does not compete with its members, so it has no incentive to favor one network's traffic over another's.

How Networks Connect and Peer at an IXP

The process follows a predictable sequence:

1. Join the exchange. A network signs up as a member and arranges connectivity to the IXP's colocation facility — either by placing equipment there or by connecting from a nearby site.
2. Get a port. The network receives a port on the switching fabric and an address on the peering LAN.
3. Establish peering sessions. The network configures BGP sessions with other members it wants to exchange traffic with. This can be done bilaterally (one-to-one agreements) or via the route server (one session that reaches many peers).
4. Exchange routes and traffic. Once sessions are up, the networks announce their routes and traffic flows directly between them across the fabric.

The key point: the IXP provides the meeting place and the switching, but the peering relationships themselves are decided by the networks. An IXP does not force anyone to peer with anyone else.

Why Networks Use an IXP

• Lower latency. Traffic takes a direct path between peers across the fabric instead of traveling through transit providers, often reducing the number of hops.
• Lower cost. Peering at an IXP can reduce reliance on paid transit for traffic that can be exchanged directly.
• Improved redundancy. With many peers reachable through one fabric, a network has multiple paths and is less dependent on any single interconnection.
• Scale. One port and one facility give access to many potential peers, rather than one link per partner.
• Neutrality. A neutral exchange treats all members' traffic alike, which keeps interconnection predictable.

Major IXPs and Their Role

Large IXPs concentrate a significant share of regional and global traffic. DE-CIX operates multiple neutral Internet Exchanges across Europe, the Middle East, Africa, Asia, and the Americas, which means a network connecting at one of its exchanges can reach peers across several regions. The practical effect is that major IXPs function as hubs of the interconnection ecosystem: the more networks that join, the more valuable the exchange becomes to each member, because there are more potential peers reachable through the same fabric.

Quick Check: When an IXP Makes Sense

An IXP is worth considering when a network wants to reach many peers in a region, reduce latency and transit costs, and gain redundancy without building dozens of private links. It is less relevant when a network only needs to reach one or two specific partners, in which case a private interconnection may be simpler. The deciding factors are usually how many peers you want to reach, where they are located, and whether the exchange's facilities and neutrality fit your interconnection strategy.

Peering is a settlement-free interconnection between two autonomous systems (ASes) in which each network exchanges traffic destined for the other's customers at no charge. It is the alternative to buying transit, and it makes sense when two networks exchange meaningful amounts of traffic and both expect to benefit. Deciding where to peer usually comes down to three things: which Internet Exchange (IX) or private interconnect puts you closest to the networks you actually want to reach, what port speeds and resilience that location offers, and whether the participant mix there justifies the cost of a presence.

Peering vs. transit vs. paid peering

These three arrangements are often confused, but they differ in who pays and what is exchanged.

Transit is the default: it guarantees reachability to the whole Internet through a single provider. Peering does not replace transit — it reduces how much traffic you need to send through it. Paid peering sits in between and is typically used when one side would not otherwise agree to settlement-free interconnection.

Why networks peer

The main motivations are practical rather than ideological:

• Lower latency. Traffic takes a more direct path instead of routing through a transit provider's backbone.
• Reduced transit costs. Traffic that moves over peering links no longer consumes paid transit capacity, which can delay or avoid capacity upgrades.
• More direct paths. Fewer intermediate networks means fewer points where performance can degrade.
• Greater control over routing. You decide which prefixes you announce and accept, and how traffic is balanced across links.

For content networks, peering puts caches and origin servers closer to end users. For access networks, it reduces the cost of delivering traffic their subscribers request. Both sides benefit when the traffic is roughly balanced.

What you need before you can peer

Peering is not a product you switch on; it requires infrastructure and configuration on both sides.

1. An ASN and public address space. You need an autonomous system number and provider-independent (PI) address space, or address space you are authorized to announce.
2. A presence at the interconnection point. This means a colocation rack, a cross-connect, or a port on the IX fabric. Without physical presence, there is no link.
3. A choice of public or private peering. Public peering uses the shared IX switching fabric, where one port can reach many networks. Private peering is a dedicated link between two networks, typically for high-volume or latency-sensitive traffic.
4. BGP configuration. You configure BGP sessions, announce your prefixes, and apply import and export policies. The expected result is that both sides see each other's routes and traffic begins to flow.

A useful rule of thumb: start with public peering at an IX to reach many networks over one port, then add private interconnects for your largest traffic partners.

Peering at an IX vs. private interconnects

The two options trade reach against control.

Most networks use both: public peering for breadth, private links for the handful of partners that carry the most traffic.

How to choose an Internet Exchange

Once you know you want to peer, the IX decision is about proximity and ecosystem.

• Location. Choose an IX near your users or your major traffic partners to keep latency low. DE-CIX, for example, operates neutral Internet Exchanges across Europe, the Middle East, Africa, Asia, and the Americas, so geography is a primary filter.
• Participant mix. An IX is only as useful as the networks present on it. Check whether the content providers, access networks, and regional ISPs you want to reach are already there.
• Port speeds. Confirm the IX offers the port sizes you need now and can scale to later.
• Resilience. Look at redundancy within the fabric and whether you can connect from more than one location or provider.
• Neutrality. A neutral IX does not compete with its participants, which matters for fair and predictable interconnection terms.

DE-CIX describes its interconnection services as premium and operates multiple neutral exchanges, which fits the pattern of an IX chosen for ecosystem breadth rather than a single route.

Common pitfalls

• Traffic ratios. Some networks expect roughly balanced traffic before agreeing to settlement-free peering. Very asymmetric flows can make peering harder to justify to the other side.
• Route filtering. Without proper prefix and AS-path filters, you risk route leaks or hijacks. Filtering is a prerequisite, not an optional hardening step.
• Single points of failure. One peering link or one IX is not resilient. Redundant links across locations or providers protect against outages.
• Assuming peering replaces transit. Peering covers the networks you interconnect with; transit still covers the rest of the Internet.

If you are evaluating whether to peer at all, start by measuring where your traffic goes and which networks it crosses. If a large share of your traffic terminates in networks you could reach directly, peering at an IX near those networks is usually the next step.