AIS data for marine insurance that holds up in a coverage dispute.
Assess a vessel before binding, monitor exposure between renewals, and reconstruct a voyage when a claim is contested. Real-time positions from our own network, with the raw signal and its provenance intact.
100,000+
Vessels tracked / day
49M+
AIS positions / day
40+
Countries covered
<5s
Antenna to your API
AIS data for underwriting is only as strong as the record behind it.
When a reinsurer or a tribunal asks how a vessel’s position was established, a processed position report is not evidence.

Processed AIS cannot evidence its own origin.Most AIS reaches an underwriter already cleaned, fused and smoothed. Adequate for a screen, inadequate under dispute, because the file cannot establish what the raw signal was, which independent receiver collected it, or at what moment.
A gap on one feed cannot be attributed.A transponder switched off and a hole in a single provider’s coverage present identically, so dark activity flags carry false positives directly into vetting decisions. Vessel-originated spoofing and area-wide GNSS jamming leave distinct patterns, but only where separate receivers can be compared for the same box and the same window.
We operate the source and retain the record.We run our own physical infrastructure, terrestrial and ship-borne, with satellite feeds for open ocean. Every station runs the same standardised hardware and encrypts each message at the instant of capture. Every position is nanosecond time-stamped and trust scored by our anomaly detection models.
Submit a contested voyage.Send an IMO number or MMSI with a date range, and we will return the positions our network collected, with receiver metadata and trust scores attached.
Verify a disputed voyageFrom pre-bind vetting to a claims investigation.

Pre-bind due diligence on a vessel, fleet or owner
Before quoting hull and machinery, cargo, war risk or P&I cover, examine how the vessel has behaved: AIS gaps, ship-to-ship transfer patterns, port call history, MMSI reuse, IMO mismatches and flag changes, with the underlying messages retained rather than summarised away.
Continuous monitoring while the risk is in force
Monitor the whole book rather than a sample of it. Identify entry into a Joint War Committee Listed Area, a Voluntary Reporting Area, or a sanctions-adjacent port call while there is still time to charge additional war risk premium, serve notice or set a reserve.
Sanctions screening supported by an auditable record
Sanctions law, not a policy clause, places the screening burden on the insurer. Clauses such as LMA3100A, the Lloyd’s Market Association sanctions limitation clause, and its Joint Hull equivalent JH2010/009, suspend cover only where paying a claim would expose the insurer. They are silent on how the check is to be conducted. A vendor dashboard produces an image, not a record. Retain an auditable trail of what was screened, when, and on which underlying positions, with provenance carried on every message.
Voyage reconstruction for claims and coverage disputes
Reconstruct where a vessel was against what it broadcast. Comparing what separate independent receivers collected for the same area and window is what distinguishes vessel-originated spoofing from area-wide interference affecting all surrounding traffic.
Corridor and port accumulation after rerouting
Rerouting around Bab el-Mandeb, and war-risk pricing at Hormuz, converted per-vessel exposure into corridor and port level accumulation. Live traffic supports modelling of in-transit cargo accumulation and multi-policyholder event exposure on your own assumptions.
A raw feed for models built in house
Where you build in house rather than licensing a finished risk score, take raw NMEA over TCP, a REST API or a WebSocket stream, and run your own portfolio, pricing and accumulation models on data you can inspect line by line.
How the data is produced,
and how you can check it.
Every station runs the same dedicated, standardised hardware and encrypts each message at the instant of capture.
Monitor
Cover the fleets you write
Track 100,000+ vessels a day across 40+ countries, so a portfolio can be watched between renewals instead of sampled once at quote.
Verify
Know which receiver collected it
Every position is nanosecond time-stamped and given a trust score by our anomaly detection models, so manipulated or spoofed signals are flagged rather than quietly merged into a clean track.
Act
Into vetting, pricing or the claims file
Take it as raw NMEA over TCP, a REST API or a WebSocket stream, in under five seconds from antenna to your API, and attach the underlying records to the decision you have to defend.
AIS data for marine insurance: the questions underwriters ask.
Is AIS data admissible as evidence in a marine insurance claim?
Admissibility is a matter for the tribunal, not for a data provider, and in practice it turns on provenance: whether the origin of the data can be established and its integrity demonstrated from collection onward. Our messages are encrypted on the hardware at the moment of capture, nanosecond time-stamped and carry receiver metadata, so the chain from antenna to file is documented rather than asserted. We supply the underlying records, not only a chart image.
How do you tell AIS spoofing from GNSS jamming?
The distinction is established from the pattern across vessels rather than from a single track. Vessel-originated spoofing typically affects one transponder while surrounding traffic behaves normally, whereas area-wide GNSS interference distorts many vessels in the same box simultaneously. Comparing what independent receivers collected for the same window is what makes the difference observable, and a single fused feed cannot support that comparison.
What does an AIS gap actually prove about a vessel?
In isolation, less than most vetting workflows assume. A gap may indicate that the transponder was switched off, or that no receiver was in range at the time, and a single provider’s feed rarely distinguishes the two. Trust scores and receiver metadata allow coverage during the window to be confirmed before a gap is recorded as dark activity in a file.
Do you cover the vessels and areas we write, and how do we check?
It depends on the vessel and the area, because we supply only what our own network collected. Provide the IMO number or MMSI and the window in question, and we will confirm what our network covered there, including where reception is thin, before any commitment.
Do P&I clubs have to monitor AIS for sanctions compliance?
Expectations vary by club, market and jurisdiction. Sanctions clauses such as LMA3100A and JH2010/009 suspend cover where a payment would expose the insurer, but they prescribe no method of checking. The obligation to screen sits in the underlying OFAC, OFSI and EU regimes. What compliance teams are generally required to produce is a defensible record of what was screened and on which data. That is a question of provenance, and provenance is the part we supply.
Related sectors
Bring us the voyage you cannot settle.
Send an IMO number or MMSI with a date range, and we will return what our network collected and the origin of every message.
Verify a disputed voyage


