Ninth Night: CENTCOM Extends Iran Strike Campaign to Chabahar and Konarak
US Central Command said a fresh wave of strikes against Iran began at 7pm ET on 19 July 2026, the ninth consecutive night, with Chabahar and Konarak among the reported targets.

Air defence systems activated over the city of Konarak in Sistan-Baluchestan province late on 19 July 2026, according to the War Footage Witness channel on Telegram, which posted the alert at 23:35 UTC. Within minutes, the Russian-aligned intelligence account rnintel reported renewed US attacks on the Chabahar-Konarak corridor and a separate strike on Abadan in southwest Iran, the latter appearing as a single Telegram entry at 23:24 UTC and not independently corroborated elsewhere in the available record.
US Central Command has now publicly confirmed the operation. At 23:00 ET on 19 July (03:00 UTC, 20 July), CENTCOM announced that a new wave of strikes against Iran had begun at 7pm ET, marking the ninth consecutive night of bombardment. The command's statement, reposted by Clash Report at 23:22 UTC and by the OSINT Live account at 23:19 UTC, says the strikes "will continue degrading Iranian military capabilities used to attack" US forces and allies. Targets in the southeast were not named in the CENTCOM text itself; the geographical claims attached to Chabahar and Konarak originate from Telegram channels citing local accounts, not from CENTCOM's own readout.
The escalation sits in the open. The campaign is no longer being framed as a retaliatory one-off; it is described, by the executing command, as a rolling operation measured in consecutive nights.
A port city in the crosshairs
Konarak sits roughly 50 kilometres southwest of Chabahar, the deep-water port Iran has spent two decades developing as its outlet to the Gulf of Oman and the Indian Ocean. The complex is the terminus of an Iranian rail link intended to extend into Afghanistan and Central Asia and has been the focus of Indian investment under the Chabahar agreement signed in 2016. That a US strike package now reportedly extends to facilities in or around Konarak places the war inside Iran's commercial perimeter, not only its missile and proxy architecture.
Reporting from the southeast is thin and runs through partisan channels. War Footage Witness, the source for the Konarak air-defence alert, is an aggregator of frontline footage; rnintel, which carried the Chabahar-Konarak and Abadan claims, is a Russian-aligned channel that regularly relays both Russian and Iranian state framing. Neither outlet is a substitute for on-the-ground verification, and the CENTCOM statement itself does not itemise which facilities were hit. Readers should treat the precise target set as contested.
The Russian-language picture
Moscow's information space has been unusually active around the campaign. Russian Telegram channels have circulated maps, video purportedly shot in the dark over Khuzestan and Sistan-Baluchestan, and casualty claims that no Western wire has yet matched. The rnintel feed alone ran three escalatory posts inside a ten-minute window on the night of 19 July, an editorial tempo consistent with a channel amplifying, rather than originating, breaking claims. The structural effect is to set a baseline tempo of crisis in Russian-speaking audiences ahead of any independent confirmation, and to seed regional capitals with the impression that the strikes are broader and more indiscriminate than CENTCOM's own language allows.
That is not, on its own, evidence of fabrication. It is the standard pattern of an aligned channel converting official communiqués into a higher-frequency, more emotionally charged feed. The pattern matters because Iranian-state media, cut off from much of the open web, increasingly sources its English-language claims from this same Russian-language pipeline.
Nine nights, and what the framing leaves out
CENTCOM's choice of words is doing real work. The command describes the objective as "degrading Iranian military capabilities used to attack" US forces and partners, a formula that locates the war in Iran's arsenal, not in Iran's territory. It does not name the proxy front, the nuclear file, or the diplomatic track. There is no embedded casualty framing, no humanitarian language, no reference to civilian infrastructure in or around Chabahar, even though the city of roughly 100,000 residents sits adjacent to the reported strike zone.
What the public posture leaves out is as informative as what it includes. No benchmark for success has been offered: nine consecutive nights of strikes, by the command's own count, but no stated endpoint, no quantitative measure of degradation, and no indication of which Iranian capability the campaign is meant to foreclose. The Iran file has, since the early months of 2026, moved between direct action and back-channel negotiation in a way that makes the rhythm of nightly strikes a policy instrument in itself: pressure without a public negotiating position.
What remains uncertain
The known facts are narrow. CENTCOM has confirmed a ninth consecutive night of strikes beginning at 7pm ET on 19 July 2026. The executing command has not itemised targets. The Konarak air-defence alert and the Chabahar and Abadan strike claims live on Telegram channels whose incentives are not those of a wire service. The campaign's cumulative effect on Iranian air defence, missile production, and proxy resupply is not, on the public record, being measured by any independent body. The sources available to Monexus do not specify casualty figures, the number of munitions used per night, or whether the Chabahar port itself, as distinct from surrounding military sites, has been struck.
What can be said is that the operational tempo has hardened, that the geography has widened toward Iran's commercial southeast, and that the public framing is being held to a tight, capability-focused script. The next forty-eight hours will test whether the script holds: whether Iran responds through proxies or directly, whether the Chabahar corridor draws a diplomatic reaction from India, and whether the Russian-language information space begins to diverge sharply from what the US command is willing to put on the record.
Desk note: Monexus is framing the night through the CENTCOM statement as primary, with Telegram-channel claims around Chabahar, Konarak and Abadan held as counter-claim material rather than confirmed targeting. The nine-night framing is taken from the command's own language.
Wire provenance
This editorial synthesis draws on the following public wire/social posts:
- https://t.me/ClashReport
- https://t.me/osintlive
- https://t.me/rnintel
- https://t.me/wfwitness