Jakarta-Bangka-Batam-Singapore (B2JS): 2.18× baseline latency
What we measured
| Cable | Jakarta-Bangka-Batam-Singapore (B2JS) |
| Segment | Singapore, SG → Singapore, SG |
| Detected | 2026-03-16 04:33 UTC |
| Resolved | 2026-03-16 05:31 UTC |
| Duration | 58m |
| Observed latency | 95.2 ms |
| Baseline | 43.7 ms · 2.18× |
| Increase | +118% |
| Severity | warning |
Who is affected
Countries where Jakarta-Bangka-Batam-Singapore (B2JS) 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 73 cables (1% of submarine diversity) | Apricot, Asia Connect Cable-1 (ACC-1), Asia United Gateway East (AUG East) +69 more | median 240 ms today vs 232 ms over 30 days (60 routes) - unchanged |
| Singapore resilience index: 78 · resilient |
1 of 46 cables (2% of submarine diversity) | APCN-2, Apricot, Asia Connect Cable-1 (ACC-1) +42 more | median 107 ms today vs 188 ms over 30 days (81 routes) - faster |
Dependence is structural (share of the country's submarine cables), not a traffic share: real traffic distribution across cables is not public.
Path analysis
No usable traceroute data for this window.
Cross-probe verdict. Only one probe saw it. We treat this as a probable false positive and label it as such.
Timeline
- Alert #21: warning - Chennai
- Alert #21 resolved: Chennai
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.