asn.dev

Interconnection

AS4213 EVOCATIVE-GLOBAL

Hosting ARIN NSP

Exchanges 10 9 active
Countries 1 most in United States
Regions 1
Largest fabric 350 Seattle Internet Exchange

Recorded presence

Internet exchanges

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS4213, 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
Seattle Internet ExchangeSeattle, United States206.81.80.61Open350
Coresite - Any2 WestLos Angeles, United States206.72.211.125Open344
Any2 CaliforniaLos Angeles, United States206.72.210.144Open319
Equinix Internet Exchange San Jose (Bay Area)San Jose, United States206.223.117.34Open192
Equinix Internet Exchange New YorkNew York, United States198.32.118.52Open120
Massachusetts Internet ExchangeBoston, United States206.53.143.78Open73
Equinix IBX Secaucus retiredSecaucus, United States206.223.117.34Open64
Megaport DallasDallas, United States206.53.174.20—31
Megaport IX Los AngelesLos Angeles, United States206.53.172.8Open29
Megaport IX SeattleSeattle, United States206.53.171.9Open17

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.