Skip to content

Home/Sectors/Subsea & survey

AIS data for subsea cable protection, corridor by corridor.

Most cable faults originate from anchors and fishing gear, in shallow water close to shore. We supply the underlying vessel positions on which anchor-drag alerting, cable burial risk assessment and damage claims depend.

100,000+

Vessels tracked / day

49M+

AIS positions / day

40+

Countries covered

<5s

Antenna to your API

Submarine cable monitoring AIS data is only as good as the reception under it.

A subsea monitoring contract is decided by reception over your route, not by a worldwide vessel count.

  • Anchors and fishing gear cause most cable faultsFaults concentrate in shallow, nearshore water. That band is where satellite revisit is thinnest and where a terrestrial network, receiving by line of sight, carries the load. Test reception over your route, in your season, at your required update rate.

  • Alert speed rests on position rateA dragging anchor crosses a cable corridor in minutes, even where the drag runs for hours. A slow or intermittent position rate over that corridor puts the alert after the strike. We deliver from antenna to your API in under five seconds, across a network carrying more than 49 million positions a day.

  • AIS carries no authenticationAIS is cooperative: transmission can be stopped, an MMSI reused, a position falsified. An unexplained gap over your corridor merits investigation, but only against a reception baseline you can rely on. Every message we collect is encrypted on the hardware the instant it is captured, nanosecond time-stamped, and scored by anomaly detection models.

A reception sample over your cable routeSend the corridor coordinates and a date range, and we return the raw positions our own network collected there, with receiver attribution and timestamps intact.

Get AIS for your cable route

From cable route survey to live corridor monitoring.

  • Cable protection zone and corridor alerting

    Define a corridor around an in-service cable or pipeline and run your alerting on positions delivered under five seconds after reception. Anchoring, loitering, slow-speed transit and trawling are all visible in the underlying track before they appear in a fault report.

  • Cable burial risk assessment and depth of lowering

    A CBRA, and the DNV-RP-F107 or F111 work alongside it, requires traffic distributions rather than dashboards. Positions from our own network arrive with the gaps characterised, so depth of lowering and burial specification rest on an auditable input.

  • MGN 654 navigational risk assessment and EIA consenting

    The Shipping and Navigation chapter of an EIA, and for offshore renewable projects a Navigational Risk Assessment under MCA MGN 654, both require seasonally resolved traffic baselines that withstand challenge. Every position we collect carries its receiver attribution and its timestamp, so the traffic record behind an FSA can be traced to source.

  • Cable damage investigation and claim recovery

    A cable claim turns on which vessel was over the fault position at fault time, and whether any other was present. Every position we supply retains its originating receiver, its nanosecond timestamp and its trust score, so the track withstands challenge.

  • Marine coordination during survey, lay, burial and repair

    Across cable route survey, pre-lay grapnel run, lay, burial and repair, marine coordination requires third-party traffic in the corridor in real time, not in the next day's report. The live stream feeds guard vessel tasking and Notice to Mariners compliance.

  • An independent second source over your corridor

    Where a monitoring platform is already licensed, an independently collected feed establishes whether an unexplained gap over your corridor was a transmission gap or a reception gap. Two independent sources make that question answerable.

How the positions over your corridor are produced.

One network, one hardware standard, from the antenna on the coast to the corridor on your screen.

Monitor

Cover the route, not the planet

Track vessels over your cable route, protection zone or pipeline corridor in real time. Class A and Class B, with AtoN messages included, delivered as raw NMEA over TCP, REST or a WebSocket stream into whatever alerting you already run.

Verify

Know where each fix came from

Every station runs the same dedicated standardised hardware and encrypts each message the instant it is captured. Positions reach you nanosecond time-stamped, with a trust score from our anomaly detection models and the originating receiver still attached.

Act

Prevent it, or prove it

Run the corridor into anchor-drag alerting and guard vessel tasking while the cable is in service. When something does go wrong, the same positions, with their provenance intact, go into the CBRA revision, the claim file or the flag state referral.

Subsea cable and pipeline questions we are asked most.

How much AIS coverage do I need to monitor a subsea cable route?

There is no single global answer, because the figure that matters is local. Coverage is determined by reception density over the corridor in question and the update rate achieved there, not by a worldwide vessel count. Request a raw sample from any provider, ourselves included, over your own route coordinates and date range, then assess the gaps directly.

Can AIS data be used to prove which vessel damaged a submarine cable?

AIS normally forms the backbone of such a case, provided it withstands scrutiny. Cable claim practice asks whether an identified vessel was at the fault position at the approximate fault time, whether it was engaged in an activity capable of causing the damage, and whether any other vessel was present. A smoothed, blended track from an unattributed source will not survive cross-examination. We supply positions with the originating receiver, the nanosecond timestamp and the trust score intact, so counsel and surveyors can evidence the provenance of each fix.

What is the difference between terrestrial and satellite AIS for cable protection?

Terrestrial receivers collect transmissions by line of sight from the coast, producing fast, frequent positions in the shallow nearshore water where anchoring and trawling damage cables. Satellite AIS reaches open ocean beyond shore station range, but revisit is slower and messages collide in dense traffic. Most cable corridors require both, weighted towards terrestrial close in. Our network runs terrestrial and ship-borne receivers on one hardware standard, with satellite feeds for open ocean.

What vessel traffic data is required for a cable burial risk assessment?

A CBRA under the Carbon Trust methodology is driven by traffic distributions over the route: vessel type, size, draught, speed profile and seasonal variation, from which anchoring exposure is derived. It requires historical AIS as a model input rather than a dashboard, with the gaps made visible, because thin data understates exposure and specifies under-burial that is paid for later in repair campaigns. What we supply is raw positions from our own network, in a form that goes straight into the model rather than onto a screen.

How do you detect a vessel that turns off AIS near a subsea cable?

We do not sell dark vessel detection as a product, and we would treat any claim of certainty in it with caution. What we supply is what makes a gap meaningful: a reception baseline over your corridor from receivers we own and operate. Where a vessel was transmitting and our receivers covered that water, we can evidence what was collected and when it stopped. Whether the silence was a transmission gap or a reception gap then becomes an answerable question rather than an inference.

See what our network receives over your cable route.

Send the corridor coordinates and a date range, and we will return raw positions collected by our own network, not an illustrative coverage map.

Get AIS for your cable route