Iran–Gulf developments — 18 October 2026
Strikes in the strait went on at their October pace, and the attacks spread. A container ship struck on 13 October sank the next day, the second large ocean-going ship confirmed sunk in the war. Tankers were reported struck off Saudi Arabia's Gulf coast at Al Jubail, and Iran's navy told ships east of the strait to coordinate with it. UKMTO counted combined transits about 70 per cent below pre-war. It said most attacked ships no longer report, so its count is a floor. No cover was found written, and nothing changed in the IMO's view or the legal régime. On the Saudi front, Houthi missiles reached the Yemeni government's seat in Aden. The Security Council, in a presidential statement, affirmed Saudi Arabia's right of self-defence; the statement authorises nothing. Egypt offered to defend the kingdom if asked, outside the Makkah Agreement, and no force was attributed to that agreement. Nothing between Washington and Tehran is in force. The IAEA's pages could not be read, and verification access was not reviewed.
The developments
A second large ship sank, the attacks reached the Saudi Gulf coast, and the count is now a floor
UKMTO's weekly overview of 16 October lists four ships struck in the strait on 13 October. One, a container ship, caught fire, drifted and sank on 14 October about four nautical miles north-west of Ras Shaykh Masud. Its crew were evacuated without injury. Singapore's maritime authority confirmed the sinking of the Singapore-flagged GFS PRIDE, as reported by gCaptain, which called it the second confirmed sinking of a large ocean-going ship in the war. Iran said the ship struck a mine. On 16 October India's shipping minister said the crude tanker ST 3 had been struck by a projectile in the strait, with its fifteen Indian crew safe. The same day UKMTO, as relayed, reported a tanker struck about 68 nautical miles north-east of Al Jubail in Saudi Arabia, with the crew evacuated. A small-boat attack on a tanker off Al Jubail was reported on 17 October. UKMTO counted twelve attacks in the week to 14 October, ten of them in the strait. It said it is struggling to report the true number because most vessels attacked refuse to report to it. Since 6 July, 55 of 74 projectile strikes were on the southern route, while most vessels broadcasting on AIS route via Iran's. Combined transits were 254 in the week, about 70 per cent below pre-conflict levels, and AIS-visible transits fell to 42 from 60. On 13 October Iran's navy said it had deployed units in a new formation east of the strait, across the Sea of Oman and the Arabian Sea. It warned ships not to switch off their transponders and urged them to "coordinate with Iranian armed forces for safe passage". An Iranian official told Reuters that Tehran had changed the type and pace of its attacks about ten days earlier. Kpler put oil through the strait at 2.9 million barrels on 11 October, the month's low, against a pre-war daily 17.1 million.
Why it matters. The physical risk spread. A month ago the strikes were in the strait's lanes. This window they reached the Sohar anchorage and Saudi Arabia's Gulf coast, and sank a ship. UKMTO's own pattern is the sharpest fact: the strikes fall mostly on the southern route, while most ships visible on AIS use the route through Iranian waters. Iran's navy statement is a declared reach outside the strait. It tells ships what to do in waters no riparian has given Iran authority over. It is unilateral, and it is not a régime. What did not move is what the question measures. No cover is written on charterers' terms, the IMO's view stands, and no navigational régime is accepted. Transits are counted, and counting is not access. The item does not establish who fired on any vessel. Iran claimed none of this week's strikes, its mine account of the GFS PRIDE is a party's, and no host government attributed them.
- Voluntary Reporting Area Weekly Overview No. 11
- Containership sinks as Hormuz attacks spiral out of control
- Iran steps up Hormuz surveillance: Attacks soar, oil flows crash again
- Oil tanker struck in Strait of Hormuz, says Indian ports minister
- Tanker struck by unknown projectile off Saudi coast — UKMTO
The Houthi movement's fire reached the Yemeni government's seat, and the front's structure did not change
On 15 October Houthi missiles struck the al-Maashiq presidential palace in Aden. The government said five were killed and sixteen wounded, among them guards and civilian staff, and that the Prime Minister was unharmed. The movement's military spokesman said it had struck a "Saudi military operations headquarters". On 16 October two missiles landed on the grounds of Aden airport about 500 metres from a departing Yemenia aircraft, with no casualties. The movement said it had targeted a military headquarters at Badr camp beside the airport. Aden's security department called it the second attack on the airport in under a week. The Saudi-led coalition said it intercepted a ballistic missile aimed at Yanbu on 16 October and destroyed two launchers east of Saada on 17 October. On 13 October the Saudi energy ministry had reported a limited fire at Aramco's headquarters complex in Dhahran. A Saudi deputy minister, Rayed Krimly, said Iran had "encouraged" the escalation. On 16 October Iran's foreign ministry spokesman rejected "any claim that Iran has played a role" in Houthi operations and offered to mediate.
Why it matters. The geography widened to the government's seat in the south. The structure the module recorded a week ago is unchanged. It is an offensive on the coast under Saudi air cover, answered by a missile and drone campaign against Saudi territory and now against the government Riyadh backs. There is no channel between Riyadh and Sanaa, no truce and no external strike on the movement. Iran's denial and offer to mediate are positions. Krimly's charge is a position too. Neither is evidence of what Tehran supplied or directed. The strikes on Aden are at no energy or base marker the module counts. The Dhahran fire was at an office, and the Yanbu missile was intercepted, so the energy series records no strike at a node.
The Security Council affirmed Saudi Arabia's right of self-defence, and the kingdom's defenders multiplied outside any procedure
On 15 October, at its 10244th meeting, the Security Council adopted a presidential statement, issued as S/PRST/2026/4. It condemned "the reckless strikes" of 10 and 11 October on King Khalid International Airport, which by the Council's figures killed 13 and wounded more than 300, and strikes on other airports and Aramco facilities. It condemned Houthi attacks and threats against shipping in the Red Sea and Bab al-Mandab, affirmed Saudi Arabia's inherent right to self-defence under international law, and stressed full implementation of resolution 2216 and its arms embargo. On 17 October Egypt's President asked parliament to convene in emergency session to authorise Egypt to defend Saudi Arabia "if we are asked to do so". He said: "We are seeking only to defend." Parliament was due to meet on 18 October, after this window. On 16 October Pakistan's Prime Minister called the bilateral defence agreement and the Makkah alliance "historic milestones". He named no force. Türkiye said on 8 October, found late, that the Agreement's text was ready to go to its parliament.
Why it matters. A presidential statement is adopted by consensus, so every Council member put its name to the affirmation of Saudi self-defence. That is its weight, and it is also its limit. It is not a resolution, it imposes no measure, and it authorises no use of force. Affirming an inherent right recognises a right that already exists and confers nothing new. It says nothing about the campaign in Yemen. The defence of Saudi Arabia is gaining offers, not a procedure. Egypt, which is not a Makkah signatory, offered help on request, through its own parliament. Türkiye's ratification step is domestic law, not an implementing instrument. No government has said that a force is in the kingdom under the Makkah Agreement, and its Secretary General has taken no public act. The observable that would change this reading is a ministry naming a unit or capability as provided under the Agreement.
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-10-11Every Iran–Gulf review All weekly briefs