asn.dev

Interconnection

AS1547 IDK-NETWORK

Unclassified RIPE

Exchanges 13 13 active
Countries 7 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 AS1547, 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 6

ExchangeLocationTheir addressPolicyMember ports
DE-CIX FrankfurtFrankfurt, Germany80.81.194.70Open1,078
LINX LON1London, United Kingdom195.66.224.200Open931
AMS-IX AmsterdamAmsterdam, Netherlands80.249.208.97Open882
Neutral Internet ExchangeAmsterdam, Netherlands193.239.117.123—669
MSK-IX MoscowMoscow, Russia195.208.208.89—506
Coresite - Any2 WestLos Angeles, United States206.72.211.27Open344
Any2 CaliforniaLos Angeles, United States206.72.211.27Open318
Toronto Internet ExchangeToronto, Canada206.108.35.141Open287
Equinix Internet Exchange ChicagoChicago, United States208.115.136.192Open283
DE-CIX MadridMadrid, Spain185.1.192.174Open226
New York International Internet ExchangeNew York, United States198.32.160.123Open213
Berlin Commercial Internet ExchangeBerlin, Germany193.178.185.62Open153
Pittsburgh Internet ExchangePittsburgh, United States206.71.141.44Open45

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