Kuwait-Iran cable: latency up to 4.5× normal, 14 Jul 2026
What we measured
| Cable | Kuwait-Iran |
| Segment | Ganaveh, IR → Kuwait City, KW |
| Detected | 2026-07-14 19:33 UTC |
| Resolved | 2026-07-15 00:09 UTC |
| Duration | 4h 35m |
| Observed latency | 145 ms |
| Baseline | 193.3 ms · 4.54× |
| Increase | +354% |
| Severity | critical |
Who is affected
Countries where Kuwait-Iran 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 |
|---|---|---|---|
| Iran resilience index: 88 · resilient |
1 of 6 cables (17% of submarine diversity) | FALCON, Gulf Bridge International Cable System/Middle East North Africa Cable System (GBICS/MENA), OMRAN/EPEG +2 more | average 50 ms over the last day vs 127 ms over 30 days - faster |
| Kuwait resilience index: 56 · moderate |
1 of 6 cables (17% of submarine diversity) | 2Africa, FALCON, Fiber Optic Gulf (FOG) +2 more | no measurement today; median 71 ms over 30 days (32 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 2026071402: critical - ratio 4.54x
- Alert #150 resolved: RTT 144.96ms (baseline 193.29ms), 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.