Interconnection
AS44444 FORCEPOINT-CLOUD-AS
Hosting RIPE NSP
Recorded presence
Internet exchanges
Internet exchanges where Packet Clearing House has a port recorded for AS44444, 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.
Europe 13 North America 10 Asia-Pacific 9 Africa 2 Latin America 1
| Exchange | Location | Their address | Policy | Member ports |
|---|---|---|---|---|
| IX.br (PTT.br) São Paulo | São Paulo, Brazil | 187.16.217.101 | Selective | 2,704 |
| DE-CIX Frankfurt | Frankfurt, Germany | 80.81.196.178 | Selective | 1,078 |
| LINX LON1 | London, United Kingdom | 195.66.224.170 | — | 932 |
| AMS-IX Amsterdam | Amsterdam, Netherlands | 80.249.211.69 | — | 882 |
| Neutral Internet Exchange | Amsterdam, Netherlands | 193.239.117.64 | — | 669 |
| NAPAfrica IX Johannesburg | Johannesburg, South Africa | 196.60.8.150 | Selective | 603 |
| France-IX Paris | Paris, France | 37.49.236.119 | Selective | 570 |
| Equinix Internet Exchange Singapore | Singapore, Singapore | 27.111.228.144 | Selective | 496 |
| Equinix Internet Exchange Ashburn | Ashburn, United States | 206.126.236.89 | — | 391 |
| BroadBand Internet eXchange Tokyo | Tokyo, Japan | 101.203.88.206 | Selective | 361 |
| London Network Access Point | London, United Kingdom | 5.57.80.35 | Open | 314 |
| Equinix Internet Exchange Warsaw | Warsaw, Poland | 2001:7f8:42::a504:4444:1 | — | 297 |
| Toronto Internet Exchange | Toronto, Canada | 206.108.35.38 | Selective | 286 |
| DE-CIX New York | New York, United States | 2001:504:36::ad9c:0:1 | — | 285 |
| Equinix Internet Exchange Chicago | Chicago, United States | 208.115.136.145 | — | 282 |
| DE-CIX Mumbai | Mumbai, India | 103.27.170.44 | Open | 278 |
| Megaport IX Sydney | Sydney, Australia | 103.26.68.129 | Selective | 269 |
| SwissIX | Zurich, Switzerland | 91.206.52.215 | — | 256 |
| Equinix Internet Exchange Sydney | Sydney, Australia | 45.127.172.47 | — | 238 |
| Johannesburg Internet Exchange | Johannesburg, South Africa | 196.60.96.78 | Selective | 217 |
| IX Australia (Sydney NSW) | Sydney, Australia | 218.100.52.30 | — | 197 |
| Equinix Internet Exchange Miami | Miami, United States | 198.32.243.85 | — | 178 |
| Equinix Internet Exchange Tokyo | Tokyo, Japan | 203.190.230.81 | Selective | 128 |
| Torino Piemonte Exchange Point | Torino, Italy | 194.116.96.53 | — | 122 |
| Equinix Internet Exchange New York | New York, United States | 198.32.118.118 | — | 120 |
| Megaport Frankfurt IX | Frankfurt, Germany | 2001:7f8:8:20:0:ad9c:0:1 | — | 114 |
| UAE-IX | Dubai, United Arab Emirates | 185.1.8.81 | Selective | 113 |
| Megaport Dusseldorf IX | Düsseldorf, Germany | 194.146.118.71 | — | 98 |
| Equinix Internet Exchange Palo Alto | Palo Alto, United States | 198.32.176.150 | — | 76 |
| Equinix Los Angeles IBX | Los Angeles, United States | 206.223.123.211 | — | 72 |
| CERN IXP / Equinix Internet Exchange Geneva | Geneva, Switzerland | 192.65.185.241 | — | 55 |
| LINX NoVa | Reston, United States | 206.55.196.25 | Selective | 48 |
| MegaPort IX Singapore | Singapore, Singapore | 103.41.12.15 | Selective | 47 |
| DE-CIX Phoenix | Phoenix, United States | 149.112.27.44 | Selective | 41 |
| Extreme IX Bangalore | Bangalore, India | 38.10.0.25 | Open | 41 |
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-11 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,346 exchanges and 98,138 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.