VIGIL CONSILIUM Search
Context. Not headlines.
Weekly BriefIran–Gulf

Iran–Gulf developments — 13 September 2026

The module's first ordinary review measures against the launch baseline of 4 September, and the thing the baseline said was true of the war's first six months stopped being true in forty-eight hours. Hormuz did not change: the strait stayed physically open, commercially shut and lightly used, with seven transits recorded on 9 September. What changed is everything the region had been using instead of it. On 10 September the Saudi east–west pipeline — the largest Hormuz bypass in existence — was struck by drones the Iraqi government says were launched from Maysan province, and the Ministry of Energy shut it as a precaution. On the morning of the same day, and the day after, the Houthi movement took the last government-held stretch of Yemen's Red Sea coast, including Perim island inside Bab el-Mandeb — the outlet that pipeline delivers to. Neither event closed a waterway and this brief says so plainly; what they did was remove the assumption that Saudi crude has somewhere else to go. Alongside them: the heaviest Houthi attack wave on Saudi territory of this round, which no Makkah signatory answered with the agreement; a further United States–Iran exchange; and the IAEA Board's referral of the Iran file to the Security Council, which changes the forum and not the access.

Published 2026-09-13Reporting window 2026-09-04 → 2026-09-135 developments

The developments

Maritime

The strait did not change, and the week's two developments were about everything else

Legal, physical and commercial access to the Strait of Hormuz were unchanged through the window. No party closed the water and none reopened it; commercial tracking recorded seven vessel transits on 9 September, down from twelve the previous day against a ten-day average of fourteen, and no liquefied natural gas carrier was recorded leaving that day. Protection-and-indemnity cover for Hormuz voyages is still not being written on terms charterers accept, which is the condition that stopped the traffic in March and has not moved since. Iranian state media said on 11 September that foreign ministers of the eight littoral states would meet in Muscat on Monday 14 September, presenting the meeting as the point at which a joint Iran–Oman navigation arrangement would be signed; an Iranian official told Reuters the same week that no signed agreement was expected from it. The meeting falls after this brief's cutoff and nothing about its outcome is stated here.

Why it matters. This module's first lens is the strait because everything else in it is downstream of who can move what through where, and the discipline the baseline set on 4 September is worth restating in a week that did not test it: the strait is not open or closed, it is three separate states that have moved independently all war, and the one that stopped the traffic is commercial. Nothing in the window bears on that. What the window did was attack the alternatives, which is a different problem and one the module has not had to hold before — for six months the honest answer to "what happens if Hormuz stays shut" included a pipeline and a Red Sea route, and this week both of those answers were interrupted. The Muscat table is the live test of the commercial condition and Vigil takes no position on what it will produce: the two Iranian statements about it contradict each other, both are on the record, and the observable is a published instrument, not a meeting.

Confidence: High High for the transit counts, which are commercial vessel tracking and are reported consistently, and for the absence of any change in the cover market, which rests on the same market reporting the baseline used. Moderate for what the Muscat meeting is: its date and participation are stated by Iranian state media and by regional reporting, its intended output is described in two incompatible ways by Iranian sources, and no Omani or Gulf Cooperation Council announcement of an agreement text has been identified. No forecast of the meeting's result is offered.
Territorial change

The Yemeni side of the second strait changed hands, and the strait stayed open

The Houthi movement took the port of Mokha at dawn on 10 September and over the following day Dhubab, the coastal villages south of it, Perim (Mayyun) island inside Bab el-Mandeb and Zuqar in the Hanish group — the last government-held stretch of Yemen's Red Sea coast. The Presidential Leadership Council's vice chairman, Tareq Saleh, said he had ordered a strategic retreat and the formation of an alternative command centre, and reporting places a remaining government force on the Hanish islands. A Houthi politburo member stated that navigation and trade in the Red Sea and Bab el-Mandeb are safe and orderly and that the exception remains Saudi shipping; a Houthi commander said the strait could be considered under the movement's administration, and Al Jazeera reported no official announcement of control over the strait. One count put transits at twelve on the evening of 10 September against twenty-nine or thirty normally. No independently observed interference with non-Saudi shipping from the new positions has been identified.

