What Is an Internet Exchange (IXP)? How Networks Meet to Exchange Traffic

Introduction

When people talk about peering, they often say it happens "at an IXP." The phrase gets used casually — but an Internet Exchange Point is a concrete, physical thing, and understanding it explains a lot about why the Internet is fast, cheap, and resilient in the places it is.

Internet Exchange Point (IXP) — a shared switch fabric where networks connect to exchange traffic directly, without a transit provider in the path.

Route Server — an IXP-operated BGP router that lets a single BGP session reach every other route-server client on the fabric.

If you've read Transit vs Peering, you know networks interconnect in two ways: they pay a transit provider to reach the whole Internet, or they peer directly with specific neighbors. An IXP is the place where that second option happens at scale — a shared switch fabric where hundreds of networks show up and exchange traffic directly.

What Is an IXP?

An Internet Exchange Point (IXP) is a physical infrastructure that lets many networks connect to a shared switching fabric and exchange traffic directly with one another.

Think of it as a meeting room. Each network plugs a router into the room's shared network. Once inside, it can exchange traffic with any other network in the room — without that traffic ever traversing a transit provider.

   Net A ─┐
   Net B ─┤
   Net C ─┼──▶ [ IXP Switch Fabric ] ◀──┬─ Net D
   Net E ─┤                              └─ Net F
          └─  ...many more members

Key points:

It's a meeting point, not a network. An IXP doesn't carry your traffic to the whole Internet. It only carries traffic between its own members.
It's usually layer 2. Members share a LAN; each connects a router port and gets an IP on the IXP subnet.
It's run by an operator. Some IXPs are member-run non-profits (LINX, AMS-IX); some are commercial (Equinix). Either way, they operate the fabric, not your routes.
Examples: DE-CIX (Frankfurt), LINX (London), AMS-IX (Amsterdam), SIX (Seattle), and hundreds more worldwide.

Read Transit vs Peering for why networks meet here in the first place.

How an IXP Works

The mechanics are simpler than the jargon suggests.

You get a port. You (or your colocation provider) connect a router to the IXP's fabric and pay the IXP for a port — typically priced by speed (1 / 10 / 100 / 400 Gbps).
You get an IP on the IXP LAN. Your router receives an address on the IXP's shared subnet.
You peer. You exchange routes with other members. There are two ways:
- Bilateral peering: a direct BGP session between you and one other member.
- Multilateral peering via a route server: one BGP session to the IXP's route server, which reflects your routes to every other route-server client. This is how you reach hundreds of peers through a single session.
Traffic flows across the fabric. When your prefix and a peer's prefix are advertised to each other, traffic between you travels directly across the IXP — without traversing a transit provider or a third party.

The crucial detail: the IXP operator runs the fabric; it does not route your traffic to the Internet. It's plumbing for members to interconnect. Everything beyond the IXP's members still requires transit.

IXP vs Transit

This is the distinction that clears up most confusion, and it mirrors the transit-vs-peering split:

Dimension	IXP	Transit
What it is	A place to peer	A service that carries you everywhere
Who you reach	Only IXP members (and their customers)	The entire Internet
Commercial model	You pay a port fee; peering is settlement-free	You pay recurring transit fees
Role	Optimize specific traffic	Baseline global reach
Replaces the other?	No — they're complementary	No — peering doesn't reach everything

An IXP is where peering happens; transit is what gets you the rest of the Internet. You generally want both: transit for reach, IXP peering to offload and speed up traffic with the networks you exchange the most with.

IXP vs Data Center

People often confuse the two, but they're different layers:

Dimension	IXP	Data Center
What it is	A managed switching fabric for peering	Real estate: power, cooling, physical security
Primary function	Interconnect networks to exchange traffic	House servers, storage, and networking gear
Who operates it	IXP operator (non-profit or commercial)	Data center provider (e.g., Equinix, Digital Realty)
What you pay for	Port to the fabric (by speed)	Space, power, cooling, cross-connects
Can you use one without the other?	Usually needs a data center to host the fabric	Yes — many tenants just host servers, no IXP

An IXP's fabric is frequently housed in a data center, because colocating there makes it easy for members to plug into the fabric. And a single IXP can span multiple data centers in a city via the operator's own links. The simple rule: a data center is the building; an IXP is the interconnection service inside or across buildings.

Public Peering at an IXP

"Public peering" means peering across the IXP's shared fabric — as opposed to private peering (PNI), a dedicated direct link between just two networks.

The advantage of public peering is scale: one port and (often) one route-server session connect you to every member who also peers publicly. Instead of negotiating hundreds of bilateral sessions, you plug in once and reach the room. This is why IXPs are where the bulk of settlement-free peering happens.

Private peering still has its place — when two networks exchange enough traffic that a dedicated link is cheaper or more predictable than sharing the fabric. Many large interconnections (for example, a CDN and a major ISP) run as PNIs.

Route Server vs Bilateral Peering

At an IXP, you have two ways to set up peering. The choice comes down to scale versus control:

Dimension	Route Server (Multilateral)	Bilateral Peering
How it works	One BGP session to the IXP's route server → routes reflected to all clients	Direct BGP session between you and one other member
Reach	Every route-server client on the fabric, from one session	One peer per session
Setup effort	Low — configure once, reach many	High — negotiate and configure each peer individually
Control over routing policy	Less granular — peer applies the same policy to all route-server clients	Full — tailor policy per peer
Best for	Networks new to peering or with many small peers	High-volume, strategic peering relationships
Filtering	Route server applies each member's IRR/RPKI filters automatically	You manage filters directly on the session

