SHEFA-2 cable: latency up to 2.1× normal, 19 Nov 2026
What we measured
| Cable | SHEFA-2 |
| Segment | Banff, GB → Torshavn, FO |
| Detected | 2026-11-19 23:04 UTC |
| Resolved | 2026-11-20 01:01 UTC |
| Duration | 1h 57m |
| Observed latency | 27.3 ms |
| Baseline | 28.3 ms · 2.1× |
| Increase | +110% |
| Severity | warning |
Who is affected
Countries where SHEFA-2 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 |
|---|---|---|---|
| Faroe Islands resilience index: 36 · vulnerable |
1 of 2 cables (50% of submarine diversity) | FARICE-1 | median 86 ms today vs 86 ms over 30 days (36 routes) - unchanged |
| United Kingdom resilience index: 100 · resilient |
1 of 68 cables (1% of submarine diversity) | 2Africa, Amitie, Apollo +64 more | median 62 ms today vs 79 ms over 30 days (3433 routes) - faster |
Dependence is structural (share of the country's submarine cables), not a traffic share: real traffic distribution across cables is not public.
Vessels nearby at the time of the incident
- F/V GURE ANDRE (fishing): slow drift over the route, 1.8 km from the route, 27.1 h before the start
Vessels near a cable route are seen before incidents about as often as on ordinary days: 61% against 57% over 79 incidents since 6 Aug 2026. How this is counted
Alert check
Not confirmed. We asked other measurement points, and they did not see the trouble. The alert stays on record but is not counted as an incident. what this means
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 2026111901: warning - ratio 2.1x
- Alert #251 improving: 1/3 consecutive OK
- Alert #251 improving: 2/3 consecutive OK
- Alert #251 resolved: RTT 27.32ms (baseline 28.3ms), 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.