Interconnection

AS24961 MYLOC-AS IP Backbone of WIIT AG formerly myLoc managed IT AG

Hosting RIPE

Exchanges 13 13 active

Countries 4 most in Germany

Regions 1

Largest fabric 1,078 DE-CIX Frankfurt

Recorded presence

Internet exchanges

recorded

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

Exchange	Location	Their address	Policy	Member ports
DE-CIX Frankfurt	Frankfurt, Germany	80.81.192.162	Open	1,078
AMS-IX Amsterdam	Amsterdam, Netherlands	80.249.208.219	Selective	882
Milan Internet Exchange	Milan, Italy	217.29.67.151	—	418
Speed Internet Exchange	Dronten, Netherlands	185.1.222.19	Open	284
SwissIX	Zurich, Switzerland	91.206.53.33	Open	256
InterIX Internet Exchange	Amsterdam, Netherlands	2001:7f8:134::d	Open	234
DE-CIX Dusseldorf	Düsseldorf, Germany	185.1.170.3	Open	227
DE-CIX Munich	Munich, Germany	185.1.208.16	Open	211
ERA-IX Amsterdam	Amsterdam, Netherlands	185.1.240.55	—	199
DE-CIX Hamburg	Hamburg, Germany	185.1.210.31	Open	196
Berlin Commercial Internet Exchange	Berlin, Germany	193.178.185.161	Open	153
Milan Neutral Access Point	Milan, Italy	185.1.114.86	Open	118
Megaport Dusseldorf IX	Düsseldorf, Germany	194.146.118.11	Open	98

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