Incident report · 2026033002
SEAX-1: 0.88× baseline latency
Resolved · 4h 30m
What we measured
| Cable | SEAX-1 |
| Segment | Mersing, MY → Batam, ID |
| Detected | 2026-03-30 05:02 UTC |
| Resolved | 2026-03-30 09:33 UTC |
| Duration | 4h 30m |
| Observed latency | 69.3 ms |
| Baseline | 79 ms · 0.88× |
| Increase | +345% |
| Severity | warning |
Path analysis
No usable traceroute data for this window.
Cross-probe verdict. Too few independent vantage points were watching this endpoint to reach a cross-probe verdict.
Timeline
- Alert #30: warning — Batam
- Alert #30 resolved: Batam
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 2026033002: SEAX-1. https://geocables.com/incident/2026033002
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>