asn.dev

Interconnection

AS5650 FRONTIER-FRTR

Residential DROP-listed space ARIN NSP

Exchanges 10 10 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 AS5650, 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 10

ExchangeLocationTheir addressPolicyMember ports
Equinix Internet Exchange AshburnAshburn, United States206.126.237.215Selective390
Seattle Internet ExchangeSeattle, United States2001:504:16::1612—350
Coresite - Any2 WestLos Angeles, United States206.72.211.99Selective344
Any2 CaliforniaLos Angeles, United States206.72.211.99Selective318
Equinix Internet Exchange ChicagoChicago, United States208.115.136.146Selective283
Equinix Internet Exchange DallasDallas, United States206.223.118.230Selective231
FL-IX - The Florida Internet Exchange / Community IX - FloridaMiami, United States206.41.108.120Selective181
Equinix Internet Exchange New YorkNew York, United States198.32.118.193Selective120
Equinix Internet Exchange Palo AltoPalo Alto, United States198.32.176.27—76
Equinix Internet Exchange SeattleSeattle, United States198.32.134.5Selective45

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-14 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,346 exchanges and 98,276 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.