Batam Dumai Melaka (BDM): 1.91× baseline latency
What we measured
| Cable | Batam Dumai Melaka (BDM) |
| Segment | Melaka, MY → Batam, ID |
| Detected | 2026-04-23 17:01 UTC |
| Resolved | 2026-04-23 18:32 UTC |
| Duration | 1h 30m |
| Observed latency | 314.2 ms |
| Baseline | 164.6 ms · 1.91× |
| Increase | +106% |
| 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 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 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. Only one probe saw it. We treat this as a probable false positive and label it as such.
Timeline
- Alert 2026042301: warning - ratio 2.06x
- Alert #91 improving: 1/3 consecutive OK
- Alert #91 resolved: RTT 314.23ms (baseline 164.59ms), 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.