Internet exchange point
A shared network where many operators meet and hand traffic straight to each other, instead of paying a third network to carry it between them.
Updated 20 September 2026 · 6 primary sources
An internet exchange point is a shared network where many operators meet. Each member connects a router to it and hands traffic straight to the others. A packet between two members never crosses a third network that charges for carrying it. The standard puts it plainly: exchanges "provide IP data interconnection facilities for their participants, typically using shared Layer 2 networking media such as Ethernet".
PeeringDB, the directory operators keep themselves, listed 1,325 exchanges in 171 countries on 20 September 2026. The United States has 212 of them. Indonesia has 80, more than Germany's 59, which turns out to matter for proxies.
Peering, transit and the route server
There are two ways to reach the rest of the internet. Transit means paying a larger network to carry your traffic anywhere it needs to go. Peering means handing traffic straight to another network that wants it, usually without money changing hands for the exchange itself. An exchange point is where the second kind happens at scale.
Meeting every member one by one is work, so exchanges run route servers. A route server is a broker: each member keeps one session with it rather than one with every other member. The standard calls the result multilateral interconnection "among three or more External BGP (EBGP) speakers using a single intermediate broker system".
The idea is older than the standard, and the hardware in the first attempt dates it. A route server was proposed in October 1995 for members sharing an "ATM, SMDS or Frame Relay" fabric. Nobody built it. In October 2005 the IETF recorded that implementations did not exist and moved the document to Historic status. The working version arrived in September 2016, by which time the shared medium was ordinary Ethernet.
| Arrangement | Who pays | The path |
|---|---|---|
| Transit | You pay the carrier per megabit | You, the carrier, then onward |
| Peering at an exchange | Each side pays its own port | You, then the other member |
| Private peering | Both sides pay for the link | You, then the other network |
Where the networks behind our proxies sit
On 20 September 2026 we took every network behind the live addresses on our free proxy list: 7,934 addresses in 1,711 networks. Of those networks, 1,360 keep a PeeringDB record and 1,023, or 59.8 percent, have at least one port at an exchange. Where a network is present at all, the median is three exchanges.
The busiest exchanges for these networks are not the famous ones. Six of the top ten are in Indonesia, which fits that country's 80 exchanges, and the European names appear further down. Frankfurt shows 101 of our networks although the exchange there has 1,019 members in total, so our addresses are simply not where the large European networks meet.
The most connected networks are not proxy networks either. The three with the most ports hold 207, 167 and 105 of them, and they are a software company, a cloud provider and a hosting company. Exchange presence measures how much traffic a network carries for its own business, not what it sells.
| Exchange | Our networks there |
|---|---|
| IIX-Jakarta | 288 |
| JKT-IX, Jakarta | 278 |
| OpenIXP, Indonesia | 203 |
| AIX, Depok | 116 |
| DE-CIX Frankfurt | 101 |
| AMS-IX, Amsterdam | 85 |
| ODIX Omadata, Surabaya | 82 |
| Equinix Singapore | 77 |
| IX.br, Sao Paulo | 75 |
| BIX Jakarta | 73 |
Exchanges and proxies
A proxy is only as close to a target as its network is. An address in a network with ports at dozens of exchanges often reaches a large site across one or two networks. An address in a small access network may cross two or three carriers first, and every extra network is somewhere a packet waits.
This also draws the map of free proxies. Their networks meet at the Indonesian exchanges, and the addresses follow, which is why free lists are heavy with Indonesian entries. For paid work the useful question is not how many exchanges a network has joined. It is whether that network meets the target's network at all, and that is easier to measure than to look up.
How HProxy handles it
Our free list names the network behind every address, so its exchange presence can be looked up in PeeringDB in a minute. For a target that matters, measure the latency from the exit you plan to use rather than reading a peering list.
Frequently asked questions
What is an internet exchange point?
A shared network where operators meet to hand traffic directly to each other. Each member connects a router, and traffic between two members stays between them instead of crossing a paid carrier.
What is peering?
Two networks agreeing to exchange traffic between their own users directly, usually without paying each other for it. At an exchange point one port can carry that traffic to many networks at once.
What is the difference between peering and transit?
Transit is a paid service that takes your traffic anywhere. Peering carries only the traffic between the two networks that peer, and it is normally settlement-free, with each side paying for its own port.
How many internet exchange points are there?
PeeringDB listed 1,325 in 171 countries on 20 September 2026. The United States had 212, Indonesia 80 and Germany 59, though exchanges differ enormously in size.
Does peering make a proxy faster?
It can shorten the path, which usually means lower latency, but it is not a promise. What matters is whether your exit network reaches the target's network directly, so measure from the exit you will use.
Which networks are at the most exchanges?
Among the networks behind our free list, the top three hold ports at 207, 167 and 105 exchanges. They are a software company, a cloud provider and a hosting company, none of which sells proxies.
What is a route server?
A shared machine at an exchange that passes routing information between members, so each member keeps one session instead of one per member. The IETF standardised the method in September 2016.
Have exchanges always worked this way?
No. The first route server design, from October 1995, assumed members shared an ATM, SMDS or Frame Relay fabric. It was never implemented and was retired in October 2005. The standard in use today dates from September 2016 and describes Ethernet.
Sources
- RFC 7947: Internet Exchange BGP Route Server, IETF, E. Jasinska, N. Hilliard, R. Raszuk, N. Bakker, 2016-09.
- RFC 7948: Internet Exchange BGP Route Server Operations, IETF, N. Hilliard, E. Jasinska, R. Raszuk, N. Bakker, 2016-09.
- RFC 1863: A BGP/IDRP Route Server alternative to a full mesh routing, IETF, D. Haskin, 1995-10.
- RFC 4223: Reclassification of RFC 1863 to Historic, IETF, P. Savola, 2005-10.
- PeeringDB: exchanges, networks and exchange ports, PeeringDB (records kept by the operators), 2026-09-20.
- Exchange presence of the networks behind our free proxy list, HProxy measurement, 2026-09-20.
Back to the full glossary.