asn.dev

Interconnection

AS9354 TDNC Community Network Center Inc.

Residential APNIC

Exchanges 12 12 active
Countries 6 most in Japan
Regions 3
Largest fabric 931 LINX LON1

Recorded presence

Internet exchanges

recorded

Internet exchanges where Packet Clearing House has a port recorded for AS9354, 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 9 North America 2 Europe 1

ExchangeLocationTheir addressPolicyMember ports
LINX LON1London, United Kingdom195.66.227.200Open931
BroadBand Internet eXchange TokyoTokyo, Japan101.203.88.81Open361
Coresite - Any2 WestLos Angeles, United States206.72.211.203Open344
Any2 CaliforniaLos Angeles, United States206.72.211.203Open319
JPIX TokyoTokyo, Japan210.171.224.140Open301
BroadBand Internet eXchange SingaporeSingapore, Singapore103.231.153.12Open157
BroadBand Internet eXchange OsakaOsaka, Japan218.100.9.40Open134
Equinix Internet Exchange TokyoTokyo, Japan203.190.230.6Open128
JPIX OsakaOsaka, Japan103.246.232.140Open113
BroadBand Internet eXchange Hong KongHong Kong, China103.203.158.114Open101
Korea Internet Neutral Exchange KINXSeoul, South Korea139.150.100.145Open64
Equinix Internet Exchange OsakaOsaka, Japan203.190.227.3Open26

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.