Kuwait-Iran: 0.24× baseline latency
What we measured
| Cable | Kuwait-Iran |
| Segment | Ganaveh, IR → Kuwait City, KW |
| Detected | 2026-07-15 10:31 UTC |
| Resolved | 2026-07-15 17:02 UTC |
| Duration | 6h 30m |
| Observed latency | 117.6 ms |
| Baseline | 499 ms · 0.24× |
| Increase | +125% |
| Severity | warning |
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 80 ms over the last day vs 137 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 | average 167 ms over the last day vs 182 ms over 30 days - 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. Too few independent vantage points were watching this endpoint to reach a cross-probe verdict.
Timeline
- Alert 2026071501: warning - ratio 2.25x
- Alert #151 improving: 1/3 consecutive OK
- Alert #151 improving: 1/3 consecutive OK
- Alert #151 resolved: RTT 117.57ms (baseline 498.97ms), 14 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.