Italy-Libya cable: latency up to 2.2× normal, 17 Nov 2026
What we measured
| Cable | Italy-Libya |
| Segment | Mazara del Vallo, IT → Tripoli, LY |
| Detected | 2026-11-17 19:30 UTC |
| Resolved | 2026-11-18 14:01 UTC |
| Duration | 18h 30m |
| Observed latency | 30.1 ms |
| Baseline | 30 ms · 2.23× |
| Increase | +100% |
| Severity | critical |
Who is affected
Countries where Italy-Libya 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 |
|---|---|---|---|
| Italy resilience index: 100 · resilient |
1 of 38 cables (3% of submarine diversity) | 2Africa, ANDROMEDA, Asia Africa Europe-1 (AAE-1) +34 more | median 84 ms today vs 76 ms over 30 days (3014 routes) - unchanged |
| Libya resilience index: 84 · resilient |
1 of 6 cables (17% of submarine diversity) | Europe India Gateway (EIG), LFON (Libyan Fiber Optic Network), Medusa Submarine Cable System +2 more | median 105 ms today vs 130 ms over 30 days (175 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
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).
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 2026111701: warning - ratio 2.23x
- Alert #249 improving: 1/3 consecutive OK
- Alert #249 improving: 2/3 consecutive OK
- Alert #249 improving: 1/3 consecutive OK
- Alert #249 improving: 2/3 consecutive OK
- Alert #249 improving: 1/3 consecutive OK
- Alert #249 improving: 2/3 consecutive OK
- Alert #249 improving: 1/3 consecutive OK
- Alert #249 improving: 2/3 consecutive OK
- Alert #249 improving: 1/3 consecutive OK
- Alert #249 improving: 2/3 consecutive OK
- Alert #249 resolved: RTT 30.09ms (baseline 29.99ms), 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.