Port Speeds at Internet Exchange Points in Japan

Total ports
2,030
Median port
20 Gbps
90th percentile
200 Gbps
400G+ ports
73

Port Speed Mix Today

Current port speed mix by technology class
Speed classPorts / capacity
<1G42 ports (2.1%), 2.82 Gbps (0.0% of capacity)
1G250 ports (12.3%), 269.02 Gbps (0.2% of capacity)
10G871 ports (42.9%), 10.21 Tbps (6.7% of capacity)
25G6 ports (0.3%), 175 Gbps (0.1% of capacity)
40G22 ports (1.1%), 920 Gbps (0.6% of capacity)
100G766 ports (37.7%), 104.2 Tbps (67.9% of capacity)
400G64 ports (3.2%), 30.4 Tbps (19.8% of capacity)
800G9 ports (0.4%), 7.2 Tbps (4.7% of capacity)

Speed Class Adoption Since 2016

Share of ports by speed class, latest month
Speed classShare of ports
<1G2.1%
1G12.3%
10G43.1%
25G0.4%
40G1.1%
100G37.5%
400G3.1%
800G0.4%

400G+ Scoreboard

#IXPCity400G ports800G ports400G+ capacityShare of its ports
1BBIX TokyoTokyo20212.8 Tbps5.1%
2JPNAP TokyoTokyo1529.2 Tbps5.7%
3JPIX TOKYOTokyo1136.8 Tbps4.3%
4BBIX OsakaOsaka702.8 Tbps4.4%
5JPIX OSAKAOsaka423.2 Tbps4.5%
6JPNAP OsakaOsaka602.4 Tbps5.1%
7Equinix TokyoTokyo10400 Gbps0.6%

Recent 400G+ Activations (90 days)

DateNetworkIXPChange
2026-09-03AS6939 Hurricane ElectricJPNAP Tokyo100 Gbps → 400 Gbps
2026-08-28AS6939 Hurricane ElectricBBIX Osaka100 Gbps → 400 Gbps
2026-08-24AS2527 Sony Network CommunicationsBBIX Tokyo200 Gbps → 400 Gbps
2026-08-03AS53813 Zscaler AS53813BBIX Tokyo200 Gbps → 400 Gbps
2026-08-03AS53813 Zscaler AS53813BBIX Tokyo200 Gbps → 400 Gbps
2026-07-23AS23620 DMM.com LLCJPNAP Tokyo100 Gbps → 400 Gbps
2026-07-08AS23620 DMM.com LLCJPNAP Tokyo100 Gbps → 400 Gbps
2026-07-01AS215724 Edgevana, Inc.BBIX Tokyonew port at 400 Gbps

In Japan, IXP members connect through 2,030 ports. The median port is 20 Gbps, 41.3% of ports run at 100G or faster, and 73 ports have entered the 400G era. Speed classes are inferred from aggregate connection speeds: totals that are exact multiples of a standard rate count toward the largest rate that divides them (a 500 Gbps LAG is 100G-class), while a LAG landing exactly on a standard rate — say 4x100G reporting 400G — is indistinguishable from a native port in PeeringDB. Numbers straight from PeeringDB, refreshed every night.