OHMEGA/MONSTER

Strait of Hormuz impaired, not closed: strikes and vessel damage reduce traffic despite ongoing transits

CENTCOM and IMO-confirmed incidents point to active maritime disruption in July, while conflicting Iranian and U.S. claims persist and traffic remains lower—not shut—according to reported shipping patterns.

IranUnited States

The Strait of Hormuz is not closed, but it is no longer operating normally.

CENTCOM says it has carried out repeated strike waves against Iran, including strikes it says were meant to degrade Iran’s ability to attack commercial shipping. Reuters reported traffic through Hormuz fell to multi-week lows, and the IMO’s confirmed-incidents log shows multiple damaged vessels and seafarer fatalities in the region in early and mid-July. That is not just rhetoric. It is active maritime impairment.

Hormuz matters because it is a chokepoint: a narrow passage through which a large share of traffic must move, so disruption there can have outsized effects. But importance is not proof of closure. The evidence here supports a narrower reading: the corridor is under stress, not definitively shut. Reuters reported Iran saying passage was not possible and its Guards saying the strait was closed, while U.S. officials said Hormuz remained open to commercial traffic. CENTCOM also said commercial transits continued and that more than 800 commercial vessels and 400 million barrels of crude—by the date of the CENTCOM report, counting transits since early May—had moved through since early May. Those claims cannot all describe the same state of affairs, which is why the best reading is contested control, not settled blockade.

The traffic drop may still be real without amounting to a full shutdown. Reuters said traffic continued at reduced levels and that operator caution was helping drive the pattern. Reuters-quoted shipping officials described a “managed conflict,” meaning shipping continues but operators deliberately adjust routes and schedules to reduce exposure to attacks, and CNBC cited shipping-industry views that the middle lane was too dangerous because of mine risk, with firms showing different risk appetites. Ships can keep moving while also deciding to move less, move differently, or move with AIS (the ship-tracking broadcast that lets others see a vessel’s location) switched off. That is compatible with precautionary routing, not just enforced closure.

The market lane is real, but only partly verified here. CNBC reported expectations that war-risk premiums would rise sharply and that shipowners and charterers were pausing transit decisions. It also reported tanker traffic had fallen and that shipping firms were reassessing routes. What this run did not verify directly is the precise live premium level or a clean market sheet. So the honest statement is that risk pricing appears to be moving, while the magnitude remains unproven here.

The tail risk is larger: a durable closure or broader regional escalation. That remains a scenario, not a demonstrated fact. For now, the reader should hold the spectrum, not a binary: confirmed impairment, continued though reduced movement, official claims that conflict, and a still-unproven leap to full blockade.

ScoreMeaning
1Near-normal traffic (not observed in this profile)
2Elevated disruption, still the better of two count days
3High — multi-week low (relative language)
4Very high — further day-over-day drop and/or two-month low language
5Near-closure / sustained blockade (not evidenced)

AI-assisted analytic, built only from cited data.

Date (2026)CENTCOM completed-wave statementIMO incident / damage evidenceReuters traffic evidenceLag: IMO damage vs nearest prior completed waveLag: traffic report vs nearest prior completed waveStrength
Jul 11Completed third round of strikes that week; >300 targets (shipping-degrade intent stated)Multiple damaged vessels in Strait of Hormuz / Gulf of Oman area—0 days (same day)—CENTCOM: count+date · IMO: date · traffic: —
Jul 12Completed new wave; dozens of targets at multiple locations (shipping-degrade intent stated)— (no Jul 12 damage date in profile summaries)—— (no IMO damage date this day)—CENTCOM: count+date · IMO: — · traffic: —
Jul 13Completed latest wave at 10:15 p.m. ET; targets included Bushehr, Chah Bahar, Jask, Konarak, Abu Musa, Bandar AbbasMultiple damaged vessels listedMulti-week low amid renewed strikes/attacks on ships; tanker traffic “past day” at lowest in two months / lowest since May 25 (Reuters item dated Jul 13)0 days (same day as Jul 13 wave; also 1 day after Jul 12)0 days if “past day” is treated as contemporaneous with the Jul 13 report; otherwise undated day-levelCENTCOM: date · IMO: date · traffic: relative (no daily vessel count this day)
Jul 14— (no completed-wave statement in profile)Multiple damaged vessels listed—1 day after Jul 13 wave—IMO: date · others: —
Jul 15—Multiple damaged vessels listed13 vessels crossed Hormuz (prior-day figure in Jul 16 Reuters report)2 days after Jul 13 wave2 days after Jul 13 waveIMO: date · traffic: count+date
Jul 16—Multiple damaged vessels listed9 vessels crossed Hormuz (down from 13 the previous day); reduced commercial traffic / operator caution2+ days (3 days after Jul 13 wave)2+ days (3 days after Jul 13 wave)IMO: date · traffic: count+date + qual
Jul 17—As-of totals only: 58 confirmed incidents; 17 seafarer fatalities (not a daily incident date)—n/a (cumulative as-of, not day log)—IMO: count+as-of date · not day-resolved