Why it matters. Physical access to the strait changed hands; passage through it did not close, and the module keeps those apart deliberately because conflating them is how a foothold becomes an imaginary blockade. Bab el-Mandeb has Djiboutian and Eritrean shores opposite, and the wider of its two channels runs west of Perim: holding the island is a change in who is nearest to the lanes, not a change in whether the lanes are usable. The fall in transits on 10 September is a change in what shipowners chose to do on the day the news broke, which is a market fact and not evidence of an act against a vessel. What the advance does establish is position on the Yemeni side of the outlet that Saudi Arabia's east–west pipeline delivers to, which is why it and the pipeline attack belong in the same week rather than in separate files. Four things stay apart here: a stated intention to retake the ground, which government field commanders have expressed; operational preparation, which the regroup order is; a counteroffensive, which has not been reported; and a territorial reversal, of which none is established.

Confidence: Moderate High for the fact that the coast changed hands, which both a senior military official of the internationally recognised government and a Houthi official confirmed. Moderate for the extent: no control line has been independently verified, the movement's claim of six districts and 5,400 square kilometres is its own, and the size of the remaining government force on the Hanish islands rests on a single account. The central finding — that no interdiction of general shipping has been observed — is an absence, and it is held only to the limit of what public reporting would show.
Energy

The Hormuz alternative was attacked in the middle on the morning its mouth changed hands

The east–west crude pipeline was struck on the morning of Thursday 10 September in the Riyadh and Medina areas. The Ministry of Energy said it had been shut down as a precautionary measure after multiple attacks, with a number of injuries requiring medical care. The Ministry of Foreign Affairs said the following day that several drones had originated from Iraq, that Saudi Arabia would not respond at this stage at the request of the Iraqi prime minister, and that it reserved the right to take all necessary measures. Iraq said its investigation placed the launches in Maysan province, dismissed the commander of the Maysan Operations Command and ordered an investigative council. No group claimed the attack. Satellite-based analysis reported substantial impacts at two pumping stations; no operator or ministry damage assessment and no restart date has been published. Brent settled around $104 a barrel on 11 September after a weekly gain reported at more than seven per cent, and United States diesel prices reached a record.

Why it matters. The line exists to move Saudi crude away from one contested strait, and it opens onto another; within forty-eight hours it was under pressure at its middle and at its mouth. The baseline of 4 September described the bypasses as real mitigation that is not a replacement, and the week narrows that further: mitigation that can itself be interrupted is a thinner thing than a route, and the distinction between a design ceiling of up to seven million barrels a day, a wartime terminal throughput estimated near three, and a line that is currently not pumping at all is now three different numbers rather than two. Two further things are worth separating. The first attack on Saudi territory in this war launched from Iraq opens a second unattributed-attack file beside the March Ras Tanura one, and an attack nobody claims is a different analytical object from one a party owns. And Riyadh's decision not to respond, at the request of a third government, is a fact about Saudi choice rather than about Saudi capability; reading it as either restraint or weakness goes beyond what the statements support. What none of this establishes is how long the line stays down, what was damaged, or how much crude has actually stopped moving — no operator figure exists and none is invented here.

Confidence: High High for the attack, the shutdown, the two Saudi ministerial statements and the Iraqi attribution of the launch site and the dismissal that followed it, all of which are official and were reported consistently. Moderate for the damage, which rests on third-party satellite analysis and on the fact of a precautionary shutdown. The market figures are close-of-day quotations for 11 September and carry that vintage; no forecast is attached to them, and no claim is made about volumes lost.
Military

The heaviest attack on Saudi territory of this round, answered by a condemnation and a denial

