October 14 Update: Aramco Dhahran Building Hit

Checked October 14, 08:20 UTC. Events occurred October 13 and early October 14.

Saudi Arabia's Energy Ministry says an Aramco administrative building in Dhahran was attacked on Tuesday evening, causing a limited fire and no injuries or deaths. The coalition says it intercepted a ballistic missile at Dhahran and that fragments fell in a residential area; officials have not said whether the building took a direct hit. No production, processing or export impact has been reported. See the Aramco alert.

Saudi Civil Defense says debris from two intercepted cruise missiles injured four people and damaged 15 homes in Riyadh on Tuesday evening. The coalition reported intercepting a ballistic missile aimed at the capital on Wednesday morning. Reuters now puts the toll from Saturday's airport attack at 13 dead, one more than GACA's October 11 statement. The coalition says it struck Houthi fuel sites in Sanaa, Hodeidah and Dhamar on October 13.

Our Middle East panel holds the desk threat assessment at 8/10. A strike on an office complex shows reach into the Eastern Province; a hit at Abqaiq, Ras Tanura or Yanbu would change the supply picture. The October 14 daily brief covers prices and Hormuz shipping.

Sources: Saudi Energy Ministry and Saudi Civil Defense via SPA, October 13-14; coalition statements, October 13-14; Reuters, October 13-14, syndicated by Al-Monitor. Older sections retain their original reporting dates and are not current operating guidance.

October 12 Update: Sunday Attacks at Riyadh and Dammam

Checked October 12, 09:29 UTC. These are separate October 11 events.

GACA reported an attack on King Khalid International Airport on Sunday afternoon and a separate evening attack at King Fahd International Airport in Dammam. Saudi Press Agency carried the Riyadh statement. Its Dammam statement described damage and safety assessments underway. AFP subsequently reported one Pakistani resident killed and 11 people injured in Sunday's Riyadh attack, citing GACA. These figures must not be combined with Saturday's casualty count.

Monday's GACA notice extended the suspension of Riyadh operations. No reopening or new deadline has been established in this review. Earlier closure windows below are historical reports, not evidence of resumed flights. See the new airport alert.

Our Middle East and defense panels hold the desk threat assessment at 8/10. Repeated aviation disruption warrants fresh personnel-travel checks; the statements do not establish damage to Saudi petroleum facilities or lost crude output. The daily brief separates these transport risks from operator-reported offshore shut-in estimates.

Sources: SPA/GACA, October 11, Riyadh 16:37 GMT and Dammam 18:36 GMT; AFP and GACA operational notice, October 12. Older sections retain their original reporting dates and are not current operating guidance.

October 11 Update: Airport Attack Toll Confirmed

Checked October 11, 08:00 UTC. Updates the October 10 attack, not a new Sunday strike.

GACA's statement dated October 11 reports 12 deaths and 309 injuries, including critical injuries, after Saturday afternoon's attack on King Khalid International Airport. Material damage remains under assessment. This supersedes the unknown casualty total in the dated October 10 update below.

AP reports, citing Flightradar24, that the airport closure was extended until at least 9 p.m. Sunday local time. A closure window does not confirm reopening. AP also reports Trump considering US participation in strikes against the Houthis; the sources reviewed do not establish a decision.

Our geopolitical and defense assessment holds the desk threat score at 8/10. The casualty update increases pressure for a response but does not quantify an oil-production loss, refinery outage or interruption to export loading. Personnel travel and cargo operations need separate checks. See the casualty-update alert. The October 11 daily brief covers the wider supply picture.

Sources: GACA statement dated October 11; AP, October 11. Earlier sections retain their original dates and are historical reporting.

October 10 Update: Riyadh Airport Operations Suspended

Checked October 10, 20:30 UTC.

GACA said King Khalid International Airport was attacked on Saturday afternoon, injuring several people. Operations were temporarily suspended for damage and safety checks; the injury count was still being assessed. Asharq Al-Awsat and Arab News reported the authority's October 10 statement. No confirmed death toll or reopening time was established in the sources reviewed. See the October 10 airport alert.

AFP reported on October 10 that at least five people were in intensive care, citing an unnamed source at a Riyadh hospital. The report, carried by Times of Israel, does not establish an official casualty total. The FCDO's October 10 travel advice tells British nationals to avoid King Khalid International Airport until it is secure and monitor Saudi authorities' advice.

The three deaths confirmed after the October 8 attacks belong to that earlier event. They are not an October 10 casualty count. Our assessment separates disruption to passenger aviation from oil supply: the airport statement does not establish lost crude output, a refinery outage or interrupted terminal loading. The reserve-release analysis explains why transport access and usable fuel supply require separate evidence.

Sources: GACA statement, October 10, as reported by Asharq Al-Awsat and Arab News; GACA October 9 statement on the October 8 attacks; AFP via Times of Israel, October 10; FCDO travel advice updated October 10. Earlier updates below retain their original dates.

October 9 Update: Riyadh Airport Deaths Confirmed

Saudi Arabia's civil aviation authority (GACA) confirmed on October 9 that "two attacks targeted King Khalid International Airport facilities and a Saudia aircraft" on October 8, killing three Saudi nationals. Saudia said the aircraft's captain was among them. The Houthis claimed several strikes on the airport, including two cruise missiles; the GACA statement does not name the attacker. Six people have now died at Saudi airports this week. Almost half of King Khalid's departures were cancelled by 1500 GMT on October 8, per Cirium, and Lufthansa and Air India suspended Riyadh flights. See the October 9 alert.

The strikes came on the day the Houthis warned workers at all Saudi oil facilities to stay away from sites they call targets. No Saudi energy site or port was reported hit on October 8-9. A regional source says Riyadh will not agree to a truce until Yemen's government regains all lost territory, and the coalition says it destroyed three Houthi launch platforms. Aramco is in talks with term customers about loading next year's contract barrels outside Hormuz; no final decision has been made. Our Middle East panel holds the desk's threat assessment at 8/10 and would move it on a confirmed hit that stops Yanbu loading.

October 8 Update: Houthi Airport Strikes Turn Lethal

Saudi Arabia's civil aviation authority said on October 7 that attacks on Abha and King Khalid international airports on October 6-7 killed three people and injured 36, per the Saudi Press Agency. Two were killed and 28 injured at Abha; one was killed and eight injured at Riyadh's King Khalid. The coalition said it intercepted a ballistic missile north of Riyadh on Wednesday. The Houthis claimed a further ballistic missile at King Khalid on Thursday, which Saudi Arabia had not confirmed. Riyadh flights were delayed and cancelled.

Our defense panel reads the campaign as a sustained second front against the region's main producer, now reaching the capital. It does not change the desk's threat assessment, which holds at 8/10 because the standing trigger is maritime. On October 7, a tanker was struck north of Qatar in the first deep-Gulf attack since September 9 (see the October 8 alert). Loadings at Yanbu and in the Gulf, reported on October 5, have not been reported disrupted.

Panel assessment: Defense Analyst and Maritime Analyst.

October 5 Update: Export Recovery Across Two Routes

Reuters reported on October 5 that Saudi loading from both the Red Sea and the Gulf contributed to the recovery in regional crude exports. The same report cites provisional Kpler data showing a seven-day regional crude export average of 18.3 million barrels a day as of September 30. That regional total includes several routes and Gulf of Oman transfers; it is neither Saudi export volume nor measured Hormuz throughput.

The October 4 OPEC+ decision maintains September required production levels for November among the seven participating countries. Their next meeting is November 1. Production requirements do not establish actual production, terminal capacity or available cargoes.

Our maritime and regional panels assess that Red Sea loading provides route flexibility, while each voyage retains its own security exposure. Southbound shipments face Bab el-Mandeb exposure; northbound shipments have a different route. The defense panel holds the desk's regional threat assessment at 8/10. See the October 5 daily brief for the reserve response and renewed tanker incidents.

Scope: This October 5 update supersedes earlier statements below that Yanbu had no confirmed loading. Earlier dated sections are historical reference material; their infrastructure, military, inventory, freight and insurance figures have not been reverified for October 5.

Panel assessment: Middle East Expert, Energy Strategist, Maritime Analyst and Defense Analyst.

Day 211 Update: France Sends a Guard to Yanbu (September 26)

Emmanuel Macron said France will send soldiers, radars and air-defence systems to protect Yanbu, agreed with Riyadh and "not to engage in any conflicts." He gave no numbers or dates. It is the first Western ground-based commitment to the bypass. On this desk's defense panel's assessment, short-range systems could come from French forces already in the UAE within weeks; only a SAMP/T battery would add meaningful protection against ballistic missiles, and none has been named.

