Saudi Arabia's East-West Pipeline, branded Petroline, is the single most important piece of crude-export infrastructure outside the Strait of Hormuz. During the 2026 crisis it has been carrying ~3 mb/d from the Eastern Province to the Red Sea terminal at Yanbu — almost four times pre-war throughput. Without it, Saudi Arabia's entire export book would be hostage to Hormuz transit. And without an open Red Sea route downstream of Yanbu, the pipeline's value collapses to zero.

⚠️ STATUS (Sep 22, 2026) — PARTIAL RESTART AT LOW RATE. Per 2026-09-22-reuters-saudi-ew-pipeline-restart (Reuters, three sources briefed): Saudi Arabia has restarted operations at the East-West Pipeline as of Sep 22, with one Yanbu cargo scheduled later in the day (bound for China). Pipeline is pumping at a low rate (rate undisclosed). Aramco target = 4 mb/d (one source); a security source says full resumption could take weeks. Saudi Aramco has not officially confirmed (Reuters comment request unanswered). Pre-shutdown throughput was ~4 mb/d. This is NOT a return to pre-shutdown capacity; it is a partial, low-rate restart with downstream Bab al-Mandab disruption unchanged. See "Status: Sep 22 Restart" section below for full detail.

Status: Sep 22 Restart (PARTIAL-LOW-RATE)

What is confirmed (Sep 22, 2026)

Fact Source Confidence
Pipeline restarted, operations resumed Reuters Sep 22 (3 sources briefed on the matter) High
Pipeline pumping at a low rate (rate not disclosed) Reuters Sep 22 (2 of 3 sources) High on "low"; rate number unknown
One cargo scheduled to load at Yanbu later Sep 22, bound for China Reuters Sep 22 (1 source) High
Aramco target = 4 mb/d Reuters Sep 22 (1 source) Medium (single source)
Full resumption = weeks Reuters Sep 22 (1 security source) Medium
Saudi Aramco has NOT publicly confirmed Reuters Sep 22 ("did not immediately respond to a request for comment") High — explicit

What is NOT confirmed / unknown

Unknown Why it matters
Actual initial throughput rate Reuters says "low rate" but gives no number. Aramco target = 4 mb/d, but initial rate is some unspecified fraction.
Damage assessment from Sep 11 strikes Multiple pumping stations in Riyadh and Medina regions hit (2026-09-12-aljazeera-saudi-pipeline-shutdown-explainer); no public engineering assessment has been published.
Whether the full 4 mb/d is achievable within stated "weeks" "Weeks" is qualitative; could be 2 weeks or 6+ weeks.
Aramco's official statement Reuters comment request unanswered at time of publication. The company may issue a separate statement, or remain silent on operational security grounds.
Whether Bab al-Mandab downstream is navigable for Yanbu crude Houthi embargo active since Jul 20; Mayun island seized early Sep (2026-09-12-aljazeera-saudi-pipeline-shutdown-explainer). No change reported in the Sep 22 wire. First cargo is China-bound (likely Mediterranean via Port Said STS or Sidi Kerir) — not south to Bab al-Mandab.
Hormuz-side loadings compensating during the Sep 11–22 outage The National (Sep 22): 7 VLCCs / 14 mmbbl loaded at Ras Tanura over the weekend — i.e., Saudi diverted to Gulf/Hormuz route while pipeline was down. This affects net disruption accounting.

Status label

Confirmed partial restart at low rate; full restoration = weeks-scale; downstream Bab al-Mandab disruption unchanged; Aramco has not officially confirmed.

Implications for Saudi export routing

  1. Yanbu-bound cargoes have restarted (one cargo Sep 22, China-bound). This is NOT a return to the 4–5 mb/d Yanbu loadings that prevailed pre-Sep 11.
  2. Mediterranean re-route is being prepared — Port Said (Egypt, STS) and Sidi Kerir (Egypt, direct discharge) are receiving pre-positioned tankers. This routes Yanbu crude north, not south, bypassing Bab al-Mandab risk. It also adds 1–3 days to Mediterranean-bound voyages vs. direct Red Sea / Suez routing.
  3. Hormuz-side loadings remain elevated. Saudi loaded 7 VLCCs (~14 mmbbl) at Ras Tanura over the weekend (Sep 20–21). This is consistent with a dual-track export strategy: Yanbu partial-restart + Hormuz ramp-up to compensate. It does NOT imply Hormuz has fully normalized — it implies Saudi is using whatever routing works while the pipeline and downstream channels remain fragile.
  4. Pre-shutdown 4 mb/d rerouting is the recovery benchmark, not the current state. Initial restart rate is below this; "low rate" could be anywhere from a few hundred thousand b/d to ~3 mb/d.

Implications for production shut-ins

