Trapani-Kelibia 2 (KELTRA-2): 1.67× baseline latency
What we measured
| Cable | Trapani-Kelibia 2 (KELTRA-2) |
| Segment | Kelibia, TN → Trapani, IT |
| Detected | 2026-04-18 13:02 UTC |
| Resolved | 2026-04-18 14:31 UTC |
| Duration | 1h 29m |
| Observed latency | 84.4 ms |
| Baseline | 50.6 ms · 1.67× |
| Increase | +139% |
| Severity | warning |
Who is affected
Countries where Trapani-Kelibia 2 (KELTRA-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 |
|---|---|---|---|
| Italy resilience index: 97 · resilient |
1 of 38 cables (3% of submarine diversity) | 2Africa, ANDROMEDA, Asia Africa Europe-1 (AAE-1) +34 more | median 68 ms today vs 72 ms over 30 days (19 routes) - unchanged |
| Tunisia resilience index: 52 · vulnerable |
1 of 6 cables (17% of submarine diversity) | Didon, HANNIBAL System, Medusa Submarine Cable System +2 more | average 60 ms over 30 days |
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 2026041802: warning - ratio 2.39x
- Alert #87 improving: 1/3 consecutive OK
- Alert #87 resolved: RTT 84.39ms (baseline 50.6ms), 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.