NO-UK cable: latency up to 2× normal, 19 Jun 2026
What we measured
| Cable | NO-UK |
| Segment | Newcastle, GB → Stavanger, NO |
| Detected | 2026-06-19 05:01 UTC |
| Resolved | 2026-06-19 23:01 UTC |
| Duration | 18h 0m |
| Observed latency | 20.3 ms |
| Baseline | 21.7 ms · 2.02× |
| Increase | +102% |
| Severity | warning |
Who is affected
Countries where NO-UK 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 |
|---|---|---|---|
| Norway resilience index: 100 · resilient |
1 of 19 cables (5% of submarine diversity) | Arctic Way, Bodo-Rost Cable, Eviny Digital +15 more | no measurement today; median 86 ms over 30 days (104 routes) |
| United Kingdom resilience index: 100 · resilient |
1 of 68 cables (1% of submarine diversity) | 2Africa, Amitie, Apollo +64 more | median 76 ms today vs 74 ms over 30 days (1011 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. Other measurements did not confirm the event. We treat this as a probable false positive and label it as such.
Timeline
- Alert 2026061901: warning - ratio 2.02x
- Alert #136 improving: 2/3 consecutive OK
- Alert #136 resolved: RTT 20.32ms (baseline 21.7ms), 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.