asn.dev

Interconnection

AS53334 TUT-AS

Unclassified APNIC NSP

Exchanges 10 10 active
Countries 4 most in United States
Regions 3
Largest fabric 928 LINX LON1

Recorded presence

Internet exchanges

recorded

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

North America 5 Europe 4 Asia-Pacific 1

ExchangeLocationTheir addressPolicyMember ports
LINX LON1London, United Kingdom195.66.225.103Selective928
AMS-IX AmsterdamAmsterdam, Netherlands80.249.214.197Open891
Neutral Internet ExchangeAmsterdam, Netherlands193.239.118.80Selective671
Equinix Internet Exchange AshburnAshburn, United States206.126.238.52Selective388
Seattle Internet ExchangeSeattle, United States206.81.81.184Selective349
Coresite - Any2 WestLos Angeles, United States206.72.211.202Selective344
Any2 CaliforniaLos Angeles, United States206.72.211.202Selective318
Speed Internet ExchangeDronten, Netherlands185.1.222.54Selective286
Singapore Internet ExchangeSingapore, Singapore103.16.102.109Selective278
Equinix Internet Exchange DallasDallas, United States206.223.118.52Selective231

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