Who owns it when a vessel goes dark?

When a vessel loses connectivity in a shipping lane, four parties typically have a stake in the failure: the VSAT provider, the LTE or LEO supplier, the systems integrator, and the fleet manager. The fleet manager is the only one accountable for the operational consequences. The other three are accountable for their respective service components — and each component has an exclusion clause that covers exactly the scenario where the other component is needed.

The result is a structure where connectivity failure produces a circular accountability problem. The vessel is dark. Nobody owns it.

The four-party problem

The VSAT provider's SLA excludes outages caused by beam congestion, adverse weather, and handoff failure to secondary bearers. The LTE provider's SLA excludes events outside terrestrial network coverage. The integrator's support agreement covers configuration faults, not carrier-side outages. The fleet manager holds contracts with all three and a liability to the vessel operator for connectivity continuity.

This structure is not accidental. Each party has designed their contract to exclude the scenarios most likely to cause outages. The gap between those exclusions is where vessels go dark.

The fleet manager holds all the contracts. None of them cover the actual failure mode.

What connectivity accountability means in practice

Accountability in a connectivity contract means more than credit mechanisms. It means a named responsible party for each failure category, a defined escalation path when that party disputes responsibility, and a time-bound commitment to root cause analysis — not just restoration.

Most maritime connectivity contracts contain none of these elements. The SLA defines uptime targets and credit triggers. It does not define who investigates a disputed outage, what evidence standard applies, or what happens when root cause is genuinely ambiguous. The fleet manager fills the gap by spending internal resource investigating a failure that one or more of their vendors caused.

The USCG CySO mandate and what it tells us

In 2025, the USCG introduced the requirement for a designated Cyber Security Officer on commercial vessels operating in US waters. The mandate creates a named individual — accountable by name, with defined responsibilities — for cybersecurity governance. The governance principle is sound: ambiguous accountability produces gaps. Named individuals produce enforcement.

The same principle applies to connectivity performance. GAO-25-107244 identified persistent gaps in Coast Guard cyber oversight — the same accountability failure pattern. Multiple responsible parties, undefined escalation paths, no single named owner of the failure outcome.

A vessel that goes dark because of connectivity failure and a vessel that goes dark because of a cyber incident share the same operational consequence. The accountability architecture that resolves one resolves both.

What accountability architecture looks like

A connectivity accountability framework has four elements:

None of these elements require new technology. They require contract language that reflects operational reality — that vessels operate across multiple bearers, multiple coverage zones, and multiple contractual relationships, and that someone must be accountable for the outcome.

The starting point

The USCG mandate names a person. Maritime connectivity contracts need to name one too. Before the next connectivity RFP is issued, the accountability question — who owns it when the vessel goes dark — should have a documented answer. That answer belongs in the contract, not discovered during the incident.