Aden-Djibouti cable: latency up to 2.1× normal, 9 Jun 2026
What we measured
| Cable | Aden-Djibouti |
| Segment | Djibouti City, DJ → Aden, YE |
| Detected | 2026-06-09 21:01 UTC |
| Resolved | 2026-06-10 04:31 UTC |
| Duration | 7h 30m |
| Observed latency | 76.9 ms |
| Baseline | 81.4 ms · 2.08× |
| Increase | +108% |
| Severity | warning |
Who is affected
Countries where Aden-Djibouti 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 |
|---|---|---|---|
| Djibouti resilience index: 68 · moderate |
1 of 12 cables (8% of submarine diversity) | 2Africa, Africa-1, Asia Africa Europe-1 (AAE-1) +8 more | no measurement today; median 165 ms over 30 days (40 routes) |
| Yemen resilience index: 65 · moderate |
1 of 5 cables (20% of submarine diversity) | Africa-1, Asia Africa Europe-1 (AAE-1), FALCON +1 more | no measurement today; median 54 ms over 30 days (11 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
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 2026060901: warning - ratio 2.08x
- Alert #133 improving: 1/3 consecutive OK
- Alert #133 improving: 2/3 consecutive OK
- Alert #133 resolved: RTT 76.86ms (baseline 81.37ms), 4 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.