Saudi air defences intercepted Houthi missile fire aimed at Khamis Mushait early Sep. 26 (one missile per coalition spokesman Maj. Gen. Turki al-Malki via AP, two per CBS). Houthi spokesman Yahya Saree claims the Sep. 24 salvo hit Aramco facilities at Yanbu; Riyadh confirms only six interceptions. Yanbu still has no confirmed loading, with Kpler's six slots due by Sep. 27, and war-risk cover for Saudi-linked tankers there is ~3% of hull value, up from under 1% in early July. See the Sep. 26 brief.

Day 210 Update: Missiles Aimed at Yanbu Before It Loads (September 24-25)

Six Houthi ballistic missiles aimed at Yanbu and Taif were intercepted on Sep. 24, according to coalition spokesman Maj. Gen. Turki al-Malki. Damage and casualties are unknown; alerts sounded in Jeddah and Mecca before the all-clear (AP via CP24). It is the first named ballistic targeting of Yanbu in this crisis.

The terminal has still not loaded a tanker since the East-West pipeline restarted Sep. 22. Aramco told European refiners it is building a "critical mass" of crude first; pressure tests take several days and full capacity may be six weeks out after three pumping stations were damaged Sep. 11 (Reuters via Baird Maritime). The China cargo scheduled for Sep. 22 did not load, nor did two Sep. 23 slots. Kpler has six tankers (four Aframaxes, a Suezmax, a VLCC) due Sep. 24-27. See the Sep. 25 brief.

Day 208 Update: Petroline Is Pumping, and This Desk Corrects Itself (September 18-23)

  • No scan ran Sep 18 through Sep 22. This update closes a six-day gap in one pass rather than backfilling five unverified days, disclosed here for the record.
  • Correction, and it goes first because two numbers this desk published earlier today do not exist. An earlier version of this page carried Petroline as "confirmed" moving ~1.1M bbl/d on Aramco's own word, and Yanbu as having loaded a tanker around Sep 20. Aramco has said nothing. No wire carries either figure. Both are withdrawn in full, and the ~1.0-1.3M bbl/d ceiling this desk derived from Yanbu's lifting capacity remains a derivation, never a measurement.
  • What is actually sourced. Reuters (Nidhi Verma, Florence Tan, Trixie Yap, Sep 22 03:56) has Saudi Arabia restarting the line, with two of three sources briefed on the matter describing it as "pumping at a low rate," volume undisclosed. Crude has resumed flowing to Aramco's Red Sea refineries and one cargo was scheduled to load at Yanbu bound for China. Aramco did not respond to a request for comment, so the restart arrived with no company statement and no force majeure on day 12. Separate that from the aspiration in the same wire: 4M bbl/d is a target attributed to one unnamed source, and a security source says full resumption could take weeks. A target is not a flow, and "low rate" is not a number.
  • The Yanbu-China cargo is the finding nobody framed, and it breaks a call this desk was carrying. Canon held that a westbound restart serves Europe only, because the Red Sea cannot reach Asia at economic voyage length. Yanbu to Ningbo southbound through Bab el-Mandeb and Malacca is ~6,500nm, low-to-mid 20s in days, within a few hundred miles of a direct Gulf voyage. The Houthi bar names Saudi vessels, not Saudi cargo, so selling FOB at Yanbu onto a Chinese-chartered hull walks around it. Red Sea war-risk cover last printed ~0.3-0.75% against 7.5-10% for Hormuz. One cargo is a proof of concept rather than a channel, and the live tail is the bar widening from Saudi vessels to Saudi cargo.
  • Escalation cuts 9 to 8, and the desk owns that its own cut rule under-fired. On Sep 17 this desk pre-committed to cutting on any two of three dated tests by end of Sep 21: a Yanbu loading or departure, a named throughput figure in bbl/d, or a European term buyer restoring a cancelled cargo. Exactly one landed, and it landed Sep 22, a day past the deadline. Read strictly, 9 holds. The rule was a bad instrument, demanding two independent confirmations of what is substantially one physical fact, and the physical fact has happened. The cut stands on the substance: the 9 required export capability at or near zero on all routes, and that clause is false on Petroline and false again on Hormuz at a six-month flow high. Rewriting a definition to preserve a level is how a board loses calibration. Read the cut narrowly: it is a bypass-infrastructure call, not a verdict on the strait, where the lit-transit band holds at 9-14/day, still >80% dark, against a pre-war ~125/day.
  • The sentence this desk is withdrawing for the second time, and this time without a hedge. On Sep 16 this page said the Kingdom "has no major export route that avoids" Hormuz. Sep 17 softened that to capability impaired rather than absent. It is now simply false. The Kingdom has a route, it is running, and the first barrels out of it are going east rather than west.
  • King Khalid Air Base breaks an 11-day silence, and answers one question while skipping the other. A Ministry of Defense statement (~Sep 20) admits "limited damage to support infrastructure" and calls capability "unaffected." It does not address the F-15SR loss (tail 5539, 55th Squadron) a Houthi spokesman claimed Sep 16 with FLIR video and wreckage imagery. Eleven days of silence followed by a partial admission reads as managed disclosure. This desk's own 96-hour concealment rule is vindicated by the eventual admission, and the aircraft claim remains unconfirmed by Riyadh.
  • Force majeure still not declared. Odds are unchanged at 33-38% public by any route and 22-26% Aramco itself declares. The Sohar ship-to-ship channel to China keeps operating in parallel; nothing about the Petroline restart touches the ~$10/bbl freight advantage that keeps it running.
  • The Marib front is unresolved. Houthi forces continue pressing the outskirts of the fields that fund the Saudi-backed government; government forces with coalition air support have not lost the core infrastructure. No territorial change this cycle. The casualty figure this desk carried on Sep 17 (194 killed, 880 wounded over two weeks) was not refreshed for the gap period and should be read as stale.

