CENTCOM Marks 13 Straight Nights Of Iran Strikes

Surface-to-air missiles mounted on a launcher against a blue sky — Photo: PX Media / Shutterstock

The 13 consecutive nights of U.S. Central Command strikes on Iran are best understood not as a discrete flare‑up, but as a textbook case of how great powers now wage limited war to defend maritime commerce while battling over who gets to define “self‑defense.”

Key Points

CENTCOM presents the 13‑night campaign as a defensive operation to protect commercial shipping in the Strait of Hormuz, directly tied to specific attacks on civilian vessels.
Across those nights, U.S. forces hit hundreds of Iranian military targets – command centers, air defenses, anti‑ship missile and drone sites, coastal radar, IRGC naval assets – explicitly to degrade Iran’s capacity to threaten shipping.
The trigger narrative is contested: Washington attributes the crisis to Iranian attacks on at least three commercial vessels, while Tehran disputes aspects of the account and portrays its own actions as defensive, but without offering detailed counter‑evidence in the public record.
There is, so far, no independently verified battle‑damage assessment showing how much Iran’s maritime strike capability was actually reduced, leaving the effectiveness of the campaign an open analytical question.
This episode fits a recurring pattern in maritime security: an attack on shipping, a focused strike campaign against coastal and anti‑ship infrastructure, and a parallel information war over legality, proportionality, and escalation.

From vessel attacks to a 13‑night campaign

The sequence began with what U.S. officials describe as a clear trigger: attacks by Iran’s Islamic Revolutionary Guard Corps (IRGC) on commercial vessels transiting the Strait of Hormuz. Multiple CENTCOM statements and corroborating news reports trace the July strike campaign back to three commercial ships attacked in the strait, followed by additional incidents including the M/V Ever Lovely. In response, at the direction of President Trump, CENTCOM initiated a sustained operation against military targets inside Iran, framed from the outset as retaliation aimed at restoring freedom of navigation rather than regime change or territorial occupation.

By CENTCOM’s own tally, the campaign rapidly scaled. A third round of strikes in one week alone hit roughly 140 Iranian military targets, part of more than 300 targets struck in the first three nights of that phase. Earlier releases describe other rounds hitting in excess of 80 targets, including air defense systems, coastal radar, anti‑ship missile sites, and over 60 IRGC small boats in and near the strait. As of the thirteenth consecutive night, CENTCOM reported sustained attacks on Iranian military command centers, drone storage facilities, communication networks, coastal surveillance sites, and maritime capabilities – all explicitly linked to the threat those systems pose to commercial vessels.

In parallel, U.S. officials emphasized continuity of shipping. CENTCOM stated that, despite Iranian attacks, the international waterway remained open, and that U.S. forces had helped facilitate the transit of more than 800 commercial vessels and 400 million barrels of crude oil since early May. That kind of statistic is not incidental; it is central to the narrative that this was a campaign to keep a global economic artery open, not to start a larger war.

What the United States says it was trying to achieve

CENTCOM’s stated objectives fall into two related categories: immediate defense of civilian mariners and longer‑term degradation of Iran’s ability to threaten maritime traffic. Operationally, that translated into a target set focused on what military planners call the “kill chain” for anti‑ship operations. U.S. releases and media reporting describe strikes on coastal radar, maritime surveillance infrastructure, command and control nodes, missile and drone launch sites, ammunition depots, and fast‑attack craft used by the IRGC Navy.

The logic is straightforward. To threaten a tanker in the Strait of Hormuz, Iran needs to detect it (surveillance radar and coastal sensors), communicate targeting data (communications networks and command centers), and then employ weapons (anti‑ship cruise missiles, drones, naval boats, or mines). The U.S. campaign mapped almost exactly onto that architecture. CENTCOM highlighted the use of precision munitions, including 5,000‑pound deep‑penetrator bombs against hardened missile sites along the Iranian coastline, characterizing those sites as housing anti‑ship missiles that directly threatened international shipping. Other waves of strikes went after vessels reportedly attempting to lay naval mines and the missile launch facilities supporting them, which U.S. spokespeople again labeled defensive actions to protect both U.S. forces and commercial ships.

Strategically, CENTCOM placed this within Operation Epic Fury, a broader effort described as dismantling the Iranian regime’s security apparatus while prioritizing locations posing an “imminent threat.” Yet even in that wider frame, the messaging keeps returning to the maritime dimension: each major release ties the timing and scope of strikes to discrete episodes of “unwarranted aggression” against commercial shipping and the need to defend freedom of navigation.

Iran’s narrative and the evidentiary gap

