KetchCan1 Submarine Fiber Cable System: latency up to 2.2× normal, 13 Oct 2026
What we measured
| Cable | KetchCan1 Submarine Fiber Cable System |
| Segment | Ketchikan, US → Prince Rupert, CA |
| Detected | 2026-10-13 15:34 UTC |
| Resolved | 2026-10-13 19:02 UTC |
| Duration | 3h 28m |
| Observed latency | 40.1 ms |
| Baseline | 40.1 ms · 2.21× |
| Increase | +121% |
| Severity | warning |
Who is affected
Countries where KetchCan1 Submarine Fiber Cable System 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 |
|---|---|---|---|
| Canada resilience index: 100 · resilient |
1 of 21 cables (5% of submarine diversity) | AmeriCan-1, APOCS 1, APOCS 2 +17 more | median 11 ms today vs 63 ms over 30 days (194 routes) - faster |
| 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 109 ms over 30 days (3311 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 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 2026101301: warning - ratio 2.21x
- Alert #226 improving: 1/3 consecutive OK
- Alert #226 improving: 2/3 consecutive OK
- Alert #226 resolved: RTT 40.08ms (baseline 40.06ms), 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.