Day 202 Update: The Repair Clock Collapses and This Desk Retires Its Own Number (September 16-17)

  • Bloomberg reports half of Petroline back within days, full capability in about six weeks. Salma El Wardany, Sep 16 at 12:35 PM EDT: Saudi Arabia "is seeking to return about half the capacity" of the line within days by "working to bypass a damaged section", and is looking to return it to "full capability in about six weeks". The sourcing is one person familiar, anonymous, and "Aramco and the Saudi energy ministry didn't respond to requests for comments." Every other outlet carrying this is syndicating the same wire, which is reach rather than corroboration. Read the report as cutting both ways against prior canon: a days-to-half-capacity restart sat in no branch this desk was carrying, and six weeks to full is LONGER than the AP's three-to-five weeks. More bullish on partial, more bearish on full.
  • "Half of capacity" does not convert to barrels, and this desk will not convert it. Three baselines are live at once: Bloomberg's own ~7M bbl/day "full capacity earlier this year" puts half at ~3.5M, Reuters' 4-5M bbl/day pre-attack puts half at ~2.0-2.5M, and the Kpler and desk-canon ~2.0M bbl/day of actual August flow puts half at ~1.0-1.25M. Same two words, a 3.5x spread. Anyone quoting a barrel figure off that phrase has picked a baseline without telling you which one.
  • Damage closes at two pumping stations, PS8 and PS9. Reuters (Maha El Dahan and Jonathan Saul, Sep 16) puts the count at two, against 11 pumping stations plus 2 pressure relief stations on the line. The third station this desk inferred from Soar Atlas imagery is dropped. The Payne Institute for Public Policy at the Colorado School of Mines (Sep 13) confirms fire damage at two stations using VIIRS Nightfire, and found that most of the eight thermal clusters detected along the corridor "coincide with existing flare pits used for emergency gas burn-off, not new pipeline ruptures." Two discrete damage points are bypassable in a way eight rupture points would not be, so the physical evidence is an independent reason to take the restart claim seriously rather than a second-hand echo of it.
  • A pipeline restart is not an export restart, and this is the most abused point in the coverage. Yanbu the terminal is a separate unresolved failure: no restart, no force majeure, no Aramco statement, nothing departed since Sep 11, and Aramco declined to comment to Euronews on Sep 16. Crude arriving down a repaired line into a suspended terminal fills tanks. It does not clear cargoes. Yanbu also halted loading BEFORE tank cover ran out, so inbound crude was never the binding constraint, and a bypass welded in the desert does not address whatever the constraint at the water actually is.
  • Tank cover correction: the Sep 16-18 exhaustion call was answering a question that stopped being live. Yanbu storage has fallen below 15M bbl, from close to 21M in July (OilPrice, Sep 17). The earlier five-to-seven-day estimate measured EXPORT cover at a lifting rate that went to zero on Sep 11. With loadings suspended the draw is refinery-only, ~680,000 bbl/day across YASREF (~430,000) and the Yanbu Refinery (~250,000), which makes 15M bbl ~22 days of cover, DERIVED. The old figures were not wrong on their own terms. The question they answered died when the loadings stopped, and this desk carried the answer past the question.
  • The at-risk figure is ~1.8-2.3M bbl/day of crude. Three independent corroborations sit behind the 2.0-2.5M bbl/day the desk adopted on Sep 16: Goldman Sachs' "the remaining 2mb/d of recent Yanbu exports", Bloomberg's Sep 16 report that Saudi oil exports "slumped to just about 3 million barrels a day in August, the lowest in at least nine years" with Yanbu shipments that "still made up a bulk of the sales", and Kpler and desk canon at ~2.0M bbl/day into the western system in August. The energy panel refines that down today to ~1.8-2.3M bbl/day, taking Yanbu at 60-75% of a ~3.0M bbl/day export total. That 60-75% split is DESK INFERENCE, not a reported figure.
  • Sohar predates the strike by three weeks, so it is a scale-up and not an improvisation. Aramco is offering Arab Light, Arab Medium and Arab Heavy to LONG-TERM Asian buyers for loading off Sohar Port, Oman, outside the Strait of Hormuz. A Bloomberg piece dated Aug 17 2026 shows the offer on the table three weeks before Petroline was hit. The maritime read matters: loading "off" Sohar rather than "at" it means a ship-to-ship anchorage transfer, not a loading terminal, and there is no Saudi crude storage at Sohar. The barrels still cross Hormuz on an Aramco-controlled shuttle. What changes is that the buyer's hull and cargo title never enter the strait, which moves war risk and cover off the buyer and onto Aramco.
  • SAMA followed the Fed in full, and the peg question is unmeasured rather than answered. SAMA raised its repo rate 25bp to 4.50% and the reverse repo to 4.00% on Sep 17, inside 24 hours of the Federal Reserve's 25bp hike to 3.75-4.00%, "in line with SAMA's mandate of preserving monetary stability." The desk's pre-commitment that SAMA would follow the full 25bp resolves yes. It does not follow that there is no peg stress, and this desk withdraws that reading: a central bank defending a peg tightens in full precisely when it is under pressure, so a full follow is what you would see in both the calm world and the early-stress world. The instrument that discriminates is the 12-month USDSAR forward, and it could not be found. Absence of a measurement is not a measurement of absence. What the corridor does say is that the repo at 4.50% now sits 50bp above the US upper bound with no domestic Saudi inflation problem driving it, so the entire increment is peg maintenance. The result is procyclical: Riyadh has tightened into the quarter its export revenue collapsed, which reprices private credit upward at the moment non-oil GDP most needs support.
  • The military asymmetry is the finding. The coalition says it intercepted a Houthi drone south of Mecca; the Saudi Foreign Ministry called it a "cowardly terrorist attack" and asserted the "legitimate right to take all necessary measures to defend" the holy city, while the Houthis called the claim a "lie." Against a formal statement issued within hours over a drone that hit nothing, there is still no Saudi word on King Khalid Air Base at ~120 hours, against reported imagery of a direct hit on F-15 hangars. Houthi spokesman Yahya Saree separately claims an RSAF F-15 downed over Marib by a locally manufactured surface-to-air missile, offering FLIR engagement video, wreckage photos and a tail section reading 5539, identified as an F-15SR of the 55th Squadron based at King Khalid Air Base. Riyadh has not acknowledged it and Reuters carried it as not independently verified, so this desk adopts it as a well-evidenced claim, NOT a confirmed loss. Riyadh speaks about symbolic threats it survived and stays silent about material losses it took.
  • Escalation moves to 9/10 and holds there today. The thesis behind the move on Sep 16 was that Saudi Arabia has no major export route that avoids Hormuz. Two of today's items cut against it, the restart clock and the Sohar channel, and neither has cleared a cargo yet: Petroline is still shut, Yanbu has still loaded nothing since Sep 11, and Sohar routes Saudi barrels through the strait under an Aramco flag rather than around it. The pipeline politics case for a cut becomes real the day a Yanbu loading is confirmed, not the day a wire reports a bypass weld. Iran attribution for the Sep 11 strike remains unestablished.

Day 198 Update: Riyadh Asks Washington to Shoot and Is Told No (September 13)

  • Mohammed bin Salman called President Trump twice on Sep. 10 and asked for American strikes on the Houthis. Trump declined. Washington's counteroffer, reported by CNN on Sep. 10 and confirmed on Sep. 12, is a real-time targeting tool comparable to the Pentagon's Maven, geospatial support, and 100-plus advisers inside a newly established joint forces command. Withheld: strike participation, aerial refuelling for Saudi warplanes, and the other operational support the US supplied in earlier Yemen campaigns. Saudi officers can see targets they have no partner to service. Trump said afterward that Iran is "probably" behind the pipeline attack and that the Houthis "called us and they don't want to fight with us."
  • RETRACTED Sep 16: the ~5M bbl/day Petroline figure this desk published on Sep 13 was wrong, and the derivation built on it is withdrawn in full. On Sep 13 this desk raised its Petroline carry from ~2.5M to ~5M bbl/day on a convergence of CNN, the AP wire and Al Jazeera, all describing ~5M bbl/day of Gulf volume rerouted to Yanbu since Hormuz shut. The desk reversed that on Sep 16 and now treats the ~4M and ~5M headline figures as GROSS TERMINAL THROUGHPUT, products and NGL included, rather than crude moving on the line. A consistency check is what broke it: August supply printed 6.0M bbl/day, so a 5M bbl/day Petroline leaves 1M bbl/day for Ras Tanura and Ju'aymah combined, and Ras Tanura is the largest crude terminal on earth. The adopted figure is 2.0-2.5M bbl/day of crude at risk, refined to ~1.8-2.3M bbl/day on Sep 17 (see the Day 202 update above). The "~83% of national output on a single 1,200km line" line that followed from the ~5M figure is dead and should not be quoted. What survives the correction is the demand point: northbound demand for Saudi grades runs ~1.0-1.3M bbl/day, so a restart on its own does not clear the west-coast barrels.
  • Petroline is shut a third day with nothing published. No damage assessment, no affected-capacity figure, no restart date from the Energy Ministry. After the April 2026 attack the ministry put the temporary loss at ~700,000 bbl/day before announcing full restoration, and search engines are surfacing that April restoration as if it were current. It is not. The engineering read holds: one damaged pumping station is a throughput haircut rather than a stoppage, restart turns on whether the drone threat abates, and Yanbu will keep loading off tank stocks for days. Continued liftings are not evidence the pipe is back.
  • Cross-border fires continue on two vectors. Houthi spokesman Yahya Saree claimed a drone and ballistic missile strike on the Sharurah military base in Najran; Riyadh has not confirmed it and civil defence reported sirens on Sep. 12 with no casualties or damage. A projectile struck al-Tawwal in the Jazan region the same night, wounding two and damaging a mosque, several buildings and vehicles. Read the pair as a range demonstration rather than an attempt at effect. The no-retaliation line Riyadh gave Baghdad covers Iraq-launched drones and does not formally bind the Houthi file, but the cumulative picture is a state absorbing strikes from two directions without a visible response on either.
  • The kingdom enters Salalah with no alternative to the table. It cannot strike Iraq, having accepted Baghdad's restraint request after the Maysan commander was dismissed. It cannot strike the Houthis without the US enablement it was just denied. It cannot schedule a Petroline restart or move meaningful volume west. States sign arrangements they would otherwise refuse from exactly this position, which is why the odds of an announced or signed regional text inside 60 days move to 55-60%, while the odds of an arrangement that measurably lifts Hormuz transits hold at 20-25%. Escalation stays at 8/10; a Saudi strike inside Iraq remains one of the three named triggers for 9.

