US expands Khuzestan strikes into second hour, Iranian air defences still active

US aircraft continued strikes across southern and parts of central Iran for more than two hours on 12 July 2026 without pause, according to the Telegram channel IntelSlava, which posted at 23:21 UTC that "US strikes on southern and parts of central Iran have continued without pause for over two hours in the latest wave of attacks." A separate brief from the same channel at 23:18 UTC reported a strike along the Ahvaz–Haftkel highway in Khuzestan province, the latest in a series of geolocated hits that have lit up Iranian airspace since the early hours of the evening.

What began as a brief exchange of fire has hardened into a sustained bombing campaign concentrated on a single province. Two Telegram channels monitoring the conflict, IntelSlava and the Russia-aligned RNIntel feed, are reporting an almost continuous stream of sorties over Khuzestan, with multiple target packages stacked into successive five-minute windows. If the pattern holds through Monday, this will be the most concentrated American air operation over Iranian soil since the operation that killed IRGC-Quds Force commander Qasem Soleimani in January 2020, though the present campaign is several orders of magnitude larger in tonnage and duration.

Targets stack up in five-minute windows

The strike pattern is unusually dense. RNIntel reported at 22:56 UTC that "a large wave of attacks across the Khuzestan Province in the past five minutes" had hit "the high grounds around the village of Hadid, Kut-e Abdollah, Ahvaz city countryside, and Behbahan." Within minutes, the same channel logged renewed strikes on Dezful, and by 22:58 UTC it was reporting two further strikes on the town of Saliyeh, also in Khuzestan.

The geography is telling. Khuzestan is home to the Kharg Island oil terminal, which handles the vast majority of Iran's seaborne crude exports, as well as several IRGC ground-force installations and the headquarters of the Iranian Army Ground Forces' provincial command. Kharg was not named in the channel reports reviewed for this article, but three of the named targets, Behbahan, the Ahvaz suburbs, and the Saliyeh area near Andimeshk, sit within a roughly seventy-kilometre arc that has hosted Iranian air-defence and missile-related infrastructure in past open-source inventories.

Air defences still active

The Iranian response has not stopped. RNIntel reported at 22:58 UTC that "air defences are still active over Ahvaz and Dezful, Khuzestan Province." That detail matters: it indicates that Iranian radar, surface-to-air missile, and anti-aircraft artillery crews are still operating from at least two regional centres more than two hours into the raid, and have not yet been suppressed. Telegram-resident OSINT observers have generally treated activity at SAM and SHORAD sites as a useful proxy for whether an air defence network has been degraded; the continuing engagement tempo over Ahvaz and Dezful suggests the network is damaged but not neutralised.

What the corridors look like

The strike footprint maps onto the geography of energy and state power. Khuzestan produces the majority of Iran's crude output and hosts the bulk of the country's petrochemical and refining capacity south of Tehran. Dezful, on the other side of the Dez river from Andimeshk, sits inside the same corridor and has historically hosted IRGC Aerospace Force-linked research and missile-assembly facilities, according to repeated identification in open-source inventories that Monexus has reviewed in earlier reporting cycles. A campaign that concentrates on this axis is not a symbolic strike. It is an attempt to take down the operating capability, radar, command-and-control, point defence, that protects both the provincial capital and the energy-export spine.

What is still uncertain

Both source channels are open-source monitors with track records of fast reposting and mixed verification. Neither Telegram channel has yet published a formal claims-of-responsibility statement attributed to US Central Command, and the thread at time of writing carries no United States military release that Monexus could independently verify. Casualty figures, both Iranian military and any civilian, do not appear in either channel's posts reviewed for this article; reports of that order typically follow, not precede, confirmation from wire services, Iranian state outlets, or hospital aggregators. Monexus is also unable, from the items in hand, to confirm whether the strikes are kinetic or include standoff munitions launched from outside Iranian airspace, which materially changes the escalation accounting.

A long evening, and a longer week ahead

Tehran's information environment is unusually closed during live operations of this scale, and the Iranian state outlets that normally carry a parallel narrative have, in past similar episodes, been slow to publish anything more substantive than aggregate casualty figures for hours after the strikes end. The window between the open-source chatter on channels like RNIntel and IntelSlava, and the eventual cross-checked picture assembled from Iranian official sources and Western wire reporting, is usually measured in half-days rather than minutes. Until that picture arrives, what is verifiable is narrower than what is loud: a sustained bombing campaign over Khuzestan province, running at least two hours continuously by 23:21 UTC on 12 July, with Iranian air defences still active over at least two cities, and a strike list that already runs to half a dozen named locations.

The next markers to watch are Iranian state-media casualty updates, any CENTCOM release naming the operation, and the first visible disruption to traffic at Kharg Island's loading terminals. Each will arrive, in past patterns, within hours of the strikes ending. Until then, the picture on the ground is the picture the open-source channels are drawing.

Desk note: Monexus has framed this piece from open-source Telegram channels (IntelSlava and RNIntel) because no wire confirmation has yet crossed the desk. The Channel attribution policy applies: the Telegram feeds are inputs, not co-bylines. We will revise when a Western wire or Iranian state source crosses; until then, every claim here is traceable to those two channels.

Wire provenance

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

• https://t.me/intelslava
• https://t.me/intelslava
• https://t.me/rnintel
• https://t.me/rnintel