Strikes on Sirik and Hoveyzeh, then silence: a night of US air operations over Iran winds down

At 22:15 UTC on 12 July 2026, the Telegram channel Intelslava logged a renewed US airstrike on Sirik, a port town on Iran's southern coast near the Strait of Hormuz. Within the hour, the channel "rnintel" reported a separate US attack on the large town of Hoveyzeh in Khuzestan Province, the southwestern Iranian province that runs along the Shatt al-Arab waterway and the Iraqi border. By 23:34 UTC the same channel was signalling that the night's tempo had broken: no US airstrike on Iran in over thirty minutes, an interval it read as the operation winding down for the night.

The pattern, even at this thin evidentiary layer, is consistent with a campaign of sequenced strikes across geographically separated nodes of Iranian infrastructure or military footprint: the southern coast opposite the Gulf shipping lanes, and the oil-rich southwest that sits overland between Tehran and the Iraqi frontier. Sirik and Hoveyzeh are roughly 900 kilometres apart. The reporting on the night came from Telegram channels that aggregate open-source flight trackers, seismic readings and unverified geolocated footage; the channels themselves caution their feeds are early-warning, not confirmable attribution. They are, in practice, the first signal of what larger wire desks will sift over the following hours.

What the night looked like, in order

The Intelslava flash of 22:15 UTC placed the first new strike of the reporting window on Sirik, a town of roughly 7,000 in Hormozgan Province whose coastal approaches sit within sight of the strait through which a significant share of seaborne oil moves. The "rnintel" feed followed at 23:09 UTC with an attack on Hoveyzeh, the larger administrative centre in Khuzestan that gives its name to a marshland region north of Abadan. Hoveyzeh is not a typical first-choice target in coverage of Iran's nuclear or missile geography; its inclusion tells the reader either that the night's strike package had a wider remit than the well-rehearsed nuclear-site list, or that the Telegram-channel reporting is conflating distinct operations under a single frame.

The thirty-minute lull that followed, by 23:34 UTC, is the operational signal worth watching. Sustained US strike packages run on tanker orbits, on station time, and on rules of engagement that pace ammunition expenditure and deconfliction. A clean break of that length, observed by a channel whose stated operating logic is to timestamp each geolocated plume, is consistent with the day's tasking having been completed rather than paused. It is not, by itself, evidence that the campaign as a whole is over; it is evidence that 12 July's specific tasking order has likely been flown.

Why Hoveyzeh changes the picture

Iran-watchers conditioned on the long list of known nuclear, drone and missile sites will recognise Sirik almost immediately; it sits in the same Hormozgan corridor that US Central Command has previously flagged for fast-attack craft and anti-ship cruise missile infrastructure. Hoveyzeh will land differently. It is a municipality of a few hundred thousand people set in marshland historically associated with the Iran-Iraq war of the 1980s, an Iraqi invasion route, and the Karun river system. As a target, it reads as a logistics or command node rather than a known weapons-of-mass-destruction site. If the reporting holds through formal confirmation, the night's geographic spread suggests the operation has moved past the named nuclear-archipelago template and into a wider denial-and-degradation template.

The other open variable is what the two strikes actually struck. Telegram-channel reporting at this latency tends to capture the event, not the target. Civilian infrastructure, military sites, oil and gas handling, or Revolutionary Guard Corps facilities are all consistent with the available description, and the channels themselves do not specify. Until a US Central Command strike release, an Iranian sit-rep, or an independent OSINT geolocation of crater and shrapnel lands, the target inventory remains a gap in the public record. The silence in the half-hour since is real; the content of the night is not yet knowable from these inputs alone.

The structural frame, in plain prose

A US strike package that touches both the Persian Gulf coastline and the Iraqi-border southwest, in a single night's tasking order, fits a familiar pattern of trying to impose simultaneous pressure on separate functional layers of an adversary's defence: export capacity on the coast, command and replenishment in the interior. The reading is not exotic; it is what planners reach for when the goal is less a single decapitation blow than a systemic one, and when the political clock favours a compressed tempo over a forensic one. The contested question in Washington and in Gulf capitals will be how the second-night tasking order gets sequenced: repeat the geography and signal that the template is sustained, or shift inland toward the known nuclear sites and signal that the template is escalating. The first option resets expectations; the second raises them.

For Iran, the operating environment is now the operating environment: a defended but permeable airspace, a defended but stockable national stockpile, a populace whose casualty ledger from any night of strikes will travel through Persian-language social media faster than any official readout. The Tehran government's framing on such nights tends to converge on three lines: targets were military, losses were limited, the war is one of American choice and Iranian response. Those lines have limited purchase in the first hours but grow as the casualty ledger firms up.

What to watch before the next tasking order

Three signals will matter before the next US flight package is generated, and they will arrive in roughly that order. The first is a US Central Command strike release with target nomenclature, weapons expended and battle-damage assessment. The second is an Iranian sit-rep from state media that names affected sites and populations; Tasnim and IRNA are the outlets to watch for that release, with the caveat that they frame for an Iranian political audience. The third is a crude-market open on 13 July: Hormuz-strait risk has been a tradable line since the strikes on Sirik landed, and any move through the Asian session will be read as the market's first guess at whether the operation is repeating or expanding. None of the channels that produced tonight's reporting can supply the first item. All of them have a read on the third.

What remains unresolved

The reporting does not specify what was hit in Sirik or Hoveyzeh, nor does it confirm Iranian losses, civilian casualties, or any official Iranian response. The Telegram channels Intelslava and rnintel publish early-warning advisories and explicitly caveat their own attribution; treated as a primary source for what happened, they overreach; treated as a timeline for when something happened in roughly which area, they are useful and current. The structural ambiguity is real: the same data could read as a tightly bounded one-night operation against a long list of pre-planned targets, or as the first night of a multi-night operation whose scope broadens as it proceeds. The next forty-eight hours of formal reporting, not Telegram flash traffic, will close that ambiguity.

This publication reports the available channels verbatim and flags the limits of that reporting. Wire confirmation from a US Central Command release or from Iranian state media will be added as it lands.

Wire provenance

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

• https://t.me/intelslava
• https://t.me/rnintel
• https://t.me/rnintel
• https://en.wikipedia.org/wiki/Sirik
• https://en.wikipedia.org/wiki/Hoveyzeh
• https://en.wikipedia.org/wiki/Khuzestan_Province