Iran–Gulf developments — 27 September 2026
Both routes out of the Gulf for Saudi crude were working again by the end of the week, and neither was in a condition a market would call normal. In the Strait of Hormuz, vessels were struck on 21 and 23 September — one cargo ship set on fire and abandoned — while tracked traffic fell to seventeen transits over a weekend and what did cross was mostly Saudi state crude under escort. No war-risk cover was found written, and the navigation ministerial postponed on 13 September did not reconvene. The east–west pipeline was reported restarted on 22 September at a low rate, on unnamed sources, with no statement from the ministry or the operator. Houthi missiles and drones were directed at Riyadh, Taif, Yanbu and Khamis Mushait. Saudi Arabia reported every one of them intercepted. The response came through three channels, none of them the Gulf Cooperation Council. Britain and France committed defensive support bilaterally, France to guard the Yanbu terminal the pipeline feeds. And the Makkah Agreement held its first consultation: the three chiefs of staff met in Riyadh on 25 September. That is movement from undertaking toward mechanism. It is not an invocation, and no contribution was named. Between Washington and Tehran, the first mediated talks in months on 22 September were followed by an Iranian offer to reopen the strait within seven days on conditions, reported rejected on 26 September. The nuclear lane was otherwise quiet.
The developments
The strait was struck twice in three days, and what still crosses it is state cargo, not a market
UKMTO reported on 21 September that an inbound tanker in the Strait of Hormuz was struck by an unknown projectile, leaving two crew with minor injuries, and that an LPG tanker was hit by debris from unknown projectiles the same day; both continued under their own power. A security firm identified the first as a UK-flagged tanker hit by a drone. On 23 September UKMTO reported a cargo vessel struck by an unknown projectile in the strait, left on fire and adrift, with all crew evacuated and two casualties reported without saying whether killed or injured. No party claimed any of the strikes and no position was published. Kpler and LSEG counted 17 commodity vessels through the strait on the weekend of 19–20 September against 37 the weekend before, against about 125 a day before the war, and trackers note that tankers running with transponders off are outside those counts. Saudi escorted loadings inside the Gulf continued: Kpler data showed six very large crude carriers loading nearly 12 million barrels at Ras Tanura and Juaymah on 21 September, and Saudi Hormuz-route exports of about 42 million barrels in the week of 13 September. No war-risk cover was found written on terms charterers take up, no change to listed areas was identified, and the Salalah ministerial on a navigation arrangement, postponed on 13 September, had not reconvened and published nothing by 26 September.
Why it matters. Held apart, the three accesses still move in different directions, and this week the physical one moved the wrong way. Legal access did not move. No meeting sat and no text appeared. Commercial access did not move either: no cover, no uptake, and that is the condition that emptied the water in March. Physical passage was contested again inside the strait itself. Two strike days in three and a ship abandoned are the kind of facts that keep underwriters where they are. What makes the week readable is the traffic count. Visible transits halved in a week while Saudi state loadings carried on, so the water is being used by the actor with a navy alongside it and avoided by the ones without. That is the opposite of a market judgment that the risk has fallen, and it is why this module records the strait as more used and still closed. The pipeline restart that followed on 22 September gives Saudi crude a second exit again. It does nothing for Kuwait, Qatar or Iraq, which have none. What this item does not establish is who fired on the three ships. No party claimed them and no authority attributed them, and the module records none.
- Tanker Hit by Projectile in Strait of Hormuz, UKMTO Reports
- UK maritime agency says Hormuz tanker hit by debris from projectiles
- Projectile strikes cargo vessel in Hormuz
- Tankers go dark in Strait of Hormuz, visible traffic falls by more than half
- Six VLCCs load nearly 12 million barrels at Ras Tanura amid Hormuz disruptions
The pipeline is reported running again, and the only people who have not said so are the ones who run it
Reuters reported on 22 September, on three sources briefed on the matter, that Saudi Arabia had restarted the east–west pipeline that day and that it was pumping at a low rate, with one cargo scheduled to load at Yanbu for China; a security source said full resumption could take weeks. Wire coverage the same day put a 40 per cent rate within days and a full restart at six to eight weeks. Maritime Executive, citing Bloomberg, the Financial Times and commercial satellite imagery, described a shunt laid around a damaged pumping station, three stations damaged, and up to six weeks to restore nameplate capacity. The capacity figures differ by source: a line of up to 4 million barrels a day in the Reuters account, 7 million nameplate in the other. Reuters dates the shutdown to 11 September; the Ministry of Energy's announcement was of 10 September. Brent fell by more than two dollars on the day. No Saudi ministry or Aramco statement of the restart, its rate, a timeline or a damage assessment had been published by 26 September. The Houthi movement claimed strikes on Aramco facilities at Yanbu on 24 September; the coalition said it intercepted six ballistic missiles fired at Taif and Yanbu, and no damage was reported by anyone but the movement.
Why it matters. Twelve days after the Hormuz alternative was cut at its middle, oil is reported moving west again, and last week's three incompatible repair timetables have been overtaken by a fact rather than settled. The module records the restart and nothing more. "Low" is the only rate any source gives. The percentages are estimates by people who do not run the line, and the capacity arithmetic this record has carried since the baseline is unchanged: a 2019 design ceiling, a Yanbu terminal estimated near three million barrels a day in wartime, and domestic refinery offtake before export. The standing question asks whether the fixed nodes are being restored faster than they are re-struck. This week the answer is a reported restoration against a strike side that was a covered zero at the published markers. The Yanbu claims met Saudi reports of interception, and the module counts neither the claims nor the interceptions. The observable itself is not met. It asks the ministry or the operator to state a restart, a rate or a damage assessment, and a restart that is reported rather than announced is exactly what that wording exists to keep apart.
Radio Pakistan announced on 23 September that retired Lieutenant General Nauman Mahmood had been appointed the first Secretary General under the Makkah Joint Defence Agreement, heading a General Secretariat being established in Riyadh; Pakistani reporting places the decision at the Istanbul committee of 31 August. On 24 September the foreign ministers of Saudi Arabia, Pakistan and Türkiye met on the sidelines of the United Nations General Assembly. They condemned "the heinous attacks targeting the holy city of Makkah" and affirmed the kingdom's right of self-defence under Article 51. They agreed to convene their chiefs of staff to explore ways to assist Riyadh under the agreement, which Türkiye called technical negotiations. On 25 September the three chiefs met in Riyadh. Their statement, issued by Pakistan's military and confirmed by the Saudi defence minister, resolves to begin immediately translating the agreement's commitments into effective military cooperation. It names intelligence cooperation, military coordination and the integration of defence capabilities. No invocation, contribution, operation, command arrangement or procedure was announced. The Associated Press had reported on 16 September that Turkish and Pakistani officials had received no Saudi request under the agreement.
Why it matters. For seven weeks this agreement had an undertaking and institutions on paper, and through the heaviest attacks on a signatory of this round it produced statements of intent only. This week it produced its first act in its own name: a named Secretary General and the three chiefs in the capital under attack, meeting expressly to examine assistance under the agreement. That is a real step on the ladder from commitment to mechanism and the standing assessment has been advanced to record it. It is also exactly one step. The ministers grounded Saudi action in Article 51, a state's own right, not the agreement's. The chiefs named areas of cooperation, not a contribution. Nothing published says what the agreement owes, who decides it or on what threshold. Pakistani reporting that lists liaison officers, joint planning cells and air-defence specialists describes what could come next, not what was agreed. The module's standing question has always asked for an act, and this is the first. What separates a consultative forum from a collective-defence mechanism is still unobserved: a contribution named as made under the agreement, or a signatory saying it has invoked it.
- Pakistani, Saudi, Turkish military chiefs meet to discuss ways to assist Riyadh under Makkah defence pact
- Makkah pact military chiefs vow immediate implementation of defence commitments
- Lt Gen (retd) Nauman Mahmood appointed first Secretary General of Makkah Joint Defence Agreement
- Pakistan, Turkiye edge closer towards joining Saudi war against Houthis
- Saudis seeking allies' help in fight with Houthi rebels
Houthi fire reached Riyadh, and the help that arrived came from London and Paris, one state at a time
The Saudi-led coalition said it intercepted a ballistic missile fired at Riyadh at dawn on 19 September; a Reuters eyewitness saw flames and smoke near King Khalid International Airport. The movement claimed "sensitive sites" in Riyadh and Aramco facilities at Yanbu. On 24 September the coalition reported six ballistic missiles fired at Taif and Yanbu shot down. On 26 September it reported two drones directed at Riyadh and two ballistic missiles at Khamis Mushait shot down. The Gulf Cooperation Council's Secretary-General condemned the attacks and named no collective measure. Found late, and dated to when they happened: the coalition said on 15 September that it had downed a drone south of Mecca, which the movement called a lie, and Saudi state television reported on 17 September the first civilian death of this round, from drone debris over Taif. The Associated Press reported on 16 September that Saudi Arabia had asked France, Britain, Pakistan and Egypt for air-defence support as its interceptor stocks ran low, and that the United States showed no interest in renewed military involvement. On 21 September the British Prime Minister announced Royal Air Force air-to-air refuelling for Saudi aircraft on defensive missions, for several weeks and under review. On 24 September President Macron said France would send "soldiers, radar systems and defense systems" to protect Yanbu, "not to get us involved in any conflicts". Italy's defence minister had announced on 18 September a national deployment of warships to protect Italian shipping through Bab el-Mandeb.
Why it matters. The attacks changed in reach, not in kind. Every Saudi account is of interceptions, and the module records no damage in Riyadh or at Yanbu that any party other than the movement has stated. What the week clarified is the architecture of the answer. The Cooperation Council condemned. The Makkah partners consulted. The support that was actually committed was bilateral and European and defensive. A tanker aircraft and a guard for one terminal are small, deliberate commitments, each bounded by the government making it. The French one is tied to the terminal the restarted pipeline delivers to, which is the clearest statement yet of where outside governments locate the exposure. None of it is a Cooperation Council act, and none of it touches the question of integrated Gulf air defence, which remains without a shared picture, warning system or rules of engagement. The southern strait again showed no independently observed interference with non-Saudi shipping from the Houthi-held shore. That is the third window in a row, and Italy's announcement is not yet an operation.
- Saudi coalition says it intercepted Houthi drones and missiles bound for Saudi Arabia
- Saudi Arabia confirms Yemen's Houthi rebels tried to attack its capital with a ballistic missile
- Five killed as Saudi Arabia and Yemen's Houthis trade attacks
- U.K. to offer Saudi Arabia aerial refueling to counter Houthi attacks
- France to send military to protect Saudi Arabia on Red Sea oil route, Macron says
- Gulf Cooperation Council condemns Houthi missile, drone attacks on Saudi Arabia
- Italy to deploy warships to protect shipping through Bab al-Mandeb
Washington and Tehran talked through mediators, Iran offered the strait for a ceasefire, and the offer was refused
On 22 September United States envoys and Iran's foreign minister held their first mediated shuttle talks in months on the sidelines of the General Assembly, through Qatar and Oman, on ending the war and reopening the Strait of Hormuz; the United States president called the meeting very productive. On 25 September Iran's foreign minister proposed a seven-day ceasefire in which the strait would reopen on conditions — frozen assets released, oil sanctions and the naval blockade lifted — with talks on a final deal to follow. On 26 September the Wall Street Journal reported that the president had rejected the proposal and told aides he expects a new bombing campaign after the November midterm elections, and he was quoted rejecting it. Found late and dated: on 19 September a senior Iranian official said Iran's conditions had been passed to Washington through Qatar.
Why it matters. The strait is the subject of this module, and for the first time in months it was on a negotiating table rather than only in a war — offered by the party that closed it, as the price of a ceasefire. That is the week's clearest statement of what Iran thinks the strait is worth, and the refusal is the clearest statement of what Washington thinks the offer was worth. Neither changes the water: no régime was agreed, no cover was written and the vessels struck on 21 and 23 September were struck while the talks ran. What would separate a channel from a process is a second round with a schedule, or an arrangement that survives a strike.
Where this fits
This is one conflict's dated review for the week. The cross-conflict edition for the same week carries the most consequential findings from every conflict Vigil covers. The standing picture this review updates is the Iran–Gulf coverage. How Vigil grades, dates and sources its claims is set out in the methodology, and anything later found wrong is recorded in the corrections log.
By email Get Vigil’s Weekly Briefs and new Analytical Notes by email. What Vigil Dispatch sends
← Previous Iran–Gulf brief — 2026-09-20Every Iran–Gulf review All weekly briefs