What Actually Happens at an Internet Exchange

I've spent years hanging around network operator mailing lists and meetups, the world where people quietly keep the internet's plumbing working, and one thing still surprises newcomers to it. A huge amount of the internet's speed and reliability comes down to a room of switches in an unglamorous data center, run by no single company. That room is called an internet exchange point, or IXP. Almost nobody outside networking has heard the term. Fair enough. It has no app, no login page you'd ever visit. But it shapes how fast your video call connects and how much your internet provider pays to keep serving you.

Here's the problem an IXP solves. Every network on the internet, your provider, a university, a company running its own online services, is its own island. To reach anywhere else, that island needs a way to hand off traffic. The default method is transit. You pay a larger network to carry your data wherever it needs to go, roughly the way you'd pay a shipping company instead of building your own roads. Transit still matters for reaching distant or obscure parts of the internet. It costs money for every gigabyte moved, though, and it rarely takes the shortest path.

Now picture two networks that trade a lot of traffic with each other. Say one is a local provider and the other runs a popular streaming service, and a large share of that provider's customers watch something from that service most evenings. Routing all of that through a paid transit provider, when the two networks could simply share a switch, wastes money and time. It costs money, it adds delay, and it loads a third party's equipment with traffic that has nothing to do with them. Exchanging that traffic directly fixes all three problems at once. That's the entire premise of an IXP: get networks physically close enough to hand traffic to each other and skip the middleman.

The mechanics

Mechanically, it's simpler than it sounds. An IXP is basically a shared switching fabric, a set of switches sitting in a well-connected facility that member networks plug into. Once connected, a member sits a short physical hop from every other member on that fabric. The relationships built on top of that connection are called peering. Two networks agree to exchange traffic meant for each other, usually without either side paying the other, on the assumption that both benefit about equally.

The part that saves everyone real trouble is the route server. Without one, peering with a large group of networks at an exchange means negotiating and configuring a separate session with each one, which is exactly the kind of repetitive manual work network engineers try to avoid. A route server lets a member announce its routes once and have them distributed to every other participant who wants them, while receiving everyone else's routes back through that same connection. It doesn't carry the actual traffic; that still flows directly between members. It just handles the bookkeeping of who can reach whom, turning "negotiate with everyone separately" into "talk to the route server and let it sort out the rest."

Who runs it

What I like about IXPs, after years of listening to operators talk about them, is the culture built around them. Exchanges are almost never owned by one of the networks using them. Most run as member associations or non-profits, sometimes with a small paid staff whose job is keeping switches running and billing fair. Nobody involved wants a for-profit gatekeeper sitting in the middle of every peering relationship, deciding who gets favorable treatment.

Neutrality matters more than it sounds. The moment one participant controls the exchange, every other participant starts wondering whether they're getting a fair deal, and that suspicion quietly poisons the whole arrangement. So exchanges tend to bend over backward to stay boring and procedural, with published policies and boards elected by the membership, and fees set to cover costs rather than generate profit. It's a deliberately unsexy way to run infrastructure, and I mean that as a compliment.

Where AI fits into this

The newest pressure on this model comes from AI traffic, and it is arguably where exchanges become more useful, not less. Training runs mostly stay contained inside a single data center or a tightly coupled cluster, so they barely touch the public internet. Inference is a different story. Every time someone sends a prompt to a hosted model, that request and the answer that comes back cross the same public paths as everything else, and the volume of that traffic is climbing fast as more products build AI features into everyday use.

Serving inference well rewards exactly what an IXP is good at: keeping a request close to where it started instead of routing it across a continent and back. A slow round trip is noticeable in a live conversation with a model, so providers running inference at real scale have a strong incentive to peer close to their users, the same incentive that pulled video and gaming traffic onto exchanges years earlier. I expect the companies and cloud regions serving that traffic to become some of the more significant members at the exchanges that get this right, the same way major content and streaming platforms did before them. It is a good problem for this part of the industry to have: one more reason for more networks to sit in the same room and hand traffic to each other directly.

Feeling attached to something built out of switches and cable, doing thoroughly unglamorous work, is a little strange, but operators talk about their local exchange the way people talk about a well-run local co-op. Nothing flashy about it, right up until someone proposes changing how it's governed. Then every member suddenly has an opinion. That mix of dull mechanics and stubborn shared governance is a big part of why the internet has stayed as decentralized as it has, at least in the corner of it I've gotten to watch up close.