Iran does not accept this framing, but its counter‑case in the open record is thinner and less specific. Iranian officials and state media have characterized their own actions as “defensive” and accused the United States of escalation and aggression, especially after Washington revoked sanctions relief and moved to blockade Iranian ports. Tehran has also disputed aspects of Washington’s account of the shipping incidents, including whether its forces fired warning shots, what status it claimed for the Strait of Hormuz at various points, and whether U.S. or U.S.-linked assets were the true targets.

However, the material surfaced here does not include a detailed Iranian evidentiary package: no release of naval logs, radar tracks, or munition forensics tracing particular attacks to alternative culprits. Reuters and other outlets note that the U.S. narrative relies heavily on CENTCOM’s own claims and that early reporting left some target specifics unclear, especially in the first rounds of strikes. CNN and others explicitly describe conflicting maritime-traffic narratives between Washington and Tehran, which fuels skepticism but does not, by itself, disprove the U.S. account.

In legal and strategic debates, this asymmetry matters. When one belligerent supplies highly specific descriptions of targets and stated purposes – even if those come from self‑interested institutions – and the other offers broad denials without technical counter‑evidence, external analysts tend to anchor their reconstructions on the more granular record, while keeping in mind its provenance. That is the situation here: the strongest publicly available detail comes from CENTCOM and media organizations relaying CENTCOM’s statements.

What we still do not know

Three major uncertainties remain. First, attribution of the original shipping attacks rests publicly on U.S. statements rather than a fully documented, independent incident reconstruction. The kind of analysis that would definitively settle responsibility – AIS (Automatic Identification System) data, satellite imagery, acoustic signatures, and independent inspection of damaged hulls – is not present in the open sources provided. Analysts can infer plausibility from capability and past behavior, but that is not the same as conclusive proof.

Second, target‑to‑incident linkage is generalized. CENTCOM and others list categories of targets – anti‑ship missile sites, coastal radar, command centers – rather than publishing a target folder for each strike that ties a specific facility to a specific attack or ongoing operational plan against shipping. That is normal for an ongoing operation; it is also why outside observers cannot independently verify whether every target struck was directly connected to the maritime threat, or whether some were chosen for broader coercive leverage.

Third, there is no transparent, quantitative battle‑damage assessment in the public domain. U.S. statements say the mission was to “further downgrade” or “degrade” Iran’s ability to attack civilian mariners and commercial vessels and imply success, but they do not disclose post‑strike intelligence estimates of remaining Iranian inventories, readiness levels, or operational tempo. Conversely, Iran has not provided its own detailed accounting of damage and residual capacity. The result is a familiar fog: we know what was targeted and with what intent, but not in precise terms what effect it had on Iran’s real‑world ability to threaten shipping.

The strikes may have paused, but President Trump says the pressure on Iran hasn't.

After 13 consecutive nights of U.S. strikes, CENTCOM announced no new attacks Friday night as diplomatic talks continue.

Still, Trump made clear the military is ready to escalate if negotiations…

— charlie ward (@charliewwg1wga) July 25, 2026

Pattern, precedent, and implications for maritime security

Stepping back, the 13‑night campaign sits squarely within a broader pattern of how states use limited force in contested maritime chokepoints. Time and again – in the Persian Gulf of the 1980s, the Red Sea in the 2010s, and now the Strait of Hormuz – a sequence emerges: a merchant vessel is attacked or threatened; a powerful state conducts targeted strikes against the perceived author’s anti‑ship infrastructure; both sides then wage an information war over whether those strikes were defensive and proportionate or escalatory and coercive.

In this case, the United States has coupled kinetic action with economic and legal tools: reimposing sanctions on Iranian oil exports, announcing a blockade on ships entering or exiting Iranian ports, and emphasizing coalition support for keeping the waterway open. Iran, for its part, has used closure declarations, retaliatory drone and missile strikes on regional states, and its own legal and rhetorical arguments about sovereignty and self‑defense. The operational facts at sea – which ships are attacked, which lanes stay open – thus exist alongside a dense layer of narrative and legal maneuvering.

For commercial operators, insurers, and regional states, the practical stakes are less about who wins the narrative and more about risk and precedent. If sustained U.S. strikes demonstrably reduce the frequency and severity of attacks on tankers, they will reinforce the long‑standing role of U.S. naval power as guarantor of Gulf shipping. If, however, Iran adapts quickly or other actors step into the gray zone, the campaign could come to look like a costly episode of mutual punishment that changes little in the underlying threat environment.

Finally, there is the question of where such campaigns stop. Here, the strikes ran for 13 consecutive nights, then paused amid diplomatic activity, with President Trump and U.S. officials insisting that pressure on Iran continues in other forms. That arc – rapid escalation, intense but bounded use of force, then a pause leveraged for negotiations – is now a familiar script in U.S.–Iran interactions. The more often it is repeated, the more it shapes expectations on both sides about how far they can push without tipping into full‑scale war, and about how attacks on commercial shipping will be answered in the years ahead.