asn.dev

Interconnection

AS11983 -Reserved AS-

Hosting ARIN

Exchanges 9 9 active
Countries 1 most in United States
Regions 1
Largest fabric 390 Equinix Internet Exchange Ashburn

Recorded presence

Internet exchanges

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS11983, 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 9

ExchangeLocationTheir addressPolicyMember ports
Equinix Internet Exchange AshburnAshburn, United States206.126.239.87Selective390
Seattle Internet ExchangeSeattle, United States206.81.81.137Selective350
Equinix Internet Exchange ChicagoChicago, United States208.115.137.102Selective281
Equinix Internet Exchange DallasDallas, United States206.223.119.189Selective231
Equinix Internet Exchange San Jose (Bay Area)San Jose, United States206.223.116.102Selective192
FL-IX - The Florida Internet Exchange / Community IX - FloridaMiami, United States206.41.108.200Open181
DE-CIX DallasDallas, United States206.53.202.159Selective176
DE-CIX ChicagoChicago, United States149.112.11.44Selective83
DE-CIX PhoenixPhoenix, United States149.112.27.20Selective41

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.