Qatar-U.A.E. Submarine Cable System: latency up to 2.2× normal, 5 Nov 2026
What we measured
| Cable | Qatar-U.A.E. Submarine Cable System |
| Segment | Abu Dhabi, AE → Doha, QA |
| Detected | 2026-11-05 01:31 UTC |
| Resolved | 2026-11-05 04:33 UTC |
| Duration | 3h 2m |
| Observed latency | 106.1 ms |
| Baseline | 105.7 ms · 2.18× |
| Increase | +118% |
| Severity | warning |
Who is affected
Countries where Qatar-U.A.E. Submarine Cable System 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 |
|---|---|---|---|
| Qatar resilience index: 83 · resilient |
1 of 9 cables (11% of submarine diversity) | 2Africa, Asia Africa Europe-1 (AAE-1), FALCON +5 more | median 164 ms today vs 170 ms over 30 days (114 routes) - unchanged |
| United Arab Emirates resilience index: 100 · resilient |
1 of 22 cables (5% of submarine diversity) | 2Africa, Africa-1, Asia Africa Europe-1 (AAE-1) +18 more | median 170 ms today vs 125 ms over 30 days (1202 routes) - slower |
Dependence is structural (share of the country's submarine cables), not a traffic share: real traffic distribution across cables is not public.
Vessels nearby at the time of the incident
- HADI: slow drift over the route, 2.0 km from the route, 24.5 h before the start
Vessels near a cable route are seen before incidents about as often as on ordinary days: 61% against 57% over 79 incidents since 6 Aug 2026. How this is counted
Alert check
Not confirmed. We asked other measurement points, and they did not see the trouble. The alert stays on record but is not counted as an incident. what this means
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. Our own cross-check concluded this was an operator reroute, not a cable fault. We publish it anyway, labelled as such.
Timeline
- Alert 2026110501: warning - ratio 2.18x
- Alert #245 improving: 2/3 consecutive OK
- Alert #245 resolved: RTT 106.05ms (baseline 105.68ms), 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.