Gulf2Africa (G2A) cable: latency up to 2.2× normal, 4 Jul 2026
What we measured
| Cable | Gulf2Africa (G2A) |
| Segment | Berbera, SO → Salalah, OM |
| Detected | 2026-07-04 03:02 UTC |
| Resolved | 2026-07-04 06:00 UTC |
| Duration | 2h 58m |
| Observed latency | 138.3 ms |
| Baseline | 106 ms · 2.23× |
| Increase | +123% |
| Severity | warning |
Who is affected
Countries where Gulf2Africa (G2A) 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 |
|---|---|---|---|
| Oman resilience index: 100 · resilient |
1 of 20 cables (5% of submarine diversity) | 2Africa, Asia Africa Europe-1 (AAE-1), Bay of Bengal Gateway (BBG) +16 more | no measurement today; median 109 ms over 30 days (44 routes) |
| Somalia resilience index: 69 · moderate |
1 of 6 cables (17% of submarine diversity) | 2Africa, Africa-1, Djibouti Africa Regional Express 1 (DARE 1) +2 more | median 21 ms today vs 28 ms over 30 days (7 routes) - faster |
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 changed route while latency was elevated. A reroute of this kind usually follows a fault somewhere on the original path.
Cross-probe verdict. Too few independent vantage points were watching this endpoint to reach a cross-probe verdict.
Timeline
- Alert 2026070401: warning - ratio 2.23x
- Alert #143 resolved: RTT 138.32ms (baseline 106ms), 8 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.