The cable is underwater. The response starts above it.

What happened

On 14 January 2025, NATO launched Baltic Sentry to strengthen protection of critical undersea infrastructure, using ships and maritime patrol aircraft. The EU followed with its Cable Security Action Plan on 21 February 2025, covering prevention, detection, response, recovery and deterrence.

The offshore incident has two working timelines

An infrastructure operator needs to establish the service impact and organise restoration. An investigating authority needs to preserve observations and examine possible causes. The same inspection finding can matter to both, but their next decisions are different. A repair plan does not settle responsibility for the damage, and an investigative hypothesis does not tell the operator when a connection will be usable again. This distinction should remain visible in an operational picture.

Consider an illustrative fault report followed by a vessel observation and later a repair inspection. Each record has a time of occurrence, a time of reporting and an organisation able to verify it. Their sequence can change as more precise information arrives. A shared timeline should let participants inspect those changes. It should not move an observation into a narrow fault window just to make a suggested connection fit.

A cable alarm is not an attribution

A service interruption can establish that a link has failed. A vessel track can establish where a reported position was recorded. Neither fact alone proves who damaged the cable or why. Operators restore service; investigators establish cause and responsibility. Those tasks need shared evidence, with different permissions.

The handover that matters

In an illustrative incident, the operator reports a fault time window. The maritime authority compares it with available tracks. A repair team records the damage location and findings. If those reports remain in separate conversations, every handover starts with the same questions: which cable, what time, what has actually been confirmed?

• Place and time. Keep cable segments, the fault window and approved vessel observations together, with source and timestamp.
• Verification. Separate automated detections, eyewitness reports and confirmed inspection results. Missing AIS data does not prove hostile activity.
• Response. Record who is checking the report, who owns restoration and which authority can take a decision.
• Evidence. Preserve original reports and corrections. Sharing an operational view must not erase the provenance needed for an investigation.

With one shared picture

Meridian’s proposed role is to organise the authorised reports, locations and decisions around one incident. It does not detect a seabed fault by itself, establish intent or authorise a boarding. Any cable-sensor interface would need operator agreement, engineering and acceptance testing.

Read a vessel track with its limits attached

A map makes nearby movements easy to notice. It can also make proximity appear more meaningful than the evidence supports. A vessel-position feed records reported positions at particular times; gaps, delays and changes of identifier need investigation before they become conclusions. The cable’s mapped route may also have a different level of precision from the location later established by inspection. Keeping those qualities visible matters when comparing the records.

An analyst might mark a relationship for review, identify the source needed to check it and assign that question to the competent partner. The answer should return with its source and limits. If it contradicts the initial interpretation, that correction belongs in the history. Local AI could help summarise authorised reports, but decisions about cause, intent and legal action remain with the responsible authorities. An automatic association should never be presented as a finding simply because the software drew a line between two objects.

Make restoration and evidence handovers inspectable

A focused Meridian pilot could follow one approved example from fault notification through inspection report to a handover. Operator and authority would define the shared cable segment, permitted observations and the information each participant needs for the next task. A test could introduce a late timestamp correction or an incomplete position feed. Reviewers would check whether confirmed findings remain distinct from open questions and whether the responsible source can still be retrieved.

The deployment would need agreed access enforcement, audit and retention, while original evidence remains with the organisation responsible for it. European control is relevant because a common view can contain commercially sensitive routes and investigative material. Processing locations, maintenance access and permitted exports must be agreed rather than implied by the map. The practical objective is a reliable exchange between people doing different jobs, with enough context to act and enough provenance to reconsider a conclusion later.

A shared picture should make a response faster to organise, not make an uncertain attribution look certain.