east-west-pipeline's prior storage-lag analysis remains valid: at 4 mb/d pre-shutdown inbound to Yanbu, Yanbu's 3–5 mb working storage could absorb 1–2 days of full flow before forcing Aramco to throttle Eastern Province production. The reverse logic applies during the Sep 11–22 shutdown:

  • During the shutdown, Yanbu was drawing down storage to continue loading. Per Egypt Oil & Gas (Sep 22, citing Reuters): "stocks at Yanbu could sustain shipments for only several days without pipeline flows" — consistent with the 3–5 mb working storage assumption but tighter than the KB's prior wording.
  • The 9–12 day outage (Sep 11 → Sep 22) likely forced Aramco to either:
  • (a) Throttle Eastern Province production by some amount (most likely — matches prior analysis); OR
  • (b) Drain Yanbu storage while continuing limited Hormuz-side loadings.
  • A partial restart at "low rate" does not fully reverse this. Even at 2 mb/d inbound (mid-range estimate), Yanbu will refill storage before Aramco can return to full Eastern Province throughput. Some level of production cut persists until the pipeline is back at the 4 mb/d pre-shutdown rate AND Bab al-Mandab is navigable.

Implications for the 14–18 mb/d Thierry Bros estimate

2026-09-12-thierry-bros-x-shock-14mbd-disrupted's reconciliation is partially but not fully reversed:

State Period Net barrels unavailable
Bros baseline (pre-Sep 11) Jul – Sep 10 ~14 mb/d
Post-shutdown peak Sep 11 – Sep 21 ~17–18 mb/d (full) / ~13–15 mb/d (production-cut basis)
Post-partial-restart (today, Sep 22) Sep 22 onwards ~15–17 mb/d (full) / ~11–13 mb/d (production-cut basis)

The exact post-restart figure depends on the initial rate (not disclosed). At 1 mb/d initial restart, the figure is closer to 16–18 mb/d; at 3 mb/d, it is closer to 14–16 mb/d. The 14 mb/d Bros headline is no longer current — it is somewhere between Bros' 14 mb/d baseline and the 17–18 mb/d post-shutdown peak.

Critical caveat: pipeline restart ≠ production restoration

Per task acceptance criteria: "no claim that pipeline restart restores all Saudi exports." This is reinforced by:

  1. Pipeline capacity ≠ production throughput. Even at the full 4 mb/d target, Saudi's pre-crisis export book was substantially larger (~7–8 mb/d of crude exports) and required multiple routings.
  2. Bab al-Mandab downstream is still embargoed. Yanbu crude heading south faces Houthi risk; the Sep 22 first cargo is heading north (China via Mediterranean), not south.
  3. Hormuz re-route compensates partially. Saudi loaded 14 mmbbl at Ras Tanura over the weekend. This is a partial substitution, not a return to normal Hormuz flow.
  4. Damage at pumping stations is undisclosed. Multiple stations hit in Riyadh and Medina regions. Even a 4 mb/d target is contingent on engineering assessment not yet public.

Route capacity is not production restoration. A 4 mb/d Yanbu-bound restart at most restores 4 mb/d of bypass capacity, not 4 mb/d of new Saudi production. The Eastern Province production shut-in during Sep 11–22 may have been on the order of 1–3 mb/d, and that shut-in is partially but not fully reversed.

What It Is

