Batam-Rengit Cable System (BRCS): latency up to 4.3× normal, 18 Nov 2026
What we measured
| Cable | Batam-Rengit Cable System (BRCS) |
| Segment | Rengit, MY → Tanjung Pinggir, ID |
| Detected | 2026-11-18 04:33 UTC |
| Resolved | 2026-11-19 22:35 UTC |
| Duration | 1d 18h |
| Observed latency | 70.1 ms |
| Baseline | 100.2 ms · 4.29× |
| Increase | +329% |
| Severity | warning |
Who is affected
Countries where Batam-Rengit Cable System (BRCS) 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 74 cables (1% of submarine diversity) | Apricot, APX West, Asia Connect Cable-1 (ACC-1) +70 more | median 219 ms today vs 215 ms over 30 days (4858 routes) - unchanged |
| Malaysia resilience index: 100 · resilient |
1 of 34 cables (3% of submarine diversity) | APCN-2, Asia Africa Europe-1 (AAE-1), Asia Link Cable (ALC) +30 more | median 171 ms today vs 181 ms over 30 days (304 routes) - unchanged |
Dependence is structural (share of the country's submarine cables), not a traffic share: real traffic distribution across cables is not public.
Vessels nearby at the time of the incident
- RAWABI RANGER (tug or special): slow drift over the route, 0.7 km from the route, 25.5 h before the start
- MERANTI DAYA 88 (tanker): slow drift over the route, 0.8 km from the route, 42.7 h before the start
- ENA HABITAT (other): anchorage, 3.4 km from the route, 27.2 h before the start
- ENA SAMURAI (tug or special): anchorage, 3.4 km from the route, 12.5 h before the start
- ODETTE (tug or special): moored, 3.7 km from the route, 12.4 h before the start
Vessels near a cable route are seen before incidents about as often as on ordinary days: 61% against 57% over 79 incidents since 6 Aug 2026. How this is counted
Alert check
Not confirmed. We asked other measurement points, and they did not see the trouble. The alert stays on record but is not counted as an incident. what this means
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. Other measurements did not confirm the event, so we do not count it as a cable fault.
Timeline
- Alert 2026111801: critical - ratio 4.29x
- Alert #250 improving: 1/3 consecutive OK
- Alert #250 improving: 2/3 consecutive OK
- Alert #250 improving: 1/3 consecutive OK
- Alert #250 improving: 2/3 consecutive OK
- Alert #250 improving: 1/3 consecutive OK
- Alert #250 improving: 1/3 consecutive OK
- Alert #250 improving: 2/3 consecutive OK
- Alert #250 resolved: RTT 70.13ms (baseline 100.18ms), 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.