Home
Explore Cables Locations Map ISP status Transit map Country resilience Check my connection
Live Network radar Live Map Cable monitoring Events log Cable incidents Big screen
Learn Research Guide Methodology Latency Overland links Deployments by year Pulse Open dataset API Widgets What's new About Contact

Batam-Rengit Cable System (BRCS)

In Service

64 km · 2 Landing Points · 2 Countries · Ready for Service: 2007

Ctrl + Scroll to zoom
Tap to interact with map

Specifications

Length64 km
StatusIn Service
Ready for Service2007
Landing Points2
Countries2

Owners

XLSmart

Landing Points (2)

Location Country Position
Rengit, Malaysia MY Malaysia 1.6771°, 103.1477°
Tanjung Pinggir, Indonesia ID Indonesia 1.0668°, 104.0166°

If this cable is cut

What each country and landing point keeps if Batam-Rengit Cable System (BRCS) goes down. A calculation from our cable and landing-point database, not a forecast.

CountryOther international cablesLand linksWhat remains
Malaysia29 yes reserve of 29 cables
Indonesia29 yes reserve of 29 cables

Landing points with no other cable nearby

  • Rengit, Malaysia: no other cable lands within 50 km.

On an island this means losing the submarine link; on the mainland traffic can still go over land.

Our alerts on this cable in the last 180 days: 1, last on 24 Apr 2026. Events feed →

Counted: other international cables landing in the same country (domestic cables between points of one country are not a way out), other cables at landing points within 50 km, and whether the country has land links. Not counted: cable capacity, operator contracts and satellite. Use as a first look at dependence, not as a statement of what would happen.

Live Performance

1,214
measurements
9
probes
224
days monitored
217.6
ms avg RTT
1
anomalies

Monitored from 2026-03-07 through 2026-10-18 - live ICMP round-trip time measurements via our monitoring probes. All values below are recomputed daily from raw probe data.

Measurement sources

Probe Location Samples Avg Min-Max Last seen
#64821 control probe 250 242.1 ms 2.9-359.8 2026-10-18
own probe Minsk BY 146 210.5 ms 206.3-306.8 2026-04-28
own probe Almaty KZ 146 253.7 ms 249.0-279.6 2026-04-28
own probe Tbilisi GE 145 219.9 ms 216.0-315.0 2026-04-28
own probe Jerusalem IL 145 230.2 ms 221.7-330.0 2026-04-28
own probe Sevastopol UA 144 234.5 ms 227.2-305.2 2026-04-28
own probe Moscow RU 142 207.7 ms 205.9-210.7 2026-04-28
#1033 control probe 95 76.5 ms 4.2-292.6 2026-05-17
#4429 control probe 1 120.8 ms 120.8-120.8 2026-03-14

About the Batam-Rengit Cable System (BRCS) Cable System

Based on 1,023 measurements from GeoCables monitoring infrastructure, March-April 2026.

The Batam-Rengit Cable System - BRCS - is a sixty-four-kilometre submarine link between two points that face each other across a narrow stretch of the Singapore Strait. The Indonesian landing sits at Tanjung Pinggir, on the northern coast of Batam Island, the largest island in the Riau Archipelago. The Malaysian landing is at Rengit, a small coastal village in the southern Johor district of Batu Pahat, fifteen kilometres south of Singapore's land border with Malaysia. The cable was placed in service in 2007, has been operational for nineteen years, and is owned by XLSmart - an Indonesian operator formed in 2025 by the merger of XL Axiata and Smartfren. By any meaningful submarine standard, sixty-four kilometres is a short cable. The Atlantic crossings are 6,000 km. The Pacific crossings exceed 13,000. BRCS is the cable equivalent of a footbridge between two municipalities of the same metropolitan region.

A footbridge that, judging by our measurements, almost no traffic uses.

Light in optical fibre travels at roughly two hundred thousand kilometres per second - about two-thirds of vacuum c. A round-trip across sixty-four kilometres of glass should resolve in 0.63 ms. That number is the physics floor for BRCS: the smallest possible round-trip, the value below which no measurement on this cable can fall without violating relativity. We do not measure 0.63 ms. We measure 50.40 ms. The minimum round-trip we have observed in 169 measurements between Rengit and Tanjung Pinggir, sent in the standard direction MY → ID, is exactly that: fifty milliseconds and forty microseconds. That is eighty times the physics floor. For a cable this short, an 80× multiplier is not measurement noise. It is a routing decision rendered as a measurement.

Forward and reverse take different oceans

