CeltixConnect-1 (CC-1): 1.82× baseline latency
What we measured
| Cable | CeltixConnect-1 (CC-1) |
| Segment | Dublin, IE → Holyhead, GB |
| Detected | 2026-05-13 09:01 UTC |
| Resolved | 2026-05-13 13:01 UTC |
| Duration | 4h 0m |
| Observed latency | 72.9 ms |
| Baseline | 40.1 ms · 1.82× |
| Increase | +113% |
| 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: 97 · resilient |
1 of 16 cables (6% of submarine diversity) | AEC-1, Beaufort, Emerald Bridge Fibres +12 more | average 37 ms over the last day vs 62 ms over 30 days - faster |
| United Kingdom resilience index: 97 · resilient |
1 of 67 cables (1% of submarine diversity) | 2Africa, Amitie, Apollo +63 more | median 82 ms today vs 69 ms over 30 days (102 routes) - slower |
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. Only one probe saw it. We treat this as a probable false positive and label it as such.
Timeline
- Alert 2026051301: warning - ratio 2.13x
- Alert #117 improving: 1/3 consecutive OK
- Alert #117 improving: 1/3 consecutive OK
- Alert #117 improving: 2/3 consecutive OK
- Alert #117 improving: 1/3 consecutive OK
- Alert #117 improving: 2/3 consecutive OK
- Alert #117 resolved: RTT 72.93ms (baseline 40.05ms), 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.