asn.dev

Interconnection

AS2914 NTT-DATA-2914

Transit DROP-listed space ARIN NSP

Exchanges 10 10 active
Countries 6 most in United States
Regions 2
Largest fabric 1,078 DE-CIX Frankfurt

Recorded presence

Internet exchanges

recorded

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

Europe 6 North America 4

ExchangeLocationTheir addressPolicyMember ports
DE-CIX FrankfurtFrankfurt, Germany80.81.192.46Restrictive1,078
LINX LON1London, United Kingdom195.66.224.138Restrictive932
AMS-IX AmsterdamAmsterdam, Netherlands80.249.208.36Closed882
Equinix Internet Exchange AshburnAshburn, United States206.126.236.12Restrictive390
Equinix Internet Exchange ChicagoChicago, United States208.115.136.12Restrictive282
Equinix Internet Exchange San Jose (Bay Area)San Jose, United States206.223.116.12Restrictive192
ESpanix Madrid Lower LANMadrid, Spain193.149.1.36Restrictive177
Equinix Internet Exchange Palo AltoPalo Alto, United States198.32.176.14Restrictive76
Catalunya Neutral Internet Exchange PointBarcelona, Spain193.242.98.154Restrictive57
Netnod Sundsvall- GävleSundsvall, Sweden194.68.128.227Restrictive18

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-10 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,346 exchanges and 98,215 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.