Russia's Connectivity Map: Sparse Routes, Strategic Risks
Highlighted routes, latency, landing points and nearby vessels→
Connectivity Map: Many Cables, Few Routes
Russia is one of the rare cases where a vast territory is paired with relatively modest submarine infrastructure. With 28 landing points, 13 cables, and an isolation index of 20/100, these figures are modest for a country with a coastline stretching from the Baltic to the Bering Strait. For comparison: the United Kingdom, of comparable size, has an order of magnitude more international cable connections.
Geographically, the cables are distributed across three unconnected clusters. The Far East: Polar Express (12,650 km, RFS 2022) is the longest, running along the Arctic coast; the Russia-Japan Cable Network (RJCN, 1,800 km, RFS 2008) and the Hokkaido-Sakhalin Cable System (HSCS, 570 km, RFS 2008) connect Sakhalin to Japan; the Far East Submarine Cable System (1,855 km, RFS 2016) links Nakhodka and Nevelsk. A separate cluster is the Baltic: the Kingisepp-Kaliningrad System (Baltika, 1,115 km, RFS 2021) is the only submarine connection linking Kaliningrad to mainland Russia across the sea. The South: the Georgia-Russia cable (433 km, RFS 2000) crosses the Black Sea, and the short Kerch Strait Cable (46 km, RFS 2014) spans the Kerch Strait.
All three clusters almost entirely lack redundancy: a failure in one region cannot be compensated by another. Within the country, traffic moves via terrestrial routes, which themselves become bottlenecks.
Regulation and Censorship: DNS as the First Line of Defense
Russia has long been building a model of a sovereign internet: the 2019 "Sovereign Runet" law, the TSPU system (technical means to counter threats), and the Roskomnadzor registry. This is a well-known context that requires no special measurements.
GeoCables' own probes capture a specific picture: 21.4% of DNS checks return blocked or altered responses (data as of June 2, 2026). This is a moderate level on our scale but significant: one in five DNS queries encounters interference. This figure is typical for countries with centralized blocklists, where filtering is implemented not through deep packet inspection (DPI) but via DNS poisoning or response redirection-a technically cheaper but easily detectable method.
Important: DNS censorship measures what is visible at the level of name resolution. Circumvention tools (VPN, DoH, Tor) alter this statistic for individual users but do not negate the fact of interference in the infrastructure.
War and Its Impact on the Network Space
GeoCables monitors 14 conflict zones within Russia: Sevastopol, Belgorod, Kursk, Bryansk, Rostov regions, and eight other areas. The maximum alert level on our scale reaches 1.0-the ceiling of our metric. However, there is currently no active alert: the zones are being monitored, but no threshold events for automatic notifications have been recorded in the past 30 days.
Signals from open sources over the past 60 days paint a different picture: a strike on an oil refinery in Moscow, incidents involving the "shadow fleet" in the English Channel, and warning shots fired by a Russian warship near a British yacht in the English Channel. These events do not directly affect cable infrastructure but shape a geopolitical backdrop where the risks of escalation on maritime routes are not abstract. The English Channel is a transit corridor for most transatlantic cables; Russian military presence there near cable routes is a factor that operators can no longer ignore.
RTT anomalies over the past 30 days: 1 event on cables connected to Russia. A single anomaly does not indicate a break but is logged in the monitoring history.
Chokepoints: Three Vulnerable Nodes
Three points of particular risk stand out structurally.
- Kaliningrad. Baltika is the only submarine cable connecting the exclave to the mainland across the Baltic Sea. Terrestrial routes pass through Lithuania and Belarus. Any damage to Baltika turns Kaliningrad into an internet island, dependent on the political will of neighbors for terrestrial transit. The Baltic has been a theater of heightened activity since 2022: cable damages between Finland, Estonia, and Germany have already occurred, with responsibility unestablished.
- Kerch Strait. The Kerch Strait Cable (46 km, RFS 2014) connects Crimea to Russia. It is physically vulnerable: shallow waters, active shipping, and military activity in the region. Legally, it is an internationally disputed territory, adding an additional layer of uncertainty to any repair operations.
- Sakhalin as a Transit Hub. Three cables (RJCN, HSCS, Far East) converge on Sakhalin. The island becomes an aggregator for Far Eastern traffic. Damage at this node affects multiple routes at once-Japan, the Kuril Islands, and mainland Far East.
Neighboring transit countries are critical for two clusters. In the Baltic, Finland, Estonia, and Germany are key, as European internet traffic passes through or near their waters. In the South, Georgia remains a transit point via the Georgia-Russia cable, despite political tensions in relations.
What GeoCables Monitors
All 13 cables with Russian landing points are under constant monitoring. Priority routes based on vulnerability criteria:
- Kingisepp-Kaliningrad System (Baltika) due to the exclave logic and Baltic context;
- Kerch Strait Cable due to its geographic proximity to a conflict zone;
- Polar Express as the newest Arctic route (RFS 2022), testing the new geopolitical dynamics of the North;
- RJCN and HSCS as key gateways for Russia to the global internet via Japan.
DNS monitoring via probes has been ongoing continuously since early June 2026. RTT anomalies on cables are logged within a 30-day window: one anomaly in the past month represents a baseline level for infrastructure of this scale, but each event is analyzed for correlation with conflict signals from the 14 monitored zones.