Bandar Abbas on fire: what we know about the reported US strikes on southern Iran

Plumes of smoke climbed over the southern Iranian port of Bandar Abbas shortly before 22:00 UTC on 12 July 2026, captured on camera and circulated across Telegram channels that had spent the previous hour reporting blasts in and around the city. By 22:45 UTC, one of those channels was claiming an explosion near Bandar Abbas airport; two hours later, another said possible new blasts were still being assessed. No major Western wire had publicly confirmed the operation by the time this article went to press.

What the open-source record shows, for now, is a coordinated series of reported US strikes on Iranian military and communications infrastructure along the Persian Gulf coast, with follow-on explosions reported in Ahvaz further inland. The pattern, if the preliminary accounts hold up, points at the kind of target package that has been on the open-source watchlist in the Gulf for years: the Strait of Hormuz naval posture, IRGC facilities guarding the approaches, and the cellular and radar backbone that Iranian commanders rely on to coordinate retaliation.

What the channels actually carried

At 21:51 UTC on 12 July, the open-source intelligence feed Intelslava reported "heavy US strikes" on Bandar Abbas, attributing the operation to US forces without naming platforms or weapon types. Three minutes later, a channel called FotrosResistancee posted footage of smoke coming from a site in the city, and added a second claim: that a communications tower in Sirik, hit multiple times before in earlier reported exchanges, had been struck again. Sirik sits south-east of Bandar Abbas along the Makran coast and houses naval and missile infrastructure.

By 21:58 UTC, Iranian state outlet PressTV was running its own push notification: "several explosions heard in southern Iranian city of Bandar Abbas," with footage of smoke rising from a struck site. The fact that Iran's own state media was carrying the story within seven minutes of the initial reports is itself worth noting. Iran's domestic audience was being told, in real time, that the strike had happened.

At 22:04 UTC, the channel World Footage Witness put out a second piece of reporting from inside Iran: initial reports of explosions in Ahvaz, a city of roughly 1.3 million residents about 800 kilometres north-west of Bandar Abbas, alongside the footage already circulating from the gulf. Twenty-three minutes after that, GeoConfirmed Watch posted renewed explosions in Bandar Abbas. At 22:45 the same channel added a fresh note about a blast near the airport of Bandar Abbas, an airport that sits inside a city that hosts the IRGC Navy's main operating base. By 00:08 UTC on 13 July, GeoConfirmed Watch was still pushing preliminary claims of additional blasts.

The geographic spread is the part that needs to be made explicit. Bandar Abbas is not just any city. It is the headquarters of the IRGC Navy, the port that flanks the western mouth of the Strait of Hormuz, and the staging ground for Iranian fast-boat operations against commercial shipping. To hit it, and then to be reported hitting something in Ahvaz, a city dominated by oil and gas infrastructure, suggests a target set that is broad enough to be uncomfortable for the official line that this is a constrained counter-terror action.

Why Ahvaz matters more than it looks

The decision, if the reporting holds, to extend strikes beyond the Gulf coast to Ahvaz is the most consequential element in the overnight's reporting. Ahvaz is the capital of oil-rich Khuzestan province and the hub of operations for the National Iranian Oil Company and the South Pars gas complex downstream. Striking infrastructure there would open a new front in any campaign aimed at degrading Iran's revenue stream and military reach.

It is also the kind of escalation that would not happen by accident. The pattern of earlier US operations against Iranian proxies and Iranian assets inside Iran has been to hit the IRGC's Quds Force infrastructure, the missile silos in Khorasan, and the drone production facilities around Isfahan and Shahid Moghaddasi. Hitting Khuzestan infrastructure is qualitatively different. It puts at risk the civilian energy system on which Iran's domestic grid, and the gas flows that feed large parts of the regional power grid, depends.

