Interconnection

AS34655 DOCLER-AS

Hosting RIPE

Exchanges 11 11 active

Countries 6 most in Germany

Regions 3

Largest fabric 932 LINX LON1

Recorded presence

Internet exchanges

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS34655, 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 3 Asia-Pacific 2

Exchange	Location	Their address	Policy	Member ports
LINX LON1	London, United Kingdom	195.66.224.210	Open	932
Equinix Internet Exchange Singapore	Singapore, Singapore	27.111.229.137	Open	496
Milan Internet Exchange	Milan, Italy	217.29.67.129	—	418
Coresite - Any2 West	Los Angeles, United States	206.72.210.13	Open	344
Any2 California	Los Angeles, United States	206.72.210.13	Open	319
Singapore Internet Exchange	Singapore, Singapore	103.16.102.207	Open	277
DE-CIX Dusseldorf	Düsseldorf, Germany	185.1.170.92	—	227
New York International Internet Exchange	New York, United States	198.32.160.55	Open	214
DE-CIX Munich	Munich, Germany	185.1.208.98	—	211
DE-CIX Hamburg	Hamburg, Germany	185.1.210.103	—	196
Luxembourg Internet Exchange	Luxembourg, Luxembourg	188.93.170.48	Open	103

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.