OMRAN/EPEG: 1.24× baseline latency
What we measured
| Cable | OMRAN/EPEG |
| Segment | Khasab, OM → Chabahar, IR |
| Detected | 2026-06-03 15:02 UTC |
| Resolved | 2026-06-03 17:31 UTC |
| Duration | 2h 29m |
| Observed latency | 142.5 ms |
| Baseline | 114.9 ms · 1.24× |
| Increase | +429% |
| Severity | critical |
Who is affected
Countries where OMRAN/EPEG 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), Kuwait-Iran +2 more | average 80 ms over the last day vs 137 ms over 30 days - faster |
| 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 144 ms today vs 182 ms over 30 days (10 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 2026060301: critical - ratio 5.29x
- Alert #131 improving: 1/3 consecutive OK
- Alert #131 improving: 1/3 consecutive OK
- Alert #131 improving: 2/3 consecutive OK
- Alert #131 resolved: RTT 142.54ms (baseline 114.86ms), 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.