AI-assisted analytic, built only from cited data.

BinMeaning
Durable closureSustained near-zero transits over multiple consecutive days, or explicit blockade/closure enforcement that would support a lasting shutdown
Managed disruptionReduced but continuing transits, day-to-day variation, operator-caution explanations, episodic incidents, residual “slipping through” traffic
Insufficient evidenceCategory is relevant to the question but the profile has no supporting observation

AI-assisted analytic, built only from cited data.

Source recordSources / claims / limits

How this piece is framed: A live shipping-impairment story: confirmed operational risk has already reduced and rerouted movement through Hormuz, while the larger claim of a durable closure or blockade remains contested and unproven. The reader should watch a spectrum, not a binary: strikes and vessel incidents create real impairment; some transits continue; official claims conflict; market behavior looks precautionary but is not fully quantified here.

Charts & tables — each built only from the cited claims below, by an AI tool

  • Transit severity index: normalize transits/turn-backs into a single daily ‘disruption’ measure — from claims clm_709f7803dc, clm_97f3a25a08, clm_32cc8f1002, clm_ec511e3868, clm_7bdc89cd12 · as of 2026-07-17
  • Timeline reconciliation: strike waves vs IMO confirmed incidents vs traffic drops — from claims clm_73cb94c4da, clm_44f9c1b2ec, clm_717c2569d1, clm_3ddddd4e12, clm_0a218bd847, clm_0760d38c23, clm_94a53c4899, clm_97f3a25a08, clm_32cc8f1002, clm_709f7803dc, clm_7bdc89cd12 · as of 2026-07-17
  • ‘Closure likelihood’ signal vs ‘managed risk’ signal using evidence-bearing indicators — from claims clm_4dba983b80, clm_a873e3114e, clm_2379c4b364, clm_e42b87d108, clm_709f7803dc, clm_97f3a25a08, clm_32cc8f1002, clm_ec511e3868, clm_7bdc89cd12, clm_cd2c3a14bb, clm_283e4171ed · as of 2026-07-17

Sources