The East-West Pipeline runs approximately 1,200 km across the Arabian Peninsula from Abqaiq (Eastern Province, adjacent to Ghawar and Aramco's main processing complex) westward to Yanbu on the Red Sea coast. Key parameters:

  • Nameplate capacity: ~5 mb/d across two parallel lines (per csis-seigle-2026; brookings-timing-impending-crude-crisis cites up to 7 mbd theoretical max).
  • Pre-2026 throughput: 1.5–2 mb/d, mostly feeding Yanbu's domestic refineries and a modest export program.
  • Construction era: Built in the 1980s specifically to give Saudi Arabia a land bridge to bypass Hormuz. It is the only pipeline in the Gulf region with multi-million-bpd capacity — ~3× over the UAE Habshan–Fujairah line and an order of magnitude over every other Gulf state's bypass capacity (Iraq, Kuwait, Bahrain, and Qatar have zero bypass, per csis-seigle-2026).
  • Endpoint: Yanbu export terminal on the Red Sea, where crude loads into VLCCs for routing north to Suez/Sidi Kerir or south toward Bab al-Mandab.

Strategic Role During the 2026 Crisis

When Hormuz effectively closed after February 28, 2026, the East-West Pipeline became the binding constraint for Saudi export routing. The ramp-up is documented quantitatively:

Period Yanbu loadings / pipeline status Source
Pre-conflict (Feb 2026) ~0.735 mb/d (baseline) wood-mackenzie-crude-export-collapse-60pct-2026
April 2026 >3.0 mb/d wood-mackenzie-crude-export-collapse-60pct-2026
Aug 2026 (Kpler) ~1.43 mb/d 4q26-supply-cliff-risk
Aug 2026 (IEA alt-route estimate) 3.5–5.5 mb/d combined Saudi/UAE 2026-09-22-reuters-saudi-ew-pipeline-restart (citing IEA via Egypt Oil & Gas)
Sep 10–11, 2026 SHUT — drone strikes from Iraq (Riyadh + Medina regions) 2026-09-11-cnbc-saudi-east-west-pipeline-shutdown · 2026-09-12-aljazeera-saudi-pipeline-shutdown-explainer
Sep 11–21, 2026 SHUT — precautionary shutdown; Yanbu loadings halted bab-al-mandab-compounding-scenario "Status: ACTIVE"
Sep 22, 2026 (today) PARTIAL RESTART — LOW RATE (rate undisclosed); one Yanbu cargo scheduled, China-bound 2026-09-22-reuters-saudi-ew-pipeline-restart
Target throughput 4 mb/d (Aramco, per one source) 2026-09-22-reuters-saudi-ew-pipeline-restart
Full resumption timeline Weeks (security source) 2026-09-22-reuters-saudi-ew-pipeline-restart
Nameplate 5 mb/d csis-seigle-2026

That is a ~4× ramp-up in roughly six weeks (Feb → April 2026). The IEA's May 2026 Oil Market Report (iea-oil-market-report-may-2026) confirmed the pattern — "Saudi Arabia and UAE successfully redirected some exports to terminals loading outside the Strait" — and the April IEA dataset (iea-oil-market-reports-2026) showed combined Saudi-Yanbu + UAE-Fujairah flows at ~7.2 mb/d (vs <4 mb/d pre-war).

Sep 11, 2026 — Sep 22, 2026 disruption interval: Pipeline offline ~9–12 days. Pre-shutdown 4 mb/d bypass stranded. Yanbu storage drained to "several days" of shipment runway per Egypt Oil & Gas. Aramco likely throttled Eastern Province production during the outage. Sep 22 partial restart begins the recovery but does not fully reverse the disruption.

IEA combined alternative-route estimate (via Egypt Oil & Gas Sep 22): Saudi Arabia + UAE together have 3.5–5.5 mb/d of available alternative export capacity. Logistics required to reroute substantial volumes "have not been extensively tested" — i.e., the IEA is flagging this as a fragile workaround layer, not a robust alternative.

Critically, brookings-timing-impending-crude-crisis labels the pipeline as a "structural" rather than "temporary" offset. Even with a Hormuz resolution, the East-West corridor represents a permanent re-routing of Saudi flows.

Vulnerability Profile

The pipeline runs through Saudi territory — primarily empty desert — but is not risk-free, and its terminal endpoint is materially exposed:

  1. Historical Houthi attacks. In 2019, the Houthis claimed responsibility for drone attacks on the East-West Pipeline that briefly disrupted flows. The pipeline is a named target, not a hypothetical one.
  2. Pumping stations. A long-haul crude pipeline depends on a chain of pumping stations at regular intervals — soft targets relative to the buried pipeline. A coordinated attack on 2–3 stations could halt throughput regardless of pipeline integrity.
  3. Yanbu terminal exposure. A fixed coastal facility with storage, loading arms, and tank farms — a named, mappable asset that has featured in Houthi targeting rhetoric throughout the 2023–2026 Red Sea crisis.
  4. Cut scenarios, in order of likelihood: pumping station attack (days–weeks repair), pipeline rupture (days–weeks), Yanbu terminal strike (months to rebuild), or downstream chokepoint closure (Bab al-Mandab or Suez), which makes the pipeline worthless as an export route even if it operates perfectly.
  5. Geographic concentration. Despite the long overland route, value concentration is at two nodes (pumping chain + Yanbu terminal), not distributed along the line. A small number of successful strikes could neutralize the entire bypass.

The pipeline is attackable in principle, robust in practice — but the practice has not been stress-tested under sustained Houthi campaign conditions in 2026.

The Compounding Effect With Bab al-Mandab

This is the most important structural insight of the article and the reason the East-West Pipeline is paired with bab-al-mandab-compounding-scenario in the KB. The pipeline's value is wholly conditional on the Red Sea being open downstream.

  • Pipeline operates AND Yanbu works AND Bab al-Mandab open AND Suez open → full Saudi export flexibility (~3 mb/d via bypass, with downstream routing options).
  • Pipeline operates AND Yanbu works AND Bab al-Mandab closed → bypass becomes useless for export; crude can only be stored at Yanbu or shipped via SuezMed at much lower throughput.
  • Pipeline operates AND Yanbu works AND Bab al-Mandab closed AND Suez impaired → total loss of Saudi export flexibility through the Red Sea route.

bab-al-mandab-compounding-scenario describes this dual-chokepoint risk as "disastrous" — Chatham House framing carried forward in the KB. The pipeline becomes a liability rather than an asset if its output cannot exit: Aramco must either shut in Eastern Province production or fill storage until it overflows. Neither outcome is benign.

Market participants often treat the pipeline as proof that "Saudi Arabia can route around Hormuz." This is only half-true. Saudi can route around one chokepoint, not two simultaneously — and the Bab al-Mandab scenario implies exactly that.

Saudi Storage Buffer and Lag Dynamics

Saudi Arabia holds ~8 mb of combined commercial + strategic storage, with Yanbu's working storage estimated at ~3–5 mb. These determine the lag between disruption and forced production cut:

Scenario Lag before production cut
Pipeline cut (no crude reaches Yanbu) Days, not weeks (storage drains via loading; if loading stops, no buffer loss — but no export either).
Yanbu receiving crude but Bab al-Mandab closed Days to weeks. At 3 mb/d inbound, the 3–5 mb Yanbu working storage fills in 1–2 days at full pipeline throughput, forcing Aramco to throttle Eastern Province production within days.
Sudden disruption (no warning) Hours to days; production cut forced within ~48 hours.
Telegraphed disruption (Houthi rhetoric, military buildup) Weeks; Aramco pre-emptively throttles production and builds storage at slower rates.

The inbound flow rate is the critical variable. At post-ramp-up 3 mb/d, Yanbu storage can absorb approximately one to two days of full pipeline flow before reaching working capacity. Above that, Aramco faces a forced production cut — and Eastern Province cuts translate directly into reduced global supply because Saudi spare capacity is the marginal swing producer. This is the second-order mechanism by which an East-West Pipeline failure or downstream closure becomes a global supply event rather than a local infrastructure problem.

Relation to the 4Q26 Supply Cliff

4q26-supply-cliff-risk identifies the East-West Pipeline as one of the primary adaptation mechanisms that allowed the EIA to halve its 4Q26 shut-in forecast from 11.3 mb/d (August STEO) to 5.7 mb/d (September STEO). The pipeline is part of the working-but-fragile adaptation layer.

The cliff risk applies directly:

  1. Yanbu single-point-of-failure. Kpler data (per 4q26-supply-cliff-risk) shows Yanbu at ~1.43 mb/d in August, down ~60% from peak. Whether seasonal, demand-driven, or a leading indicator is unclear — but the trend is downward, not upward.
  2. Mine-clearing delay. Until Hormuz mines are cleared and shipping returns to normal war-risk premia, the Red Sea downstream route is the primary outlet for Yanbu crude. Any Houthi escalation that re-prices Bab al-Mandab insurance would force Yanbu exports to fall, immediately stranding Saudi crude at the terminal.
  3. Refinery turnaround overlap. 4Q is European refinery maintenance season. Suez/Sidi Kerir throughput — the largest single alternative outlet for Yanbu crude — is partially constrained when European refineries are down. Compounding effect with refined-products-as-shock-center.
  4. Pipeline disruption + Bab al-Mandab closure = full Saudi export collapse. This is the bab-al-mandab-compounding-scenario scenario played out at the pipeline level. Probability is low but impact is discontinuous: a single weekend of Yanbu attacks plus a Houthi Bab al-Mandab campaign would convert the East-West Pipeline from Saudi Arabia's primary adaptation asset into stranded infrastructure within 48–72 hours.

The pipeline is therefore a Tier 2 concept because it is conditional — its value depends on the integrity of multiple downstream links, and its failure mode is fast, asymmetric, and globally consequential.

Created 2026-09-15 — kb-full-ingest / 1.2-concept-extraction (gap fill, post-3.0)
Updated 2026-09-22 — partial-restart status (low rate, target 4 mb/d, weeks-scale full restoration, no Aramco official confirmation). Implications added for export routing (Yanbu → Mediterranean primary, Hormuz ramp-up as substitute), production shut-ins (partially but not fully reversed), and 14–18 mb/d Thierry Bros reconciliation. Critical caveat: pipeline restart ≠ production restoration. Q-pages intentionally not edited per task acceptance criteria.
Updated 2026-09-23 — TankerTrackers (@TankerTrackers, X) observed USN-BL 13 Mbpd / SoH 10.35 Mbpd / bypass 2.65 Mbpd as independent physical-flow confirmation that EW Pipeline partial-restart is insufficient (Saudi swung back east, doubling USN-BL egress in <30 days). The 13 Mbpd is OBSERVED flow, not a disruption estimate — not added to the 15–17 mb/d / 11–13 mb/d reconciliation (would constitute double-counting). No Q-page edits applied.