Day 197 Update: A 30-Year Supply Low and the Back Door Closes (September 7-12)

  • August supply printed 6.0M bbl/day, down 2.3M month-on-month and the lowest in more than three decades. The headline reads as a production story. It is a logistics story. Ras Tanura and Ju'aymah have been near zero since Feb. 28, so Hormuz cannot explain a July-to-August delta. Most of the fall traces to Bab el-Mandeb: August was the first full month under the Houthi Red Sea campaign, and the binding effect is not interdiction but voyage length, with a Cape routing to Asia running ~54 days against ~24 direct. Doubling round-trip days halves the effective export rate without a single hit landing.
  • Jizan was struck again on Sep. 7, while still offline. Aramco's Jizan facilities took fresh attacks with damage under assessment, described by one source as similar in scale to the prior month's strike. Attribution is not established. This desk is retiring the "new restart date" watch as obsolete: the correct line is that the 400,000 bbl/day unit was re-struck while shut, not that a restart slipped. Note also that Jizan is refining capacity, not crude supply, so it belongs in the product and crack-spread picture rather than in the 6.0M bbl/day print. Separately, Houthi strikes across four southern cities injured 73 civilians.
  • Perim Island closes the back door. Houthi forces seized Perim on Sep. 11, along with Mocha, Dhubab and the Hanish group. Two directions leave Yanbu and Muajjiz: north through Suez and SUMED, which touches neither chokepoint and serves the Med, northwest Europe and the US Atlantic, or south through Bab el-Mandeb to Asia. There is no third option and no reroute. A shut southern lane does not redirect a Yanbu-to-Asia cargo, it deletes the leg, because the alternative runs ~14,500nm against 6,400.
  • The kingdom's effective export ceiling is now visible. Northbound demand for Saudi grades is only ~1.0-1.3M bbl/day deep, which strands ~1.5-1.8M bbl/day of southbound volume. The "5M bbl/day spare" on the East-West pipeline is spare steel serving a market that cannot absorb it. Effective capacity is Ras Tanura and Ju'aymah through a contested Hormuz, plus ~1.0-1.3M bbl/day north out of Yanbu, and the August print is that constraint already binding.
  • A coverage detail that selects who can lift. The Gard and Skuld ancillary war-risk withdrawal effective Aug. 16 runs south of 25 degrees 30 minutes north. Yanbu at ~24N and Muajjiz at ~23.7N both sit inside the withdrawn zone. Fixed-premium charterers', traders', crew and carriers' liability cover is gone at the Saudi Red Sea loadports, while mutual P&I and FD&D hold. That favours Bahri's own fleet and mutual-entered owners over trading houses, and Bahri is itself a target: its VLCC Amzan was struck 63nm west of Yanbu on Aug. 24.
  • OPEC+ held October output flat on Sep. 6. The seven core members, Saudi Arabia among them, maintained September levels rather than delivering the incremental ~188,000 bbl/day hike this desk had expected. Read it as a bookkeeping correction rather than restraint: a cartel exercising restraint into $104 oil does not simultaneously print a 30-year supply low. Next meeting Oct. 4.

Day 187 Update: Jizan's Restart Slips Past Its Target, No New Date (September 2)

  • The refinery misses its restart window: Aramco's Aug 30 target date for bringing the 400,000 bbl/day Jizan refinery back online passed without an official statement in either direction, silence that ran two full days before resolving into a low-key acknowledgment that the date has slipped. No replacement date has been set, and no restart has been confirmed. Read: the outage now runs longer than the kingdom's own internal timeline projected in early August
  • What has not changed: no fourth confirmed Houthi strike on Saudi territory has landed since the Aug 9 and Aug 13 hits logged in the August 20 update below, and Bab el-Mandeb closure risk holds at 75-90%, unchanged since late July. The broader crisis picture is equally static, deal-collapse probability holds at 85-90% and this desk's escalation read sits at the low end of 5-8/10, both flat since the Islamabad MoU's Aug 16-17 lapse
  • Why a slipped date still matters: Jizan is the one Saudi-specific data point this desk has been tracking toward resolution since the Aug 9-13 strikes, and a slip without a new target extends the kingdom's refining-capacity gap by an unknown margin rather than closing it. The next real signal on this line is a confirmed hard date, not further silence

Day 174 Update: Jizan Correction, At Least Three Strikes on the Refinery (August 20)

  • Correction leads today: this desk's standing line that no third Houthi strike on Saudi land infrastructure had landed since Jul 24-25 was wrong. Houthi drone strikes on Aramco's Jizan refinery (400,000 bbl/day; rendered Jazan in most international reporting) are now confirmed for both Aug 9 (fire extinguished, no casualties; Al Jazeera, NBC, NPR) and Aug 13 (Bloomberg calls it the "second time in less than a week," two drones per Saba; Middle East Monitor concurs). That makes at least three strikes on the refinery: Jul 24-25, Aug 9, Aug 13. A possible fresh hit Aug 19-20 appears in a CBS liveblog with ambiguous dating; treat as unconfirmed pending next cycle. Aramco has still issued no official damage or restart statement, the Aug 15 restart date was never officially confirmed, and its status is now unknown
  • What repetition changes: the southwest is a persistent Houthi target set, worked repeatedly at low cost, while the east-coast nodes, Abqaiq, Ras Tanura, Ju'aymah, Jubail, remain the catastrophic scenario this page has carried since the Aug 6 coordinated-strike warning. The correction also cuts the weight this desk puts on its own quiet periods: two strikes went unlogged for up to eleven days, so "no new strike" reads now carry lower confidence until the sourcing picture tightens
  • The frame tightens around a kingdom keeping its head down: Trump announced an "Economic D-Day" campaign against Iran Aug 19-20, economic warfare plus a secondary-sanctions ultimatum to third countries, and ordered US envoys to halt all talks. Iran's Armed Forces Chief Abdollahi warned Aug 19 that Gulf states aiding US operations are "considered participation alongside US forces," a frame that reaches the kingdom's basing (King Fahd Air Base access stands) and airspace. The UAE cut all economic ties with Iran Aug 19, one day after Iran fired two ballistic missiles toward UAE territory (UAE MoD: launched from Iran, assessed as targeting maritime traffic, both fell in the sea). No Saudi follow-on has materialized, and this desk puts the odds of one at ~30% within a week absent another launch at GCC territory. Restraint diplomacy is holding, for now
  • Market and baselines: Brent traded $93.9 intraday Aug 20, up 2.5%, a fifth straight gain. Bab el-Mandeb closure risk holds at 75-90%. Deal collapse has moved from a probability band to the operative state: the Islamabad MoU expired Aug 16-17

Day 161 Update: Najran Struck, Coordinated Strike Warning, Jeddah Pact Advances (August 6-7)

  • Najran hit, 11 wounded: a Houthi cross-border strike wounded 11 civilians in Najran Province on Aug 6, 7 Saudi nationals, 1 Yemeni, 2 Egyptian, 1 Pakistani, including a 4-year-old with burns, confirmed by the Saudi Press Agency and the Coalition Joint Forces Command. The wound pattern, dispersed and non-lethal, reads as unguided rocket or drone fire into a populated border area rather than a precision hit, continuation of the exchange that began with Riyadh's Jul 24-25 Hodeidah strikes rather than a capability jump
  • A harder warning arrives alongside it: Saudi, US, and regional intelligence issued a credible, multi-source warning the same day of imminent coordinated strikes, Iraq-based militias from the north, Houthis from the south, both under IRGC direction, aimed at energy infrastructure, ports, and airports. Nothing has hit as of this writing, but two-front coordination under one command authority is a different signature than the single-source claims this desk has tracked for months. Exposure, if it materializes, centers on the kingdom's east-coast nodes, Abqaiq, Ras Tanura, Yanbu, Jubail, the same target class Jizan's still-idle refinery already previews at smaller scale
  • Riyadh hedges its security bet: Saudi Arabia advanced a trilateral defense pact with Turkey and Pakistan in Jeddah on Aug 7, MBS, Erdogan, PM Shehbaz Sharif, and Army Chief Asim Munir all present, building on the Sept 2025 Saudi-Pakistan pact. Best read as insurance against the coordinated-attack scenario: Turkish air-defense and drone-counter capability plus Pakistani manpower layered atop a US security guarantee that has not prevented three separate hits on Saudi soil since late July
  • Baseline otherwise holds: no new Kuwait strike since Aug 1, Jizan's 400,000 bbl/day refinery remains shut with its Aug 15 restart still Aramco-unconfirmed, and Bab el-Mandeb closure risk holds at 75-90%, unchanged, since Najran is a cross-border land strike distinct from the vessel-attack pattern that stat tracks. Deal-collapse probability holds 85-90%, high end of band. See today's daily brief for full detail

Day 156 Update: MBS Presses Trump for Restraint as Jizan Sourcing Broadens (August 2)

  • Riyadh works the phone as a weekend strike option sits paused: Crown Prince Mohammed bin Salman reportedly called Trump directly to urge restraint on the threatened US/Israel strike on Iran's energy infrastructure, warning that Iran could retaliate against Gulf energy infrastructure, Saudi's own included, if the strike proceeds. The strike did not execute over the weekend; Trump's framing, an "imminent deal," not a stand-down, keeps the threat live rather than closed. MBS's warning lands with particular weight given Jizan is already reported down
  • Jizan sourcing broadens, Aramco still silent: additional outlets now report the ~400,000 bbl/day shutdown, IGCC complex and tank farm damage, and the tentative Aug 15 restart date as established fact rather than the single Reuters/IIR chain this desk has been flagging since Jul 29. That is a sourcing upgrade, not independent confirmation; Aramco and the Saudi government have still not issued an official statement on either the damage or the restart timeline
  • No new Bab el-Mandeb incident: no third Houthi strike on Saudi territory since Jul 24-25, and no fresh vessel-attack claim since the NCC Ghazal incident Jul 28. Bab el-Mandeb closure risk holds at 75-90%, unchanged. Deal collapse probability holds at 85-90% on this desk's tracking, tilting toward the lower half of that band for the first time in several versions given the paused strike and the Iran-denied Qatari corridor proposal reported the same cycle. See Aug 2's daily brief for the full picture