Most networks start with the route server — it's the fastest path to many peers. As individual relationships grow in volume, they graduate to bilateral sessions for finer control. The two aren't mutually exclusive; many networks use both simultaneously at the same IXP.

Why CDNs Love IXPs

Content Delivery Networks live or die by proximity to users. And users' traffic originates inside eyeball networks — the ISPs and mobile carriers that serve end users. Those eyeball networks are exactly the members that congregate at IXPs.

So a CDN connects to IXPs to exchange traffic directly with the eyeball networks whose users it serves:

Lower latency. Traffic stays local — from the CDN's edge node, across the IXP fabric, straight to the ISP. No detour through transit.
Lower cost. That traffic is settlement-free peering, not paid transit.
Better performance. A more direct routing path across the fabric avoids the extra latency of transit detours, and the direct fiber path typically means more consistent latency and lower jitter.

IXPs are also the physical anchor for anycast: a CDN advertises the same prefix from edge nodes at many IXPs, and local users naturally reach the best available instance according to BGP routing policy. The IXP is the point where "the best available instance" actually meets "the local eyeball."

A Common Myth: "An IXP Gives You the Whole Internet"

It doesn't — and this is the same misunderstanding we saw with peering in general.

Connecting to an IXP lets you exchange traffic with the IXP's members (and their customers). It does not give you reach to networks that aren't members. To reach the rest of the Internet, you still need transit.

An IXP is a meeting room, not a highway. You meet everyone in the room for free; to call anyone outside, you still need the phone company (transit). This is why nearly every network that joins an IXP also keeps transit — the two solve different problems.

Do You Need an IXP?

For most organizations, no. If you're a typical site or service, you buy transit (or use a cloud provider), and your provider handles peering on your behalf. You never touch an IXP.

You start to want an IXP when:

You run your own ASN and announce your own prefixes (read What Is an ASN?).
You exchange serious volume with specific networks that are present at a nearby IXP — peering that traffic offloads transit cost and cuts latency.
You want control over path and performance to those networks.

The natural progression is: get transit first (baseline reach), then — once real traffic exists — join a local IXP and peer with the heavy hitters. Day one, transit is enough. An IXP is the optimization you add when the traffic justifies the port.

FAQ

Is an IXP the same as the Internet?

No. An IXP is a meeting point where member networks interconnect. It carries traffic only between its members. The Internet is the sum of all networks and the transit and peering that connects them — far larger than any single IXP.

Do I need my own ASN to use an IXP?

Yes, to peer. Peering is an arrangement between Autonomous Systems, so you announce your own prefixes via BGP at the IXP — which requires an ASN. You can be colocated in a data center that hosts an IXP without peering, but using the IXP to peer needs an ASN.

What is a route server?

A route server is an IXP-run BGP router that lets members peer multilaterally. Instead of setting up a separate BGP session with every peer, you open one session to the route server, and it reflects your routes to all other route-server clients (subject to each member's filters). One session, hundreds of peers.

Can I peer without a route server?

Yes. A route server makes multilateral peering convenient, but it isn't required. Two networks can still establish bilateral peering — a direct BGP session between them — with no route server involved. Many high-volume peering relationships are bilateral by choice. The route server is a shortcut, not a prerequisite.

Is peering at an IXP free?

The peering itself is usually settlement-free — no money changes hands between peers. But the IXP charges a port fee for connecting to the fabric, and you bear the cost of your own router, transport, and colocation. "Free peering" doesn't mean "free to operate."

Can a small network join an IXP?

Yes. IXPs have open membership — a small network can take a port and peer with much larger ones. The barrier is operational and financial (a port costs money), not size.

What's the difference between public and private peering?

Public peering happens across the IXP's shared fabric (often via a route server) and reaches many members at once. Private peering (PNI) is a dedicated direct link between two specific networks, used when their traffic volume justifies a private connection.

Conclusion

An Internet Exchange is one of those pieces of infrastructure you never see but use constantly. It's the room where the Internet's networks meet to exchange traffic directly — settlement-free, local, and fast.

It isn't the Internet, and it doesn't replace transit; it's the optimization layered on top, the way peering is the optimization layered on top of transit. For the curious, an IXP is also where much of the Internet's resilience and performance quietly comes from: hundreds of networks, one fabric, direct paths. And for anyone running their own ASN, it's the natural next step after transit — the place where your network finally shakes hands with the rest of the neighborhood.

Key Takeaways

An IXP is a shared switch fabric where networks connect to peer directly — a meeting point, not the Internet.
Members exchange traffic across the fabric via BGP; a route server lets one session reach many peers.
An IXP reaches only its members; transit is still needed for the rest of the Internet.
An IXP is a service, often housed in a data center — not the same as the data center itself.
CDNs rely on IXPs to reach eyeball networks directly, with lower latency and cost.
Route servers scale peering to many; bilateral sessions give you fine-grained control over key relationships.

In One Sentence

An Internet Exchange is a shared switch fabric where networks connect to peer directly — the meeting point of the Internet, not the Internet itself.

Continue Reading

Transit vs Peering: What's the Difference? — why networks meet at an IXP in the first place, and how transit and peering fit together.
What Is Anycast? How One IP Address Reaches the Nearest Server — how CDNs use IXPs to put the best available instance in front of users.
What Is an ASN? A Complete Beginner's Guide — the network identity you need to peer at an IXP.
BGP Basics: How the Internet Learns Where to Send Traffic — the protocol that makes route servers and peering sessions possible.
What Is RPKI? Securing BGP Route Advertisements — how route servers and peers filter your announcements to prevent hijacking.
How to Get Your Own ASN — the step-by-step path to the ASN you'll need before connecting to an IXP.