The sources available to Monexus do not specify which targets in Ahvaz were hit, nor whether the second wave represents a deliberate broadening of operations or a separate intelligence-driven package. What can be said is that the reporting of fresh blasts in two Iranian cities less than 800 kilometres apart, within ninety minutes of each other, would be operationally consistent with a pre-planned, multi-axis first strike rather than a single dramatic event.

Where the Hormuz logic lives

The underlying strategic argument for any strike package of this shape is well-rehearsed in open-source defense analysis. Iran retains a layered threat to commercial shipping in the Hormuz transit, a chokepoint through which roughly a fifth of global seaborne oil typically passes. Anything that meaningfully degrades Iranian maritime and air defences lowers the expected cost to Western naval forces that would have to escort commercial tankers through the strait in a sustained crisis.

What changes in 2026 is that the US posture in the Gulf has been visibly hardening for several months, with forward-deployed air defence systems, additional combat aviation and maritime assets, and a steadily more aggressive information campaign around Iranian weapons transfers to its regional proxies. The strikes Monexus is tracking appear to sit inside that trajectory, not as a one-off reaction to an incident.

What makes the Bandar Abbas package politically more dangerous for Washington than previous Iranian-targeting operations, however, is what follows the first strike. A US president can order a single decisive hit and sell it to allies as a discrete counter-terror action. It is much harder to sell a campaign of strikes across Iran's coastal and oil heartland as anything other than the opening of a major new war in the Middle East. The reporting available as of this publication suggests the operation has already begun to look like the latter.

The information fight has already started

Almost as fast as the explosions were reported, so was the framing. PressTV's confirmation that the strikes had landed was paired, in the same brief window, with unattributed footage inside the channels that already had a stake in showing the strikes as either legitimate defense or illegitimate aggression. Iranian state media will follow its usual playbook: civilian harm amplified, foreign aggression at the centre of every bulletin, and an implied threat of retaliation.

The Western wire silence, by contrast, is conspicuous. Reuters, AP, the BBC and the Pentagon had not, as of 00:30 UTC on 13 July, published confirmations or denials of the strikes Monexus is tracking. That silence can be read two ways. It can be operational: strikes inside Iran are not being confirmed, or denied, from the podium for security reasons while the package is still in motion. Or it can be political: a degree of caution about premature confirmation while the political cost of what has been done is still being absorbed in Washington, Tehran, and the Gulf capitals.

Monexus readers should treat every claim about damage, target type, platform used and casualty count as preliminary until a Western wire or a US or Iranian government readout is published. The geographic spread is real, the time signature is consistent, and Iranian state media itself is acknowledging the events. Beyond that, the open-source record needs what every responsible correspondent should demand at a moment like this: corroboration, attribution, time.

What the morning will decide

The next twelve hours will shape the story much more than the past twelve have. Two signals will matter most. First, whether the Pentagon and US Central Command publish a substantive readout and accept political ownership of the strikes. A no-comment posture past first light in Washington would harden the sense that this is an operation the administration is still deciding whether to confirm. Second, whether Iran's retaliation is confined to information operations and proxy actions, or whether Iranian forces move on a US or allied target directly.

What Monexus can say now, with the sources it has, is the geography: two large Iranian cities hit, on the same night, in a target pattern consistent with degrading Iran's ability to threaten shipping in the Gulf and to disrupt regional energy supply. What Monexus cannot yet say is the casualty count, the platforms used, or the political framing the strike will be sold under.

How Monexus framed this versus the wire: this article surfaces open-source reporting from Telegram channels and Iranian state media during the first hours of an unfolding military operation, holding back from any casualty claims or target-identifications until they can be sourced. The wire silence is itself the story.

Wire provenance

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

• https://t.me/intelslava
• https://t.me/FotrosResistancee
• https://t.me/presstv
• https://t.me/wfwitness
• https://t.me/GeoPWatch
• https://t.me/intelslava
• https://t.me/GeoPWatch
• https://t.me/GeoPWatch
• https://t.me/GeoPWatch