Interconnection

AS34549 MEER-AS meerfarbig GmbH & Co. KG

Hosting ARIN NSP

Exchanges 13 13 active

Countries 6 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 AS34549, 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 12 North America 1

Exchange	Location	Their address	Policy	Member ports
DE-CIX Frankfurt	Frankfurt, Germany	80.81.196.151	Open	1,078
LINX LON1	London, United Kingdom	195.66.225.198	Open	932
KleyReX Internet Exchange	Frankfurt, Germany	193.189.82.41	Open	465
DE-CIX New York	New York, United States	206.82.105.102	Open	285
SwissIX	Zurich, Switzerland	91.206.52.244	Open	256
DE-CIX Dusseldorf	Düsseldorf, Germany	185.1.170.199	Open	227
DE-CIX Madrid	Madrid, Spain	185.1.192.200	Open	227
DE-CIX Munich	Munich, Germany	185.1.208.185	Open	211
Local Internet Exchange Frankfurt	Frankfurt, Germany	185.1.166.39	Open	202
DE-CIX Hamburg	Hamburg, Germany	185.1.210.177	Open	196
DE-CIX Marseille	Marseille, France	185.1.47.103	Open	113
CH Swiss Internet Exchange	Zurich, Switzerland	185.1.59.146	Open	111
Community-IX.ch	Zurich, Switzerland	185.1.105.15	—	24

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.