Skip to content
You can now search across every topic, entity and event.What's new
Iran Conflict 2026
21JUN

Iran fires back across the Gulf again

2 min read
17:51UTC

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 Hormuz shuts as Vance flies to GenevaJump 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 1. 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 2.

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.

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 →
Artesh claims Kuwait and Bahrain strikes
The Army's named Operation Saeqeh phase 10 followed the 14 July Gulf-wide retaliation.
Occurred 15 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.
Led to
IRGC sets Kuwait's Shuaiba complex alight
The 14 July Gulf-wide retaliation against Kuwait, Bahrain and Jordan precedes the 17 July Shuaiba strike on Kuwait.
Occurred 17 Jul 2026
Read story →
Bahrain says it thwarted a missile wave
Bahrain's thwarted attacks extend the Gulf-wide retaliation pattern first seen 14 July.
Occurred 18 Jul 2026
Read story →
Different Perspectives
Hengaw
Hengaw
The Norway-based monitoring group reported the Urmia executions of Omid Behzad and Pouria Safvat, the only source to do so, consistent with its documented pattern of recording far more executions than the Iranian state acknowledges. Iran's government has not confirmed either execution.
Shipping and insurance underwriters
Shipping and insurance underwriters
War-risk premiums price the Houthi campaign because the group announces its targets in advance, but a reopening Trump has promised without a published text gives underwriters no benchmark to reprice Hormuz cover against. Insurers want a text before they move rates, not a promise.
Houthi movement
Houthi movement
Spokesman Yahya Saree claimed strikes on two tankers in the Red Sea and Gulf of Aden on 5 August, only one of which UKMTO could confirm. The group's campaign against shipping continues on its own schedule, independent of any Hormuz arrangement further north.
Oman
Oman
Muscat has brokered the coordinates both Tehran and Washington's wire sources now describe differently, but has published no account of its own. Oman's position depends on treating Hormuz as a shared route, which is not what Iran is currently describing.
United States Central Command
United States Central Command
CENTCOM raised its interdiction tally from 35 to 44 redirected vessels and disclosed its first boardings on 3 August, the day before Trump promised a reopening. The command's own enforcement record does not yet reflect the release the President has described.
Iran's Foreign Ministry
Iran's Foreign Ministry
Spokesman Esmaeil Baghaei described the agreed Hormuz coordinates as a wholly new corridor under Iranian management, not a split of the existing route, days after his own deputy rejected Oman's lane proposal. Tehran wants the arrangement read as a change of ownership, not a compromise on access.