Home
Explore What GeoCables can do Cables Locations Map My path ISP status Country resilience Check my connection Blocked websites
Live Network radar Live Map Cable monitoring Events log Cable incidents Big screen
Learn Test yourself Research Guide Methodology Latency Overland links Deployments by year Earthquakes Open dataset API Widgets What's new About Contact
Incident report · 2026111801

Batam-Rengit Cable System (BRCS): latency up to 4.3× normal, 18 Nov 2026

Resolved · 1d 18h
XTelegramWhatsAppFacebook

What we measured

CableBatam-Rengit Cable System (BRCS)
SegmentRengit, MY → Tanjung Pinggir, ID
Detected2026-11-18 04:33 UTC
Resolved2026-11-19 22:35 UTC
Duration1d 18h
Observed latency70.1 ms
Baseline100.2 ms · 4.29×
Increase+329%
Severitywarning

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.

CountryDependence on this cableOther submarine cablesWhat 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

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

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 2026111801: Batam-Rengit Cable System (BRCS). https://geocables.com/incident/2026111801

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>

← All cable events

Advertisement

Log In

Access your routes, favorites, and API key

Create account Forgot password?