Saudi Arabia conducted air and cruise-missile strikes on Houthi-held areas in al-Jawf, al-Bayda, Marib and Taiz in the days to 8 September. On 8 September the Houthi movement struck Abha, Khamis Mushait, Jazan and Najran with ballistic missiles and drones; the Saudi-led coalition's spokesman said 73 people were wounded, including women and children, and that fires broke out at oil facilities and utilities in the southern region, where operations were temporarily suspended. The movement said it had struck Aramco facilities and King Khalid air base in answer to more than a hundred Saudi strikes over three days. Türkiye condemned the attacks the same day without mentioning the Makkah Agreement; Pakistan's defence minister said on 9 September that the agreement would become operational in the event of continued unprovoked aggression, and Pakistani officials said on 10 September that no immediate military response was under consideration and described the pact as a defensive alliance operating through deterrence. Separately, United States forces struck five Iranian tankers on 9 September after the Revolutionary Guard was reported to have targeted a United States warship twice in two days; Iran said it had attacked ten ships near the strait and fired missiles at United States forces at Al-Azraq in Jordan.

Why it matters. The first armed attack on a Makkah signatory's territory since the agreement was signed was also the first occasion on which its response machinery would have been visible, and what became visible was that there is none in public. That is the finding, and it is narrower than it sounds: an absence of published procedure is not evidence that the commitment is hollow, because a deterrent arrangement may be designed to leave the form of a response undetermined, and institutional work may be proceeding out of sight on the timetable the 31 August committee statement implies. What can be said is that the two non-Gulf signatories answered a qualifying event with a condemnation and an explicit statement that no military response was being considered, and that Saudi Arabia ran the week through the arrangements that already work. The United States–Iran exchange is the other half of a two-front week and is recorded as the continuation it is: the interdiction campaign and the retaliation pattern are both established, and nothing in this exchange changed either. No casualty claim from any party in either exchange is carried here as established.

Confidence: Moderate High for the Saudi casualty figure, which is Saudi Arabia's own and is stated as such, for the Turkish statement and for the Pakistani statements, all official or directly quoted. Moderate for the Houthi strike composition and the count of Saudi strikes in Yemen, which are the movement's claims. Low for the outcomes claimed in the United States–Iran exchange by either side: the tanker count is a United States statement, the ten ships and the Al-Azraq strike are Iranian statements, and no independent confirmation of damage or casualties in either has been identified.
Political

The nuclear file moves to the Security Council, and the access question does not move at all

The IAEA Board of Governors held a special session on 7 September at which Director General Rafael Grossi said the Agency is unable to verify the status of Iran's declared nuclear material and facilities for want of access and information, and called it a matter of serious proliferation concern to be addressed with the utmost urgency. On 9 September the Board adopted a resolution submitted by France, Germany, the United Kingdom and the United States finding Iran in non-compliance with its safeguards obligations and referring the file to the United Nations Security Council, by 23 votes to 3 with 8 abstentions — the first such referral in twenty years. Iran's permanent representative in Vienna, Reza Najafi, called the resolution a political tool; the Foreign Ministry spokesman had said before the vote that Tehran would take countermeasures if the file were referred, and none had been announced by this brief's cutoff. No inspection has been carried out at any declared site other than Bushehr since 28 February.

Why it matters. A referral changes the forum and not the facts. The Agency's position on 9 September is the position it has held since June, and the resolution restores no access, obtains no inspection and establishes nothing about the programme. It matters for two reasons that have little to do with enrichment. It exhausts the Board's own escalation ladder, so the question of what to do about non-cooperation now sits with a Council on which two permanent members can veto any measure — which is why the move is widely read as declaratory. And it removes the last procedural reason for Tehran to keep the Agency's file open as a bargaining position, which makes this module's nuclear observable — an inspection actually carried out at a declared site other than Bushehr — harder to meet rather than easier. What this item does not do is grade Iran's conduct. The absence of verification establishes neither that enrichment continued nor that it stopped, this week as in every week since February, and the referral does not disturb that symmetry in either direction.

Confidence: High High for the session, the resolution, the vote and the sponsors, which are matters of record, and for the Agency's stated position, which is what the item reports. The grade applies to the institutional facts and to the Agency's position, not to any proposition about what Iran is doing, which is precisely what nobody can currently grade. Whether the referral produces any Council action is not forecast here.

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-04Every Iran–Gulf review All weekly briefs