Skip to content
You can now search across every topic, entity and event.What's new
European Oil Markets
18JUN

Iran fires back across the Gulf again

2 min read
12:45UTC

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 Russia cliff landed while screens sold IranJump to analysis ↓
EconomicAssessed
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
Gulf oil producer
Gulf oil producer
Secured OPEC's confirmed 188,000 b/d September increment with the next meeting set for 6 September, but the Secretariat's own 2 August release says nothing about the fourth quarter. Output guidance beyond September remains undisclosed even as delegate sourcing keeps filling that gap.
Money manager positioned in WTI
Money manager positioned in WTI
Added 21,402 lots to a 108,307 net long in NYMEX WTI in the week to 28 July, against just 1,485 added to Brent's 15,740, a roughly fourteen-to-one split. Conviction sits in the American benchmark even as the European diesel story sets the record.
Indian refiner buying Urals
Indian refiner buying Urals
Bought Russian crude at a discount that narrowed to $1-2 a barrel in the week to 29 July from over $10, as Hormuz risk pushed it toward Urals. If that risk eases with the strike now called off, the discount it is currently enjoying could re-widen just as fast.
Russian diesel exporter
Russian diesel exporter
Novak tied any lifting of the diesel export ban, due to lapse 31 July, to an unspecified market recovery with no date, and pushed the gasoline ban to end-2026. An open-ended constraint suits an exporter benefiting from the record European crack it feeds.
War-risk underwriter
War-risk underwriter
Withdrew war-risk cover for Saudi-linked hulls on 24 July and has not reinstated it, holding Bab el-Mandeb tanker transits near 7.5 a day. A cancelled strike does not by itself trigger the committee review needed to re-accept the class.
Northwest European refiner
Northwest European refiner
Sources only 17% of diesel imports from Saudi Red Sea ports against the Mediterranean's 24%, so the ARA crack at $85.86 trails the Med print by $5.81. Lower Red Sea exposure is cushioning it against the rerouting cost, not eliminating it.