asn.dev

Interconnection

AS13760 UNITI-FIBER

Residential ARIN

Exchanges 11 11 active
Countries 1 most in United States
Regions 1
Largest fabric 391 Equinix Internet Exchange Ashburn

Recorded presence

Internet exchanges

recorded

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

ExchangeLocationTheir addressPolicyMember ports
Equinix Internet Exchange AshburnAshburn, United States206.126.236.36—391
Seattle Internet ExchangeSeattle, United States206.81.80.198—350
Equinix Internet Exchange DallasDallas, United States206.223.118.97Selective231
FL-IX - The Florida Internet Exchange / Community IX - FloridaMiami, United States206.41.108.1—181
DE-CIX DallasDallas, United States206.53.202.61Selective176
Digital Realty Atlanta Internet ExchangeAtlanta, United States206.126.110.129—174
Montgomery Internet ExchangeMontgomery, United States206.53.200.18Selective24
Jacksonville Internet ExchangeJacksonville, United States206.123.7.21Selective18
DACS-IX EastBaltimore, United States206.83.44.17Selective12
Tampa Internet ExchangeTampa, United States206.108.114.26—12
DACS-IX WestFremont, United States206.83.140.14Selective6

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.