asn.dev

Interconnection

AS55818 MCIX-AS-AP MC-IX Matrix Internet Exchange RS-1

Residential APNIC Network Services

Exchanges 11 11 active
Countries 7 most in United States
Regions 3
Largest fabric 1,076 DE-CIX Frankfurt

Recorded presence

Internet exchanges

recorded

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

Asia-Pacific 4 Europe 4 North America 3

ExchangeLocationTheir addressPolicyMember ports
DE-CIX FrankfurtFrankfurt, Germany80.81.195.48Selective1,076
AMS-IX AmsterdamAmsterdam, Netherlands80.249.212.208Open891
MSK-IX MoscowMoscow, Russia195.208.210.69—508
BroadBand Internet eXchange TokyoTokyo, Japan101.203.90.45Selective362
Seattle Internet ExchangeSeattle, United States206.81.80.154Selective349
Coresite - Any2 WestLos Angeles, United States206.72.211.45Selective344
Any2 CaliforniaLos Angeles, United States2001:504:13::211:45Selective318
JPIX TokyoTokyo, Japan210.171.225.115Selective300
NetIXSofia, Bulgaria185.1.226.14Selective264
DE-CIX ASEAN (Singapore, Malaysia, Brunei)Singapore, Singapore103.162.254.31Selective138
AMS-IX SingaporeSingapore, Singapore112.137.24.46Case-by-case14

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.