13JUL

Iran fires back across the Gulf again

2 min read

10:50UTC

Kuwait intercepted Iranian missiles and drones on 14 July while Bahrain sounded air-raid sirens, and Iran's strikes again reached Jordan after the blockade order.

← Back to Iran declares Hormuz closed; US says open Jump to analysis ↓

ConflictAssessed

Key takeaway

Iran's Gulf-wide barrage now answers the blockade order itself, while its US-base destruction claims stay unconfirmed.

Kuwait reported intercepting Iranian missiles and drones on 14 July while Bahrain sounded air-raid sirens, and Iran's strikes again reached Jordan ¹. The reprisal cycle itself is familiar: Iran fired on Azraq air base and three Gulf states on 9 July , answering CENTCOM's earlier 90-target wave.

This barrage followed the blockade order and the fourth strike night rather than another round of CENTCOM sorties, which ties Iran's Gulf-wide retaliation directly to the enforcement move. Iranian domestic outlets went further, claiming the IRGC destroyed US positions at Camp Arifjan and Ali Al Salem in Kuwait and at Juffair and Sheikh Isa in Bahrain ².

No US or Gulf source has confirmed any such hit, and the same Farsi coverage frames the war as a mutual exchange in "southern waters and military centres" while omitting the blockade entirely. The claim sits with a long run of unverified IRGC base-strike boasts, and it is recorded here as an assertion, not a fact.

Deep Analysis

In plain English

Every time the US tightens the blockade, Iran fires back at the Gulf countries hosting American bases rather than at US forces themselves, letting Tehran show retaliation without directly provoking the kind of response that would follow an attack on American troops.

Deep Analysis

Root Causes

The retaliation follows the escalation ladder Iran has run since early June: each CENTCOM strike on Iranian territory or the reinstated blockade is answered with missile and drone fire against the Gulf states hosting US forces, Kuwait's Ali Al Salem and Bahrain's Fifth Fleet headquarters among the recurring targets, rather than against US assets directly.

Jordan's repeated inclusion, despite having no coastline on the strait, reflects its symbolic role in Iran's response pattern rather than any direct Hormuz stake, extending the template set on 9 July.

Escalation

Sideways for now: Iran is hitting Gulf host states rather than US forces directly. The trigger to watch is whether the IRGC's claimed strikes on US positions in Kuwait and Bahrain are ever verified, which would remove that calibration.

What could happen next?

Risk
If the IRGC's claimed strikes on US positions in Kuwait and Bahrain are later confirmed, the calibrated pattern of hitting host states rather than American forces breaks down, raising the odds of a direct US response.

Source Landscape

This story draws on mixed-leaning sources from Qatar

Qatar

Primary parallel: Jordan's 9 July inclusion, ten missiles at Azraq air base alongside strikes on Bahrain, Kuwait and Qatar, set the template this 14 July retaliation repeats: a blockade-linked strike answered by fire against multiple Gulf host states in a single day.

Counter-parallel: The 28 June salvo on Kuwait's Ali Al Salem base and Bahrain's Fifth Fleet headquarters triggered a US verbal stand-down within a day, showing this pattern has previously produced de-escalation rather than further strikes, an outcome not yet visible this time.

Consensus view: IISS regional assessments have tracked a widening pattern since Jordan's 9 July Azraq strike: each CENTCOM enforcement action against the blockade has produced a matching Iranian salvo against Gulf host states rather than against US forces directly.

Counter-view: IRGC-aligned Iranian media has framed the claimed strikes on US positions in Kuwait and Bahrain as legitimate military successes, a framing this reporting notes remains unconfirmed by any independent source.

Key tension: Whether Iran's Gulf-wide retaliation is calibrated to signal capability without triggering direct US-Iran confrontation, or whether the unverified base-strike claims indicate an intent to escalate that has simply not yet succeeded.

Sources:Al Jazeera·Entekhab

Mentions:Iran →Kuwait →Bahrain →Jordan →Islamic Revolutionary Guard Corps (IRGC) →Camp Arifjan →Juffair →IISS →Qatar →Tehran →Washington →CENTCOM (US Central Command) →

First Reported In

Update #154 · US enforces Hormuz closure with blockade

Al Jazeera· 15 Jul 2026

Read original →

Causes and effects

Caused by

Iran hits Jordan and three Gulf states

The 14 July Gulf retaliation extends the 9 July Azraq/Gulf-states strike cycle, this time tied directly to the naval blockade.

Occurred 9 Jul 2026

Read story →

This Event

Iran fires back across the Gulf again

Iran's retaliation now tracks the blockade order and strike nights directly, tying its Gulf-wide fire to Washington's enforcement move rather than a fresh sortie.

Different Perspectives

Oil market and P&I insurers

Brent cleared $87 intraday only once CENTCOM's blockade became physical rather than declared, even though P&I Clubs had already excluded Hormuz war risk a week earlier on 7 July: capital hedged ahead of enforcement, but prices moved only after it.

UAE reporting

UAE reporting placed the Omani tanker deaths at one seafarer against the International Maritime Agency's count of two, the first time in this war that a Gulf state's casualty figures have diverged from an international monitor's.

Jordan

Iranian strikes reached Jordan again on 14 July as part of the Gulf-wide retaliation for the Hormuz blockade, extending the conflict's geographic footprint to a state with no direct stake in the strait itself.

Bahrain

Bahrain sounded air-raid sirens on 14 July during Iran's Gulf-wide retaliation, the same day CENTCOM's blockade order and fourth night of strikes pushed the conflict's physical reach into the wider Gulf littoral.

Kuwait

Kuwait intercepted Iranian missiles and drones on 14 July as Tehran's blockade retaliation reached Gulf states beyond Iran's immediate shoreline, confirming Kuwaiti airspace now sits inside Iran's retaliatory envelope.

Oman

Oman absorbed the war's first tanker casualties in its own waters on 14 July, with two supertankers disabled and seafarers killed, putting the sultanate's shipping lanes directly in the path of the blockade fight for the first time.