Interconnection

AS2734 CORESITE

Hosting ARIN NSP

Exchanges 10 10 active

Countries 1 most in United States

Regions 1

Largest fabric 344 Coresite - Any2 West

Recorded presence

Internet exchanges

recorded

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

Exchange	Location	Their address	Policy	Member ports
Coresite - Any2 West	Los Angeles, United States	206.72.210.244	Open	344
Any2 California	Los Angeles, United States	206.72.210.244	Open	319
DE-CIX New York	New York, United States	2001:504:36::aae:0:1	—	285
New York International Internet Exchange	New York, United States	2001:504:1::a500:2734:1	Open	214
FL-IX - The Florida Internet Exchange / Community IX - Florida	Miami, United States	206.41.108.19	Open	181
San Francisco Metropolitan Internet Exchange	San Francisco, United States	206.197.187.10	Open	109
DE-CIX Chicago	Chicago, United States	149.112.11.61	Open	83
Massachusetts Internet Exchange	Boston, United States	206.53.143.10	Open	73
United IX Chicago	Chicago, United States	206.41.110.27	Open	69
Quad Cities Internet Exchange	Davenport, United States	206.83.43.19	Open	67

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.