asn.dev

Interconnection

AS131958 T-NET Tama Cable Network Co.,Ltd.

Residential APNIC

Exchanges 12 12 active
Countries 8 most in Japan
Regions 3
Largest fabric 1,078 DE-CIX Frankfurt

Recorded presence

Internet exchanges

recorded

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

ExchangeLocationTheir addressPolicyMember ports
DE-CIX FrankfurtFrankfurt, Germany80.81.195.149Open1,078
LINX LON1London, United Kingdom195.66.228.65Open932
AMS-IX AmsterdamAmsterdam, Netherlands80.249.213.157Open882
BroadBand Internet eXchange TokyoTokyo, Japan101.203.89.95Open361
Coresite - Any2 WestLos Angeles, United States206.72.211.41Open344
Any2 CaliforniaLos Angeles, United States206.72.211.41Open319
JPIX TokyoTokyo, Japan210.171.225.82Open301
BroadBand Internet eXchange SingaporeSingapore, Singapore103.231.152.36Open157
BroadBand Internet eXchange OsakaOsaka, Japan218.100.9.218Open134
JPIX OsakaOsaka, Japan103.246.232.182Open113
BroadBand Internet eXchange Hong KongHong Kong, China103.203.158.36Open101
Korea Internet Neutral Exchange KINXSeoul, South Korea139.150.100.158Open64

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.