CENTCOM opens a new strike wave on Iran as the Strait of Hormuz comes back into frame
US Central Command said late on 12 July 2026 that its forces had begun a fresh wave of strikes on Iran, framing the operation around Tehran's ability to target shipping in the Strait of Hormuz.

At 21:21 UTC on Sunday 12 July 2026, US Central Command announced that its forces had begun a new wave of strikes against Iran. The message, relayed through CENTCOM's own channels and picked up within minutes by Intelslava and the Gaza Alanpa Telegram feeds, framed the operation in maritime terms: the strikes, the command said, were intended to further weaken Tehran's ability to target shipping in the Strait of Hormuz. By 21:44 UTC Middle East Eye had logged the announcement in its live blog; by 22:17 UTC OANN's Telegram channel was carrying a fuller version of the same CENTCOM statement, citing the strikes as part of a widening regional campaign.
The pattern matters. This is not a single sortie over a single facility. It is an openly sequenced escalation, declared in real time, with the justification written into the press notice before the ordnance lands. The Strait of Hormuz is the hinge: roughly a fifth of seaborne oil passes through it, and any sustained threat to tankers there moves from a military story into a freight, insurance and bond-market story within hours.
What CENTCOM actually said
The command's announcement, as carried by the Telegram channels and by Middle East Eye, is short. It describes the operation as "additional strikes" rather than a new campaign, and ties the targeting to Iran's ability to threaten ships in the strait. That phrasing does two things at once. It places the strikes inside a legal and rhetorical frame of self-defence of sea lanes, and it signals that what is being degraded is a capability, not a single piece of infrastructure. The distinction is not trivial: a capability-based target set tends to imply a longer, rolling air tasking order rather than a one-night barrage.
OANN's relay, which appeared at 22:17 UTC, adds the editorial gloss that the strikes are happening "as conflict heats up in region," a useful reminder that the announcement does not arrive in a vacuum. The Middle East Eye live entry, timestamped 21:44 UTC, fixes the same window and the same target logic. Both pieces sit on top of the same CENTCOM source; neither claims new ground on casualty counts, weapon types, or specific Iranian sites hit. The sources do not specify what was struck, where, or with what.
Why the Strait of Hormuz is doing the rhetorical work
Maritime chokepoints have a habit of becoming the public justification for strikes that, on a map, look like they are about something else. The strait is narrow, heavily trafficked, and the body of water through which Qatari LNG, Saudi and Iraqi crude, and the bulk of the Gulf's hydrocarbon exports move. Any Iranian capability that could complicate that traffic, anti-ship missiles, fast-attack craft, mining capability, drone swarms, is therefore, by definition, a target that a maritime superpower can describe as defensive. The CENTCOM wording leans into that frame without naming hardware.
What is missing from the public messaging is the other half of the calculation. Iran has, in previous episodes, demonstrated the ability to disrupt tanker traffic through harassment, seizure, and proxy action rather than overt naval combat. Strikes that frame themselves around "the ability to target ships" are strikes against a doctrine, not a dockyard. That makes them harder to verify and easier to extend.
The escalation logic, in plain language
Two readings of the announcement are plausible, and the sources do not yet let a reader choose between them. The first is that this is a discrete, capability-focused round, designed to push Iran's maritime threat surface back by a measurable margin for a defined window. The second is that it is the opening bracket of a longer campaign, in which "additional strikes" becomes a standing phrase rather than a one-off event. Both readings are consistent with the language CENTCOM used; both are consistent with the absence, so far, of any specific target list.
A third possibility should be on the table: that the public framing around the strait is partly designed for audiences outside Iran. Energy-importing governments, insurers pricing war risk premia, and shipping companies deciding whether to transit are all reading the same CENTCOM lines. Each one of those audiences draws a slightly different conclusion from the word "additional." That is not a conspiracy. It is what well-sequenced public statements tend to do.
What the sources do not yet tell us
The Telegram relays and the Middle East Eye live entry are the public record for now. They confirm the announcement, the timing, and the maritime framing. They do not name Iranian targets, do not give weapon types, do not give casualty figures on either side, and do not specify which US assets are involved. Iranian state-aligned outlets have not, in this thread, been logged with a counter-claim; the absence of a Tehran response in the available sources is itself a data point, but a thin one. Any assessment of what was actually destroyed, and what Iran chooses to do next, will have to wait for corroborated reporting from wire services, satellite imagery, and Iranian official channels.
What can be said with confidence is narrower. A regional combatant command publicly announced a new strike wave on Iran on the evening of 12 July 2026. The justification it chose was the security of shipping through one of the world's most important oil corridors. The campaign name is the strait, and the strait is, by construction, a global audience.
Desk note: this piece is built from four relays of the same CENTCOM announcement, picked up between 21:21 and 22:17 UTC on 12 July 2026. The wire services have not yet published target lists or casualty figures, and the article is deliberately scoped to what those primary relays support. Monexus will widen the source set as independent reporting, satellite imagery, and an Iranian response become available.
Wire provenance
This editorial synthesis draws on the following public wire/social posts:
- https://t.me/intelslava
- https://t.me/gazaalanpa
- https://t.me/OANNTV