Strait of Hormuz, Round Eight: Inside the 18 July U.S. Strike Wave on Iran

At 6 p.m. Eastern Time on 18 July 2026, U.S. forces began a new wave of airstrikes against Iran, ordered by the Commander in Chief and announced publicly by U.S. Central Command. The release carried an explicit dual mandate: retaliate for the previous night's attacks on American service members in Jordan, and degrade Iran's capacity to threaten commercial shipping in the Strait of Hormuz. The announcement came less than forty-eight hours after CENTCOM confirmed two U.S. service members had been killed in action, and roughly twenty-four hours after it declared its seventh wave of strikes complete. The operational tempo is now one major wave per day, with the language hardening in equal measure.

What is unfolding across the Persian Gulf and its northern approaches is the most sustained direct U.S. air campaign against Iranian territory in the history of the Islamic Republic. It is also a campaign whose stated justification has visibly shifted inside forty-eight hours, from a defensive posture around commercial shipping to a punitive posture against Iranian paramilitary forces. That shift matters. It tells readers where the escalation ladder sits, and who is being asked to climb it.

What CENTCOM actually said

The CENTCOM statement, published at the top of the 6 p.m. ET hour and reproduced in full by the OSINTdefender and Open Source Intel Telegram channels, is unusually short by Pentagon standards. Its operative sentence names Islamic Revolutionary Guard Corps forces as the target, and frames the strikes as a punitive measure for the Jordan attack of the previous night, in which two U.S. service members were killed. The release also references the broader stated goal of degrading Iran's ability to threaten commercial shipping in the Strait of Hormuz. The single release, in other words, fuses two justifications that American officials have, in past confrontations, treated as legally and operationally distinct: a retaliation strike against a named adversary force, and a freedom-of-navigation campaign against an obstructionist state actor.

The Open Source Intel channel separately amplified a third line from the release, that the strikes are designed to "further degrade Iran's ability to threaten" commercial shipping, language that mirrors phrasing used by U.S. naval commands in earlier this month's Strait of Hormuz operations. The repetition matters. Washington has now used near-identical wording across two distinct operational packages, which suggests a deliberate signalling architecture rather than ad-hoc drafting.

What the public CENTCOM release does not say is also revealing. It does not name the specific IRGC units struck. It does not specify whether the targets sit inside Iran proper or in adjacent theatres where IRGC-Quds Force assets operate. It does not quantify Iranian casualties or damage assessments. That opacity is conventional for wartime U.S. operational communications, but in a conflict where Tehran's English-language outlets are also broadcasting claims in real time, the information asymmetry is sharper than usual.

A week compressed into days

The Bellum Acta News channel, citing CENTCOM's own reporting, recorded that the seventh wave of strikes finished the previous night. That puts the tempo at roughly one major wave per day across the past week, an intensity that has few modern precedents. The American bombing campaigns against Iraqi positions in 1991 and against Serb positions in 1999 unfolded over weeks. The current Iran operation is, by contrast, a rolling daily cadence with overlapping justifications.

For Iran, that cadence creates a strategic problem distinct from the physical damage. Each wave forces a decision: retaliate and risk triggering another, larger wave; absorb and risk signalling weakness; or escalate asymmetrically through proxies, including the Jordan attack itself, which CENTCOM now formally attributes to IRGC-linked forces. The Jordan strike is the pivot of the entire week. It is the event that turned a shipping-protection operation into a force-protection retaliation operation, and that, in turn, gave Washington the legal and political cover to widen the target set inside Iran.

Iranian state-aligned outlets have, in past reporting cycles, framed U.S. naval operations in the Gulf as aggression masked as freedom of navigation. The current sequence complicates that frame because the Jordan attack is a separate, geographically distinct event, and CENTCOM's explicit naming of IRGC forces as the retaliatory target gives Washington an act-of-self-defence argument that travels more easily with third-party governments than a freedom-of-navigation argument alone would.

The shipping lane that everyone watches

