Incident report · 2026090505
JAKABARE: 0.09× baseline latency
Resolved · 8h 0m
What we measured
| Cable | JAKABARE |
| Segment | Sydney, AU → Changi North, SG |
| Detected | 2026-09-05 04:32 UTC |
| Resolved | 2026-09-05 12:32 UTC |
| Duration | 8h 0m |
| Observed latency | 14.3 ms |
| Baseline | 157.3 ms · 0.09× |
| Increase | +101% |
| Severity | warning |
Who is affected
Countries where JAKABARE 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.
Timeline
- Alert 2026090505: warning - ratio 2.01x
- Alert #191 improving: 1/3 consecutive OK
- Alert #191 improving: 2/3 consecutive OK
- Alert #191 resolved: RTT 14.34ms (baseline 157.29ms), 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.
How to cite
GeoCables (2026). Incident 2026090505: JAKABARE. https://geocables.com/incident/2026090505
Embed this map
<iframe src="https://geocables.com/embed.php?type=map&id=jakabare" width="640" height="420" frameborder="0" loading="lazy" style="border:0;border-radius:10px"></iframe>