Port Speeds at Internet Exchange Points in Indonesia

Total ports
5,173
Median port
10 Gbps
90th percentile
40 Gbps
400G+ ports
22

Port Speed Mix Today

View as table
Current port speed mix by technology class
Speed classPorts / capacity
<1G63 ports (1.2%), 4.1 Gbps (0.0% of capacity)
1G1,868 ports (36.1%), 2.01 Tbps (2.2% of capacity)
10G2,687 ports (51.9%), 27.53 Tbps (29.9% of capacity)
25G14 ports (0.3%), 405 Gbps (0.4% of capacity)
40G95 ports (1.8%), 3.95 Tbps (4.3% of capacity)
100G424 ports (8.2%), 49.1 Tbps (53.3% of capacity)
400G21 ports (0.4%), 8.4 Tbps (9.1% of capacity)
800G1 ports (0.0%), 800 Gbps (0.9% of capacity)

Speed Class Adoption Since 2016

View as table
Share of ports by speed class, latest month
Speed classShare of ports
<1G1.0%
1G36.6%
10G51.8%
25G0.3%
40G1.8%
100G8.1%
400G0.4%

400G+ Scoreboard

#IXPCity400G ports800G ports400G+ capacityShare of its ports
1IIX-JakartaJakarta702.8 Tbps0.8%
2ILIXJakarta Selatan502 Tbps4.6%
3JKT-IXJakarta401.6 Tbps0.4%
4Digital Edge EPIX JakartaJakarta401.6 Tbps3.7%
5BIX JakartaJakarta01800 Gbps0.5%
6DE-CIX JakartaJakarta10400 Gbps0.6%

Recent 400G+ Activations (90 days)

DateNetworkIXPChange
2026-10-20AS17451 Biznet NetworksBIX Jakarta500 Gbps → 800 Gbps
2026-10-13AS20940 Akamai TechnologiesJKT-IX300 Gbps → 400 Gbps
2026-09-16AS17885 XLSmart AS17885IIX-Jakartanew port at 400 Gbps
2026-09-12AS152063 ILIXILIX100 Gbps → 400 Gbps
2026-09-10AS138840 PARSAORAN GLOBAL DATATRANS - NAPILIXnew port at 400 Gbps
2026-09-10AS134651 Yetoya Solusi IndonesiaILIX100 Gbps → 400 Gbps
2026-09-01AS138915 Kaopu Cloud HKIIX-Jakarta40 Gbps → 400 Gbps
2026-08-28AS139205 JalabyteIIX-Jakarta300 Gbps → 400 Gbps

In Indonesia, IXP members connect through 5,173 ports. The median port is 10 Gbps, 8.6% of ports run at 100G or faster, and 22 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.