Roughly a fifth of the world's seaborne oil passes through the Strait of Hormuz. That statistic is widely cited and is the structural backdrop to every U.S. naval deployment in the Gulf for the past four decades. What is different in the July 2026 sequence is that the threat to that shipping has become a stated target of strikes, rather than merely the rationale for forward naval presence. CENTCOM's release language, "threats to commercial shipping in the Strait of Hormuz," is the closest formal U.S. articulation yet that the Iranian capacity to threaten the lane is itself a target, alongside any specific platforms Iran might use to enforce a closure.

The operational implication is significant. U.S. strikes are now oriented not just at clearing a specific mine, fast-attack craft, or anti-ship missile battery, but at degrading the broader Iranian capacity to threaten the lane at all. That is a larger and more diffuse target set than the one named in earlier waves. It also implies a longer sustainment horizon, because Iranian capacity to threaten the strait is not a single facility but a network of facilities, missile batteries, naval bases, and command nodes spread across the southern coast.

Market sensitivity to Hormuz disruption has historically been acute. Even threats that did not materialise into closures have moved crude benchmarks within trading sessions. A sustained daily-strike cadence against Iran's ability to threaten the strait would, on past evidence, sustain a higher risk premium in crude pricing for the duration of the campaign, regardless of whether the lane is ever physically closed.

What the sources disagree about

The Telegram-sourced reporting in this cluster converges on what CENTCOM said and when. It diverges on almost everything else. The OSINTdefender and Open Source Intel channels frame the operation as retaliation and degradation, with emphasis on the Jordan attack as the trigger. The Bellum Acta News channel emphasises the cumulative nature of the campaign, highlighting that the seventh wave finished only the previous night. RNIntel treats the announcement as breaking news, foregrounding the Commander in Chief's direction and the dual mandate.

What none of the channels can settle from open sources alone is the scale of Iranian casualties, the identity of the specific IRGC units hit, whether the strikes reached targets deep inside Iranian territory, and whether the Jordan attack that triggered the latest wave was, as CENTCOM implies, an Iranian-directed operation or, as some Iranian-aligned outlets have framed previous incidents, an action by allied militias acting without explicit IRGC command authority. That ambiguity is itself a feature of the information environment around this campaign. Western wire services will, in the coming days, attempt to settle some of these questions; Iranian outlets will contest others.

What to watch next

Three dates will determine whether the current tempo holds. First, Iran's formal response to the eighth wave, which the IRGC or the Ministry of Defence is expected to articulate within hours of the strikes. Second, the next U.S. operational communique, which will indicate whether the target set widens further or narrows as the Jordan-attack justification is consumed. Third, the next market open in crude and freight derivatives, which will price in whether the shipping-threat framing has stuck and whether insurance underwriters adjust their Hormuz war-risk premia.

If the tempo holds at one major wave per day, with each wave tied to a new act of attribution rather than to a fixed target list, the campaign is on a trajectory toward something functionally indistinguishable from a rolling air superiority operation over Iranian territory. If the tempo breaks, the political space opens for a mediated pause, brokered through the channels that have historically absorbed U.S.-Iran escalations. The sources reviewed here do not yet resolve which path is more likely. They do, however, make the central fact of 18 July 2026 unambiguous: a direct, publicly announced U.S. air campaign against Iranian forces is now running at a daily cadence, and its stated mandate has expanded, in the space of forty-eight hours, from ship protection to force retaliation.

Desk note: Monexus framed this piece against the Telegram-sourced CENTCOM announcements rather than against Western wire summaries, because the original CENTCOM release carries the specific operational language the analysis turns on. Where the Telegram channels diverge on emphasis, the divergence is named in the article. Western wire confirmation of casualty figures, target identities, and Iranian damage assessments is not yet available in this cluster; readers should treat those specific claims as pending until corroborated.

Wire provenance

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

• https://t.me/s/osintlive
• https://t.me/s/osintlive
• https://t.me/s/osintlive
• https://t.me/s/osintlive
• https://t.me/s/rnintel
• https://t.me/s/BellumActaNews