The story sharpens when both directions are inspected. Across 169 measurements from Rengit (MY) to Tanjung Pinggir (ID), the average round-trip is 278.75 ms. Across 20 measurements in the opposite direction - Tanjung Pinggir to Rengit - the average is 112.97 ms. Both directions involve the same physical pair of endpoints. Both should produce the same measurement on a 0.63 ms-floor cable. The forward path takes 2.5× as long as the reverse, and both are far above the floor. The symmetry gap between them is roughly 198 ms.

This kind of asymmetry is not a property of the cable. Submarine cables themselves do not introduce direction-dependent latency at this scale; light travels at the same speed in both directions of a fibre pair, and the wet plant - repeaters, branching units, terminal equipment - is symmetric by design. The asymmetry is introduced in BGP. Each side of the connection has independent control over how its outbound traffic is routed, and that routing is governed by transit costs, peering agreements, and AS-path length. The existence of a particular submarine cable underneath the route is not a parameter the BGP decision algorithm sees.

What our measurements describe is not BRCS's link characteristics. They describe the routing system around BRCS, observed through the cable's terminal IPs. The MY-side operator's outbound preference takes traffic out to a regional carrier hub - most plausibly Singapore, which sits within twenty kilometres of both landing points and hosts every major Asia-Pacific carrier exchange - before that traffic returns south to Batam Island. The ID-side operator's outbound preference takes a shorter detour, but still not the cable directly. The cable is in the water, electrically powered, optically transmitting. It is also, by the routing layer's reckoning, irrelevant.

Why a sixty-four-kilometre cable exists in the first place

If neither side is using BRCS for direct ID-MY exchange, why does the cable exist? The answer is the same answer as for most short submarine cables in the region: it is cheaper than the alternative, for some specific kinds of traffic, even if it is not the chosen path for general internet exchange. BRCS provides a bilateral backstop. It allows XLSmart's Indonesian customers to reach Malaysian destinations without paying transit through Singapore IXPs for a subset of traffic - typically operator-internal flows, capacity reservations, or specific content-delivery agreements where the two carriers have negotiated bilateral terms.

The general internet, however, follows the BGP path. And that path goes through Singapore.

Where the variance lives

Long-distance probes targeting Tanjung Pinggir from Moscow, Minsk, Tbilisi, Jerusalem, Sevastopol, and Almaty produce strikingly consistent round-trips. The 138 measurements from Minsk show a standard deviation of 0.81 ms across an average of 207 ms. The 140 measurements from Moscow show a standard deviation of 0.84 ms across an average of 207.68 ms. These are international paths, ten thousand kilometres long, transiting four or five separate cable systems and as many peering points, and yet they are stable to within a millisecond. The 169 measurements over the local pair - sixty-four kilometres - have a standard deviation of 68.16 ms.

The cable that should be the cleanest measurement on the system is the noisiest one. International long-haul routes have been ironed flat by twenty years of peering negotiations between major Tier-1 carriers; domestic and bilateral edges between two adjacent national operators carry the residual jitter of inter-carrier policy, traffic engineering experiments, and the soft economics of capacity provisioning. We have measured the same shape on JaKa2LaDeMa (B2JS), the longer Indonesian domestic ring that terminates a few hundred kilometres from BRCS. Its local pair shows the same elevated variance and the same routing-driven floor multiplier.

What 80× looks like next to other cables

For most cables in our monitoring set, the observed minimum round-trip lands somewhere between 1× and 5× the physics floor. Gondwana-1 between New Caledonia and Sydney measures at 1.081× - essentially at the floor - because it is the only cable carrying that traffic, with no realistic alternative path; routing has nowhere else to go. ARCOS-1 in the Caribbean measures at 0.613× - below the floor - because traffic chords across the Caribbean basin via Florida hubs instead of looping around the cable's full ring path.

BRCS at 80× sits at the opposite end of this spectrum. The cable exists. The cable is operational. The cable is owned by an operator with a substantial subscriber base on at least one of its sides. The routing layer surrounding the cable does not use it. Three out of every four packets travelling from Rengit to Tanjung Pinggir spend their time in carrier networks that are neither Indonesian nor Malaysian - Singapore being the most likely waypoint. The cable is sixty-four kilometres. The route is not.

The 80× floor multiplier on BRCS is, in the end, a quantitative summary of the gap between owning a cable and being routed across it. The first is a capital expense decision. The second is a routing-policy decision. The two do not always agree, and when they do not, the cable shows up in our measurements as a fast direct link that almost nobody travels.

What next: Explore Batam-Rengit Cable System (BRCS) on the interactive submarine cable map, browse the full catalog of submarine cables, or follow live network events and real-world internet latency.

Health

Status✓ Normal
RTT99.03 ms / base 95.73 ms
Last checked2026-10-18 02:33

Monitored by our probe network. Open monitoring →

RTT History

