What an IXP Is
An Internet Exchange Point is a shared facility — usually a data center floor with a high-speed Ethernet switch fabric — where independently operated networks connect their routers and agree to exchange traffic directly. Instead of routing packets through a paid transit chain, two networks at the same IXP can peer directly: traffic between their customers crosses the IXP switch and nothing else.
| Term | Meaning | Why It Matters |
|---|---|---|
| Peering | Two networks directly exchange traffic, usually at no cost to either party | Shorter paths, lower cost, often lower latency |
| Transit | One network pays another to carry traffic to the broader internet | Necessary when peering does not cover the destination |
| Route server | An IXP-operated BGP server that distributes routes to all members simultaneously | Lets hundreds of networks peer without setting up bilateral sessions with each other |
| Colocation (colo) | Data center space where networks install their routers and cross-connect to the IXP switch | Physical location where IXP connections are made |
| PNI (Private Network Interconnect) | A direct fiber link between two large networks, bypassing the IXP switch | Used when two networks exchange very large traffic volumes |
How an IXP Works Physically
A typical IXP operates a Layer 2 switching fabric — a large Ethernet switch (or mesh of switches) spanning one or more colocation data centers. Each member network connects a router port to the IXP switch via a cross-connect cable. They then establish BGP sessions over that switch, advertise their IP prefixes, and start receiving traffic destined for their networks from other members.
Large IXPs like DE-CIX (Frankfurt), AMS-IX (Amsterdam), LINX (London), and NYIIX (New York) have hundreds to thousands of member networks and exchange traffic measured in terabits per second. A typical member pays a port fee based on port speed (1G, 10G, 100G) and a monthly fee for their colocation space.
Why IXPs Improve the Internet
- Shorter paths: Traffic between two networks in the same city no longer has to route through a distant transit provider's core. A packet from a local ISP to a local CDN cache can cross the IXP switch in microseconds instead of traveling to a distant city.
- Lower latency: Each removed transit hop reduces round-trip time. Local IXP peering can reduce ping to a streaming server from 30–50ms (via transit) to 1–5ms (via local IXP).
- Lower cost: Transit bandwidth is expensive at scale. IXP peering replaces transit fees for member-to-member traffic. Savings for large networks can reach millions of dollars per year.
- Resilience: Multiple peering paths at an IXP give networks alternative routes if a transit provider has issues. Traffic can reroute through peering without customer impact.
- CDN efficiency: CDN providers like Cloudflare, Akamai, and Fastly peer at hundreds of IXPs globally, placing cached content as close to end users as possible. Your ISP's IXP peering with these CDNs is a major factor in how fast web pages and video load for you.
How Home Users Feel IXP Effects
You never interact with an IXP directly, but its effects are visible in everyday experience:
- If your ISP peers well at a local IXP with Netflix, YouTube, or Cloudflare, video starts faster, loading is more consistent, and the CDN edge server is geographically close
- If peering is poor or absent, your traffic for a specific service may route through a congested transit path — causing that one service to feel slow while everything else is fine
- Running a traceroute to a streaming service shows the path your traffic takes; few hops and low latency often indicate IXP peering; many hops through distant cities indicate transit routing
Notable Global IXPs
| IXP | Location | Peak Traffic (approx.) | Member Count (approx.) |
|---|---|---|---|
| DE-CIX Frankfurt | Frankfurt, Germany | 14+ Tbps | 1,000+ |
| AMS-IX | Amsterdam, Netherlands | 10+ Tbps | 900+ |
| LINX | London, UK | 8+ Tbps | 900+ |
| NYIIX | New York, USA | 1+ Tbps | 300+ |
| Equinix IX | Multiple US/global cities | Various | Various per location |
Frequently Asked Questions
Is an IXP the same as an ISP?
No. An ISP sells internet connectivity to end customers — businesses and homes. An IXP is a neutral shared infrastructure where ISPs, cloud providers, CDNs, and other networks connect to exchange traffic with each other. The IXP does not sell internet service to consumers; it facilitates peering between networks.
Can IXP peering improve my ping?
Yes, indirectly. When your ISP peers at an IXP with the service you use, the traffic takes a shorter, more direct path. Instead of routing through a distant transit provider's backbone, packets cross a local switch. This can reduce round-trip time by 10–50ms depending on the alternative path. The effect is most noticeable for streaming, gaming, and any latency-sensitive application.
Do home users connect to IXPs directly?
No. Only network operators (ASNs with their own IP address blocks) can connect to IXPs. Home users benefit through their ISP's peering relationships. The quality of your ISP's peering at regional IXPs is one of the factors that differentiates ISPs with similar speed plans but different real-world performance.
How can I tell if my traffic is using IXP peering or transit?
Run a traceroute to the destination and look at the number of hops and latency. Few hops with latency under 5–10ms to reach a major CDN usually indicates local IXP peering. Many hops with the path traversing distant cities indicates transit routing. Tools like bgp.he.net can look up the ASN at each hop to identify which network's infrastructure you are traversing.