East-West Submarine Cable System: latency up to 13.1× normal, 28 Apr 2026
What we measured
| Cable | East-West Submarine Cable System |
| Segment | Mersing, MY → Penarik, ID |
| Detected | 2026-04-28 15:00 UTC |
| Resolved | 2026-05-10 17:30 UTC |
| Duration | 12d 2h |
| Observed latency | 585.4 ms |
| Baseline | 34.7 ms · 13.12× |
| Increase | +100% |
| Severity | critical |
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 230 ms today vs 203 ms over 30 days (1061 routes) - unchanged |
| Malaysia resilience index: 100 · resilient |
1 of 34 cables (3% of submarine diversity) | APCN-2, Asia Africa Europe-1 (AAE-1), Asia Link Cable (ALC) +30 more | median 217 ms today vs 180 ms over 30 days (47 routes) - slower |
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. Other measurements did not confirm the event. We treat this as a probable false positive and label it as such.
Timeline
- Alert 2026042802: critical - ratio 13.12x
- Alert #97 improving: 1/3 consecutive OK
- Alert #97 improving: 1/3 consecutive OK
- Alert #97 improving: 1/3 consecutive OK
- Alert #97 improving: 1/3 consecutive OK
- Alert #97 improving: 1/3 consecutive OK
- Alert #97 improving: 1/3 consecutive OK
- Alert #97 improving: 1/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.