Day 152 Update: Jizan Shutdown Reported, Then Aramco Infrastructure Named as a Casus Belli in Iraq (July 29)

  • Jizan's damage picture gets materially worse, still unofficial: a Reuters report citing a private IIR consultancy note, republished across a dozen outlets but tracing to that single origin, says Aramco shut the 400,000 bbl/day refinery Jul 27 with damage to the Integrated Gasification Combined Cycle complex and the tank farm, a tentative Aug 15 restart. That is a materially harder picture than the storage-tank-only OSINT read logged in the Day 151 update below, but Aramco again did not reply to Reuters' request for comment, and no Saudi government confirmation exists for either version. Treat the shutdown as reported, not established
  • Aramco infrastructure becomes part of a new front's justification: overnight Jul 28-29, Iran fired ballistic missiles at a US base reportedly in Jordan, intercepted with no US casualties; US and Saudi jets struck Iran-backed militia sites across eastern Iraq in response, the first coalition strikes inside Iraq this crisis window. CENTCOM tied the strikes to "over 30 IRGC-directed aerial drone attacks in the last 72 hours" against US forces and Saudi Aramco energy infrastructure, including Jizan by name, casting the kingdom's refinery as a US-actionable target in its own right rather than only a Houthi target. Saudi Arabia's Defense Ministry separately invoked Article 51 self-defense citing the same drone campaign. This is the first time an IRGC-directed drone campaign, not solely Houthi action, has been tied to the Jizan strike, an open attribution question this desk is carrying rather than resolving
  • New Houthi tanker claim, flag pattern holds: Houthi spokesman Yahya Saree claimed a missile strike on the Saudi-flagged tanker NCC Ghazal in the Red Sea Jul 28; UKMTO partially corroborates an explosion reported during transit, crew safe, no environmental damage. This is a vessel-attack claim distinct from the Jizan/Yanbu infrastructure tally, and it hits a Saudi-flagged hull, consistent with the existing flag-based blockade scope rather than an expansion of it
  • Oil rallied off overnight lows, not a re-rating: Brent gained ~3.4% to ~$87/bbl and WTI ~3.6% to ~$82/bbl measured off Tuesday's overnight trading lows, short of a clean settlement-to-settlement 5%/24h move. Bab el-Mandeb closure risk holds at 75-90% and deal-collapse odds hold at 85-90% on this desk's tracking, tilting toward the top of that band given the new Iraq front

Day 151 Update: Riyadh Joins the Hormuz Talks Directly as Oil's Slide Deepens (July 28)

  • Saudi Arabia enters the Hormuz-specific diplomatic channel: FM Faisal bin Farhan held a direct call with Iran's Araghchi and Oman's Al-Busaidi on Jul 27, the first time Riyadh has joined what had been a bilateral Oman-Iran track on the dual-corridor reopening mechanism. This is a real widening, not just added detail, and sits alongside Qatar and Pakistan re-presenting their separate 10-day ceasefire/MoU-restoration proposal the same day. In tension with both: Iran's foreign ministry spokesman Baghaei said flatly Jul 27 that Tehran is "not engaged in any negotiations with the United States," the hardest public denial of a US channel logged this crisis window
  • Monday's price move was bigger than first reported: Brent's actual Jul 27 settlement came in at $88.36, down 8.7%, well past the ~5% captured at Monday's open; WTI settled at $82.61, down 7.5%. Tuesday extended the decline to a third straight losing session near $86.58, ~14% off last Thursday's close. Nothing physical justifies that scale on its own; this reads as compounding de-escalation optimism (the CENTCOM pause, the widening Hormuz channel, and a separate Caspian Pipeline Consortium resumption easing a non-Gulf supply worry), not a signal that Hormuz or Bab el-Mandeb has actually reopened
  • Jizan gets its first detailed damage picture, still unofficial: an independent satellite-imagery assessment (not an Aramco or Saudi government product) puts likely damage at two storage tanks in the eastern tank farm plus the Jazan Bulk Plant, with no visible hit on crude distillation, hydrocracking, hydrotreating, or hydrogen units, consistent with an inventory loss rather than a refining-capacity loss. Treat as a working estimate; the official assessment this desk has been waiting on since Jul 25 still has not been published. No third Houthi strike has landed since Jul 24-25, and Bab el-Mandeb closure risk holds at 75-90%, unchanged, since nothing has walked back the "escalation for escalation" posture on either side. Deal-collapse probability across the wider crisis holds at 85-90% on this desk's tracking

Day 150 Update: Yanbu Cleared, Monday's Price Test Breaks the Other Way (July 27)

  • Yanbu confirmed undamaged: Saudi officials stated the export terminal, the Red Sea outlet for the East-West Pipeline bypass, "was no longer at risk" and sustained no damage from the Jul 24-25 Houthi strike. Jizan refinery still has no official Aramco or government damage assessment. No third Houthi strike has landed since
  • The Monday price test broke the wrong way: Brent opened at $91.70/bbl (-5.25%), easing to $92.27 (-4.66%) by mid-morning European trading, off the $96-98 plateau held since the Jul 24 settlement. The driver is a third consecutive CENTCOM pause night and renewed Oman-Iran talks on a Hormuz reopening mechanism, not confirmation of Saudi damage; the Aramco strike alone would have argued for a higher print, not a lower one
  • Closure risk unchanged at 75-90%: the Yanbu resolution and the quiet 48 hours since the last Saudi-Houthi exchange are read as the blockade holding at its current level rather than de-escalating; nothing has walked back the "escalation for escalation" posture on either side. Deal-collapse probability across the wider crisis holds at 85-90% on this desk's tracking, though Monday's market move is consistent with traders pricing something closer to 65-75%

Day 149 Update: Houthis Hit Aramco Directly (July 25-26)

  • The vow becomes an attack: Houthi forces fired ballistic missiles, cruise missiles, and drones at Aramco's Jizan refinery and the Yanbu export terminal overnight Jul 24-25, the first direct strike on Saudi oil infrastructure this crisis window. Every prior Houthi action under the Jul 20 blockade targeted tankers, not facilities. This makes good on the "escalation for escalation" vow issued after Riyadh's Jul 24 Hodeidah strike, and it took under 24 hours to convert from words to a strike on the kingdom's own soil
  • Yanbu held, on the numbers available: a Patriot battery intercepted both incoming ballistic missiles at the terminal. Jizan is a different story: satellite data (NASA FIRMS) confirms a fire at the refinery, and trading sources describe "some damage," though that detail is single-sourced and Aramco has issued no official assessment of either site as of this writing
  • Riyadh answers again: the Coalition Joint Forces Command confirmed a second retaliatory strike on Houthi targets Jul 25, warning of further response "without leniency." That is two Saudi strikes on Houthi positions inside 48 hours, a tempo this desk has not seen since the blockade began Jul 20
  • Why Yanbu is the number that matters: Jizan's ~400,000 bbl/day of refining capacity is substitutable through imports if it stays offline. Yanbu is not substitutable at all, it is the sole outlet for the East-West Pipeline bypass, and with Hormuz-dependent exports collapsed toward zero (1 tanker transited Jul 23, the lowest since May 7), every barrel the kingdom currently gets to market clears that one terminal. No confirmed loading-capacity loss exists yet; the demonstrated fact is that the terminal now sits inside Houthi engagement range, not just the shipping lane in front of it
  • Closure risk revised up again: to 75-90% from 70-85%, reflecting a demonstrated shift from tanker-only targeting to direct infrastructure strikes, the more dangerous half of the "escalation for escalation" threat. This desk's separate defense read puts the odds of a third Saudi-Houthi round at ~50/50 within 72 hours, given the two-strike pattern already set and Riyadh's "without leniency" language. Deal-collapse probability across the wider crisis holds at 85-90%, unchanged
  • Separately, the Iran-US track cooled: CENTCOM paused its strike campaign against Iran after 13 consecutive nights, the first pause in two weeks, reportedly because Trump held off a 14th-night plan to let a new Oman-mediated channel on Hormuz reopening mechanics develop. That front easing while the Saudi-Houthi front hardens is not treated here as a stable trade-off; the Houthis remain Iran's proxy, and a further hit on Saudi oil infrastructure is a plausible trigger for the paused campaign to resume

