asn.dev

Interconnection

AS25180 EXPONENTIAL-E-AS

Unclassified RIPE

Exchanges 11 11 active
Countries 4 most in Germany
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 AS25180, 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 7 North America 4

ExchangeLocationTheir addressPolicyMember ports
DE-CIX FrankfurtFrankfurt, Germany80.81.194.187Selective1,078
LINX LON1London, United Kingdom195.66.224.186Selective931
AMS-IX AmsterdamAmsterdam, Netherlands80.249.210.52Case-by-case882
Equinix Internet Exchange AshburnAshburn, United States206.126.237.170Selective390
London Network Access PointLondon, United Kingdom5.57.80.102Open314
DE-CIX New YorkNew York, United States206.82.104.101Selective285
DE-CIX DusseldorfDüsseldorf, Germany185.1.171.12Selective227
New York International Internet ExchangeNew York, United States198.32.160.75Selective213
DE-CIX MunichMunich, Germany185.1.208.227Selective211
DE-CIX HamburgHamburg, Germany185.1.210.15Selective196
LINX NoVaReston, United States206.55.196.21Selective48

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