Incident report · 2026091601
Batam Dumai Melaka (BDM): 0.42× baseline latency
Resolved · 1h 59m
What we measured
| Cable | Batam Dumai Melaka (BDM) |
| Segment | Batam, ID → Melaka, MY |
| Detected | 2026-09-16 12:32 UTC |
| Resolved | 2026-09-16 14:32 UTC |
| Duration | 1h 59m |
| Observed latency | 13.6 ms |
| Baseline | 32.2 ms · 0.42× |
| Increase | +189% |
| Severity | warning |
Who is affected
Countries where Batam Dumai Melaka (BDM) comes ashore, how much of their submarine diversity this cable represents, and what our probes currently measure into them.
| Country | Dependence on this cable | Other submarine cables | Our probes see |
|---|---|---|---|
| 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 239 ms today vs 252 ms over 30 days (6 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 220 ms today vs 237 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. Terrestrial links are not measured.
Timeline
- Alert 2026091601: warning — ratio 2.89x
- Alert #202 improving: 1/3 consecutive OK
- Alert #202 improving: 2/3 consecutive OK
- Alert #202 resolved: RTT 13.55ms (baseline 32.16ms), 4 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 2026091601: Batam Dumai Melaka (BDM). https://geocables.com/incident/2026091601
Embed this map
<iframe src="https://geocables.com/embed.php?type=map&id=batam-dumai-melaka-bdm" width="640" height="420" frameborder="0" loading="lazy" style="border:0;border-radius:10px"></iframe>