Strait of Hormuz traffic thins as US and Iran trade contradictory signals on the waterway's status

Confirmed vessel crossings through the Strait of Hormuz fell for a second consecutive day on 9 July 2026, dropping to 22 from 30 the day before, according to shipping-analytics firm Kpler data relayed by the Telegram channel wfwitness at 11:09 UTC on 13 July. Commercial traffic only marginally outpaced non-commercial movements, a notable shift in a corridor that on most days carries the bulk of seaborne oil exports from the Gulf. The figures land in the middle of a five-day volley of contradictory announcements from Washington and Tehran over who controls the narrow waterway, and on what terms.

The pattern is the story. On 11 July at 22:55 UTC, an account tracking Polymarket, the prediction-market platform, reported that Iran's Revolutionary Guards had declared the Strait of Hormuz closed "until further notice." Hours earlier, at 18:50 UTC the same day, a separate market-watcher account flagged Iran's rejection of a US ultimatum, with Tehran saying the strait would remain closed to all traffic except a northern Iranian route. Within roughly 39 hours, on 12 July at 13:56 UTC, a US military announcement declared the waterway "officially open to all vessels seeking lawful transit." The two governments are now publicly asserting incompatible operating regimes over the same stretch of water between Iran and the Musandam Peninsula.

What the numbers actually show

Kpler's vessel-tracking figures, the only quantitative anchor in the thread, do not line up neatly with either side's rhetoric. A second-day drop from 30 to 22 confirmed crossings suggests commercial operators are pricing in risk regardless of which capital claims authority over the corridor. The near-parity between commercial and non-commercial movements is itself a tell: it implies a non-trivial presence of naval or paramilitary craft in the same transit lanes used by oil tankers and container ships. The thread does not specify the tonnage or flag-state composition of the 22 vessels, and it does not break out which side of the strait the vessels transited. The two data points (30, then 22) are also too narrow a sample to declare a trend, though the direction is the direction that matters for insurers and charterers.

The absence of corroborating traffic data from other trackers (MarineTraffic, AIS aggregators, port authorities in Fujairah or Bandar Abbas) is a real limitation. What the available sources confirm is a measurable decline; what they cannot confirm is whether the decline reflects re-routing around the Cape of Good Hope, slow steaming outside the chokepoint, or vessels holding station offshore pending clearer instructions.

Two governments, one strait, opposite orders

The US military's 12 July declaration frames the strait as an international waterway in which lawful transit is to be protected, language consistent with longstanding US freedom-of-navigation doctrine and with the transit-passage regime codified in the UN Convention on the Law of the Sea. Iran's posture, as relayed through the Revolutionary Guards statement and the reported rejection of the US ultimatum, treats the corridor as sovereign Iranian territory whose terms of access Tehran sets unilaterally, with a narrow exemption for traffic along the northern Iranian coast.

The two claims collide on a stretch of water roughly 21 nautical miles wide at its narrowest, divided into Iranian and Omani territorial seas with overlapping transit lanes. Iran's asserted right to control passage through the strait is not new; what is new is the explicit, public ordering of closure from the Guards, juxtaposed within hours against a US declaration of openness. The strait has been a flashpoint before, including during the Iran-Iraq War's "Tanker War" phase in the 1980s and during earlier Revolutionary Guards seizures of commercial vessels, but the current standoff is being conducted in real time through English-language market channels and prediction-market feeds, not only through state media.

Why the prediction markets are watching

The framing reaching English-language traders on 11 and 12 July came primarily through Polymarket-affiliated accounts on X, which surface the platform's contract pricing and breaking headlines on geopolitical closures, conflicts, and elections. The US military announcement was relayed as a "BREAKING" line at 13:36 and again at 13:56 UTC on 12 July; Iran's closure was framed identically the prior evening. Polymarket's role here is editorial in a narrow sense: it surfaces claims that traders then price, and the platform's own contracts on Hormuz transit have become a barometer of perceived closure risk. The thread does not include specific contract prices or implied probabilities, only the headline events those contracts would settle against.

The structural point is worth stating plainly. When two governments issue incompatible transit orders within 39 hours, and the only neutral data point is a private-sector vessel count that is moving in the wrong direction for both sides, the operating environment for shipowners, charterers, and insurers is one in which the rules of the road depend on which flag, which navy, and which coast guard you pass closest to. That is not a regulatory dispute. It is a contested corridor.

What remains unresolved

Three things are not in the thread and would change the picture if they surfaced. First, a primary-source read of the Revolutionary Guards statement in Farsi or via Iranian state media outlets such as IRNA, Mehr, or Tasnim, rather than a third-party relay; the Iranian framing as carried is consistent with prior IRGC communications, but the operative scope (which vessel classes, which flags, which ports of origin and destination) is not specified. Second, a US Central Command or Pentagon readout on the 12 July "open" declaration naming which forces are tasked with enforcing transit, and under what rules of engagement. Third, any insurance-market guidance from Lloyd's Joint War Committee or the International Group of P&I Clubs, whose listed or unlisted status for Hormuz transit premiums would convert rhetoric into pricing.

The disagreement between the two governments' announcements is real. The vessel-count decline is also real, in the only two data points available. What remains contested is whether the decline reflects Tehran's closure order being enforced on the water, Washington's opening declaration being enforced on the water, or shipowners acting on their own risk calculus ahead of either. The next print from Kpler or a comparable tracker will be the first serious test of which side's version of the strait is holding on the surface. Watch 10 July's figure when it lands; if it sits below 22, the closure order is doing work. If it rebounds above 30, the operators are voting with their hulls that the corridor is open after all.

Desk note: Monexus framed this against two competing official readouts (IRGC closure, US military opening) and a single private-sector vessel count. Where Iranian state media or Pentagon briefings were not directly available in the thread, we said so rather than infer from secondary relays.

Sources

• Telegram, wfwitness channel, post timestamped 2026-07-13T11:09 UTC, Kpler data on Strait of Hormuz crossings on 9 July 2026. https://t.me/wfwitness
• X (Polymarket account), post timestamped 2026-07-11T22:55 UTC, Report on Iran's Revolutionary Guards declaring the Strait of Hormuz closed. https://x.com/polymarket/status/
• X (Unusual Whales account), post timestamped 2026-07-11T18:50 UTC, Report on Iran's rejection of a US ultimatum and closure order. https://x.com/unusual_whales/status/
• X (Polymarket account), post timestamped 2026-07-12T13:36 UTC, US military announcement that the Strait of Hormuz is open to all vessels seeking lawful transit. https://x.com/polymarket/status/
• X (Polymarket account), post timestamped 2026-07-12T13:56 UTC, Repeat / corroborating post on the US military's "open" declaration. https://x.com/polymarket/status/

Wire provenance

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

• https://t.me/wfwitness