Undersea cables and the Baltic: when a sanctions story became a security one

Why the Baltic

The Baltic is shallow, narrow, busy and full of infrastructure. Power interconnectors, data cables and pipelines cross it in every direction, mostly lying on or just under the seabed in water that a large ship’s anchor can easily reach.

It is also the loading region for a large share of the Russian crude and product exports that move on the tonnage this site tracks. Those two facts put an ageing, opaquely owned fleet in daily proximity to critical infrastructure, in a sea where nine coastal states have both strong interests and limited jurisdiction over passing traffic.

The mechanism, which is mundane

An anchor that is not properly secured, or that is deliberately let go, can drag along the bottom for a long distance. If it crosses a cable, it can part it. Repairs require a specialist vessel, take weeks, and cost sums that are large even by the standards of energy infrastructure.

Nothing about this requires sophistication. That is precisely what makes it difficult: the same physical event is consistent with negligence, with a poorly maintained ship losing control of ground tackle, and with deliberate damage. From the seabed, the three look identical.

The attribution problem

This is where the legal difficulty starts, and where reporting most often gets ahead of the evidence.

Establishing that a particular vessel caused particular damage is usually possible, from track data, anchor marks and damage to the ship. Establishing intent is a different matter, and states have been notably careful in their public language for that reason. Damage is a fact; sabotage is a conclusion.

Jurisdiction compounds it. Outside the territorial sea, a coastal state’s powers over a foreign ship are limited, and the general rule that a ship is subject to its flag state applies. That is why cases have turned on details: where exactly the vessel was, whether it later entered a state’s waters, and whether its flag state cooperated.

Why it changed the conversation about tankers

Before the cable incidents, the argument for acting against the shadow fleet was made in sanctions terms, and that argument divides states. Countries that do not support the underlying sanctions policy have no reason to help enforce it.

Infrastructure damage and pollution risk are different. A coastal state does not need to hold a view on oil price caps to object to a poorly maintained ship with unverifiable insurance transiting its waters near a power interconnector. That reframing gave Baltic and North Sea states grounds to act that stand on their own: verifying flag and insurance, inspecting in port, escorting vessels through sensitive stretches.

It is the same shift the IMO made when it framed the dark fleet as a matter of fraudulent registration and safety rather than of sanctions policy. Broader agreement is available on safety than on foreign policy, and states have noticed.

What the insurance question does here

A cable repair bill is exactly the kind of third-party liability that protection and indemnity cover exists to meet.

A vessel with cover from an International Group club has an insurer that can pay, and an incentive to settle. A vessel whose cover comes from an insurer nobody can verify presents the infrastructure owner with a claim against a single-ship company whose only asset is a twenty-year-old tanker. The practical result is that the cost lands on the grid operator and its customers.

That is why demands to see evidence of insurance have become a standard part of the flag-check approach described in stateless vessels, and it is the strongest non-sanctions argument for scrutinising this fleet.

What this site does with incidents

Incidents are part of the data model, with kinds covering seizure, boarding, detention, casualty and others, each requiring a date and a source before it appears on a page.

They are populated conservatively. An incident enters a vessel’s record when a primary document or a major outlet reports it with a date and identifies the hull, and the record states what the source said rather than characterising it. For an event whose interpretation is contested between governments, restating the source and linking it is the only defensible thing a public dataset can do.