Day 148 Update: Riyadh Strikes Back (July 24-25)

  • Threat becomes action: Saudi-led coalition strikes hit Houthi-controlled sites in Hodeidah governorate late July 24, telecommunications facilities and Kamaran Island, injuring one woman per Houthi media; Saudi's Ministry of Defense said the port of Hodeidah itself was not targeted. This is the kingdom's first combat action against the Bab el-Mandeb blockade, making good on the "force" threat issued July 22 and left unexecuted for two days
  • The Houthi response is a warning, not yet an action: the Houthi-run foreign ministry called the strikes the start of "escalation for escalation." Nothing has followed as of this writing. Whether that promise converts into a widened blockade (Saudi-origin cargo on any flag, not just Saudi-flagged hulls) or a strike on Saudi mainland/Aramco-linked infrastructure is the question that determines whether this stays a contained exchange or fuses with the Hormuz crisis into a genuine dual-chokepoint emergency
  • The flag-based workaround held through the strikes: two COSCO-operated VLCCs (flagged Singapore and Hong Kong, not China) carried ~4M barrels of Saudi-origin Yanbu crude through Bab el-Mandeb Jul 23-24 without incident, confirming Riyadh's non-Saudi-flag carve-out was still functioning in the hours before and after the Hodeidah strikes. This desk treats that pattern as provisional, not structural, given last night's escalation
  • Closure risk revised up again: to 70-85% from 65-80%, reflecting a demonstrated Saudi willingness to escalate rather than absorb losses indefinitely, paired with an explicit Houthi threat of reciprocal escalation. This desk's separate geopolitical read puts overall escalation risk at 8 out of 10 (up from ~7), while judging the Saudi target set, telecom infrastructure and an island facility rather than the port, as calibrated signaling rather than the reopening of the 2015-2022 war. Deal-collapse probability across the wider crisis holds at 85-90%, unchanged

Day 146 Update: First Confirmed Strike at Bab el-Mandeb (July 22-23)

  • From diversion to casualty: the Saudi-flagged tanker Encelia was struck by a projectile in the Red Sea after departing Yanbu and caught fire at the bow. UK Maritime Trade Operations confirmed the hit independently; the Saudi Press Agency confirmed the vessel and the fire. Crew are fighting the blaze and are reported safe. The Houthis also claim a strike on a second tanker, the Layla, not yet independently confirmed. This is the first confirmed vessel casualty since the blockade went operational July 21-22
  • Houthis harden their own framing to match: spokesman Yahya Saree declared Bab el-Mandeb "fully closed" to Saudi-flagged tankers going forward, an escalation from the "embargo" language used since the July 20 declaration. Seatrade Maritime independently counts at least 7 vessels that have changed course; the Houthis claim 10
  • Riyadh's threat is now under real pressure to become operational: Saudi Arabia threatened "force" against the blockade July 22 and has not yet used any. A confirmed strike on a named, flagged tanker raises the cost of continued restraint on both sides of that choice, hold off and the bypass keeps degrading voyage by voyage, strike back and the kingdom opens a direct fight with the Houthis on top of the Hormuz standoff it is already managing
  • Insurance repricing pending: the 0.75% Bab el-Mandeb war-risk hull premium set off the bare declaration has not yet been re-quoted since the strike; expect the next dated print to move materially higher. One shipbroker (Breakwave Advisors) reported a charterer this week pricing a 54-day Yanbu-to-South Korea option via Suez and the Cape of Good Hope, against ~24 days direct, the clearest sign yet that Asia-bound charterers are treating the Cape diversion as a real option rather than a hypothetical
  • Closure risk revised up again: to 65-80% from 55-70%, reflecting a demonstrated attack rather than diversion behavior alone. The pipeline itself remains undamaged; this is a sea-lane risk sitting downstream of a still-functioning bypass. Deal-collapse probability across the wider crisis holds at 85-90%, unchanged

Day 145 Update: Blockade Goes Operational, Vessels Divert (July 21-22)

  • From declaration to practice: the July 20 Houthi embargo produced its first hard evidence of operational effect on July 21. At least six vessels reversed course rather than complete Saudi-bound transits, including the VLCC Xin Long Yang; CNN separately reports two Saudi crude tankers turned back. No vessel has been struck or boarded near Bab el-Mandeb yet, but charterers do not reroute a VLCC on rhetoric alone, this is the same leading indicator that preceded Hormuz's own war-risk blowout earlier in the crisis
  • Riyadh hardens its position: Saudi Arabia's Foreign Ministry moved from Monday's flat "disinformation" denial to "categorically dismissed," pledging "all lawful measures under international law" to protect shipping, and citing 300+ ships that docked at Yemen's northern ports in H1 2026 as evidence against the siege framing. The tone is sharper; the underlying operational picture (no confirmed strike) is unchanged
  • Premium already set, more pressure expected: the 0.75% Bab el-Mandeb war-risk hull premium was priced off the bare declaration a day before any vessel moved. With ships now actively diverting, the next repricing cycle should move further; the standing Hormuz band (3-10% of vessel value) remains the reference point for how far this could run
  • The Asia leg is the exposed one: Europe-bound Yanbu cargo exits north via Suez and is unaffected. Asia-bound cargo, most of the route's demand, is what's diverting. If that stalls while Yanbu-to-Europe stays clean, the kingdom's bypass strategy survives in name but fails on the leg that matters most for its highest-value Asian buyers (Japan, South Korea, India, Singapore)
  • Closure risk revised up again: to 55-70% from 50-65%, reflecting realized diversion behavior rather than a further rhetorical escalation. This is not yet a confirmed physical closure; the risk band accounts for shipping already voting with its routing before any strike has landed. Deal-collapse probability across the wider crisis holds at 85-90%, unchanged

Day 144 Update: Houthis Declare Embargo, Saudi Denies, Insurers Reprice (July 20-21)

  • Declaration, not detonation: Yemen's Houthi forces announced a formal maritime embargo against Saudi Arabia on July 20, targeting the Bab el-Mandeb transit that carries the kingdom's entire ~2.5M bbl/day Yanbu bypass (East-West Pipeline, ~7M bbl/day nameplate). The stated trigger was an alleged Saudi strike on Sanaa airport. No vessel near the strait has been hit, boarded, or turned away as of this writing; the embargo is declared, not operational
  • Riyadh pushes back: Saudi Arabia issued its first on-record response July 21, calling the embargo "disinformation" and pointing to its continuing humanitarian aid deliveries to Yemen as evidence against the Houthi claim. The denial does not settle the operational question either way, but it is a new diplomatic data point and the kingdom's first public acknowledgment that the declaration exists at all
  • The insurance market answered first: hours after Monday's declaration, and a full day before Riyadh's denial, Bab el-Mandeb war-risk hull premiums jumped ~150%, from about 0.3% to 0.75% of vessel value -- the first time underwriters have repriced this chokepoint separately from the standing Hormuz war-risk band, which sits unchanged at 3-10% of vessel value. Underwriters price probability for a living, and a 150% one-day move on a declaration alone, with zero confirmed incidents, says more about how seriously the market takes the threat than either side's public statements do. The gap to the Hormuz band still matters: even after repricing, Bab el-Mandeb sits far below Hormuz's realized-war premium, so this reads as underwriters pricing meaningful new risk, not treating the route as functionally closed
  • Loadings data points the same direction, with a caveat: Kpler tracking shows total Saudi crude loadings fell 36% over two weeks, from 9.5M bbl/day (week of June 29) to 6.1M bbl/day (week of July 13), split ~evenly between west-coast (4.23 to 2.79M bbl/day) and Asia-bound (5.30 to 3.32M bbl/day) flows. That total covers all Saudi crude loadings, not the Yanbu-pipeline-specific flow this brief carries separately at ~2.5M bbl/day, and the decline predates the July 20 embargo declaration -- it tracks with the broader threat climate since the July 14 Abha strike, not the embargo itself. Treat the two figures as related but distinct; do not read the 36% drop as embargo impact
  • Closure risk revised up again: the shift from Houthi rhetoric (brandishing Bab el-Mandeb, per the July 15 update below) to a formal declared embargo, combined with the market's own repricing, moves Bab el-Mandeb closure risk to 50-65%, up from 40-55%. The move reflects a threshold crossed on paper and in the insurance market, not an operational one; zero vessels have been hit. Deal-collapse probability across the wider crisis holds at 85-90%, unchanged