Claims, and how far we tracked each down

  • [confirmed] U.S. Central Command conducted repeated strike waves against Iranian military targets in mid-July 2026. · read in full (as of 2026-07-18)
  • [confirmed] CENTCOM said it completed a new wave of offensive strikes against Iran on July 12, 2026, hitting dozens of targets at multiple locations with precision munitions. · read in full (as of 2026-07-18)
  • [confirmed] CENTCOM said the July 12 strikes were meant to degrade Iran’s ability to continue attacking international shipping flowing through the Strait of Hormuz. · read in full (as of 2026-07-18)
  • [confirmed] CENTCOM said it completed the latest wave of strikes at 10:15 p.m. ET on July 13 and hit military targets across Iran including Bushehr, Chah Bahar, Jask, Konarak, Abu Musa, and Bandar Abbas. · read in full (as of 2026-07-18)
  • [confirmed] CENTCOM said the July 13 strikes were intended to further degrade Iran’s ability to attack commercial shipping. · read in full (as of 2026-07-18)
  • [confirmed] CENTCOM said on July 11 that it had completed a third round of strikes that week against Iran and had struck more than 300 targets to degrade Iran’s ability to attack civilian mariners and commercial vessels freely transiting the strait. · read in full (as of 2026-07-18)
  • [confirmed] Reuters reported that vessel traffic through the Strait of Hormuz fell to multi-week lows amid renewed U.S.-Iran strikes and attacks on ships. · read in full (as of 2026-07-18)
  • [confirmed] The IMO confirmed multiple vessel incidents in the Strait of Hormuz/Gulf of Oman area in early-to-mid July 2026. · read in full (as of 2026-07-18)
  • [confirmed] The IMO confirmed 58 incidents and 17 seafarer fatalities as of July 17, 2026, including multiple damaged vessels in the Strait of Hormuz and Gulf of Oman area on July 7, 11, 13, 14, 15, and 16. · read in full (as of 2026-07-18)
  • [likely] The best-grounded reading is that the situation has moved into operational shipping risk, not just rhetorical escalation. · read in full (as of 2026-07-18)
  • [likely] Iran’s IRGC navy said the Strait of Hormuz was closed until further notice after a vessel tried to transit along an unapproved route. · read in full (as of 2026-07-18)
  • [confirmed] Reuters reported that Iran said it had closed the Strait of Hormuz and that passage was not currently possible due to recent U.S. military movements; Reuters also reported that Iran’s Revolutionary Guards said they stopped two ships by shutting down their systems. · read in full (as of 2026-07-18)
  • [confirmed] Reuters reported Trump said the Strait of Hormuz is open to commercial traffic. · read in full (as of 2026-07-18)
  • [confirmed] The U.S. publicly said the Strait of Hormuz is open to commercial traffic. · read in full (as of 2026-07-18)
  • [confirmed] CENTCOM said commercial vessel transits through the corridor continued and that U.S. forces had helped facilitate the successful transit of more than 800 commercial vessels and 400 million barrels of crude oil through Hormuz since early May. · read in full (as of 2026-07-18)
  • [confirmed] Reuters reported Trump said the Strait of Hormuz is open to commercial traffic, which is an official U.S. statement that conflicts with closure framing and is consistent with calibrated signaling rather than durable shutdown intent. · read in full (as of 2026-07-18)
  • [likely] A Reuters-quoted shipping official described the Hormuz situation as a 'managed conflict' similar to the Houthis in the Red Sea, with some ships still 'slipping in and out.' · read in full (as of 2026-07-18)
  • [likely] Reuters said commercial traffic through Hormuz 'continued at reduced levels' and JMIC said traffic patterns reflected 'operator caution,' which supports the interpretation that lower transits can come from precautionary behavior and AIS-off switching rather than a sustained blockade. · read in full (as of 2026-07-18)
  • [likely] Reuters reported that commercial traffic through Hormuz continued at reduced levels and that traffic patterns reflected operator caution after recent attacks. · read in full (as of 2026-07-18)
  • [likely] CNBC quotes BIMCO's Jakob Larsen as saying the traditional middle routing remains too dangerous because of mine risk, implying ships may still transit via alternative routing and that the disruption is route-specific rather than necessarily a full chokepoint closure. · read in full (as of 2026-07-18)
  • [likely] CNBC quotes Larsen as saying shipping firms have different risk appetites and that some vessels are still willing to transit Hormuz while others stay away, showing that reduced traffic can reflect heterogeneous operator choices rather than a single blockade decision. · read in full (as of 2026-07-18)
  • [likely] CNBC reported that the traditional middle route through Hormuz was viewed as too dangerous because of mine risk, and that shipping companies showed different risk appetites rather than a single uniform blockade decision. · read in full (as of 2026-07-18)
  • [likely] War-risk premiums for Strait of Hormuz exposure were expected to rise sharply, with shipowners and charterers pausing transit decisions. · read in full (as of 2026-07-18)
  • [likely] CNBC reported industry expectations that war-risk premiums for Strait of Hormuz exposure would rise sharply and that shipowners and charterers were pausing transit decisions. · read in full (as of 2026-07-18)
  • [unconfirmed] The current live price or probability for the Polymarket U.S.-Iran invasion market was not cleanly verified in this run. · our synthesis across the evidence — no single cited source
  • [confirmed] Reuters reported Iran described Hormuz as a red line and said it could prod its Houthi allies in Yemen to close another key strait if the United States attacks Iranian infrastructure. · read in full (as of 2026-07-18)

Where we hit a limit / what to double-check

  • "The current live price or probability for the Polymarket U.S.-Iran invasion market was not cleanly verified in this run." is our reading across the evidence, not a single sourced fact.