CENTCOM opens new air campaign against Iran at 6 a.m. ET, citing capability degradation
U.S. Central Command says it began a fresh wave of strikes against Iran at 6 a.m. Eastern on 15 July 2026, framed as a continuation of the capability-degradation campaign that has defined the post-ceasefire phase.
At 06:00 ET on 15 July 2026, U.S. Central Command forces began a new wave of strikes against Iran, according to a statement the command issued and Telegram channels intelslava, rnintel and ClashReport carried within minutes of each other between 10:23 and 10:32 UTC. CENTCOM framed the operation as designed to "further degrade military capabilities Iranian forces have used to attack" U.S. assets and regional partners. The wording echoes, almost verbatim, the language used in earlier phases of the post-June air campaign, and the timing matters: the strikes reopen an active aerial front less than 48 hours after the informal de-escalation window had narrowed to a handful of trackable incidents over the Strait of Hormuz.
The opening phase of any U.S. air operation against Iran has, since June, set the template for what follows: a CENTCOM statement on the hour, instantaneous echo across open-source intelligence channels, a quiet lag from Iranian state media as the scale of incoming damage is verified, and a multi-hour gap before Washington adds operational detail. The 15 July statement fits that template. The contents do not yet. The command has not, in the messages posted by intelslava, rnintel and ClashReport, specified the targets, the weapons used, the platforms flown from, or the duration of the sortie package. What the three channels do agree on is the trigger language: capability degradation, not territorial denial or escalation termination.
What CENTCOM said, and what it did not
The 06:00 ET text is short on operational substance. It names the actor (CENTCOM), the moment (06:00 ET, 15 July 2026), the instrument (a wave of strikes) and the strategic intent (degrade Iranian military capabilities used to attack U.S. forces and partners). It does not name the target set. The Iranian capital, the Revolutionary Guard Corps air defence nodes around Isfahan and Tabriz, the missile production infrastructure around Shahroud, and the drone assembly lines around Shiraz are all plausible candidates in a capability-degradation campaign; the CENTCOM text, as carried by intelslava, rnintel and ClashReport, does not confirm any of them. Iranian state media had not, at the time of the three Telegram posts, claimed strikes on Iranian soil. The information gap on the target set is the central uncertainty in the first hour of the operation, and it will not close until satellite commercial imagery or Iranian official statements move.
The phrase "further degrade" is also worth reading closely. It is not the language of a one-off punitive strike, nor the language of a regime-change operation. It is the language of a rolling campaign. That framing matters because it tells allies, adversaries and financial markets that Washington expects this to be a sequence, not an event.
Why now
Three structural pressures converge on this 06:00 ET decision. The first is force protection: the CENTCOM statement explicitly invokes attacks on U.S. forces and partners as the proximate justification. The second is the collapse of the post-June de-escalation track, in which Iranian-proxy attacks on Gulf logistics and a U.S. retaliatory package had been nominally contained. The third is political signalling inside Washington, where a capability-degradation campaign can be prosecuted without the escalatory vocabulary that has historically triggered legislative pushback. The three-channel Telegram feed does not establish which of these three carried the most weight in the decision; it does establish that the operational language chosen is compatible with all three.
The Iranian response corridor is well rehearsed. Iranian state media has, in earlier phases of the post-June campaign, moved from initial silence to denial to a managed retaliatory frame over a 12-to-24-hour window. The proxy network, primarily through Iraqi Shia militias and Houthi missile and drone units, has typically responded inside the same window. A capability-degradation campaign against the IRGC air-defence grid specifically targets the shield that protects those proxies' Iranian logistics, which means a second-day Iranian response is more likely to come through forward assets in Iraq, Syria and Yemen than through a direct IRGC launch from Iranian airspace.
What remains uncertain
The first hour of any U.S. air operation against Iran is, by design and habit, the most information-poor hour. The CENTCOM statement carried by intelslava, rnintel and ClashReport names the operation and the intent; it does not name the targets, the duration, the sortie count, the loss expectancy, or the rules of engagement. The Iranian side has not yet, in the three channels reviewed, confirmed or denied strikes on its territory. The three Telegram channels are aligned on the timing and the wording of the CENTCOM statement; they are not, in the posts of 10:23 to 10:32 UTC, an independent verification of the strikes themselves. That distinction matters more than usual here, because the operational substance of a capability-degradation campaign is decided in the first 72 hours, and the verification chain tends to lag by 12 to 24 hours.
The second-order question is whether this is a new campaign wave or the continuation of an old one. The wording suggests the latter. If it is the latter, the template established in June and July becomes the predictor for what follows: a CENTCOM afternoon update with target imagery and sortie counts, an Iranian denial-to-retaliation arc over 12 to 24 hours, and a Gulf-states market reaction that prices the risk into insurance and freight before it prices into equities. The single most useful indicator to watch over the next six hours is whether Iranian state media breaks silence on damage assessment, or maintains the lag.
How Monexus framed this vs the wire: the Telegram channels intelslava, rnintel and ClashReport each carried the CENTCOM statement within minutes of release; the wire agencies had not, at the time of writing, posted a confirmed-strike line of their own. This article treats the CENTCOM text as the primary source and the three Telegram channels as the carriage record, and flags the operational unknowns the text does not close.
Wire provenance
This editorial synthesis draws on the following public wire/social posts:
- https://t.me/intelslava
- https://t.me/rnintel
- https://t.me/ClashReport