Day 138 Update: First Strike on Saudi Territory (July 14-15)

  • Abha struck, intercepted: Houthi forces fired ballistic missiles and drones at Abha International Airport in southern Saudi Arabia on July 14 -- the first Houthi-Saudi kinetic exchange since the 2022 ceasefire and the first strike on Saudi soil by any actor in this crisis. Saudi air defenses reported intercepts; no confirmed damage or casualties. The kingdom's unstruck status, held through five months of war, is over
  • The trigger ran through Sanaa: a July 13 strike on Sanaa airport's runway, claimed by Yemen's internationally recognized government, aimed at stopping an Iranian aircraft carrying a Houthi delegation home from Khamenei's funeral. The Houthis blame Riyadh. Saudi-led forces struck Saada in response to Abha
  • De-escalation declared over: Houthi officials declared the "de-escalation phase" over, threatened a "siege" on Saudi airports, and called Bab el-Mandeb "a strategic asset Yemen has the luxury of utilising"
  • Why this matters more than the intercepts suggest: the kingdom's entire Hormuz workaround runs through the Red Sea. The ~2.5M bbl/day East-West Pipeline bypass to Yanbu depends entirely on Red Sea/Bab el-Mandeb transit, and Suez throughput is already down 50-60% y/y (see Egypt). A Houthi force that has declared de-escalation over and openly brandishes Bab el-Mandeb puts the bypass in play without firing at a single tanker. No move against Red Sea shipping has followed the Abha exchange as of July 15 morning; Bab el-Mandeb closure risk is revised UP to 40-55% from 25-35%
  • Riyadh's dilemma is acute: it backed Washington's diplomatic track, stayed unstruck by Iran through five months of war, and has been dragged in anyway via Yemen -- the theater it has spent a decade trying to exit. Whether the exchange escalates to a second round or is contained is the key watch
  • Wider war context (Day 138): the IRGC declared Hormuz closed until further notice on July 11; the US naval blockade of Iranian ports took effect 4:00 PM ET July 14 with no enforcement actions confirmed yet (20+ warships, Iran reportedly preparing a "test" per CNN, headline-level); CENTCOM's fifth consecutive strike wave began the morning of July 15. Brent ~$85/bbl, with markets pricing the Houthi entry as incremental, not step-change. Deal-collapse probability holds at 85-90%

Energy Profile

