Guam Okinawa Kyushu Incheon (GOKI) cable: latency up to 2.1× normal, 7 Oct 2026
What we measured
| Cable | Guam Okinawa Kyushu Incheon (GOKI) |
| Segment | Kitakyushu, JP → Tumon Bay, GU |
| Detected | 2026-10-07 09:01 UTC |
| Resolved | 2026-10-14 09:03 UTC |
| Duration | 7d 0h |
| Observed latency | 138.6 ms |
| Baseline | 65.6 ms · 2.11× |
| Increase | +111% |
| Severity | warning |
Who is affected
Countries where Guam Okinawa Kyushu Incheon (GOKI) 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 |
|---|---|---|---|
| Guam resilience index: 83 · resilient |
1 of 19 cables (5% of submarine diversity) | Apricot, Asia Connect Cable-1 (ACC-1), Asia-America Gateway (AAG) Cable System +15 more | median 293 ms today vs 271 ms over 30 days (50 routes) - unchanged |
| Japan resilience index: 100 · resilient |
1 of 53 cables (2% of submarine diversity) | 5 Villages 6 Islands, APCN-2, Apricot +49 more | median 220 ms today vs 203 ms over 30 days (466 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
- Alert 2026100701: warning - ratio 2.11x
- Alert #220 improving: 1/3 consecutive OK
- Alert #220 improving: 1/3 consecutive OK
- Alert #220 improving: 1/3 consecutive OK
- Alert #220 improving: 1/3 consecutive OK
- Alert #220 improving: 1/3 consecutive OK
- Alert #220 improving: 1/3 consecutive OK
- Alert #220 improving: 1/3 consecutive OK
- Alert #220 improving: 1/3 consecutive OK
- Alert #220 improving: 2/3 consecutive OK
- Alert #220 improving: 1/3 consecutive OK
- Alert #220 improving: 1/3 consecutive OK
- Alert #220 improving: 1/3 consecutive OK
- Alert #220 improving: 1/3 consecutive OK
- Alert #220 improving: 2/3 consecutive OK
- Alert #220 improving: 1/3 consecutive OK
- Alert #220 improving: 1/3 consecutive OK
- Alert #220 improving: 1/3 consecutive OK
- Alert #220 improving: 1/3 consecutive OK
- Alert #220 improving: 1/3 consecutive OK
- baseline_shift: Alert #220 Tumon Bay closed as BASELINE SHIFT after 7+ days: frozen 65.6ms -> new baseline 139.0ms (current 138.6ms). Route changed, not a cable incident.
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.