Twelve ships, two boardings, two disables: CENTCOM's blockade math goes public

On 25 July 2026, U.S. Central Command published a running tally of its maritime operation against Iran, and the figure circulated within minutes through at least four open-source intelligence feeds. As of that day, the command says it has redirected twelve commercial vessels attempting to run the blockade, boarded two to verify compliance, and disabled two that failed to comply. Operations span the Arabian Sea and the Gulf of Oman, with U.S. forces stepping up inspections and enforcement across both waterways. The figures are modest in naval terms. The framing is not.

What CENTCOM has chosen to publicise is a measure of throughput, not firepower: ship counts, boardings, redirects, disables. That choice is itself the story. Maritime interdictions are usually described in incident reports filed after the fact. Here, the command is publishing an aggregated ledger while the operation continues, and using that ledger to define what the blockade is.

A blockade you can count

The most natural reading of the data is that the operation is calibrated for compliance rather than spectacle. Twelve redirected, two boarded, two disabled: that is a ratio that suggests most traffic is being turned, not engaged. Telegram channels monitoring CENTCOM communications have reproduced the figures in near-identical form within minutes of each other on 25 July 2026.

The arithmetic matters because it sets a precedent for how the U.S. will narrate future maritime operations in the Gulf. By publishing a running tally, rather than incident-by-incident releases, CENTCOM is signalling that the blockade will be measured by aggregate compliance rather than by any single boarding. That is also how shipping markets, insurers and Iranian counterparties will read it: as a throughput number, updated daily, against which routing decisions can be priced.

The legal floor is the part not being counted

What the ledger does not name is the legal authority under which the interdictions are taking place. The CENTCOM statement, as relayed by the monitoring channels, asserts that the blockade "remains in full effect" and reports enforcement results. The available material does not specify the domestic or international legal basis; whether the operation has been characterised as a blockade under the law of the sea, a sanctions enforcement action, or a freedom-of-navigation operation is not set out in the cited posts.

The cited CENTCOM material does not name Iran's Ministry of Foreign Affairs as having issued a counter-tally. The available source items do not specify whether Iranian authorities have, in the same 24-hour window, published their own count of vessels approached, warned or turned back. This publication finds that the absence of a published Iranian reciprocal figure, in the materials available for this article, leaves the question of how Tehran is narrating the operation open. That is the one piece of the picture the CENTCOM ledger, on its own, cannot supply.

Reading the geography

The Arabian Sea and the Gulf of Oman are not interchangeable. The Gulf of Oman feeds the Strait of Hormuz, which feeds the Persian Gulf. A blockade enforced primarily in the Gulf of Oman and the Arabian Sea reaches traffic before it funnels into the Strait; it also reaches traffic moving on routes that bypass Hormuz altogether, including those serving Iranian ports on the Indian Ocean coast. CENTCOM's stated area of operations therefore does more work than a single name suggests.

The Mozambique-channel reference that appears in one of the cited posts points in the same direction. Vessels attempting to reach Iranian ports, or to move Iranian cargo, can route around the Cape; interdictions in the Arabian Sea intercept that traffic only if it transits the Arabian Sea on the way in or out. The ledger's redirect-and-disable pattern is consistent with intercept work concentrated on the northern Arabian Sea approach, though the available source items do not specify the precise coordinates of the boardings or disables.

What the next 48 to 72 hours will show

The structural question this operation is sitting inside is whether a U.S. maritime enforcement campaign of this kind can hold without an accompanying political channel. Blockades historically resolve in one of three ways: a negotiated accommodation that ends them, an escalation that breaks them, or attrition that makes them routine. The published ledger, with its low disable count and its ongoing redirect count, suggests the U.S. is trying to settle into the third option quickly. That is Monexus analysis, not a stated CENTCOM position.

Two indicators will tell which way this is drifting. First, the disable count: if it rises without a parallel rise in boardings or redirects, the operation is moving from compliance work toward punishment work, and shipping insurance will reprice accordingly. Second, whether Tehran publishes its own count. A reciprocal ledger from Iran would mean the operation is being treated as a contest of throughput on both sides, with the diplomatic track narrowing in parallel. In the absence of that reciprocal count, the available material suggests the contest is being narrated, for now, by one side only.

Desk note: Monexus framed this as a question of what CENTCOM is choosing to publish, not as a question of who is winning. The cited threads are relay material, Telegram channels reposting a CENTCOM statement, and the primary anchor throughout is the command's own statement as relayed. Wire confirmation from Reuters, AP or BBC was not present in the materials available for this piece; the analysis above is built only on what the cited CENTCOM statement and its relays contain.

Wire provenance

This editorial synthesis draws on the following public wire/social posts:

• https://t.me/osintlive/559234
• https://t.me/osintlive/559232
• https://t.me/osintlive/559229
• https://t.me/rnintel/64929
• https://t.me/osintlive/559228
• https://t.me/osintlive/559226