MetricValue
Crude oil production capacity~12M bbl/day (world's largest spare capacity holder)
Current production~10M bbl/day (OPEC+ restrained; export-limited, not production-limited, since Feb 28)
OPEC+ quotaSuccessive 2026 increases largely undeliverable while Gulf loadings are choked; spare capacity is stranded, not absent
Crude oil exports (pre-crisis)~6.5-7M bbl/day
Proven reserves~267B barrels (2nd largest globally)
Refining capacity~3.3M bbl/day (domestic + joint ventures)
Natural gas production~11 Bcf/day (mostly associated gas; no LNG exports)
Hormuz-dependent exports (pre-crisis)~5.5M bbl/day (~80% of total exports via Ras Tanura/Ju'aymah), all routed through the Strait of Hormuz
Red Sea exports (Day 94)Pipeline pushed toward full capacity; Yanbu terminal loadings cap real throughput near ~3-4.5M bbl/day (Vortexa ~3M under wartime conditions)

Key Infrastructure

  • Abqaiq Processing Facility: World's largest crude oil stabilization plant; ~7M bbl/day capacity; critical node, as all Saudi crude passes through Abqaiq before export or pipeline routing; targeted by Houthi drones in 2019
  • Ras Tanura Terminal: ~9M bbl/day export capacity; largest offshore oil loading facility globally; located on Persian Gulf coast, fully exposed to Hormuz closure
  • Ju'aymah Terminal: ~3M bbl/day capacity; secondary Gulf coast export terminal; also Hormuz-dependent
  • East-West Pipeline (Petroline): Abqaiq to Yanbu (Red Sea); the primary Hormuz bypass. Nameplate pushed to ~7M bbl/day after NGL lines were converted to crude; Aramco says ~5M bbl/day of that is available for export with the balance feeding west-coast refineries. Aramco reported it back to full capacity Apr 12 after the Jubail-area attacks. Pre-crisis usage was ~2M bbl/day, so the wartime ramp is real but the binding constraint is downstream at Yanbu, not in the line. Current status: SHUT since Sep 11 with damage at two pumping stations, PS8 and PS9. Treat the ~5M bbl/day figure here as Aramco's stated export-available nameplate, not as observed flow; observed flow into the western system ran ~2.0M bbl/day in August (see the Day 202 update above)
  • Yanbu Terminal: Red Sea coast; the two terminals (Yanbu North/South) cap nominal combined loadings near ~4.5M bbl/day, with market sources putting tested throughput closer to ~4M and Vortexa estimating ~3M under wartime conditions. This terminal ceiling, not pipeline capacity, is what limits how much crude actually leaves the country while Hormuz is choked. Current status: no cargo has departed since Sep 11, with no restart, no force majeure and no Aramco statement; storage has drawn below 15M bbl from close to 21M in July
  • Ras Al Khair / Jubail Industrial Cities: Petrochemical and desalination complexes on the Gulf coast; exposed to Iranian missile/drone threat. Sadara ($20B Aramco-Dow JV) shut all production in late March on Hormuz supply-chain disruption (1.5M t/yr ethylene, 750K t polyethylene, plus propylene oxide and MDI offline, no restart timeline). IRGC then struck Jubail Apr 7, hitting Sadara and ExxonMobil facilities with medium-range BMs and suicide drones; physical damage extends the restart from weeks to months. Sadara carries billions in debt and the prolonged outage compounds its repayment pressure. Jubail accounts for ~6-8% of global petrochemical output
  • Ghawar Field: World's largest conventional oil field; ~3.8M bbl/day production; located in Eastern Province near Gulf coast

Key Actors

  • Crown Prince Mohammed bin Salman (MBS): De facto ruler; controls defense, economic, and energy policy. Now a lead regional mediator on the US-Iran Hormuz deal. Joined Trump's May 24 joint leader call (alongside Qatar, Jordan, UAE, Bahrain, Egypt, Turkey, and Pakistan's army chief) on the MoU. During the war he was reported "close to a decision" on joining strikes on Iran and granted the US access to King Fahd Air Base
  • Saudi Aramco: State oil company (world's most profitable); operates all upstream, pipelines, and export infrastructure; managing pipeline ramp-up to Yanbu
  • Ministry of Energy (Prince Abdulaziz bin Salman): OPEC+ coordination, production quota management, crisis supply allocation
  • Royal Saudi Air Force / Air Defense: Through the active-war phase, intercepted Iranian ballistic missiles and drones over the Eastern Province (dozens daily at peak). King Fahd Air Base access granted to US (Mar 24), a reversal from earlier refusal and the first major Saudi basing concession of the conflict. With the ceasefire indefinite but violated since Apr 21, intercept tempo fell sharply, but the threat envelope over Eastern Province oil infrastructure was never retired. On Jul 14 Saudi air defenses intercepted the Houthi ballistic missile and drone strike on Abha airport -- the first defense of Saudi territory itself in this crisis, opening a second threat axis from the southwest
  • SABIC: State petrochemical company; downstream operations at risk from Gulf coast attacks

OPEC+ Role & Compliance

  • Saudi Arabia is the de facto OPEC+ leader and swing producer
  • Spare capacity is the core story: Saudi holds ~3M bbl/d of spare capacity, the bulk of OPEC's, and it sits largely stranded behind Hormuz. The only path to market is the Petroline to Yanbu, and that path is capped at the Yanbu terminals (~3-4.5M bbl/d), not in the line itself
  • Quota mechanics are secondary while loadings are choked. Successive 2026 OPEC+ increases are undeliverable in practice; compliance discipline is hard to enforce when members cannot physically export. The constraint is export logistics, not the quota sheet
  • Aramco's own read: the CEO said (May 11) the oil market will not normalize until 2027 if the Hormuz disruption persists. Aramco still posted a Q1 profit jump on the East-West pipeline workaround, but the bypass cannot replace the ~6M bbl/d the kingdom moved through Hormuz pre-war
  • If the MoU holds and Hormuz reopens with no tolls and mines cleared, the constraint flips back to the demand side and to clearing the ~600 stranded tankers inside the Gulf; Gulf members would prioritize backlog clearance over coordinated quotas. That reopening is not yet in hand: the 60-day MoU was tentative on May 28 and remains unsigned

Crisis Exposure (Hormuz Closure, Day 94)

  • ~80% of pre-crisis exports were Hormuz-dependent (Ras Tanura, Ju'aymah terminals), effectively halted since Feb 28 and still choked. The strait is "open on paper" (Araghchi declared it open to all shipping Apr 17) but open transits have run near zero since ~May 6; mines are uncleared, insurance and P&I are not restored, and the US "dual blockade" of Iranian ports has been in place since Apr 13
  • The East-West pipeline workaround held through the war and was reported back to full capacity Apr 12 after the Jubail-area attacks. The kingdom kept moving crude to Yanbu, but the bypass cannot replace the ~6M bbl/d that went through Hormuz, and the binding limit is the Yanbu terminal ceiling (~3-4.5M bbl/d), not the line
  • Yanbu exports must transit the Bab el-Mandeb strait, where Houthi anti-ship capability (drones, missiles, Iranian coordination) sits on the far side of the bypass. The Houthis joined the war Mar 28 and explicitly threatened Bab el-Mandeb closure, so the bypass swaps one chokepoint exposure for another
  • Jubail / Sadara: Sadara shut all production in late March on Hormuz supply-chain disruption; IRGC then struck the complex Apr 7. Physical damage pushes any restart from weeks to months, and Sadara's heavy debt load means the prolonged outage carries mounting financial pressure
  • Mediator role: Saudi is now central to the diplomacy. MBS joined Trump's May 23/24 joint leader calls on the MoU. The 60-day US-Iran framework (Hormuz reopens no tolls, Iran clears mines within 30 days; US lifts the port blockade proportionally and issues sanctions waivers; Iranian nuclear commitments) was tentatively reached May 28 but is unsigned by both sides, with Trump adding demands May 29-30 that landed badly in Tehran
  • Residual military risk: the ceasefire has been indefinite since Apr 21 but repeatedly violated (US strikes Apr 19, May 7, May 25, plus late-May "defensive strikes" answered by Iranian BMs on Kuwait). Eastern Province oil infrastructure remains inside Iran's threat envelope even with intercept tempo down from the wartime peak
  • Aramco CEO (May 11): the oil market will not normalize until 2027 if the Hormuz disruption persists. DHL estimates 4-6 months to normalize logistics once the strait genuinely reopens
  • ~600 tankers are stranded inside the Gulf and ~240 waiting outside; clearing that backlog will compete with any coordinated OPEC+ quota plan once loadings resume

Ceasefire and Deal Status (Day 94)

  • Ceasefire indefinite since Apr 21 (Trump extended it from the two-week Apr 8 truce), but fragile and repeatedly violated. The US naval blockade of Iranian ports persists alongside it
  • 60-day MoU tentative May 28, unsigned by both sides. Reported terms: Hormuz reopens with no tolls and Iran clears its mines within 30 days; the US lifts the port blockade proportionally and issues sanctions waivers letting Iran sell oil; Iran commits never to pursue nuclear weapons and to negotiate an enrichment suspension. Trump added new demands May 29-30; Iranian state media says it is not finalized on its end either
  • Oil deflated on the diplomacy: Brent ~$91/bbl, down from the ~$115 WTI peak on Apr 7 and off ~19% across May, its worst month since 2020
  • Saudi exports via Yanbu continue regardless of Hormuz status, but a genuine reopening is what restores Ras Tanura and Ju'aymah capacity and unfreezes the ~3M bbl/d of stranded spare

Houthi Threat to Bypass Route

  • All Yanbu exports must transit Bab el-Mandeb strait and Red Sea, within Houthi engagement range
  • Houthis have demonstrated anti-ship capability: kamikaze drones (Iranian-supplied Shahed variants), anti-ship ballistic missiles, naval mines
  • Houthi attacks on Red Sea shipping escalated throughout 2024-2025; the Houthis joined this war Mar 28 and threatened Bab el-Mandeb closure
  • The threat is no longer latent (Jul 14): the Houthis struck Abha airport, declared the "de-escalation phase" over, and called Bab el-Mandeb "a strategic asset Yemen has the luxury of utilising" -- the first Houthi-Saudi exchange since the 2022 ceasefire, and the first time in this crisis the chokepoint has been brandished directly against Riyadh rather than Israel. Closure risk was revised UP to 40-55% from 25-35% as of July 15
  • Declared, not yet struck (Jul 20-21): the Houthis converted the rhetoric into a formal maritime embargo on July 20; Saudi Arabia denied it as "disinformation" July 21 while Bab el-Mandeb war-risk hull premiums jumped ~150% (0.3% to 0.75% of vessel value), the clearest market signal yet that underwriters are pricing the threat as real. Closure risk revised UP again, to 50-65% (see the July 21 update above)
  • Struck (Jul 22-23): the tanker Encelia was hit and set afire off Yanbu, the first confirmed vessel casualty since the blockade went operational; Houthi spokesman Yahya Saree declared the strait "fully closed" to Saudi-flagged tankers. Closure risk revised UP again, to 65-80% (see the Day 146 update above)
  • Riyadh strikes back (Jul 24-25): Saudi Arabia hit Houthi sites in Hodeidah governorate, its first combat action in this dispute; the Houthis vowed "escalation for escalation" but had not yet acted on it as of that writing. Closure risk revised UP again, to 70-85%
  • The vow acted on (Jul 24-25 overnight into Jul 26): Houthi forces struck Aramco's Jizan refinery and the Yanbu terminal directly, the first hit on Saudi oil infrastructure rather than a tanker or the strait itself. Riyadh retaliated a second time Jul 25. Closure risk revised UP again, to 75-90% (see the Day 149 update above)
  • If Houthis close Bab el-Mandeb while Hormuz stays choked, the Saudi bypass route collapses entirely
  • France deployed the Charles de Gaulle carrier group plus frigates and allied warships for Red Sea escort (USNI/France24, Mar 9); this partially mitigates but does not eliminate the risk
  • The heavier the kingdom leans on Yanbu loadings to offset Hormuz, the higher-value the Bab el-Mandeb transit becomes as a Houthi target

Structural Vulnerabilities

  • East-West Pipeline is a single-point bypass; no redundant overland route to a non-Gulf coast
  • The real ceiling is downstream: even with the line at ~7M bbl/day nameplate and ~5M available for export, the Yanbu terminals cap loadings near ~3-4.5M bbl/day. The kingdom cannot fully self-rescue from a Hormuz closure through this route alone
  • Abqaiq remains a critical chokepoint: all crude passes through it. The 2019 drone attack proved its vulnerability
  • Eastern Province (Ghawar, Ras Tanura, Ju'aymah, Abqaiq) is within Iranian missile range
  • Bab el-Mandeb / Houthi threat creates a second chokepoint on the bypass route
  • Government budget ~60-70% oil-dependent; prolonged export disruption strains fiscal position even with reserves
  • Desalination plants on Gulf coast at risk; water security linked to energy infrastructure

TankerBrief Coverage Angle

Aramco investors, Gulf-based energy companies, sovereign wealth funds, commodity trading desks, logistics and shipping firms, OPEC analysts. The Day 94 questions (would the unsigned MoU hold, when would stranded tankers clear) have been overtaken: the deal is at 85-90% collapse probability, the IRGC declared Hormuz closed Jul 11, and the collapse back to active strikes has happened. The Day 138 question, whether the Houthi-Saudi exchange stayed a single round, is answered: it escalated into a declared maritime embargo on July 20. The Day 145 question, whether the first confirmed physical incident at Bab el-Mandeb would follow the diversions, is now answered: the tanker Encelia was struck and set afire July 22. The Day 146 question, whether Riyadh converts its unexecuted force threat into an actual strike on Houthi positions, is also answered: coalition strikes hit Hodeidah governorate July 24. The Day 148 question, whether the Houthis' "escalation for escalation" vow stayed rhetorical, is answered: it did not. Jizan and Yanbu were struck directly within a day. The Day 149 question, whether Aramco's damage assessment would show confirmed loading-capacity loss at Yanbu, is now partly answered: Saudi officials confirm Yanbu itself came through undamaged, though Jizan remains unassessed. The Day 150 question that moves money is why Brent fell rather than rose at Monday's open, the first clean price test of the Aramco strike, and whether that de-escalation move holds against a still-unsigned Oman-Iran mechanism and an unresolved Jizan assessment. They need: the ~2.5M bbl/d Yanbu bypass flow and its total Bab el-Mandeb dependency, Bab el-Mandeb closure risk (holding at 75-90%), confirmed versus assessed damage at Jizan, Abqaiq and Eastern Province threat status now that Saudi oil infrastructure itself has been struck once, Ras Tanura/Ju'aymah restart readiness against a closed Hormuz, and whether the flag-based cargo workaround survives further Houthi retaliation. Base case: Brent reverts toward $94-99/bbl within the week if the diplomatic optics fail to convert into a signed mechanism; sharp downside on a signed corridor deal, sharp upside on a third Houthi strike or a material Jizan capacity-loss finding. The Day 202 questions are narrower and they are the ones that move money now: whether a bypassed Petroline restarts at half capacity within days as Bloomberg's single anonymous source says, whether Yanbu the terminal resumes loading at all, and whether a market that is trading the pipeline notices that those are two different events. Carry ~1.8-2.3M bbl/day of crude at risk rather than the retired ~2.5M and ~5M line figures, and treat the $94-99 Brent base case above as a July artifact: Brent traded $103.38-104.59 intraday on Sep 17.