asn.dev

Interconnection

AS17676 GIGAINFRA - SoftBank Corp.

Mobile ARIN NSP

Exchanges 9 9 active
Countries 4 most in Japan
Regions 2
Largest fabric 497 Equinix Internet Exchange Singapore

Recorded presence

Internet exchanges

recorded

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

ExchangeLocationTheir addressPolicyMember ports
Equinix Internet Exchange SingaporeSingapore, Singapore27.111.228.75Selective497
BroadBand Internet eXchange TokyoTokyo, Japan101.203.88.16Selective362
Seattle Internet ExchangeSeattle, United States206.81.80.197Selective349
Any2 CaliforniaLos Angeles, United States206.72.211.18—318
BroadBand Internet eXchange SingaporeSingapore, Singapore103.231.152.23Selective159
BroadBand Internet eXchange OsakaOsaka, Japan218.100.9.168Selective135
BroadBand Internet eXchange Hong KongHong Kong, China103.203.158.97Selective101
Equinix Internet Exchange Palo AltoPalo Alto, United States198.32.176.243—76
Network Service Provider IXP (Distributed IX in Edo)Tokyo, Japan202.249.2.156—26

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-11-02 by Packet Clearing House (https://www.pch.net/ixp/data), covering 1,347 exchanges and 97,999 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.