Concerto cable: latency up to 2.5× normal, 7 Nov 2026
What we measured
| Cable | Concerto |
| Segment | Sizewell, GB → Zandvoort, NL |
| Detected | 2026-11-07 22:32 UTC |
| Resolved | 2026-11-08 03:05 UTC |
| Duration | 4h 32m |
| Observed latency | 16.4 ms |
| Baseline | 15.7 ms · 2.53× |
| Increase | +153% |
| Severity | warning |
Who is affected
Countries where Concerto 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 |
|---|---|---|---|
| Netherlands resilience index: 100 · resilient |
1 of 12 cables (8% of submarine diversity) | Amerigo Vespucci, Atlantic Crossing-1 (AC-1), Circe North +8 more | median 77 ms today vs 67 ms over 30 days (2335 routes) - unchanged |
| United Kingdom resilience index: 100 · resilient |
1 of 68 cables (1% of submarine diversity) | 2Africa, Amitie, Apollo +64 more | median 74 ms today vs 79 ms over 30 days (3387 routes) - unchanged |
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
- WINDCAT 50: slow drift over the route, 0.3 km from the route, 38.5 h before the start
- WINDCAT 57: slow drift over the route, 0.3 km from the route, 14.9 h before the start
- PLATFORM P15 C (other): slow drift over the route, 0.5 km from the route, 46.3 h before the start
- MSC MIGSAN (cargo): slow drift over the route, 0.7 km from the route, 24.6 h before the start
- PURUS TIGERS 1839: slow drift over the route, 1.0 km from the route, 14.7 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 2026110701: warning - ratio 2.53x
- Alert #247 improving: 1/3 consecutive OK
- Alert #247 improving: 2/3 consecutive OK
- Alert #247 resolved: RTT 16.42ms (baseline 15.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.