Incident report · 2026031502
5 Villages 6 Islands: 2.33× baseline latency
Resolved · 59m
What we measured
| Cable | 5 Villages 6 Islands |
| Segment | Tokyo, JP → Tokyo, JP |
| Detected | 2026-03-15 04:33 UTC |
| Resolved | 2026-03-15 05:32 UTC |
| Duration | 59m |
| Observed latency | 371.4 ms |
| Baseline | 159.6 ms · 2.33× |
| Increase | +133% |
| Severity | warning |
Who is affected
Countries where 5 Villages 6 Islands 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) | APCN-2, Apricot, Asia Direct Cable (ADC) +48 more | median 186 ms today vs 250 ms over 30 days (70 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 #14: warning - Kitakyushu
- Alert #14 resolved: Kitakyushu
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 2026031502: 5 Villages 6 Islands. https://geocables.com/incident/2026031502
Embed this map
<iframe src="https://geocables.com/embed.php?type=map&id=5-villages-6-islands" width="640" height="420" frameborder="0" loading="lazy" style="border:0;border-radius:10px"></iframe>