Incident report · 2026040706
JUPITER: 0.97× baseline latency
Resolved · 4h 59m
What we measured
| Cable | JUPITER |
| Segment | Hermosa Beach, US → Daet, PH |
| Detected | 2026-04-07 10:32 UTC |
| Resolved | 2026-04-07 15:31 UTC |
| Duration | 4h 59m |
| Observed latency | 118.8 ms |
| Baseline | 122.6 ms · 0.97× |
| Increase | +116% |
| Severity | warning |
Who is affected
Countries where JUPITER 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 |
|---|---|---|---|
| Japan resilience index: 100 · resilient |
1 of 52 cables (2% of submarine diversity) | 5 Villages 6 Islands, APCN-2, Apricot +48 more | median 186 ms today vs 250 ms over 30 days (70 routes) - faster |
| Philippines resilience index: 100 · resilient |
1 of 25 cables (4% of submarine diversity) | APCN-2, Apricot, Asia Connect Cable-1 (ACC-1) +21 more | median 275 ms today vs 273 ms over 30 days (24 routes) - unchanged |
| United States resilience index: 100 · resilient |
1 of 119 cables (1% of submarine diversity) | ACS Alaska-Oregon Network (AKORN), AEC-1, Airraq +115 more | median 88 ms today vs 115 ms over 30 days (290 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. The effect was confined to a narrow set of paths, so a cable-wide fault is unlikely.
Timeline
- Alert #63: warning (backfilled)
- Alert #63 improving: 1/3 consecutive OK checks
- Alert #63 improving: 2/3 consecutive OK checks
- Alert #63 resolved: RTT 118.84ms (baseline 122.57ms)
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 2026040706: JUPITER. https://geocables.com/incident/2026040706
Embed this map
<iframe src="https://geocables.com/embed.php?type=map&id=jupiter" width="640" height="420" frameborder="0" loading="lazy" style="border:0;border-radius:10px"></iframe>