asn.dev

Interconnection

AS44324 MOEDOVE-AS MoeDove Global

Residential RIPE

Exchanges 10 10 active
Countries 8 most in Canada
Regions 3
Largest fabric 1,242 4b42 Internet Exchange Point

Recorded presence

Internet exchanges

recorded

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

ExchangeLocationTheir addressPolicyMember ports
4b42 Internet Exchange PointZurich, Switzerland185.1.125.244Open1,242
The Frys Internet ExchangeFrysian, Netherlands2001:7f8:10f::3:ad24:82Open339
London Network Access PointLondon, United Kingdom5.57.82.143Open314
Ontario Internet ExchangeToronto, Canada149.112.50.101Open205
Local Internet Exchange FrankfurtFrankfurt, Germany185.1.167.50Open202
Taipei Internet Exchange (TPIX)Taipei, Taiwan203.163.222.17Open190
Student & Technology United Internet ExchangesTaipei, Taiwan103.158.187.169Open134
UNMETERED ExchangeVancouver, Canada192.34.27.124Open128
Kansas City Internet ExchangeKansas City, United States206.51.7.208Open72
RUDAKI-IXKiev, Ukraine185.1.225.28—44

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.