Proa cable: latency up to 2.8× normal, 17 Oct 2026
What we measured
| Cable | Proa |
| Segment | Shima, JP → Tanguisson Point, GU |
| Detected | 2026-10-17 23:02 UTC |
| Resolved | 2026-10-21 18:01 UTC |
| Duration | 3d 18h |
| Observed latency | 47.5 ms |
| Baseline | 46.7 ms · 2.82× |
| Increase | +182% |
| Severity | warning |
Who is affected
Countries where Proa 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 297 ms today vs 264 ms over 30 days (59 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 225 ms today vs 203 ms over 30 days (468 routes) - unchanged |
| Northern Mariana Islands resilience index: 69 · moderate |
1 of 6 cables (17% of submarine diversity) | Atisa, Bulikula, Halaihai +2 more | average 6 ms over the last day vs 92 ms over 30 days - 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
Traffic kept the same route. Latency rose without a visible path change, which points at congestion or a fault on the existing route rather than a reroute.
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 2026101702: warning - ratio 2.82x
- Alert #230 improving: 1/3 consecutive OK
- Alert #230 improving: 1/3 consecutive OK
- Alert #230 improving: 1/3 consecutive OK
- Alert #230 improving: 2/3 consecutive OK
- Alert #230 improving: 1/3 consecutive OK
- Alert #230 improving: 1/3 consecutive OK
- Alert #230 improving: 1/3 consecutive OK
- Alert #230 improving: 1/3 consecutive OK
- Alert #230 improving: 1/3 consecutive OK
- Alert #230 improving: 1/3 consecutive OK
- Alert #230 improving: 1/3 consecutive OK
- Alert #230 improving: 1/3 consecutive OK
- Alert #230 improving: 1/3 consecutive OK
- Alert #230 improving: 2/3 consecutive OK
- Alert #230 improving: 1/3 consecutive OK
- Alert #230 improving: 1/3 consecutive OK
- Alert #230 improving: 2/3 consecutive OK
- Alert #230 improving: 1/3 consecutive OK
- Alert #230 improving: 2/3 consecutive OK
- Alert #230 resolved: RTT 47.48ms (baseline 46.65ms), 3 consecutive OK
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.