Home
Explore Cables Locations Map ISP status Transit map Country resilience Check my connection
Live Network radar Live Map Cable monitoring Events log Cable incidents Big screen
Learn Research Guide Methodology Latency Overland links Deployments by year Pulse Open dataset API Widgets What's new About Contact
Incident report · 2026102101

JUPITER cable: latency up to 3.4× normal, 21 Oct 2026

Monitoring · 3d 7h (ongoing)
XTelegramWhatsAppFacebook

What we measured

CableJUPITER
SegmentDaet, PH → Hermosa Beach, US
Detected2026-10-21 04:41 UTC
Duration3d 7h (ongoing)
Observed latency159.1 ms
Baseline84.2 ms · 3.44×
Increase+244%
Severitywarning

Who is affected

Countries where JUPITER comes ashore, how much of their submarine diversity this cable represents, and what our measurements into them show.

CountryDependence on this cableOther submarine cablesWhat the measurements show
Japan
resilience index: 100 · resilient
1 of 53 cables (2% of submarine diversity) 5 Villages 6 Islands, APCN-2, Apricot +49 more median 225 ms today vs 203 ms over 30 days (468 routes) - unchanged
Philippines
resilience index: 100 · resilient
1 of 26 cables (4% of submarine diversity) APCN-2, Apricot, Asia Connect Cable-1 (ACC-1) +22 more median 284 ms today vs 244 ms over 30 days (102 routes) - slower
United States
resilience index: 100 · resilient
1 of 122 cables (1% of submarine diversity) ACS Alaska-Oregon Network (AKORN), AEC-1, Airraq +118 more median 116 ms today vs 108 ms over 30 days (3282 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

Traffic changed route while latency was elevated. A reroute of this kind usually follows a fault somewhere on the original path.

Cross-probe verdict. Our own cross-check concluded this was an operator reroute, not a cable fault. We publish it anyway, labelled as such.

Timeline

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 2026102101: JUPITER. https://geocables.com/incident/2026102101

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>

← All cable events

Log In

Access your routes, favorites, and API key

Create account Forgot password?