One Route Left: The Houthi Second Front and Saudi Arabia's Vanishing Bypass
Yanbu was supposed to be the hedge against Hormuz. Now every barrel it loads has to clear the one strait the Houthis just put back in play.
BY THE HARBORMASTER · TANKERBRIEF DESK · PUBLISHED DAILY SINCE MARCH 1, 2026
Riyadh went five months without taking a hit. Every other Gulf capital absorbed missiles, drones, or a strike close enough to count, Bahrain, Kuwait, Qatar, Jordan, Oman, while UAE-flagged tankers took hits at sea. Saudi Arabia stayed the one Gulf state that backed Washington's diplomatic track and never became a target. That ended July 14, when Houthi missiles and drones hit Abha airport, the first strike on Saudi territory this crisis and the first Houthi-Saudi exchange since the 2022 ceasefire. Saudi air defenses intercepted the salvo. No damage was confirmed. Nobody died. Details are in that morning's alert and the brief that followed; this piece is about the part that doesn't show up in a damage assessment.
Zero barrels were lost at Abha. That is the wrong number to focus on. The Houthis closed their strike announcement by calling Bab el-Mandeb "a strategic asset Yemen has the luxury of utilising," aimed at a kingdom whose entire export lifeline, with Hormuz shut since July 11, now runs through exactly one route: the East-West Pipeline to Yanbu, ~2.5 million barrels a day, every one of which has to clear the strait the Houthis just named. Four questions decide whether that sentence stays a threat or becomes a fact. What does the Yanbu-Bab el-Mandeb route actually look like under fire, and does Saudi Arabia have anything behind it? Who is actually making the decision to escalate, Sana'a or Tehran, and does the distinction matter? What does the closest historical parallel predict? And if the corridor genuinely closes, not just gets threatened, what does that do to a market that has spent four months adapting to a shut Hormuz and has not yet priced losing its replacement?
| Metric | Jul 15 status | If Bab el-Mandeb closes |
|---|---|---|
| Saudi seaborne export capacity | ~2.5M bbl/day via Yanbu (only working route) | ~0-0.3M bbl/day |
| Non-Hormuz Gulf/Red Sea bypass total | ~4.4-4.6M bbl/day | ~1.9-2.3M bbl/day (Fujairah only) |
| Deliverable spare capacity, 30-day | N/A | ~0.3-0.6M bbl/day (15-25% coverage) |
| Brent | $85.43, flat | $102-110 base case, 1 week |
| Hull war-risk premium, Red Sea / Bab el-Mandeb transit | ~0.3% of vessel value | Dedicated surcharge, several multiples higher (panel estimate) |
| Hull war-risk premium, Hormuz / Gulf-wide band | 3-10% of vessel value | Unchanged; a Red Sea closure does not reprice the Gulf band |
Correction, July 22, 2026. As published on July 15, the war-risk row in this table read "Hull war-risk premium, Red Sea-transiting: ~5%." That was the Hormuz and Gulf-wide band, not a Red Sea rate. Red Sea and Bab el-Mandeb war risk stood at roughly 0.3% of vessel value at the time, and rose to ~0.75% on July 20 to 21 after the Houthi embargo declaration (Reuters). The row has been split so the two markets are not read as one, and the escalation estimate has been re-anchored to the Red Sea rate rather than to the Gulf band. The corresponding sentence below has been corrected to match. The full audit behind this correction is at Corrections.
The Route With No Alternative Behind It
A laden tanker out of Yanbu runs ~800 nautical miles to the Bab el-Mandeb narrows at Perim Island, call it 60-65 hours at a normal 12-13 knot clip. That total distance overstates the actual danger zone. The Houthis' demonstrated engagement envelope from the 2023-2024 Red Sea campaign concentrated in the southern third of the Red Sea and the Gulf of Aden approach, radiating from coastal launch sites around Hodeidah and Mokha, near the strait itself. The genuine high-risk stretch is the final 300-400 nautical miles, about a day of real exposure per transit, and there is no routing trick around it. Cargo bound for Asia, Saudi Aramco's dominant buyer base, runs straight through the highest-density strike zone. Cargo bound for Europe via Suez does not avoid the threat either, since it still has to hold the Red Sea's full length off the Yemeni coast first, which is part of why Suez throughput already sits 50-60% below normal.
Yanbu's two crude terminals can load ~4.5 million barrels a day nameplate, tested closer to 3-4 million under wartime conditions, against the 2.5 million currently moving, meaning the barrel count genuinely exposed is larger than today's headline flow if Aramco had been ramping toward capacity. Bab el-Mandeb itself is 18 nautical miles wide, funneled through a traffic lane closer to 2-3 usable nautical miles around Perim Island, an easy target basket for anyone with coastal radar and a truck-mounted launcher.
None of the hardware from 2023-2024 has gone away: Iranian-derived anti-ship ballistic missiles, C-802-derivative cruise missiles, explosive unmanned surface vessels, naval mines, one-way attack drones, launched from a coastline the Houthis still fully control. That campaign sank the Rubymar and the Tutor, set the crude tanker Sounion adrift and ablaze for weeks off Hodeidah while carrying ~1 million barrels of oil, and killed three crew on the bulk carrier True Confidence, across more than a year of sustained targeting. What has changed is not capability. It's the target list. In 2023-2024 the campaign nominally targeted Israel-linked shipping, and Saudi-flagged, Saudi-origin cargo was largely left alone, consistent with the 2022 truce. That immunity is gone now, by the Houthis' own words. Yanbu-loaded, Aramco-origin crude moves from incidental risk to the highest-priority target category the group has.
No tanker has been struck in the Red Sea this crisis, distinct both from the earlier cargo-vessel strikes logged in the SITREP's Bab el-Mandeb interdiction record and from the Gulf of Oman strikes on the UAE tankers and the GFS Galaxy covered in yesterday's brief. That calm is the fragile part. One confirmed hit on a Yanbu-linked hull, by the panel's read, takes Red Sea war-risk cover off its ~0.3% of vessel value base into a dedicated surcharge several multiples higher, and triggers the kind of outright tonnage refusal seen after the Sounion strike in August 2024, when owners stopped calling the Red Sea outright, price be damned. The Hormuz band, 3-10% of vessel value, is a separate market and is not the reference point for a Red Sea rate. Saudi Arabia's own carrier, Bahri, can absorb some of what independent owners refuse, but Bahri tonnage is finite and cannot carry the full 2.5 million barrels a day alone.
And behind Yanbu, there is nothing. Petroline is the only pipeline reaching saltwater outside the Gulf; Yanbu is its only outlet. The old Tapline to Sidon has been defunct for decades. Jeddah's terminal handles product, not crude, at nowhere near export scale. Moving 2.5 million barrels a day by truck would need on the order of 15,000 truckloads daily, not a real option. If Bab el-Mandeb goes from threatened to closed, the honest answer covered further down in The Bypass Map still holds: there is no bypass behind the bypass. What's left is rationing, drawing down onshore storage, paying up for the shrinking pool of risk-tolerant owners, or pushing for a Prosperity-Guardian-style naval escort, none of which is a reroute.
Who Is Actually Pulling the Trigger
Houthi command runs narrow, and that narrowness is the whole story. Final authority over military escalation sits with Abdul-Malik al-Houthi, with a small Jihad Council carrying contact to Iran's Islamic Revolutionary Guard Corps. That structure suits Tehran: it gives Iran a lever it can pull through supply and coordination without ever issuing a traceable order, while giving the Houthis room to act on their own grievances while still drawing on Iranian capability. TankerBrief's panel scores the Abha strike ~60% opportunistic, 40% Tehran-directed, and that split reflects the command structure accurately. Abdul-Malik did not need Tehran's permission to hit Abha; he needed a reason, and he got one when a strike on Sanaa's runway, credited to Yemen's internationally recognized government and blamed by the Houthis on Riyadh, hit an Iranian aircraft carrying a Houthi delegation home from Iran's Supreme Leader funeral.
Riyadh has the mirror problem on its own side. The Sanaa strike that started this sequence is credited to Yemen's Presidential Leadership Council in Aden, not to Saudi Arabia directly, and the PLC is a coalition with its own factional patrons, some Saudi-aligned, some UAE-aligned through the Southern Transitional Council, with its own institutional interest in reopening the war the Houthis interrupted in 2022. MBS may not have ordered the provocation any more than Tehran ordered the retaliation. He inherits the consequences regardless.
There's a structural detail worth flagging inside Iran itself. The July 11 declaration that closed Hormuz came from IRGC Navy in its own name, not from the new Supreme Leader's office or the Foreign Ministry, an unusual channel the SITREP itself has flagged. If the Quds Force's Yemen liaison is operating with wide discretion because the formal chain of command above it is still settling after Khamenei's succession, that argues for more autonomy on the Houthi file right now, not a centrally directed campaign. Iran built the leverage and benefits from the outcome without needing to have picked the trigger moment. That is a distinction that matters less for assigning blame than for predicting what happens next: a diffuse, opportunistic escalation is harder to switch off with a single phone call than a centrally ordered one.
What the Last Time This Happened Predicts
Two precedents matter here, for different reasons. The first is September 2019, when drones and cruise missiles knocked out ~5.7 million barrels a day of Saudi production at Abqaiq and Khurais, about half the kingdom's output, for days. The Houthis claimed it; US and Saudi assessments concluded the attack's trajectory pointed to Iranian or Iraqi-proxy origin instead. That is the clearest precedent for what deniability buys an actor: a claim that both is and is not true, structured so no single party owns the escalation risk of a confirmed state-on-state strike. What it predicts for Riyadh's response matters more. Despite a hit far more damaging than Abha, Saudi Arabia did not retaliate militarily against Iran. It absorbed the attack and worked backchannels, restraint that eventually helped feed the 2023 Saudi-Iran normalization.
The second is the Houthi missile campaign against Saudi Arabia that ran from 2015 to 2022, hitting Riyadh's airport, Abha, Jizan, and Najran repeatedly across those years. It did not end in a comprehensive settlement. It ended in an April 2022 UN-brokered truce that formally expired six months later but held informally for nearly four years through Omani-mediated backchannels and mutual exhaustion, even as the Houthis kept fighting everyone else in the interim. That is the precedent for reading whether the ceasefire is meaningfully dead. The formal truce was already a dead letter before July 14; what broke was the informal, nearly-four-year mutual-restraint understanding specific to direct Houthi-Saudi kinetic contact. Both precedents point the same direction, toward contained retaliation for a specific, personally charged provocation rather than a considered reopening of the 2015-2022 war. Both also show that "contained" is a choice renewed daily by both sides, not a guarantee, and it broke once already under less provocation than a strike on a leadership-adjacent aircraft.
The Math If the Corridor Actually Closes
The market is not pricing a Yanbu closure. Brent sat at $85.43 the morning of the Abha strike, essentially flat, a level that reflects four months of adaptation to a shut Hormuz: Strategic Petroleum Reserve barrels largely delivered, Russian crude captured into Indian and Chinese demand, and a working, if contested, ~4.4-4.6 million barrels a day of non-Hormuz bypass carrying the marginal barrel that has kept the tape from panicking. Take Bab el-Mandeb out of that mix and 55-60% of the remaining bypass disappears in one move, at the exact moment OPEC sits 18 days from its next scheduled meeting on August 2, holding spare capacity it cannot physically deliver to a ship.
Run the numbers on who actually has spare capacity and who can get it to market inside 30 days. Saudi Arabia's ~3 million barrels a day of nameplate spare capacity is worthless in this scenario, since Yanbu's terminal, not crude in the ground, is already the binding constraint, and Bab el-Mandeb closure removes the loading point entirely. The UAE's ~1 million barrels a day of spare capacity is only partly deliverable, limited to the 400,000-500,000 barrels a day of remaining pipeline headroom into Fujairah, the one Gulf export point that touches neither Hormuz nor Bab el-Mandeb and becomes the sole surviving route if this scenario plays out. Kuwait and southern Iraq add close to nothing, already Hormuz-dependent and largely offline. Non-Gulf OPEC+ producers can add an estimated 300,000-500,000 barrels a day, mostly already committed under term contracts. A second coordinated SPR-style release is possible but smaller than March's 400-million-barrel tranche, which is close to fully delivered, and carries a 35-45 day lag before it reaches the Asian refiners who would need it fastest.
Net deliverable spare capacity inside 30 days: 300,000-600,000 barrels a day, against a fresh loss of 2.2-2.5 million. That is a 15-25% coverage ratio, worse than the original Hormuz shock's own SPR coverage, because the reserve has already been partly spent and the world's remaining spare capacity sits with the two producers, Saudi Arabia and the UAE, now most exposed to the chokepoints in question. Every prior oil shock this crisis gets compared to kept at least one door open for backfill supply. The 1990-91 Gulf War removed 4.3 million barrels a day overnight and still found its floor within months, not years, because Saudi spare capacity ramped and shipped out through an open Hormuz. 1973's embargo was a "who can buy" shock, not a "can a ship leave" shock; tankers still sailed. The 1967-75 Suez closure forced a costly reroute around the Cape, but a viable alternative route existed and the industry scaled up VLCCs specifically to use it. A Yanbu cargo blocked at Bab el-Mandeb has no Cape option, because sailing back out through Suez only reaches Europe, not Aramco's dominant Asian buyer base. If this scenario materializes, it is the first in the crisis where the chokepoint closure and the world's spare capacity location coincide on the same producer at the same time, which is why the panel's one-week Brent path centers on $102-110, with tail risk to $125, well above the $92-98 already carried for a single isolated strike.
The probability of full closure, not an isolated incident but a sustained shutdown of the corridor, runs an estimated 12-18% within a week, climbing toward 30-40% cumulative within a month given that the Houthis have explicitly declared the "de-escalation phase" over while running two live escalation ladders at once, Hormuz and now the Red Sea.
Three Paths From Here
BASE CASE, 52%. Houthi rhetoric continues, further "siege" language, possibly another exchange with Saudi-led forces, without a strike on shipping. Bab el-Mandeb stays open but explicitly threatened, exactly today's status. War-risk premiums drift up on precaution alone. Brent holds $84-90.
BEAR CASE, 30%. The Houthis strike a Yanbu-bound or Saudi-linked tanker, or fire on any vessel in the Bab el-Mandeb corridor. Underwriters pull or refuse to quote war-risk cover for Yanbu-linked cargo within 72 hours of the incident. Insurance withdrawal has been the fastest-acting closure lever throughout this war, arriving ahead of confirmed physical damage the way our own scenario modeling flagged as a live risk in Closed Until Further Notice. Brent moves to $95-115 within a week, with a path to $110-130 if the closure holds past two weeks.
BULL CASE, 18%. Backchannel diplomacy, Oman or the UN Yemen envoy track, both independent of the Hormuz-Muscat channel, contains the exchange inside 5-7 days. Houthi language narrows back toward conditional framing. Brent fades toward $80-84.
The decision tree collapses to two branch points worth tracking in order. First, does Houthi command order a second strike within a week, on land or at sea. Second, if a vessel gets hit, do underwriters actually withdraw cover for Yanbu-linked cargo inside 72 hours, since the corridor can close commercially before it closes physically, exactly the mechanism that shut the Hormuz southern corridor before a single mine detonated there. A parallel signal worth weighting above Houthi rhetoric itself: whether Riyadh requests US air-defense augmentation for the southern Red Sea, the clearest tell that Saudi Arabia expects a sustained second front rather than a one-off.
Two wild cards sit outside the three-path model. Iran could use the Houthi channel as a deniable pressure release timed to the OFAC sanctions wind-down expiring July 17, landing two clocks inside the same window. And the Houthis could misattribute a strike, hitting a neutral or non-Saudi-linked vessel believing it bypass-connected; the market will not distinguish intent from outcome, and insurer withdrawal follows either way.
What to Watch
- The fate of the next tracked Yanbu-bound or Saudi-linked tanker transiting Bab el-Mandeb, and whether underwriters are still quoting it. Observable inside 72 hours, and the fastest-resolving signal on this entire tree.
- Yanbu loading and export data. A Saudi-imposed slowdown ahead of any Houthi strike is Riyadh doubting its own route, the most reliable non-rhetorical tell available.
- A second Houthi strike, or its absence, within 72-96 hours of Abha, settling whether "de-escalation phase over" was policy or a single retaliatory message.
- Any Saudi request for US air-defense augmentation or naval escort in the southern Red Sea.
- Houthi statement tone: hardening toward unconditional threats versus a shift toward conditional language exempting non-Saudi-linked traffic, the same erosion pattern that would signal a walk-back on the Hormuz closure claim.
- GL X1's sanctions wind-down expiry, July 17, tracked as a linked clock alongside the Houthi threat rather than a separate item.
Saudi Arabia spent a decade trying to exit Yemen and five months trying to stay out of the wider Hormuz war entirely. Both efforts just failed at once, through a chain of events no single actor fully controls: a Sanaa runway strike nobody in Riyadh ordered, a Houthi retaliation nobody in Tehran had to direct, landing on a kingdom whose only working export route now runs through the one strait the group just told the world it's willing to use as leverage. The physical damage from Abha was zero. The change to Saudi Arabia's position was not: a bypass built to hedge against Hormuz's closure now has no hedge of its own, and the panel's own math says the world can currently cover 15-25% of what disappears if that bypass goes the same way Hormuz did.
Sources: CENTCOM statements, Saudi state media, Lloyd's List intelligence, UN Yemen envoy reporting, TankerBrief crisis situation report v101. Panel: Maritime Analyst, Middle East Expert, Scenario Planner, Energy Strategist.