Accueil Câbles Emplacements Santé Recherches Guide
AccueilCâbles sous-marins › Batam-Rengit Cable System (BRCS)

Batam-Rengit Cable System (BRCS)

En service

64 km · 2 Points d'atterrissage · 2 Pays · Mise en service: 2007

Ctrl + Scroll to zoom

Spécifications

Longueur64 km
StatutEn service
Mise en service2007
Points d'atterrissage2
Pays2

Propriétaires

XLSmart

Points d'atterrissage (2)

Emplacement Pays Position
Rengit, Malaysia MY Malaysia 1.6771°, 103.1477°
Tanjung Pinggir, Indonesia ID Indonesia 1.0668°, 104.0166°

📡 Performance en direct

1,065
mesures
9
sondes
52
jours surveillés
228.0
ms RTT moy.
0
anomalies

Mesuré du 2026-03-07 au 2026-04-28 — RTT ICMP via les sondes RIPE Atlas. Recalculé quotidiennement à partir des données brutes. ✓ Aucune anomalie détectée sur la période.

Sources de mesure

Sonde Emplacement Mesures Moy. Min–Max Dernière
#64821 RIPE Atlas 169 280.7 ms 50.4–359.8 2026-04-28
#1014589 sonde propre Almaty KZ 146 253.7 ms 249.0–279.6 2026-04-28
#1014597 sonde propre Tbilisi GE 145 219.9 ms 216.0–315.0 2026-04-28
#1014969 sonde propre Jerusalem IL 145 230.2 ms 221.7–330.0 2026-04-28
#1015523 sonde propre Moscow RU 142 207.7 ms 205.9–210.7 2026-04-28
#1014473 sonde propre Minsk BY 140 207.1 ms 206.3–213.2 2026-04-28
#1015313 sonde propre Sevastopol UA 128 229.9 ms 227.2–252.6 2026-04-28
#1033 RIPE Atlas 49 103.3 ms 69.8–211.4 2026-04-15
#4429 RIPE Atlas 1 120.8 ms 120.8–120.8 2026-03-14

À propos du Batam-Rengit Cable System (BRCS) câble

Based on 1,023 RIPE Atlas 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 RIPE Atlas 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.

📡 Santé

Statut✓ Normal
Vérifié le2026-05-01 08:31

Surveillance via les sondes RIPE Atlas. Ouvrir le monitoring →

📊 Historique RTT

Route: #64821 → Tanjung Pinggir Mesuré: 2026-04-28 07:01
268.8 ms
Min Moy Max #
7 jours 264.3 296.6 359.8 135
30 jours 50.4 280.7 359.8 169
60 jours 50.4 280.7 359.8 169

Chronologie

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
Tanjung Pinggir
RTT Spike
163ms → 327ms (2.01×)
07:01
🔴
Tanjung Pinggir
Anomaly Confirmed
156ms → 333ms (2.14×)
06:00
Tanjung Pinggir
RTT Spike
156ms → 333ms (2.14×)
06:00
🔴
Tanjung Pinggir
Anomaly Confirmed
149ms → 311ms (2.08×)
05:30
Tanjung Pinggir
RTT Spike
149ms → 311ms (2.08×)
05:30
🔴
Tanjung Pinggir
Anomaly Confirmed
142ms → 308ms (2.17×)
05:01
Tanjung Pinggir
RTT Spike
142ms → 308ms (2.17×)
05:01
Tanjung Pinggir
RTT Spike
134ms → 319ms (2.39×)
04:31
🔴
Tanjung Pinggir
Anomaly Confirmed
134ms → 319ms (2.39×)
04:31
🔴
Tanjung Pinggir
Anomaly Confirmed
125ms → 306ms (2.45×)
04:31
Tanjung Pinggir
RTT Spike
125ms → 306ms (2.45×)
04:31
🔴
Tanjung Pinggir
Anomaly Confirmed
117ms → 267ms (2.27×)
04:00
Tanjung Pinggir
RTT Spike
117ms → 267ms (2.27×)
04:00
Tanjung Pinggir
RTT Spike
100ms → 265ms (2.65×)
03:01
🔴
Tanjung Pinggir
Anomaly Confirmed
100ms → 265ms (2.65×)
03:01
🚨
Tanjung Pinggir
Alert Created
100ms → 265ms (2.65×)
03:01
Tanjung Pinggir
RTT Spike
109ms → 264ms (2.42×)
03:01
🔴
Tanjung Pinggir
Anomaly Confirmed
109ms → 264ms (2.42×)
03:01
Tanjung Pinggir
RTT Spike
90ms → 265ms (2.96×)
02:31
Fri, Apr 17
View full event log →
🔗
Hop Anomaly
7ms → 68ms (10.12×)
05:00

FAQ

Quelle est la longueur du câble Batam-Rengit Cable System (BRCS) ?
Le câble Batam-Rengit Cable System (BRCS) mesure 64 km.
Quels pays le câble Batam-Rengit Cable System (BRCS) relie-t-il ?
Batam-Rengit Cable System (BRCS) connects 2 countries via 2 landing points.
Qui possède le câble Batam-Rengit Cable System (BRCS) ?
Le câble Batam-Rengit Cable System (BRCS) appartient à un consortium comprenant XLSmart.
Quand le câble Batam-Rengit Cable System (BRCS) a-t-il été mis en service ?
Le câble Batam-Rengit Cable System (BRCS) a été mis en service en 2007.
Batam-Rengit Cable System (BRCS)
  • Longueur64 km
  • StatutEn service
  • Mise en service2007

Calculer la distance

Trouvez la distance réelle par câble entre deux villes

Ouvrir le calculateur →
🌊 Submarine cables 🛤 Land fiber 📡 RIPE Atlas

🌐 Log In

Access your routes, favorites, and API key

Create account Forgot password?