asn.dev

Interconnection

AS13896 8X8-FUZE

Unclassified ARIN NSP

Exchanges 10 9 active
Countries 6 most in United States
Regions 3
Largest fabric 1,076 DE-CIX Frankfurt

Recorded presence

Internet exchanges

recorded

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

Asia-Pacific 4 North America 4 Europe 2

ExchangeLocationTheir addressPolicyMember ports
DE-CIX FrankfurtFrankfurt, Germany80.81.192.143Open1,076
LINX LON1London, United Kingdom195.66.227.97Open928
Equinix Internet Exchange SingaporeSingapore, Singapore27.111.229.158Open496
Equinix Internet Exchange AshburnAshburn, United States206.126.238.31Open388
Megaport IX SydneySydney, Australia103.26.69.55Open268
Equinix Internet Exchange SydneySydney, Australia45.127.173.26Open239
Equinix Internet Exchange Hong KongHong Kong, China2001:de8:7::1:3896:1Open232
Equinix Internet Exchange San Jose (Bay Area)San Jose, United States206.223.117.48Open194
Equinix IBX Secaucus retiredSecaucus, United States206.223.117.48Open64
LINX NoVaReston, United States206.55.196.60Open48

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-26 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,347 exchanges and 97,624 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.