CADMOS-2 cable: latency up to 2.2× normal, 30 Sep 2026
What we measured
| Cable | CADMOS-2 |
| Segment | Beirut, LB → Pentaskhinos, CY |
| Detected | 2026-09-30 01:31 UTC |
| Resolved | 2026-09-30 03:03 UTC |
| Duration | 1h 32m |
| Observed latency | 119.2 ms |
| Baseline | 127.5 ms · 2.2× |
| Increase | +120% |
| Severity | warning |
Who is affected
Countries where CADMOS-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 |
|---|---|---|---|
| Cyprus resilience index: 88 · resilient |
1 of 15 cables (7% of submarine diversity) | Blue, CADMOS, Ebla +11 more | no measurement today; median 32 ms over 30 days (21 routes) |
| Lebanon resilience index: 56 · moderate |
1 of 4 cables (25% of submarine diversity) | BERYTAR, CADMOS, IMEWE | median 115 ms today vs 119 ms over 30 days (62 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
No vessel activity was seen within 5 km of the cable route in the window from 48 hours before to 6 hours after the start (by AIS; vessels with transmitters off are not visible).
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. Too few independent vantage points were watching this endpoint to reach a cross-probe verdict.
Timeline
- Alert 2026093001: warning - ratio 2.2x
- Alert #216 improving: 2/3 consecutive OK
- Alert #216 resolved: RTT 119.18ms (baseline 127.52ms), 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.