asn.dev

Interconnection

AS53356 FREE RANGE CLOUD

Hosting ARIN NSP

Exchanges 10 10 active
Countries 4 most in Canada
Regions 2
Largest fabric 465 KleyReX Internet Exchange

Recorded presence

Internet exchanges

recorded

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

North America 7 Europe 3

ExchangeLocationTheir addressPolicyMember ports
KleyReX Internet ExchangeFrankfurt, Germany193.189.82.18Open465
Seattle Internet ExchangeSeattle, United States206.81.80.225Open350
Toronto Internet ExchangeToronto, Canada206.108.34.37Open286
Speed Internet ExchangeDronten, Netherlands185.1.222.175Open284
ERA-IX AmsterdamAmsterdam, Netherlands185.1.240.107—199
Fremont Cabal Internet ExchangeFremont, United States206.80.238.14—182
UNMETERED ExchangeVancouver, Canada192.34.27.4Open128
YYCIX Calgary Internet ExchangeCalgary, Canada206.126.225.121Open102
Kansas City Internet ExchangeKansas City, United States206.51.7.31Open72
CloudSingularity Internet ExchangeVancouver, Canada206.83.46.13Open18

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.