Interconnection
AS41095 IPTP
Hosting RIPE NSP
Recorded presence
Internet exchanges
Internet exchanges where Packet Clearing House has a port recorded for AS41095, largest fabric first. An exchange is shared switching where networks interconnect directly rather than paying a transit provider, so turning up at one is a deliberate choice about how this network wants to be reached. Each name opens that exchange's page, with its peering LANs and everyone else on it.
North America 16 Asia-Pacific 6 Europe 6 Latin America 2 Africa 1
| Exchange | Location | Their address | Policy | Member ports |
|---|---|---|---|---|
| IX.br (PTT.br) São Paulo | São Paulo, Brazil | 187.16.217.30 | Restrictive | 2,704 |
| DE-CIX Frankfurt | Frankfurt, Germany | 80.81.192.47 | Restrictive | 1,078 |
| LINX LON1 | London, United Kingdom | 195.66.225.64 | Restrictive | 931 |
| AMS-IX Amsterdam | Amsterdam, Netherlands | 80.249.209.196 | Case-by-case | 882 |
| NAPAfrica IX Johannesburg | Johannesburg, South Africa | 196.60.8.124 | Selective | 603 |
| Equinix Internet Exchange Singapore | Singapore, Singapore | 27.111.228.173 | Restrictive | 496 |
| Milan Internet Exchange | Milan, Italy | 217.29.66.94 | — | 418 |
| Equinix Internet Exchange Ashburn | Ashburn, United States | 206.126.236.120 | Restrictive | 390 |
| Seattle Internet Exchange | Seattle, United States | 206.81.81.26 | Restrictive | 350 |
| Coresite - Any2 West | Los Angeles, United States | 206.72.210.118 | Restrictive | 344 |
| Any2 California | Los Angeles, United States | 206.72.210.118 | Restrictive | 319 |
| Hong Kong Internet Exchange | Hong Kong, China | 123.255.90.171 | Restrictive | 307 |
| Equinix Internet Exchange Chicago | Chicago, United States | 208.115.136.227 | Restrictive | 281 |
| Singapore Internet Exchange | Singapore, Singapore | 103.16.102.103 | Open | 277 |
| Equinix Internet Exchange Hong Kong | Hong Kong, China | 2001:de8:7::4:1095:1 | Restrictive | 232 |
| Equinix Internet Exchange Dallas | Dallas, United States | 206.223.118.158 | Restrictive | 231 |
| IX Australia (Sydney NSW) | Sydney, Australia | 218.100.53.80 | Restrictive | 197 |
| Equinix Internet Exchange San Jose (Bay Area) | San Jose, United States | 206.223.117.9 | Restrictive | 192 |
| Equinix Internet Exchange Miami | Miami, United States | 198.32.243.115 | Restrictive | 178 |
| Digital Realty Atlanta Internet Exchange | Atlanta, United States | 206.126.110.176 | — | 174 |
| PIT Chile - Santiago | Santiago, Chile | 45.68.16.178 | — | 170 |
| Equinix Internet Exchange New York | New York, United States | 198.32.118.201 | Restrictive | 120 |
| DE-CIX Marseille | Marseille, France | 185.1.47.35 | Restrictive | 112 |
| Equinix Internet Exchange Los Angeles | Los Angeles, United States | 206.223.123.134 | Restrictive | 80 |
| Equinix Internet Exchange Palo Alto | Palo Alto, United States | 198.32.176.239 | Restrictive | 76 |
| Digital Realty New York Internet Exchange | New York, United States | 206.126.115.40 | — | 74 |
| Equinix Los Angeles IBX | Los Angeles, United States | 206.223.123.134 | Restrictive | 72 |
| Equinix IBX Secaucus retired | Secaucus, United States | 206.223.117.9 | Restrictive | 64 |
| Korea Internet Neutral Exchange KINX | Seoul, South Korea | 139.150.100.70 | Restrictive | 64 |
| Equinix Internet Exchange Zurich | Zurich, Switzerland | 194.42.48.95 | — | 44 |
| Equinix-LA(former Paix) retired | Los Angeles, United States | 198.32.243.115 | Restrictive | — |
Recorded rather than inferred: an address on a peering LAN is at that exchange by definition. Member ports counts every participant at the exchange, not this network's ports, so read it as a size proxy. An absent exchange means PCH has no record of it, not that the network is not there. For the operator's own claims, see its PeeringDB record.
From the exchange directory collected 2026-10-13 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,346 exchanges and 98,177 recorded member ports, licensed CC BY-NC-SA 3.0.
PeeringDB is the better-known directory and is deliberately not the source here: its acceptable-use policy forbids the bulk storage this needs. The two answer different questions anyway. PeeringDB reports what an operator declares about itself; this reports what PCH has recorded.