Incident report · 2026043003
SEAX-1: 0.39× baseline latency
Resolved · 1h 29m
What we measured
| Cable | SEAX-1 |
| Segment | Batam, ID → Mersing, MY |
| Detected | 2026-04-30 19:01 UTC |
| Resolved | 2026-04-30 20:30 UTC |
| Duration | 1h 29m |
| Observed latency | 17.6 ms |
| Baseline | 45.5 ms · 0.39× |
| Increase | +132% |
| Severity | warning |
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 2026043003: warning — ratio 2.31x
- Alert #101 improving: 1/3 consecutive OK
- Alert #101 resolved: RTT 17.62ms (baseline 45.51ms), 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.
How to cite
GeoCables (2026). Incident 2026043003: SEAX-1. https://geocables.com/incident/2026043003
Embed this map
<iframe src="https://geocables.com/embed.php?type=map&id=seax-1" width="640" height="420" frameborder="0" loading="lazy" style="border:0;border-radius:10px"></iframe>