Incident report · 2026042402
Batam-Rengit Cable System (BRCS): 2.68× baseline latency
Resolved · 4d 4h
What we measured
| Cable | Batam-Rengit Cable System (BRCS) |
| Segment | Rengit, MY → Tanjung Pinggir, ID |
| Detected | 2026-04-24 03:01 UTC |
| Resolved | 2026-04-28 07:26 UTC |
| Duration | 4d 4h |
| Observed latency | 268.8 ms |
| Baseline | 100.1 ms · 2.68× |
| Increase | +165% |
| 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. Only one probe saw it. We treat this as a probable false positive and label it as such.
Timeline
- Alert 2026042402: warning — ratio 2.65x
- Alert #93 improving: 1/3 consecutive OK
- Alert #93 force-resolved as false_positive: target_ip mismatch (Bandung anchor used instead of correct Singapore anchor for Tanjung Pinggir LPT)
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 2026042402: Batam-Rengit Cable System (BRCS). https://geocables.com/incident/2026042402
Embed this map
<iframe src="https://geocables.com/embed.php?type=map&id=batam-rengit-cable-system-brcs" width="640" height="420" frameborder="0" loading="lazy" style="border:0;border-radius:10px"></iframe>