Jakarta-Bangka-Bintan-Batam-Singapore (B3JS) cable: latency up to 2.2× normal, 17 Sep 2026
What we measured
| Cable | Jakarta-Bangka-Bintan-Batam-Singapore (B3JS) |
| Segment | Tanah Merah, SG → Jakarta, ID |
| Detected | 2026-09-17 10:02 UTC |
| Resolved | 2026-09-17 13:02 UTC |
| Duration | 3h 0m |
| Observed latency | 15.7 ms |
| Baseline | 41.6 ms · 2.21× |
| Increase | +122% |
| Severity | critical |
Who is affected
Countries where Jakarta-Bangka-Bintan-Batam-Singapore (B3JS) comes ashore, how much of their submarine diversity this cable represents, and what our measurements into them show.
| Country | Dependence on this cable | Other submarine cables | What the measurements show |
|---|---|---|---|
| Indonesia resilience index: 100 · resilient |
1 of 74 cables (1% of submarine diversity) | Apricot, APX West, Asia Connect Cable-1 (ACC-1) +70 more | median 209 ms today vs 215 ms over 30 days (3602 routes) - unchanged |
| Singapore resilience index: 78 · resilient |
1 of 47 cables (2% of submarine diversity) | APCN-2, Apricot, APX West +43 more | median 198 ms today vs 186 ms over 30 days (1611 routes) - unchanged |
Dependence is structural (share of the country's submarine cables), not a traffic share: real traffic distribution across cables is not public.
Vessels nearby at the time of the incident
- SEA BEIJING (cargo): anchorage, 0.2 km from the route, 32.2 h before the start
- SIFNOS (tanker): anchorage, 0.2 km from the route, 26.0 h before the start
- YUAN HANG CAI FU (cargo): anchorage, 0.2 km from the route, 3.6 h before the start
- JADE PROSPERITY (cargo): anchorage, 0.3 km from the route, 27.7 h before the start
- SOTIRIA (cargo): anchorage, 0.3 km from the route, 5.1 h after the start
Vessels near a cable route are seen before incidents about as often as on ordinary days: 61% against 57% over 79 incidents since 6 Aug 2026. How this is counted
Path analysis
Traffic kept the same route. Latency rose without a visible path change, which points at congestion or a fault on the existing route rather than a reroute.
Cross-probe verdict. Other measurements did not confirm the event. We treat this as a probable false positive and label it as such.
Timeline
- Alert 2026091701: warning - ratio 2.21x
- Alert #203 improving: 1/3 consecutive OK
- Alert #203 improving: 2/3 consecutive OK
- Alert #203 improving: 2/3 consecutive OK
- Alert #203 resolved: RTT 15.72ms (baseline 41.6ms), 3 consecutive OK
Detection method
Latency is sampled continuously from our probe network. An alert opens when round-trip time to a monitored endpoint holds above its rolling baseline, and closes automatically once it returns. Full method is described on the methodology page.