MEFILES · Edition No. 60Today's edition · Archive · RSS
Ten files · One region · Zero illusions
All Iran File stories → The full edition of September 13, 2026 →
Iran File — Lead

Riyadh absorbs a strike on its Hormuz bypass, declines to retaliate at Baghdad’s request, and the oil price falls anyway

Saudi Arabia shut the East–West crude pipeline on 11 September after drone strikes its foreign ministry says were flown by “several drones originating from Iraq”. It then announced it would not respond, at the request of the Iraqi prime minister. Two days earlier Houthi fighters reached Perim Island, completing their hold on the Bab al-Mandeb approaches. With Hormuz already closed, both of the kingdom’s routes to market are compromised — and Brent still fell about 3 per cent.

The Saudi Ministry of Energy said on Friday 11 September that the East–West Crude Oil Pipeline had been shut as a “precautionary measure” after drone strikes on 10–11 September. The Ministry of Foreign Affairs said the line was targeted in the Riyadh and Medina areas by “several drones originating from Iraq”, causing injuries and material damage, and expressed its “strongest condemnation”. No group has claimed responsibility. The physical evidence is independently visible: Planet Labs PBC imagery dated 11 September, distributed via Reuters and AFP, shows a fire-damaged site southeast of Medina along the pipeline route, and NASA FIRMS registered multiple large thermal signatures near the line before Riyadh confirmed anything. CNN, citing two US officials familiar with the matter, reported multiple pumping stations hit. One discrepancy should be recorded rather than smoothed: Haaretz’s live file for 11 September rendered the Saudi statement as saying the drones were launched from Iran. Al Jazeera, Newsweek and NBC all report Iraq, and the Iraqi government’s own response only makes sense if the origin was Iraqi.

The restraint is the part that has been underplayed. Reuters, carried by Haaretz, reported that the Saudi foreign ministry said it had chosen not to retaliate at this stage, following a request from the Iraqi prime minister. On Saturday 12 September Baghdad confirmed publicly that the attacks were launched from Iraqi territory and pledged an investigation — a confirmation by the Iraqi state, not an allegation by Riyadh. Bloomberg, citing a statement from the prime minister’s office, reported that Ali al-Zaidi fired the operations commander of Maysan province, which borders Iran, after finding the launch site lay inside it. The scope of that purge is not settled: Haaretz reports the military commander and the provincial police chief dismissed and the main crossing there closed, while Bloomberg records a single dismissal. No outlet has named the officers. The Times of Israel live file, citing the Iraqi prime minister’s office, reports that al-Zaidi agreed to an Iranian request for a joint investigation into drone launch platforms found near the border. That last item was retrieved from one outlet only and should be matched against INA before it is treated as established.

The strike lands on a map that closed shut this week. Houthi forces took the port of Mokha on Thursday 10 September and reached Perim Island — Mayun — on Friday, after government forces withdrew, splitting Bab al-Mandeb’s two shipping lanes under their guns. That capture was confirmed to NPR and the Associated Press by both a senior military official of Yemen’s internationally recognised government and a Houthi official, each speaking anonymously; two adversaries agreeing is the strongest confirmation available. Bloomberg supplies the causal hinge: the Houthis escalated against Red Sea shipping in July, after Riyadh shifted more of its oil exports to the Red Sea route. The bypass built to survive Hormuz created its own target set, and the target set has now been taken. MS NOW reported, and CNBC and Euronews carried, that Donald Trump rejected a request from Crown Prince Mohammed bin Salman for US strikes on Houthi positions as they approached Mokha. Riyadh and the White House have not commented. That claim is single-outlet, denied by nobody, and the most consequential unverified sentence of the week.

And the price fell. Brent settled just above $104 on the day the pipeline shut, down about 3 per cent, with Trading Economics recording $104.42 and a 2.98 per cent decline. The market was pricing three things against the news: Iranian state media said Tehran would meet Gulf states in Oman, with GCC diplomats expected to sit down with their Iranian counterpart on Monday 14 September over a temporary arrangement for shipping through the strait; the EIA raised its 2027 US crude production forecast to 14.3 million barrels a day; and the IEA sharply cut its demand outlook, forecasting a 2.5 million bpd contraction in 2026. The EIA’s September Short-Term Energy Outlook puts August’s average at $91 a barrel and forecasts Brent near $90 for the second half of the year — below spot. The same document assumes Middle East production recovers partly through “alternative routes”. It was published before those routes were hit.

Assessment: The week’s lesson is not that the Gulf is under attack; it is what the response function now looks like. Riyadh took a strike on its primary workaround, named a neighbour as the point of origin, and then publicly declined to act — because Baghdad asked. That is a bet that Iraq’s weak state is worth more to Saudi Arabia intact than punished, and it makes al-Zaidi’s 30 September deadline for confining weapons to the state a Saudi security file as much as an Iraqi one. Distrust three things. The reported Trump refusal of MBS’s request rests on one outlet and no denial, which is not corroboration. Every figure circulating for what the pipeline actually carried — the 5 million bpd rerouted, the 7 million bpd nameplate — traces to aggregation or to a single newspaper rendering of a ministry statement; nobody has published throughput. And a falling price is not a verdict on the damage. It is a forecast of demand destruction meeting a diplomatic meeting in Muscat that has not yet happened.

Iran FileMEFILES tracking
Evidence8 cited sources · Al Jazeera · Bloomberg · Haaretz · NPR/AP and 3 more
The file19 Jul: 3 stories22 Jul: 2 stories23 Jul: 2 stories24 Jul: 2 stories25 Jul: 2 stories26 Jul: 4 stories27 Jul: 3 stories28 Jul: 3 stories29 Jul: 3 stories30 Jul: 3 stories31 Jul: 4 stories1 Aug: 4 stories2 Aug: 1 story3 Aug: 3 stories4 Aug: 3 stories5 Aug: 3 stories6 Aug: 3 stories7 Aug: 3 stories8 Aug: 3 stories9 Aug: 3 stories10 Aug: 2 stories11 Aug: 4 stories13 Aug: 4 stories14 Aug: 3 stories15 Aug: 3 stories16 Aug: 3 stories17 Aug: 3 stories18 Aug: 3 stories19 Aug: 3 stories20 Aug: 3 stories21 Aug: 3 stories22 Aug: 4 stories23 Aug: 3 stories24 Aug: 0 stories25 Aug: 4 stories26 Aug: 4 stories27 Aug: 3 stories28 Aug: 4 stories29 Aug: 3 stories30 Aug: 3 stories31 Aug: 3 stories1 Sept: 3 stories2 Sept: 3 stories3 Sept: 3 stories4 Sept: 4 stories5 Sept: 4 stories6 Sept: 4 stories7 Sept: 3 stories8 Sept: 3 stories9 Sept: 3 stories10 Sept: 3 stories11 Sept: 3 stories12 Sept: 3 stories13 Sept: 4 stories
Iran File · 54 editions since 19 July 2026 · 165 stories filed · 4 in this edition