asn.dev

Interconnection

AS13002 ISIX-AS

Residential RIPE Cable/DSL/ISP

Exchanges 11 11 active
Countries 10 most in Netherlands
Regions 3
Largest fabric 1,078 DE-CIX Frankfurt

Recorded presence

Internet exchanges

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS13002, 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 8 Asia-Pacific 2 North America 1

ExchangeLocationTheir addressPolicyMember ports
DE-CIX FrankfurtFrankfurt, Germany80.81.194.23Open1,078
LINX LON1London, United Kingdom195.66.227.197Open932
AMS-IX AmsterdamAmsterdam, Netherlands80.249.210.10Open882
Neutral Internet ExchangeAmsterdam, Netherlands193.239.116.22Open669
France-IX ParisParis, France37.49.236.245Open570
Hong Kong Internet ExchangeHong Kong, China123.255.92.19Open307
Singapore Internet ExchangeSingapore, Singapore103.16.102.225Open277
UAE-IXDubai, United Arab Emirates185.1.8.142Open113
Luxembourg Internet ExchangeLuxembourg, Luxembourg188.93.170.54Open103
Belgian National Internet ExchangeBrussels, Belgium194.53.172.102Open83
LINX NoVaReston, United States2001:504:31::32ca:1Open48

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.