Blog / How the internet works /
Internet exchange points: where networks meet
You open a Nigerian news site from a Nigerian phone on a Nigerian network, and the data takes a trip through another continent and back. It sounds like a joke. For years, in many countries, it was a fair description of how things worked, and internet exchange points are the fix.
What an IXP is
An internet exchange point, usually shortened to IXP, is a physical place, normally a data centre, where many networks plug their equipment into a shared set of switches so they can pass traffic directly to each other.
The “networks” are internet service providers, mobile operators, universities, banks, content companies, hosting providers and so on. The internet is literally a network of networks, and an IXP is one of the places where they meet.
Think of a city with several bus companies. Without a shared station, if you wanted to get from one company’s route to another’s, you would have to travel out to a distant hub and come back. With a central station, you step off one bus and onto the next, a few metres away. An IXP is that central station for data.
Peering and transit
Two words explain the whole idea.
Transit is when a network pays a bigger network to carry its traffic to the rest of the internet. It’s like buying a ticket on a long-distance carrier. You get to anywhere, and you pay by volume or capacity.
Peering is when two networks agree to swap traffic between each other directly, usually without paying each other, because both benefit. Your customers can reach their customers, and the other way round, without either of you paying a third party to carry it.
An IXP makes peering easy. Instead of running a separate cable to every network you want to swap with, you connect once to the exchange and can set up peering with many members through the same port.
Why it matters to you
Three things improve when more local networks meet at a local exchange.
Speed. Traffic takes a shorter path. Fewer hops and less distance means lower latency, which is the delay I talked about in why ping matters for games and calls. A local site loaded over a local route feels quicker than one that travels abroad and back.
Cost. Traffic that stays local doesn’t need expensive international capacity. In places where international bandwidth is costly, that saving can be significant. Whether it reaches the customer’s bill is another matter, but the pressure is in the right direction.
Resilience. If an international link has trouble, local traffic between local networks can keep flowing. A page hosted nearby can stay reachable even when the route out of the country is slow. When the long cables out of a country have trouble, local traffic between local networks can keep working.
Some well-known exchanges
Some of the best-known IXPs are very large: AMS-IX in Amsterdam, DE-CIX in Frankfurt and LINX in London. Many countries have smaller ones. In Nigeria, the Internet Exchange Point of Nigeria, IXPN, runs exchanges in Lagos and elsewhere. I’m mentioning it because it’s the one I know of locally, and I’d rather you read the details on its own site than rely on my summary.
Who connects, and what it takes
Typically a network needs:
- Its own address space and a routing identity (an autonomous system number).
- Equipment in, or a link to, the exchange’s facility.
- Agreement to the exchange’s rules, and often a membership fee for the port.
- A routing setup (BGP) to announce which addresses it can reach.
Small websites don’t connect to exchanges directly. Your hosting provider, your ISP or your CDN does, and you benefit from their choices.
What this means for a website owner
If your audience is in one country and your site is hosted in another, every visitor’s request crosses borders. Sometimes that’s fine. Sometimes it adds a lot of delay.
Here are some practical angles:
- Choose hosting with an eye on your audience. A server near your readers, or a CDN that has presence in your region, shortens the path. Ask your host or CDN where their servers are.
- Test from where your readers are. A speed test run from a different continent tells you little. Look for a tool that can test from a nearby location, or ask someone local to try.
- Don’t blame your site first. If a page loads slowly only for some readers on some networks, the cause may be routing between networks rather than your code. The fix, if any, sits with providers.
- Use a CDN. It places copies of your static files closer to visitors. CDNs are big users of IXPs, because that’s where they reach many ISPs at once. I explain how in Cloudflare settings that help speed and security.
Myths
- “The internet is a cloud.” It’s cables, switches and buildings, and where they are matters.
- “An IXP makes your internet faster by itself.” It improves the path for traffic between its members. If the site you want isn’t reachable through local peering, you still go the long way round.
- “Peering is always free.” Often it is, but some arrangements involve payment, and the ports and facilities cost money.
Key takeaways
- An IXP is a shared meeting place where networks exchange traffic directly.
- Peering swaps traffic between networks. Transit pays someone to carry it further.
- More local peering means lower latency, lower costs and better resilience.
- Website owners benefit indirectly, through the hosting and CDN choices they make.
- If a site is slow for readers in one region, routing may be part of the story.
Related reading
Where is your site hosted, compared to where most of your readers are? If you don’t know, it’s worth ten minutes to find out.