Incident report · 2026040509
Blue cable: latency anomaly, 5 Apr 2026
Resolved · 1h 0m
What we measured
| Cable | Blue |
| Segment | Aqaba, JO → Marseille, FR |
| Detected | 2026-04-05 22:30 UTC |
| Resolved | 2026-04-05 23:31 UTC |
| Duration | 1h 0m |
| Observed latency | 65.9 ms |
| Baseline | 79 ms · 0.83× |
| Increase | +377% |
| Severity | critical |
Who is affected
Countries where Blue 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) | CADMOS, CADMOS-2, Ebla +11 more | no measurement today; median 33 ms over 30 days (9 routes) |
| France resilience index: 100 · resilient |
1 of 35 cables (3% of submarine diversity) | 2Africa, Africa Coast to Europe (ACE), Africa-1 +31 more | median 67 ms today vs 71 ms over 30 days (666 routes) - unchanged |
| Greece resilience index: 100 · resilient |
1 of 21 cables (5% of submarine diversity) | 2Africa, Adria-1, ANDROMEDA +17 more | median 85 ms today vs 67 ms over 30 days (71 routes) - slower |
| Israel resilience index: 77 · resilient |
1 of 8 cables (13% of submarine diversity) | ANDROMEDA, EMC West-1, EMC West-2 +4 more | median 82 ms today vs 84 ms over 30 days (27205 routes) - unchanged |
| Italy resilience index: 100 · resilient |
1 of 38 cables (3% of submarine diversity) | 2Africa, ANDROMEDA, Asia Africa Europe-1 (AAE-1) +34 more | median 94 ms today vs 81 ms over 30 days (374 routes) - slower |
| Jordan resilience index: 53 · vulnerable |
1 of 7 cables (14% of submarine diversity) | ANDROMEDA, Coral Bridge, FEA +3 more | no measurement today; median 111 ms over 30 days (9 routes) |
Dependence is structural (share of the country's submarine cables), not a traffic share: real traffic distribution across cables is not public.
Path analysis
No usable traceroute data for this window.
Cross-probe verdict. The effect was confined to a narrow set of paths, so a cable-wide fault is unlikely.
Timeline
- Alert #52: critical (backfilled)
- Alert #52 improving: 1/3 consecutive OK checks
- Alert #52 improving: 2/3 consecutive OK checks
- Alert #52 resolved: RTT 65.85ms (baseline 78.97ms)
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.
How to cite
GeoCables (2026). Incident 2026040509: Blue. https://geocables.com/incident/2026040509
Embed this map
<iframe src="https://geocables.com/embed.php?type=map&id=blue" width="640" height="420" frameborder="0" loading="lazy" style="border:0;border-radius:10px"></iframe>