Source: Reuters
Date: September 22, 2026 (Singapore / New Delhi dateline)
URL: https://www.reuters.com/business/energy/saudi-arabia-restarts-east-west-oil-pipeline-resume-exports-yanbu-sources-say-2026-09-22/
Captured via: US News syndication (reuters.com direct fetch returned 401/JS-gated)
Syndication URL: https://www.usnews.com/news/world/articles/2026-09-22/saudi-arabia-restarts-east-west-oil-pipeline-to-resume-exports-from-yanbu-sources-say
Byline: Trixie Yap, Nidhi Verma, Florence Tan; additional reporting by Jonathan Saul, Ahmad Ghaddar, Enes Tunagur (London)
Editors: Emelia Sithole-Matarise, Barbara Lewis
Copyright: © 2026 Thomson Reuters
Captured Text (Verbatim from Reuters Wire, via US News Syndication)¶
By Trixie Yap, Nidhi Verma and Florence Tan
SINGAPORE/NEW DELHI, Sept 22 (Reuters) — Saudi Arabia has restarted operations at its East-West Pipeline and could resume exports from the Red Sea port of Yanbu later on Tuesday, three sources briefed on the matter said.
Drone attacks forced Saudi Arabia to shut its East-West Pipeline on September 13, halting crude loadings at the kingdom's Yanbu port.
The resumption of supplies on Tuesday helped to drive selling on global oil markets, traders said. Brent crude futures fell by more than $2 a barrel to its lowest since September 8. [O/R]
Since disruption to oil flows through the Strait of Hormuz following the U.S.-Israeli war on Iran, OPEC's leading oil exporter has been using the pipeline to reroute around 4 million barrels per day — around 4% of global supply — to Yanbu.
The pipeline was pumping at a low rate after its restart, two of the sources said.
State oil firm Saudi Aramco did not immediately respond to a request for comment.
One of the sources said Aramco was seeking to get the pumping rate back to 4 million bpd, while a security source said full resumption could take weeks.
The pipeline will resume crude supply to Aramco refineries located on the Red Sea coast, one of the sources said, adding that one cargo was scheduled to load at Yanbu later on Tuesday. The person said it would be bound for China.
Another two trading sources said traders were getting ready for Saudi oil loadings by moving tankers to Egypt's Mediterranean Port Said for ship-to-ship transfers and also to Sidi Kerir.
Status Assessment (Sep 22, 2026)¶
| Dimension | Status | Evidence | Confidence |
|---|---|---|---|
| Confirmed restart (operations resumed) | YES — confirmed | Reuters wire, three independent sources briefed on matter | High |
| Initial throughput | LOW RATE — unspecified | "pumping at a low rate after its restart, two of the sources said" (rate not disclosed) | High on "low"; Medium on exact number (no number given) |
| Target throughput | ~4 mb/d | "Aramco was seeking to get the pumping rate back to 4 million bpd" | Medium (one source; subject to revision) |
| Full resumption timeline | WEEKS | "security source said full resumption could take weeks" | Medium (one source; security source) |
| Yanbu export resumption | Sep 22, 2026 (later in day) | "could resume exports from the Red Sea port of Yanbu later on Tuesday" | High |
| First cargo destination | CHINA | "one cargo was scheduled to load at Yanbu later on Tuesday ... bound for China" | High (one source) |
| STS / Mediterranean re-route prep | Active — Port Said + Sidi Kerir | "traders were getting ready for Saudi oil loadings by moving tankers to Egypt's Mediterranean Port Said for ship-to-ship transfers and also to Sidi Kerir" | High (two trading sources) |
| Aramco official confirmation | NOT RECEIVED | "Saudi Aramco did not immediately respond to a request for comment" | High — explicit |
| Pre-shutdown flow (context) | ~4 mb/d (~4% of global supply) | "Since disruption ... Saudi Arabia has been using the pipeline to reroute around 4 million barrels per day ... to Yanbu" | High |
| Shutdown date (per Reuters) | September 13 | "Drone attacks forced Saudi Arabia to shut its East-West Pipeline on September 13" | DISCREPANCY — see §"Shutdown Date Discrepancy" below |
| Market reaction | Brent −$2+/bbl to lowest since Sep 8 | Reuters wire; corroborated by The National ($97.81 at 14:19 UAE time Sep 22) | High |
Bottom-line status label¶
Confirmed partial restart at low rate; full restoration = weeks-scale (per security source); target rate = 4 mb/d; Aramco has not officially confirmed.
This is NOT a full operational restart, and it is NOT a return to the 4–5 mb/d bypass throughput. It is partial, low-rate, weeks-away from full. Importantly, route capacity is not the same as production restoration — even at 4 mb/d the East-West Pipeline does not by itself restore Saudi's pre-crisis export book, because the Bab al-Mandab downstream channel remains under Houthi pressure (see bab-al-mandab-compounding-scenario and 2026-09-12-aljazeera-saudi-pipeline-shutdown-explainer for Mayun island seizure context).
Key New Data Points for the KB¶
- Restart confirmed Sep 22, 2026 — three independent sources briefed on the matter (Reuters, via US News syndication). NOT confirmed by Saudi Aramco in writing.
- First cargo: Yanbu → China (one cargo, scheduled Sep 22 evening).
- Traders pre-positioning at Port Said (Egypt) for STS transfers and at Sidi Kerir (Egypt) for direct discharge. This implies the first post-restart flows may route to the Mediterranean rather than the Red Sea south to Bab al-Mandab.
- Pre-shutdown rerouting confirmed at 4 mb/d by Reuters — this matches the 4–5 mb/d range already in east-west-pipeline and bab-al-mandab-compounding-scenario.
- Bab al-Mandab status NOT addressed in this Reuters wire. The restart is conditional on downstream Red Sea/Bab al-Mandab being navigable. The Aug 24 Amzan strike and Jul 20 Houthi embargo remain in the KB; whether Houthi activity has paused in the past 48 hours is not addressed in this article.
- Yanbu storage lag detail (via Egypt Oil & Gas citing Reuters): "stocks at Yanbu could sustain shipments for only several days without pipeline flows" — consistent with east-west-pipeline's 3–5 mb working storage and ~48-hour lag analysis, but tighter than the previous KB wording suggested.
Shutdown Date Discrepancy (Reconciliation Note)¶
The KB has recorded the East-West Pipeline shutdown date inconsistently across sources:
| Source | Date cited | KB reference |
|---|---|---|
| CNBC Spencer Kimball | Sep 10–11 (drone strikes) → precautionary shutdown | 2026-09-11-cnbc-saudi-east-west-pipeline-shutdown |
| Al Jazeera Sep 12 | Sep 11 drone strike → shutdown | 2026-09-12-aljazeera-saudi-pipeline-shutdown-explainer |
| NYT Sep 12 | Sep 10–11 attacks | 2026-09-12-nytimes-saudi-oil-lifeline-attacked |
| Wikipedia Sep 12 | Sep 10–11 attacks | 2026-09-12-wikipedia-2026-east-west-pipeline-attack |
| Reuters Sep 22 | September 13 | This article |
| Egypt Oil & Gas Sep 22 | September 13 | Cited via this article |
Two possible reconciliations:
1. Reuters/Egypt Oil & Gas are using the date the precautionary shutdown took full effect (after strike assessment). The Sep 10–11 strikes triggered a precautionary pause; Sep 13 is when the shutdown was officially implemented or confirmed in Aramco/Ministry of Energy statements.
2. Reuters/Egypt Oil & Gas have a minor reporting error — the pipeline was officially shut Sep 11 per Saudi Ministry of Energy statements reported in earlier wires.
KB position (this intake): Treat Sep 11, 2026 as the strike + precautionary shutdown announcement date (per CNBC, Al Jazeera, NYT, Wikipedia consensus) and Sep 13, 2026 as either the official shutdown confirmation date or a minor reporting variance in later wires. The ~9–12 day outage (Sep 11 → Sep 22) is consistent across all sources and is what matters for the supply-loss accounting.
No double-counting risk: Either way, the pipeline was offline for ~9–12 days, not two separate events.
Implications for the 14–18 mb/d Thierry Bros Reconciliation¶
This article changes the Thierry Bros / KB reconciliation 2026-09-12-thierry-bros-x-shock-14mbd-disrupted in the following way:
Bros' original (Sep 12) framing¶
- Gross Hormuz disruption: ~18 mb/d (20 pre-crisis − 2 still flowing)
- Saudi EW bypass pre-Sep 11: 4 mb/d (offset)
- Net Hormuz disruption pre-shutdown: ~14 mb/d (Bros' headline number)
- Post-Sep-11 (Sep 12): bypass stranded → +4 mb/d stranded; net ~17–18 mb/d or ~13–15 mb/d production-cut basis
Updated (Sep 22) framing¶
| State | Date | Net barrels unavailable |
|---|---|---|
| Pre-shutdown (Bros' baseline) | July – Sep 10 | ~14 mb/d |
| Post-shutdown, post-recovery attempts | Sep 11 – Sep 21 | ~17–18 mb/d (full) / ~13–15 mb/d (production-cut basis) |
| Post-partial-restart | Sep 22 (today) | ~15–17 mb/d full / ~11–13 mb/d production-cut basis |
The partial restart at low rate does not fully reverse the Sep 11 shock. Saudi is back at some unspecified fraction of 4 mb/d — not 4 mb/d yet. The 14 mb/d Thierry Bros figure is partially restored, not fully:
- Bros' 14 mb/d (pre-shutdown net) is no longer the current number. Current is somewhere between Bros' 14 mb/d and the 17–18 mb/d post-shutdown peak.
- The 4 mb/d Saudi was rerouting is partially back — but the magnitude is unknown because Reuters doesn't give the initial rate.
- Bab al-Mandab downstream is still embargoed. Even a fully-restored 4 mb/d Yanbu throughput is partially stranded downstream until the Red Sea reopens. The Aug 24 Amzan strike and Jul 20 Houthi embargo remain live per bab-al-mandab-compounding-scenario; nothing in this Reuters wire suggests Houthi pressure has eased.
Defensible updated figure (Sep 22)¶
Net barrels unavailable: ~15–17 mb/d (full basis) or ~11–13 mb/d (production-cut basis). The exact figure depends on (a) the actual initial restart rate (not disclosed by Reuters), and (b) whether Saudi has fully throttled Eastern Province production since Sep 11 or has kept producing while Yanbu storage absorbs the imbalance.
Status: Partial — confirmed low-rate restart, full restoration weeks away, downstream Bab al-Mandab disruption unchanged.
Implications for the Scenario B Tracker¶
scenario-b-tracker-2026-09-16 currently classifies the framework as STRUCTURAL UNCERTAINTY + EM-DEMAND-DESTRUCTION RISK. The Sep 22 partial restart:
- Partially relieves one of the three chokepoints (EW Pipeline: SHUT → PARTIAL LOW-RATE). Does NOT restore full pre-Sep-11 bypass capacity.
- Does NOT relieve the other two (Hormuz: still partial; Bab al-Mandab: still ACTIVE Houthi embargo).
- Does NOT add a fourth EM-demand-destruction relief (Pakistan Sep 17 austerity still in effect; no reversal reported in this wire).
- Brent moved down on the news (Reuters: "−$2+/bbl to lowest since Sep 8"; The National: $97.81 at 14:19 UAE time Sep 22). This reverses part of the Sep 11–21 risk premium but does not return Brent to pre-shock levels.
- The "Scenario A — EW pipeline cut, reversible" trigger is now activating — Brent is moving toward the lower end of the Scenario A range ($98–110/bbl). But the partial-restart framing means the scenario is partial-reversible, not fully reversed.
Tracker implications¶
| Signal | Sep 16 baseline | Sep 22 update | Implication |
|---|---|---|---|
| EW Pipeline status | SHUT (Sep 11) | PARTIAL LOW-RATE (Sep 22) | One of three chokepoints partially relieved |
| Brent crude | ~$104/bbl (Sep 12) | ~$97–100/bbl (Sep 22, Reuters + The National) | Moved into Scenario A lower end |
| Bab al-Mandab | ACTIVE Houthi embargo | ACTIVE (no change reported) | Compounding factor unchanged |
| Yanbu loadings | Halted (Sep 11) | Resuming Sep 22 (one cargo, China-bound) | First cargo since Sep 11 |
| Aramco pipeline status statement | None | None (did not respond to Reuters) | Still no Aramco public confirmation |
| US Gulf Coast ULSD spot | $202.94/bbl (Sep 9) | TBD — needs Sep 22 fetch | Awaiting daily signal update |
Implications for the Q-Pages (Q1 / Q2 / Q3)¶
Q1 (Supply Disruption): The Sep 22 partial restart partially reverses the Sep 11 shock but does not restore pre-crisis flow. The 11–13 mb/d Q1 baseline figure remains structurally valid but directionally softening. A precise figure-update would require knowing the actual restart rate (not disclosed). Recommend NOT editing Q1 in this intake; flag for follow-up once Aramco confirms the rate.
Q2 (Price Impact): Brent has moved from ~$104/bbl (Sep 12) to ~$97–100/bbl (Sep 22). This compresses the physical/futures disconnect slightly and brings Brent into Scenario A territory. Recommend NOT editing Q2 — the price movement is a 1–2 day reaction; the broader disconnect narrative is unchanged and depends on Bab al-Mandab downstream resolution.
Q3 (Europe Impact): The Port Said + Sidi Kerir pre-positioning is directly relevant to Q3 (Mediterranean re-route is a Europe-relevant path). However, this is a 1–2 cargo story and does not yet justify a Q3 edit; flag for follow-up.
Per task acceptance criteria: "Update Q1/Q2/Q3 and home/index only if the new evidence materially changes the current-state summary; otherwise report that no Q-page change is justified." No Q-page change is justified at this intake. The restart is confirmed but partial, the rate is undisclosed, and downstream Bab al-Mandab disruption is unchanged.
Honest Caveats¶
- Direct reuters.com fetch failed (401/JS-gated). Captured via US News syndication, which carried the identical Reuters wire copy including the same byline (Trixie Yap, Nidhi Verma, Florence Tan), London additional reporters (Jonathan Saul, Ahmad Ghaddar, Enes Tunagur), and editors (Emelia Sithole-Matarise, Barbara Lewis). The text is therefore authentic Reuters wire, not a US News paraphrase. Capture method recorded in frontmatter
provenance.syndication_capture. - Three sources briefed on the matter, two trading sources, one security source — but no source is named and no source is on-the-record. This is anonymous-sourced reporting typical for oil-trade intelligence.
- "Low rate" is qualitative, not quantitative. Reuters does not give a number for the initial restart rate. Aramco target = 4 mb/d (one source). Full resumption = weeks (security source). The intermediate rate could be anywhere from a few hundred thousand b/d to ~3 mb/d.
- No Bab al-Mandab update in this wire. The downstream Red Sea status is unchanged per prior KB sources. A Yanbu-bound cargo is still subject to Houthi risk in the southern Red Sea.
- The "first cargo → China" detail is from one source. It implies China is the prioritized off-taker; consistent with china-demand-return (China ~5 mb/d below normal, China buyers may be opportunistic given price drop). But the single-source nature limits the weight of this claim.
- Egypt Oil & Gas article adds IEA's 3.5–5.5 mb/d alternative-route estimate for Saudi/UAE combined — useful for the east-west-pipeline concept update.
- Reuters "September 13" shutdown date vs. earlier Sep 11 is reconciled as a minor reporting variance; the KB retains Sep 11 as the strike+shutdown announcement date and Sep 13 as either the official confirmation or a minor variance.
Related KB Articles¶
- east-west-pipeline — primary concept; requires update for restart status
- bab-al-mandab-compounding-scenario — downstream Red Sea disruption unchanged
- scenario-b-tracker-2026-09-16 — tracker requires update for EW Pipeline status
- 2026-09-12-thierry-bros-x-shock-14mbd-disrupted — 14 mb/d reconciliation requires update
- 2026-09-11-cnbc-saudi-east-west-pipeline-shutdown — prior Sep 11 shutdown source
- 2026-09-12-aljazeera-saudi-pipeline-shutdown-explainer — Sep 12 explainer
- 2026-09-12-nytimes-saudi-oil-lifeline-attacked — NYT (paywalled)
- 2026-09-12-wikipedia-2026-east-west-pipeline-attack — Wikipedia institutional reference
- china-demand-return — China ~5 mb/d below normal (now relevant as first cargo → China)
- q1-supply-destruction — Q-page; flagged for future revision, NOT updated here
- q2-price-impact — Q-page; Brent moved to Scenario A lower end, NOT updated here
- q3-europe-impact — Q-page; Port Said/Sidi Kerir pre-positioning is Europe-relevant, NOT updated here
Ingested 2026-09-22 from reuters.com (canonical URL, direct fetch 401) captured via usnews.com syndication (HTTP 200, verbatim Reuters wire text). Author byline and editor credits preserved. Three independent sources briefed on the matter; no Aramco official confirmation. Status: CONFIRMED PARTIAL RESTART at low rate, target 4 mb/d, full restoration weeks-scale. Q-pages intentionally not edited (task scope and acceptance criteria).