US strikes hit four Khuzestan towns in under ten minutes, OSINT video shows

Four towns in Iran's oil-producing Khuzestan Province were hit by US munitions between 23:02 and 23:30 UTC on 12 July 2026, according to open-source video and two Telegram channels that track the air campaign in near real time. The geography of the strikes, scattered along a roughly 200-kilometre arc of southwestern Iran, points to a salvo-against-grid logic rather than a single high-value target.

The pattern is the story. Within the same half-hour, separate posts logged explosions at Susangerd (23:02 UTC), Hoveyzeh (23:03 UTC, then a second hit logged at 23:09 UTC), and Andimeshk (23:04 UTC). A wider column of smoke over the Ahvaz–Haftgel highway was captured in footage circulated by OSINT613 at 23:30 UTC. The clustering is the kind of open-source record that has, in earlier phases of US operations against Iranian-aligned assets, made it difficult for any party to claim deniability on the timeline.

What the record shows, and where it thins

The strongest claim the open-source record supports is the clustering itself. Telegram channels RN Intel and Intelslava, which post timestamped alerts on each new strike, and the OSINT613 footage of the Ahvaz–Haftgel highway smoke column, are independent enough in style and sourcing that a coincidence is unlikely: one is a near-real-time strike ticker, the other publishes geolocated video. Three distinct locations, three independent reports, within eight minutes. That is corroboration, not proof, but it is the kind of corroboration that any wire desk would take seriously as a working basis.

The record does not, on its own, specify what was struck. The Telegram posts name towns, not targets. Susangerd, Hoveyzeh and Andimeshk are mixed civilian-industrial nodes: Andimeshk sits inside a petrochemical corridor, Hoveyzeh lies close to the Hawizeh Marshes on the Iraqi border, and Susangerd is an agricultural town with nearby oil infrastructure. Without named facilities, damage assessments, or casualty counts in the source material, this article does not assert what was hit. The footage shows smoke, not cratering. Readers should treat the strikes as confirmed by location and timing only.

A second caveat: the channels that surface these reports are partisan. RN Intel and Intelslava track the US side of the air war with the cadence of battlefield fans, not neutral observers. Their reliability on the question of whether the US is striking is high; their reliability on why is low. The pattern they describe lines up with what a sustained US air campaign against dispersed Iranian military and proxy infrastructure would look like, but the source material does not let this article say more than that.

The grid, not the city

Read together, the four locations describe a grid, not a target. Susangerd, Hoveyzeh and Andimeshk form a triangle anchored on the Karun River, with the Ahvaz–Haftgel highway as the connective spine. This is the same corridor that carries much of Khuzestan's oil and petrochemical output to the Gulf, and the same corridor that Iran has used to move materiel to the Iraqi border in past mobilisations. Striking a grid, rather than a single node, is what a force trying to degrade a distributed network does. It is also what a force trying to make a country feel attacked does.

The two readings are not mutually exclusive, and the open-source record does not distinguish between them. The US, by long-standing practice, does not preview strike logic in real time; the Iranian side, by long-standing practice, claims hits on infrastructure the strikes did not reach. What the OSINT record does is pin down the geography tightly enough that the strategic question becomes answerable, even if the answer is not yet public.

The information order of an air war

A half-century of US air operations has produced a stable information order. Open-source reporters on Telegram and X pick up flash, smoke, sound, and timestamp. Wire agencies aggregate, add official readouts, and impose attribution. Governments issue their own count, almost always lower. Civilian casualty estimates emerge last, often from local hospitals or UN monitors, and are the figures that the historical record eventually keeps.

The order is visible in the 12 July cluster. The Telegram posts arrived within minutes of the impacts. The OSINT613 footage, geolocatable to the Ahvaz–Haftgel highway, followed. There is, in the source material available to this article, no Iranian official readout, no US Central Command statement, no wire-service casualty figure, and no UN or Red Cross presence on the ground. The strike has been logged; the strike has not been explained. That is the information condition the public will work with for the next hours and days, and the condition that any subsequent official statement, from any capital, will have to engage with rather than overwrite.

What we verified, and what we could not

Verified. Four strike events at named locations in Khuzestan Province between 23:02 and 23:30 UTC on 12 July 2026, reported by at least two independent Telegram channels (RN Intel and Intelslava). Smoke column on the Ahvaz–Haftgel highway in the same province, in footage timestamped 23:30 UTC and published by OSINT613.

Partially verified. The attribution to US forces. The Telegram posts assert US responsibility. There is no US government statement in the source material confirming or denying specific strikes at these locations and times.

Could not verify. Targets struck; damage; casualties; the type or number of munitions; the operational rationale; whether any of the locations are dual-use (civilian-military) sites; Iranian, Iraqi, or international humanitarian-agency presence on the ground.

Stakes through the next reporting cycle

The next twelve hours are the ones that matter. If US Central Command issues a readout naming the targets, the strikes will harden into a documented campaign with a stated purpose. If Iran retaliates against US forces in Iraq, Syria, or the Gulf, the cluster becomes a step in a wider war rather than a discrete action. If neither happens, the strikes will sit as one more data point in a campaign that has been, by the standards of recent US air operations, low in public explanation and high in tempo. The open-source record, in any of these paths, is now the part of the story that will not move.

Desk note: Monexus is reporting this as an OSINT-anchored strike log, not as a confirmed campaign narrative. The wire order on US operations against Iran has, in previous rounds, lagged the channels by hours; this article publishes on the channels' clock and will be updated as official readouts arrive.

Wire provenance

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

• https://twitter.com/Osint613/status/2076447329360462143/video/1
• https://t.me/rnintel
• https://t.me/rnintel
• https://t.me/intelslava
• https://t.me/rnintel
• https://t.me/rnintel