Adria-1: 1.97× baseline latency
What we measured
| Cable | Adria-1 |
| Segment | Corfu, GR → Dubrovnik, HR |
| Detected | 2026-04-14 05:01 UTC |
| Resolved | 2026-04-14 07:30 UTC |
| Duration | 2h 28m |
| Observed latency | 77.8 ms |
| Baseline | 39.6 ms · 1.97× |
| Increase | +198% |
| Severity | warning |
Who is affected
Countries where Adria-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 |
|---|---|---|---|
| Croatia resilience index: 43 · land links |
1 of 2 cables (50% of submarine diversity) | Italy-Croatia | median 72 ms today vs 74 ms over 30 days (6 routes) - unchanged |
| Greece resilience index: 97 · resilient |
1 of 21 cables (5% of submarine diversity) | 2Africa, ANDROMEDA, Apollo East and West +17 more | median 90 ms today vs 91 ms over 30 days (6 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. Only one probe saw it. We treat this as a probable false positive and label it as such.
Timeline
- Alert 2026041404: warning - ratio 2.98x
- Alert #75 improving: 1/3 consecutive OK
- Alert #75 improving: 2/3 consecutive OK
- Alert #75 resolved: RTT 77.76ms (baseline 39.56ms), 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.