Strikes on Chabahar and Bushehr: what the open-source footage is — and isn't — telling us
Footage circulating on X from southern Iran on 8 July 2026 shows fires and outages in Chabahar, Konarak and Bushehr. The clips are real, but the political chain of command behind them is not — and the gap matters for how the story lands.
At 20:35 UTC on 8 July 2026, an open-source intelligence account on X began relaying reports from people on the ground in Iran: three explosions in Konarak, one in Chabahar. Within ninety minutes the same channel had posted video it said showed fires and power outages in Bushehr, and a separate claim that power had been cut across large parts of Chabahar. By 21:06 UTC the framing on the account — @Osint613 — was explicit: the United States, it said, was "hitting anything that can threaten ships in the Hormuz."
What the public can verify, in the hours after the strikes, is narrower than the feed suggests. The footage is real, the geography is identifiable, and the timing clusters tightly. What remains unverified is the political attribution: who ordered the strikes, against which targets, and under what legal authority.
What the footage actually shows
The video clips posted to X between 20:35 and 21:06 UTC resolve to three identifiable southern-Iranian locations: Chabahar, a port city in Sistan-Baluchestan province on the Gulf of Oman; Konarak, roughly fifty kilometres to the west; and Bushehr, on the Persian Gulf coast, host to Iran's only operating civilian nuclear power plant. The @Osint613 posts describe large fires and power outages in Bushehr, and a separate claim that power was cut across parts of Chabahar following the strikes.
The same account frames the campaign as a maritime-denial operation, with the explicit aim of neutralising Iranian assets that could threaten shipping in the Strait of Hormuz. The phrasing — "anything that can threaten ships in the Hormuz" — is editorial on the account's part, not a quote from any named official. It is a read of intent, not a confirmation of targeting policy.
The attribution gap
No wire service, no U.S. government release, and no Iranian state-media outlet had, as of the timestamps on the thread, publicly claimed or denied responsibility for the strikes. The White House, the Pentagon, and Central Command have not been quoted in the available material. Iranian state media have not been quoted either. In a situation of that kind, the only people putting words on the operation are the same people who broke the video: open-source accounts assembling a picture from posts inside Iran.
That carries real evidentiary weight — the cluster of locations, the clustering of timestamps, the corroborating eyewitness language across multiple posts — and it also carries real limits. Open-source footage can show that something burned. It cannot show who lit the match, or who authorised the match to be lit. The gap between those two claims is the entire policy question.
Why the Hormuz frame matters
If the open-source read is correct — that the United States is systematically degrading Iran's ability to threaten Gulf shipping — this is not a routine tit-for-tat. It is a campaign logic, and the campaign logic is older than 2026. The premise that Iran's anti-ship missiles, fast-attack craft, and naval-mines capability constitute an unacceptable threat to commercial traffic in the Strait has been U.S. policy since at least the 2000s, sharpened under successive administrations. A strike package aimed at the infrastructure that holds that capability together is the operational expression of that premise.
The Chinese and Russian read of the same policy, when it is articulated in their press, is structural: that extra-legal U.S. force projection in the Gulf is the enforcement arm of a dollar-centred financial order, and that the strikes are an attempt to keep Gulf energy flowing through U.S.-controlled chokepoints on terms favourable to Washington. That framing does not have to be true to be influential. It is the framing under which Iran, China and Russia increasingly coordinate their diplomatic language about the Gulf.
What the sources disagree about — and what they do not
The footage and the eyewitness reports are not in serious dispute; the geography is verifiable, the timestamps cluster, the posts corroborate one another. The dispute is downstream. No source in the available thread names the specific targets hit, the ordnance used, the legal basis cited, or the Iranian-casualty figures. The U.S. claim of "anything that can threaten ships" is an account-level interpretation, not an official targeting directive. The Iranian state, in the same window, has not yet put forward its own casualty count or its own list of struck sites, which means the next forty-eight hours of wire reporting will be doing the work the open-source thread cannot: confirming, denying, and locating the political chain of command that produced the strikes.
For now, the picture is a half-picture. The fires are real, the cities are real, the strategic logic of the campaign is legible, and the policy record is empty. That gap — between the operational and the political — is what the next news cycle will have to close.
Desk note: Monexus is treating the @Osint613 thread as open-source material with verifiable geography, not as an authoritative attribution. We will tighten the framing as wire reporting lands; in the meantime, the claim that the United States is striking Iranian coastal infrastructure rests on eyewitness and video evidence, not on an official statement.
Wire provenance
This editorial synthesis draws on the following public wire/social posts:
- https://twitter.com/Osint613/status/2074961390402511276/photo/1
- https://twitter.com/Osint613/status/2074959171577856304/video/1
- https://twitter.com/Osint613/status/2074957900523459025/video/1
- https://twitter.com/Osint613/status/2074956991156342840/video/1
- https://twitter.com/Osint613/status/2074955126003609856