Route: #64821 → Tanjung Pinggir Measured: 2026-10-18 02:33
99 ms
Min Avg Max #
7 days 93.7 95.6 99.0 6
30 days 93.7 96.8 101.1 22
60 days 2.9 242.1 359.8 250

Health Timeline

Sat, Oct 3
View full event log →
Hop Anomaly
8ms → 352ms (45.82×)
09:30
Mon, Sep 7
View full event log →
Hop Anomaly
6ms → 946ms (163.28×)
17:30
Thu, Sep 3
View full event log →
Hop Anomaly
6ms → 18ms (3.03×)
15:31
Fri, Aug 7
View full event log →
Hop Anomaly
7ms → 57ms (8.53×)
10:30
Sat, Jun 27
View full event log →
Hop Anomaly
7ms → 38ms (5.83×)
22:30
Tue, Jun 23
View full event log →
Hop Anomaly
4ms → 1732ms (390.11×)
04:00
Sun, Jun 21
View full event log →
Hop Anomaly
15ms → 649ms (44.03×)
20:30
Fri, Jun 19
View full event log →
Hop Anomaly
12ms → 584ms (49.44×)
23:01
Fri, Jun 12
View full event log →
Hop Anomaly
12ms → 107ms (8.58×)
22:30
Hop Anomaly
58ms → 282ms (4.89×)
07:00
Mon, Jun 8
View full event log →
Hop Anomaly
13ms → 73ms (5.73×)
15:01
Fri, Jun 5
View full event log →
Hop Anomaly
10ms → 117ms (11.21×)
01:30
Thu, Jun 4
View full event log →
Hop Anomaly
5ms → 568ms (120.09×)
09:01
Wed, Jun 3
View full event log →
Hop Anomaly
63ms → 250ms (3.99×)
19:01
Hop Anomaly
35ms → 326ms (9.36×)
01:01
Sun, May 17
View full event log →
Tanjung Pinggir
RTT Spike
57ms → 200ms (3.52×)
02:30
Tue, May 12
View full event log →
Hop Anomaly
10ms → 645ms (62.28×)
01:00
Fri, May 8
View full event log →
Hop Anomaly
6ms → 687ms (119.18×)
15:30
Thu, May 7
View full event log →
Hop Anomaly
30ms → 120ms (4.00×)
17:00
Wed, May 6
View full event log →
Hop Anomaly
4ms → 23ms (5.03×)
03:30
Tue, Apr 28
View full event log →
Hop Anomaly
6ms → 34ms (6.08×)
21:00
Hop Anomaly
17ms → 68ms (4.03×)
19:00
Tanjung Pinggir
Resolved
100ms → 269ms
07:26
Mon, Apr 27
View full event log →
Hop Anomaly
14ms → 273ms (20.22×)
15:30
Hop Anomaly
7ms → 188ms (27.57×)
04:30
Sat, Apr 25
View full event log →
Tanjung Pinggir
Improving
100ms → 59ms
16:31
Hop Anomaly
4ms → 24ms (5.96×)
10:30
Hop Anomaly
12ms → 220ms (18.60×)
03:00
Fri, Apr 24
View full event log →
Hop Anomaly
15ms → 207ms (13.86×)
21:30
Hop Anomaly
4ms → 200ms (44.93×)
15:00

FAQ

Who owns and operates the Batam-Rengit Cable System (BRCS)?
The Batam-Rengit Cable System is owned by XLSmart, an Indonesian operator formed in 2025 through the merger of XL Axiata and Smartfren.
When was the BRCS placed into service?
The Batam-Rengit Cable System (BRCS) entered service in 2007, making it operational for nineteen years as of 2026.
What are the key landing points for the BRCS?
The BRCS has two main landing points: one at Tanjung Pinggir on Batam Island in Indonesia and another at Rengit, a village in Johor's southern district of Batu Pahat, Malaysia.
What is the capacity of the BRCS?
The exact fiber pair count for the Batam-Rengit Cable System is not specified, but it supports high-speed data transmission between Indonesia and Malaysia.
How does the BRCS compare to other submarine cables in the region?
While specific comparisons are not detailed, the BRCS serves a critical role in connecting Batam Island with Malaysia, providing essential bandwidth for telecommunications services in the area.
Batam-Rengit Cable System (BRCS)
  • Length64 km
  • StatusIn Service
  • Ready for Service2007

Calculate Cable Distance

Find the actual cable routing distance between any two cities

Open Calculator →
Submarine cables Land fiber Live probes
Explore GeoCables: interactive submarine cable map · all 723 submarine cables · live internet latency map · cable landing points worldwide

Log In

Access your routes, favorites, and API key

Create account Forgot password?