asn.dev

Interconnection

AS46562 PERFORMIVE

Unclassified ARIN

Exchanges 12 12 active
Countries 5 most in United States
Regions 3
Largest fabric 882 AMS-IX Amsterdam

Recorded presence

Internet exchanges

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS46562, 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 Asia-Pacific 2 Europe 1

ExchangeLocationTheir addressPolicyMember ports
AMS-IX AmsterdamAmsterdam, Netherlands80.249.213.215—882
Seattle Internet ExchangeSeattle, United States206.81.81.81Open350
JPIX TokyoTokyo, Japan210.171.225.41Selective301
Toronto Internet ExchangeToronto, Canada206.108.35.21—286
Equinix Internet Exchange ChicagoChicago, United States208.115.136.224—282
Equinix Internet Exchange SydneySydney, Australia45.127.173.9—238
Equinix Internet Exchange DallasDallas, United States206.223.118.153—231
Digital Realty Atlanta Internet ExchangeAtlanta, United States206.126.110.69Open174
Equinix Internet Exchange New YorkNew York, United States198.32.118.152—120
CANIX Internet Exchange - MontrealMontreal, Canada198.179.18.80—89
Equinix Internet Exchange Los AngelesLos Angeles, United States206.223.123.243Open80
Equinix Los Angeles IBXLos Angeles, United States206.223.123.243Open72

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.