Incident report · 2026040603
Tonga Cable: 0.87× baseline latency
Resolved · 4h 59m
What we measured
| Cable | Tonga Cable |
| Segment | Nuku'alofa, TO → Suva, FJ |
| Detected | 2026-04-06 10:32 UTC |
| Resolved | 2026-04-06 15:31 UTC |
| Duration | 4h 59m |
| Observed latency | 11.5 ms |
| Baseline | 13.3 ms · 0.87× |
| Increase | +108% |
| Severity | warning |
Who is affected
Countries where Tonga Cable 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 |
|---|---|---|---|
| Fiji resilience index: 81 · resilient |
1 of 9 cables (11% of submarine diversity) | APX East, Bulikula, Gondwana-2/Picot-2 +5 more | median 370 ms today vs 359 ms over 30 days (6 routes) - unchanged |
| Tonga resilience index: 57 · moderate |
1 of 3 cables (33% of submarine diversity) | Hawaiki, Tonga Domestic Cable Extension (TDCE) | median 422 ms today vs 424 ms over 30 days (6 routes) - unchanged |
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. The effect was confined to a narrow set of paths, so a cable-wide fault is unlikely.
Timeline
- Alert #55: warning (backfilled)
- Alert #55 improving: 1/3 consecutive OK checks
- Alert #55 improving: 2/3 consecutive OK checks
- Alert #55 resolved: RTT 11.51ms (baseline 13.27ms)
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 2026040603: Tonga Cable. https://geocables.com/incident/2026040603
Embed this map
<iframe src="https://geocables.com/embed.php?type=map&id=tonga-cable" width="640" height="420" frameborder="0" loading="lazy" style="border:0;border-radius:10px"></iframe>