Wire
18:39ZHROMADSKEUProtests continue in the capital and other cities of Ukraine. Protesters demand the return of Fedorov and exp…18:37ZPALESTINECYemeni forces strike Saudi oil infrastructure with drones18:35ZPRESSTVIran expects Russia to deliver 'serious response' to Ukraine's Caspian Sea attack, ambassador says18:34ZOANNTVBryan Kohberger moves to withdraw guilty plea in Idaho murders case18:34ZOSINTLIVEDisruptions expected at Ben Gurion Airport following European air traffic control system malfunction18:34ZOSINTLIVEThree men beat Ukrainian couple in Wrocław over accent, local media report18:34ZOSINTLIVEIsraeli military intercepts drones near Dead Sea, downs another over Hermon18:34ZOSINTLIVEBelgian authorities arrest woman interning at NATO Supreme Headquarters
  • S&P 500 ETF 0.19%
  • Nasdaq 100 0.94%
  • Japan ETF 0.10%
  • Europe ETF 0.28%
Terminal ↗
← The MonexusMena

Strikes land across southern Iran: what the first reports actually say

Explosions were reported in Mahshahr, Bandar Abbas and Sistan-Baluchestan within minutes of each other. The picture is incomplete, and the sourcing runs almost entirely through Iranian and Iranian-aligned channels.

Explosions were reported in Mahshahr, Bandar Abbas and Sistan-Baluchestan within minutes of each other.
Explosions were reported in Mahshahr, Bandar Abbas and Sistan-Baluchestan within minutes of each other. x.com / Photography

Within six minutes on the evening of 12 July 2026, the open-source wire moved from one explosion report to four. At 22:04 UTC the Telegram channel Intelslava flagged a blast in Mahshahr, in Iran's Khuzestan province. A minute later PressTV, the Iranian state broadcaster's English-language outlet, said several blasts had hit the southeastern province of Sistan and Baluchestan and tied them to US strikes. At 22:06 UTC the War and Witness channel posted footage it said showed the aftermath of a strike in Bandar Abbas, the major port on the Strait of Hormuz. By 22:10 UTC Intelslava had logged a second blast report inside Sistan and Baluchestan.

The sequence reads less like a single event than a rolling wave of reports from a theatre that is still unfolding. Until independent confirmation arrives, the dominant frame in Western wire services will be cautious: strikes reported, scale unknown, Iranian state media asserting US involvement. Monexus finds that the sourcing here is the story. Almost every datapoint on the open wire right now travels through Iranian state outlets or channels that explicitly cite Iranian state outlets, which means the burden of verification sits unusually heavily on the next twelve hours.

What the four reports actually say

The earliest item, from Intelslava at 22:04 UTC, is the thinnest: an explosion in Mahshahr, attributed to US action, with no detail on damage, casualties or the type of ordnance. Mahshahr sits on the northern Gulf, inside a petrochemical belt that includes the Shahid Hasheminejad gas processing complex and several large refineries. Strikes against energy infrastructure in this corridor carry immediate consequences for Iranian crude exports and for the traffic through the Strait of Hormuz.

PressTV's bulletin one minute later is more expansive and more partisan. It claims "several blasts" across Sistan and Baluchestan, the province that runs along Iran's southeastern border with Pakistan and Afghanistan, and frames the events as the consequence of US strikes. The province hosts the Chabahar port complex and large IRGC ground force deployments, and it is also the heartland of the Baluch minority, where separatist and Sunni insurgent activity has long simmered. Iranian state outlets have, in past episodes, used such moments to consolidate nationalist framing inside the country.

The third item, from War and Witness at 22:06 UTC, is the first to carry visual evidence. The channel posted footage purporting to show the aftermath of a strike in Bandar Abbas, on the northern side of the Strait of Hormuz. Bandar Abbas is home to the IRGC Navy's main base, the bulk of Iran's conventional naval tonnage, and a commercial port that handles the majority of the country's container traffic. A strike there is not a symbolic act. Intelslava's 22:10 UTC report of a second blast inside Sistan and Baluchestan pushes the count of reported strike sites to at least three distinct locations across roughly 1,000 kilometres of Iranian territory.

The sourcing problem, named plainly

The corroboration chain here runs through channels that, on the editorial compass used by most Western outlets, sit closer to the Iranian government than to independent verification. PressTV is an outlet of the Islamic Republic. Intelslava and War and Witness are pro-Iran or Iran-sympathetic open-source channels whose value is speed; their editorial control sits with their operators, not with any institutional newsroom. None of the four items cites an Iranian military briefing by name, nor a US Central Command statement, nor an on-the-ground correspondent reporting under their own byline.

That does not mean the reports are false. Open-source channels have, repeatedly during this war cycle, broken tactical detail ahead of official spokespeople on every side. It does mean the reader should hold the picture loosely until Reuters, the AP, AFP, the BBC or a verifiable Iranian or US official speaks on the record. The default Monexus position is to treat Iranian state-adjacent reporting as the start of an investigation, not its conclusion, and to weight any Western wire pickup accordingly when it arrives.

Why these three sites, and not others

Geography does most of the analytical work. Mahshahr sits on the energy corridor. Bandar Abbas sits on the naval and shipping corridor. Sistan and Baluchestan sits on the land corridor that connects Iran to Pakistan and, beyond it, to the China-backed deep-water port of Chabahar. A simultaneous strike set across all three would not be a punitive pinprick. It would be an attempt to degrade, in a single window, Iran's capacity to export hydrocarbons, to threaten shipping through Hormuz, and to project force along its southeastern frontier.

That profile is more consistent with an escalation aimed at deterrence than with a retaliatory cycle. US strikes on Iranian nuclear and IRGC facilities in June were, in the public framing from Washington, meant to set back specific programmes. Strikes across the energy, naval and land-corridor triad would be doing something different: signalling that the United States is willing to impose strategic costs that take years to reverse. Whether the reporting tonight points to a coordinated multi-site package or to a looser sequence of opportunistic hits is the question the next hours of reporting will need to settle.

What we do not yet know

The reporting as it stands is silent on casualties, on the specific facilities hit, on the weapons used, and on whether the US government has acknowledged the strikes at all. PressTV's framing asserts US authorship; the two Intelslava items frame the events as US action; War and Witness presents footage without naming the actor. Iranian opposition channels inside Iran are, for now, unable to publish freely, which means the gap left by state media is not being filled by independent Iranian voices. Regional wires have not, as of the timestamps above, carried the story. Until they do, the map of what happened tonight is drawn mostly in one colour, and the prudent read is that the picture is real but incomplete.

Desk note: Monexus is running this on an Iran-event wire, attributing only to the channels that reported the items and flagging PressTV's state affiliation in line with our standing sourcing rules for Iran-regime outlets. The next update will fold in Reuters, AP, AFP and BBC confirmation as it lands.

Wire provenance

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

  • https://t.me/intelslava
  • https://t.me/presstv
  • https://t.me/wfwitness
  • https://t.me/intelslava
Intelligence ThreadFollow on terminal ↗
© 2026 Monexus Media · AI-native reporting from public-source material