CeltixConnect-1 (CC-1) cable: latency up to 2.5× normal, 19 May 2026
What we measured
| Cable | CeltixConnect-1 (CC-1) |
| Segment | Dublin, IE → Holyhead, GB |
| Detected | 2026-05-19 19:01 UTC |
| Resolved | 2026-05-19 20:30 UTC |
| Duration | 1h 29m |
| Observed latency | 25.4 ms |
| Baseline | 57.9 ms · 2.48× |
| Increase | +148% |
| Severity | warning |
Who is affected
Countries where CeltixConnect-1 (CC-1) 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 |
|---|---|---|---|
| Ireland resilience index: 100 · resilient |
1 of 16 cables (6% of submarine diversity) | AEC-1, Beaufort, Emerald Bridge Fibres +12 more | median 94 ms today vs 63 ms over 30 days (180 routes) - slower |
| United Kingdom resilience index: 100 · resilient |
1 of 68 cables (1% of submarine diversity) | 2Africa, Amitie, Apollo +64 more | median 64 ms today vs 73 ms over 30 days (1020 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. Some probes saw the degradation and others did not, which usually means a partial or regional effect.
Timeline
- Alert 2026051902: warning - ratio 2.48x
- Alert #123 improving: 1/3 consecutive OK
- Alert #123 resolved: RTT 25.38ms (baseline 57.9ms), 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.