East-West Submarine Cable System: 0.85× baseline latency
What we measured
| Cable | East-West Submarine Cable System |
| Segment | Mersing, MY → Penarik, ID |
| Detected | 2026-06-12 09:01 UTC |
| Resolved | 2026-06-12 10:31 UTC |
| Duration | 1h 29m |
| Observed latency | 15.8 ms |
| Baseline | 18.5 ms · 0.85× |
| Increase | +169% |
| Severity | warning |
Who is affected
Countries where East-West 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 |
|---|---|---|---|
| Indonesia resilience index: 100 · resilient |
1 of 73 cables (1% of submarine diversity) | Apricot, Asia Connect Cable-1 (ACC-1), Asia United Gateway East (AUG East) +69 more | median 240 ms today vs 232 ms over 30 days (60 routes) - unchanged |
| Malaysia resilience index: 100 · resilient |
1 of 33 cables (3% of submarine diversity) | APCN-2, Asia Africa Europe-1 (AAE-1), Asia Link Cable (ALC) +29 more | median 218 ms today vs 235 ms over 30 days (6 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 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 2026061201: warning - ratio 2.69x
- Alert #134 improving: 1/3 consecutive OK
- Alert #134 resolved: RTT 15.8ms (baseline 18.49ms), 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.