Tata TGN-Gulf cable: latency up to 2.2× normal, 2 Sep 2026
What we measured
| Cable | Tata TGN-Gulf |
| Segment | Qalhat, OM → Al Khobar, SA |
| Detected | 2026-09-02 15:01 UTC |
| Resolved | 2026-09-02 17:31 UTC |
| Duration | 2h 29m |
| Observed latency | 369.9 ms |
| Baseline | 201.5 ms · 2.17× |
| Increase | +117% |
| Severity | warning |
Who is affected
Countries where Tata TGN-Gulf 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 |
|---|---|---|---|
| Bahrain resilience index: 62 · moderate |
1 of 7 cables (14% of submarine diversity) | 2Africa, FALCON, Fiber Optic Gulf (FOG) +3 more | no measurement today; median 64 ms over 30 days (6 routes) |
| 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 | median 87 ms today vs 115 ms over 30 days (44 routes) - faster |
| Qatar resilience index: 83 · resilient |
1 of 9 cables (11% of submarine diversity) | 2Africa, Asia Africa Europe-1 (AAE-1), FALCON +5 more | median 167 ms today vs 167 ms over 30 days (40 routes) - unchanged |
| Saudi Arabia resilience index: 100 · resilient |
1 of 25 cables (4% of submarine diversity) | 2Africa, Africa-1, Asia Africa Europe-1 (AAE-1) +21 more | median 148 ms today vs 145 ms over 30 days (58 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 119 ms today vs 116 ms over 30 days (222 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. Some probes saw the degradation and others did not, which usually means a partial or regional effect.
Timeline
- Alert 2026090201: warning - ratio 2.17x
- Alert #182 improving: 1/3 consecutive OK
- Alert #182 improving: 1/3 consecutive OK
- Alert #182 improving: 2/3 consecutive OK
- Alert #182 resolved: RTT 369.93ms (baseline 201.48ms), 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.