US strikes hit Bandar Abbas as Washington opens a new direct phase against Iran

At 06:18 UTC on 9 July 2026, India's LiveMint carried a wire filing that would have been unthinkable six months earlier: the United States had completed a coordinated strike package against targets inside Iran, and the Pentagon had released videos showing weapons striking 90 separate aim points. The location of one confirmed strike cluster, Bandar Abbas on the Persian Gulf coast, places this round inside the operational footprint of an exchange that Washington has framed as direct rather than proxy.

What is now described by US officials as a completed opening phase began with strikes on infrastructure tied to Iran's missile, drone, and naval forces along the southern coast, and ended, at least for now, with the targeting of facilities associated with the Islamic Revolutionary Guard Corps. The campaign's stated objective, denying Tehran the capacity to launch another round of strikes against Gulf shipping and against Israel, is the same objective that defined the indirect phase that preceded it. The method, however, is no longer indirect.

What the wire record actually shows

The visual record released by the US military and circulated by regional outlets includes footage of munitions striking hardened shelters, radar installations, and what US Central Command described as missile-assembly buildings. LiveMint's 06:18 UTC dispatch on 9 July summarised the package as 90 targets struck across multiple Iranian provinces. The locations named in the wire so far cluster around Bandar Abbas on the Gulf coast, with additional sites reported further north.

Bandar Abbas is not an arbitrary target. The port city hosts a major IRGC naval base and is the southern terminus of pipelines that move Iranian crude to the Gulf for export. Striking infrastructure there degrades both Iran's ability to threaten oil tankers transiting the Strait of Hormuz and its capacity to move petroleum revenue through its own coastline. The strike list, as filtered through the released footage, leans heavily on that logic.

Within hours of the strike release, Israeli Defence Minister Israel Katz said the Israel Defense Forces remained "ready and prepared to resume the campaign and to launch a blue-and-white operation in Iran, even for the third time," per a wire post at 17:37 UTC on 9 July. The framing matters: Jerusalem is publicly keeping its own window open, even as Washington has signalled that its first direct round is over.

The shipping war that preceded the strikes

The official justification for the operation is built on a documented escalation at sea. On 8 July, Britain's United Kingdom Maritime Trade Operations authority reported that three tankers in the Gulf were hit by projectiles in a single day, the worst such incident since late April. That reporting, captured in wire accounts at 02:58 UTC on 9 July, set up the case for direct US action.

By 03:31 UTC on 9 July, Reuters was reporting that a Saudi-flagged crude oil tanker had been damaged in the Strait of Hormuz after IRGC missile fire, according to sources cited by wire aggregators. The pattern across 48 hours: a tanker struck here, a tanker struck there, two tankers struck in a single incident, then three. The shipping war stopped being background noise the moment Saudi-flagged hulls began taking hits.

Iran's own public framing has run on a parallel track. State-aligned channels have described the strikes as an act of aggression against Iranian sovereignty and have circulated footage of damage in residential areas of Bandar Abbas. That material should be read as counter-claim with explicit sourcing caveats rather than as the dominant frame. The visible infrastructure damage in the US-released videos is consistent with military sites, not with the civilian imagery being promoted by Tehran.

Why Bandar Abbas, why now

Bandar Abbas's selection is a signal to two audiences at once. To Tehran, it says the United States is willing to put ordnance on the IRGC's naval doorstep rather than on a distant proxy facility in Syria or Iraq. To Gulf monarchies, it says the US is prepared to defend the shipping lanes that move their crude to market, even at the cost of a wider regional war. Both signals are aimed at the same outcome: a recalibrated risk calculation inside the Iranian leadership about the cost of continuing to close the strait.

The shipping data makes the case for urgency. With three tankers hit in a single day in early July and a Saudi vessel damaged in the same window, the insurance market for Gulf transit had already begun to price in the possibility that the indirect phase of the conflict would not hold. Once Saudi hulls were at risk, the political logic inside Washington shifted toward direct action rather than another cycle of attribution games and quiet interdictions.

There is also a precedent argument in play. Two previous rounds of strikes against Iranian-aligned assets, one attributed jointly to Israel and the United States in 2024 and another in late 2025, produced tactical damage but did not stop Iran's pattern of hitting Gulf shipping through proxies and direct IRGC action. The third round, if Katz's language about a "third time" holds, is being sold as the round designed to break the pattern rather than to punish it.

The unfinished campaign

Pentagon language about completing the strikes is doing a lot of work. "Completes" describes what was authorised and flown; it does not describe what comes next if Tehran retaliates by hitting another tanker, another Gulf port, or another Israeli city. The Israeli defence minister's comment on 9 July, that the IDF is ready to launch a "blue-and-white operation" in Iran, is a reminder that Jerusalem reserves the right to act on its own timeline.

Iran's response options are constrained but not exhausted. Tehran can attempt to close the Strait of Hormuz more aggressively, can fire ballistic missiles at Israeli territory, can activate Hezbollah and the Iraqi militias, or can absorb the strikes and wait for the political window in Washington to close. Each option carries a cost that has just gone up.

The world will be watching two data points over the next week. The first is whether the IRGC attempts to hit another Saudi or Emirati-flagged tanker inside the Strait of Hormuz. The second is whether Iran's domestic political space, already strained by a year of indirect war, absorbs another round of public footage of IRGC facilities in ruins. The combined answer will tell us whether Bandar Abbas was a closing chapter or the start of a longer one.

Sources

• LiveMint via Telegram, 2026-07-09T06:18: https://www.livemint.com/news/us-news/us-completes-strikes-against-iran-releases-videos-showing-strikes-on-90-targets-11783576726375
• Unusual Whales via X, 2026-07-09T02:58: https://unusualwhales.com/news/us-revokes-iran-oil-waiv
• Unusual Whales via X, 2026-07-09T03:31: https://unusualwhales.com/news/iran-intensifies-strai
• Unusual Whales via X, 2026-07-09T17:37: https://x.com/unusual_whales/status/2074610616686256600
• PressTV via Telegram, 2026-07-09: https://t.me/PressTV/1442
• Middle East Spectator via Telegram, 2026-07-09: https://t.me/Middle_East_Spectator/14218
• Warfare Witness via Telegram, 2026-07-09: https://t.me/wfwitness/2506
• OSINT Live via Telegram, 2026-07-09: https://t.me/osintlive/8711
• OSINT Live via Telegram, 2026-07-09: https://t.me/osintlive/8712
• Intel Slava via Telegram, 2026-07-09: https://t.me/intelslava/4104
• RN Intel via Telegram, 2026-07-09: https://t.me/rnintel/2299

Desk note: Monexus is leading on wire-confirmed locations and visual evidence, and treating Iranian state-media framing as counter-claim material rather than as the dominant frame, consistent with our standing guidance on conflict-zone reporting in the Middle East.