Maritime Domain Action in the Indo-Pacific Needs One Shared All-Source Picture

At a Glance

• Information advantage and allied interoperability only mean something when partners work from the same picture.
• Dark fleet activity crosses combatant command boundaries, so each partner sees only a slice of it.
• AIS shows what a vessel says about itself, not what it is doing.
• Fused intelligence shared at the insight level lets partners act on the same facts.
• A picture only gets fielded if it fits the C2 and mission network workflows teams already run.

Information Advantage Starts With a Picture Allies Can Share

Talk of information advantage and allied interoperability comes down to one practical question: Can partners act together on a trusted picture of what is moving at sea, and why?

Most do not, at least not yet. Each navy, coast guard, and agency holds its own slice, built from its own sensors and its own rules. The gaps between those slices are exactly where gray-zone shipping operates.

No Single Navy Sees the Whole Dark Fleet Route

The dark fleet does not respect command boundaries. Russia reflagged 84 dark fleet tankers to its own registry in Q3 2026, more than four times the Q2 figure, according to Windward’s Q3 2026 Maritime Risk Report. Russia now flags 223 Russian-flagged tankers, 18% of the total. One in three Aframaxes worldwide now sits in the dark fleet.

Those vessels cross theaters as a matter of routine. Iranian crude loaded in the Gulf is commonly moved ship to ship in waters off Malaysia’s Johor coast, roughly halfway between Iran and China, which buys about 90% of Iranian oil. 

Malaysia’s maritime agency has said Iranian-linked tankers exploit jurisdictional gaps near its waters. One cargo can pass through CENTCOM and INDOPACOM and several national jurisdictions before it discharges, and no single partner sees the whole route.

A recent case shows how fragmented that picture gets. A UK-sanctioned LNG carrier, now owned by a single-ship company in China and reflagged from Panama to Sierra Leone in March, loaded Russian LNG at a sanctioned plant in December 2025. India refused the cargo in May. The vessel then spent months drifting and anchoring in the South China Sea and off Johor. In September it entered the Andaman Sea for the first time in Windward’s records, went dark twice near a cluster of subsea cables, and has since sailed repeated straight lines over them.

Each partner holds one fact. The UK listed the vessel. India turned the cargo away. Coastal states from Malaysia to Thailand watched it pass. Only the full history, fused across sources and jurisdictions, shows a sanctioned vessel holding its cargo for more than nine months with no commercial reason to be where it is.

Tracking Alone Cannot Tell Partners Whether to Act

AIS shows what a vessel says about itself. It does not show what the vessel is doing. Every identity field in the broadcast, from name and flag to destination, is entered by the crew or the operator.

The Q3 2026 report shows how far that self-report can drift from reality. 

By the end of September, the IMO list of falsely flagged ships had reached 613, up 39% since January. In the Bab el-Mandeb, about one in three AIS-visible transits used the destination field to broadcast crew nationality or a political message instead of a port. GPS jamming affected 124,235 distinct vessels worldwide, roughly one in nine ships in the world fleet losing reliable position data at some point in the quarter.

A gray-zone decision cannot rest on that. Whether to shadow a vessel, board it, or flag it to a partner depends on who owns it, where it has actually been, what it has done before, and whether its behavior fits its declared purpose. Tracking answers none of those questions on its own.

A Shared All-Source Picture Lets Partners Act on the Same Facts

The fix is not more data passed around. It is one assessment that every partner can trust and act on.

All-source operational intelligence fuses AIS with whatever sources the mission requires. That can mean SAR and EO satellite imagery, RF detection, dark vessel detection, ownership and sanctions data, years of behavioral history, or any other source that sharpens the picture. 

The output is a judgment about each vessel, not a stack of feeds. Windward’s Maritime Intelligence Operations Center (MIOC) works this way, combining sensors and sources into a single operational picture and verifying findings against open reporting.

Sharing at the insight level is what lets that picture travel. Partners do not need to exchange raw collection, sensor feeds, or methods to agree that a vessel is sanctioned, has gone dark twice near a cable corridor, and has no commercial reason to be there. They need the same assessment, with the evidence behind it. Commercial, unclassified intelligence can move between allies faster than national collection because it does not carry the same release restrictions.

When the UK, India, and the coastal states along that LNG carrier’s route all see the same history, the question changes from whether anyone noticed to who acts first.

Integration Feasibility Decides What Gets Fielded

A picture that cannot reach the people who act on it does not change outcomes. For a component CIO, the first question about any new capability is not what it shows but where it lives. Technical evaluators ask the same thing in more detail. Does it run inside the systems the command already operates, or does it need another screen, another login, and another data silo?

That test decides what gets fielded. A capability that demands rip-and-replace will usually lose to one that drops into existing C2 and mission network workflows, even if the first looks better on paper.

Windward’s intelligence is built to be consumed outside its own interface. Its API is GraphQL-based, so integrators request exactly the fields a workflow needs in a single call instead of pulling whole feeds. 

Webhooks push events such as risk score changes, deceptive shipping detections, and alerts on vessels of interest straight into internal systems. Risk indicators and scores are traceable to the underlying evidence, so an assessment stays auditable after it leaves the platform. The API is also designed to sit alongside a customer’s own data, so external intelligence is correlated with what a command already holds rather than replacing it.

Questions about specific mission networks and accreditation are environment-specific, and they are the right ones to raise early with any provider.

The Handoff to Decisions Is Where Intelligence Earns Its Place

Defense planners often break the mission into three layers, written together as C5ISRT.

The handoff from ISR to a decision is where intelligence earns its place. An assessment that arrives late, sits in a separate tool, or cannot show its evidence will not survive that handoff. One that reaches the operator inside the workflow they already use, explains why a vessel matters, and is shared across partners can.

That is the line Windward draws. It provides the picture and the reasoning behind it. The decision, and anything that follows from it, belongs to the people accountable for it.

Bring the Integration Questions to Booth TB113

Maritime domain action is not a slogan. It starts with a picture partners trust, built from all-source intelligence and delivered into the systems they already run, so they can act on it together.

Windward is at TechNet Indo-Pacific through October 29 at booth TB113 in the Tapa Tower. Bring the architecture and workflow questions, and see how fused intelligence on dark fleet and gray-zone activity fits into what your command already operates. Book a meeting at the booth.

Written by Maya Romi, Windward Senior Maritime Intelligence Content Manager.