TLP:CLEAR · Disclosure is not limited.

Red Sea Shipping Disruption: Houthi Pressure Persists

Time window: Last 7 days · Audience: General analyst · Type: Situation report · DTG: 2026-09-04 01:11Z · Overall confidence: HIGH

BLUF

The Houthi threat to Saudi-linked commercial shipping in the Red Sea and Bab al-Mandab is likely to remain elevated over the next 0-14 days. Bab al-Mandab traffic is likely to stay constrained rather than fully closed, while Saudi Arabia and insurers continue adapting through rerouting, pipeline use and wider war-risk coverage.

Executive summary

Reporting indicates that Houthi threats and attacks are limiting commercial access through Bab al-Mandab, where 18 ships crossed on 2 September against an average of 24. Some major operators have made cautious, partial returns to the Red Sea and Suez, but diversions around the Cape of Good Hope remain part of the response. Saudi Arabia is moving 1.9 million barrels of crude per day through Egypt to the Mediterranean and Saudi Aramco is studying further pipeline and export-route changes. War-risk underwriters have extended designated risk areas 800 kilometres up Saudi Arabia's Red Sea coast, while reinsurers have excluded Saudi-associated vessels from some liability cover. The status and severity of the Bab al-Mandab disruption remain less certain than the wider insurance and rerouting effects. US-Iran fighting around the Strait of Hormuz is a separate disruption, although it raises the risk of additional pressure on Red Sea shipping.

Change from previous assessment

Since the 3 September brief, the core assessment is unchanged: the Houthi threat is likely to remain elevated and Bab al-Mandab transit is likely to remain constrained rather than fully closed. The current material adds evidence that underwriters have extended designated war-risk areas 800 kilometres up Saudi Arabia's Red Sea coast, reinsurers have imposed a blanket exclusion on Saudi-associated vessels, and reported marine war-risk claims have reached approximately 2 billion US dollars. It also provides a 2 September Bab al-Mandab count of 18 ships against an average of 24, strengthening the case for ongoing but incomplete disruption. The update separates Red Sea disruption more clearly from the severe Strait of Hormuz crisis. The prior piracy and Saudi-led maritime-cooperation judgements are not carried forward because the current claims add no corroborated new evidence on either issue.

Key judgments

1. The Houthi threat to Saudi-linked commercial shipping in the Red Sea and Bab al-Mandab is likely to remain elevated over the next 0-14 days. Reporting describes a Houthi naval blockade targeting the Port of Yanbu, Saudi oil sites and Saudi-linked commercial tankers, while separate reporting says resumed Houthi attacks are seriously limiting Bab al-Mandab transit. The 23 July attack on the Saudi-owned Encelia caused a fire on the bow but was attributed only to unidentified attackers, so the evidence does not establish Houthi responsibility for that incident. (Confidence: medium · ASSESSED)

• I&W: Confirmation would be a Houthi statement or an independently verified strike against a Saudi-linked tanker, the Port of Yanbu or a Saudi oil site. (0-14 days)
• I&W: The judgement would weaken if Bab al-Mandab transits returned to or exceeded the 24-ship average for seven consecutive days without a new Houthi maritime threat or verified incident. (0-14 days)

2. Bab al-Mandab commercial transit is likely to remain constrained rather than fully closed over the next 0-14 days. Navigation data recorded 18 ship transits on 2 September against an average of 24, while other reporting describes diversions around the Cape of Good Hope and only cautious, partial operator returns to the Red Sea and Suez. The evidence supports disruption, but the scale is contested because a single-day ship count differs from longer-term oil-flow and diversion measures. (Confidence: medium · ASSESSED)

• I&W: Confirmation would be daily Bab al-Mandab traffic remaining below 24 ships and at least one major operator suspending or reversing its partial return to the Red Sea. (0-14 days)
• I&W: The judgement would break if independently reported traffic reached or exceeded 24 ships for seven consecutive days and major operators expanded their Red Sea and Suez sailings. (0-14 days)

3. Saudi Arabia is likely to sustain rerouting and pipeline adaptation over the next 1-3 months, reducing its reliance on exposed maritime approaches without restoring normal Red Sea access. Saudi Arabia is moving 1.9 million barrels of crude per day through an Egyptian pipeline to the Mediterranean, Saudi Aramco is studying an East-West pipeline expansion and new export routes, and Riyadh has discussed a state-backed insurance guarantee scheme. The continuation of this pattern is an inference because the duration of the rerouting and the timing of any pipeline expansion are not established. (Confidence: medium · ASSESSED)

• I&W: Confirmation would be an Aramco announcement of East-West pipeline expansion or a new export route, or continued reporting of roughly 1.9 million barrels per day moving through Egypt. (1-3 months)
• I&W: The judgement would weaken if Saudi-linked vessels resumed sustained Bab al-Mandab use and reinsurers removed the blanket exclusion on Saudi-associated vessels. (1-3 months)

4. War-risk and liability restrictions are likely to keep the cost and availability of cover for Saudi-linked Red Sea shipping under pressure over the next 0-14 days. Underwriters have extended designated war-risk areas 800 kilometres farther up Saudi Arabia's west coast, reinsurers have imposed a blanket exclusion on vessels associated with Saudi Arabia, and reported marine war-risk claims have reached approximately 2 billion US dollars. The current insurance details are concentrated in trade reporting rather than independent official data, which lowers confidence. (Confidence: medium · ASSESSED)

• I&W: Confirmation would be a further northward expansion of designated Red Sea war-risk areas, an increase in reported claims, or additional exclusions for Saudi-linked vessels. (0-14 days)
• I&W: The judgement would weaken if reinsurers narrowed the exclusion, underwriters reduced the designated area, and reported insurance costs fell. (0-14 days)

5. It is unlikely that current reporting supports a confident judgement that Tehran is operationally directing new Houthi attacks on Red Sea shipping over the next 0-14 days. Iran's first vice-president has warned of an asymmetrical and multi-layered response, and reporting describes Houthi capabilities that could allow Iran to expand the conflict without direct involvement. The only supplied account of Iranian drone components being sent to the Houthis comes from a low-confidence social-media report and an Al Hadath correspondent, so this judgement rests on thin, uncorroborated evidence. (Confidence: low · ASSESSED)

• I&W: Confirmation would require independently corroborated evidence of Iranian equipment, personnel or command direction connected to a new Houthi attack on Red Sea shipping. (0-14 days)
• I&W: The judgement would weaken if a new Houthi attack were verified and attributed to Houthi decision-making without evidence of Iranian equipment, personnel or command direction. (0-14 days)

Outlook & scenarios

Persistent constrained transit (55%)

The Houthis maintain threats and attacks centred on Saudi-linked shipping and Bab al-Mandab. Daily transits remain below the 24-ship average, major operators retain only partial returns, Saudi Arabia continues routing crude through Egypt, and war-risk coverage remains broad. This is the most likely path over the next 0-14 days.

Wider targeting and further diversion (25%)

Houthi attacks reach additional commercial tankers or Saudi oil infrastructure at Yanbu. More operators use the Cape of Good Hope, insurers extend coverage farther north along Saudi Arabia's Red Sea coast, and Bab al-Mandab traffic falls below the 18-ship level recorded on 2 September.

Partial reopening (20%)

No further verified Houthi attack occurs against commercial shipping. Bab al-Mandab transits recover towards the 24-ship average, major operators expand their cautious return to the Red Sea and Suez, and insurance restrictions begin to narrow. Saudi Arabia continues using Egyptian and pipeline routes during the adjustment period.

US-Iran escalation reaches the Red Sea (10%)

US-Iran strikes and Iran's asymmetrical response produce an Iranian-backed Houthi operation against Saudi-linked shipping or the Port of Yanbu. Bab al-Mandab disruption widens while the Strait of Hormuz remains severely constrained, creating a simultaneous pressure point on Red Sea and Gulf shipping. This is a low-probability, high-impact wildcard.

Recommendations

1. Maintain a daily Bab al-Mandab traffic series that separates total ship transits from tanker and container-ship movements. Flag seven consecutive days below the 24-ship reference level and separately record any day below 18 ships.
2. Prioritise collection on the Port of Yanbu, Saudi oil sites and Saudi-linked tankers. Require independent corroboration before attributing incidents such as the Encelia attack to the Houthis.
3. Track Saudi Aramco decisions on East-West pipeline expansion and new export routes, Egyptian pipeline volumes, and implementation of the state-backed insurance guarantee scheme discussed in London.
4. Monitor changes in the 800-kilometre Saudi Red Sea war-risk area, the blanket exclusion on Saudi-associated vessels, and reported marine war-risk claims. Treat any further expansion or removal of the exclusion as an immediate change indicator.
5. Keep separate analytic baselines for Bab al-Mandab and the Strait of Hormuz. Do not use claims that Hormuz is shut to characterise Bab al-Mandab as closed without current Bab al-Mandab traffic data.
6. Treat Iranian-Houthi operational coordination as an intelligence gap. Seek corroborated evidence of Iranian equipment, personnel or command direction before incorporating that link into warning judgements.
7. Issue an immediate reassessment if a Houthi strike hits a Saudi-linked tanker, Yanbu or Saudi oil infrastructure, or if a major operator suspends its partial return to the Red Sea.

Confidence & uncertainty

Overall confidence is high because the underlying reporting includes high-confidence claims from the International Maritime Organisation, the US Energy Information Administration, major media, trade publications and navigation data. The main judgements are supported by several source types, although current Bab al-Mandab traffic is represented by limited daily counts and the precise severity of the disruption remains contested. Confidence is lower on Houthi responsibility for the Encelia attack and on any operational Iranian-Houthi coordination.

Intelligence gaps

• [EEI 1.1 · PARTIAL] Incidents of hostile action against commercial vessels: vessel name/IMO, position (lat/long), time/date, observable damage or casualties, and weapon type reported (missile, drone, small-arms, explosive-laden boat). Recommended collection: maritime/AIS
• [EEI 1.2 · PARTIAL] Public Houthi claims of attacks or warnings tied to specific dates/routes, including social-media posts, official statements, and timing relative to merchant transits. Recommended collection: open-source/social_media
• [EEI 1.3 · UNCOVERED] Unusual Houthi force posture indicators along Yemen’s Red Sea coast: movement or concentration of small boats, visible coastal missile/rocket emplacements, or logistics buildup at known launch sites (locations, timestamps). Recommended collection: imagery/satellite
• [EEI 1.4 · UNCOVERED] Intercepts or communications indicating orders, targeting lists, or intent to strike merchant shipping (messages referencing specific vessel classes, companies, or chokepoints). Recommended collection: signals/communications
• [EEI 2.1 · UNCOVERED] Reports or visual confirmation of floating or moored mines and debris fields in shipping lanes or approaches to Bab-el-Mandeb, with geolocation and time. Recommended collection: imagery/satellite
• [EEI 2.2 · UNCOVERED] Detection of mine-laying activity: small vessels loitering in lane approaches, unexpected AIS track patterns consistent with mine deployment, or salvage/mining vessels operating in the area. Recommended collection: maritime/AIS
• [EEI 2.3 · UNCOVERED] Hydrographic notices, naval warnings, or port authority advisories closing lanes or imposing route restrictions (text of Notice to Mariners, issuing agency, effective times/areas). Recommended collection: naval/port_authority
• [EEI 2.4 · UNCOVERED] Naval or commercial reports of mine-countermeasure operations or confirmed mine removal events (location, time, platforms involved). Recommended collection: naval/intelligence
• [EEI 3.1 · UNCOVERED] Movements and presence of foreign warships and support vessels: names/classes, task group compositions, patrol areas and timelines, and whether vessels are conducting escort or interdiction operations. Recommended collection: naval/intelligence
• [EEI 3.2 · PARTIAL] Official announcements or directives from states/coalitions regarding convoys, armed escorts, protected corridor establishment, or changes to rules of engagement for merchant protection. Recommended collection: diplomatic/public_affairs
• [EEI 3.3 · UNCOVERED] Recorded interactions between naval forces and vessels in the corridor (hailings, boardings, warnings, defensive strikes), including timestamps and outcomes. Recommended collection: maritime/AIS
• [EEI 3.4 · PARTIAL] Planned or ongoing multinational exercises, air ISR sorties, or logistics moves that increase or decrease naval capacity in the area (exercise name, participating units, dates, locations). Recommended collection: open-source/military_reporting
• [EEI 4.3 · UNCOVERED] Freight and charter market signals tied to the corridor: spot rates for container, tanker, and dry bulk routes affected by Red Sea disruptions, and reported port congestion or turnaround-time increases at nearby hubs. Recommended collection: commercial/market_data
• [EEI 4.4 · PARTIAL] Incidents of cargo denial or diversion for critical goods (crude oil, refined products, LNG, high-value container cargo) including vessel IDs, cargo type, reroute/turnback actions, and economic impact estimates where available. Recommended collection: maritime/AIS

Cited sources

[1] gCaptain · War Risk Claims Top $2 Billion as Shipping Attacks Spread Beyond Hormuz (C) · Thu Sep 03 2026 16:54:49 GMT+0000 (Coordinated Universal Time) · sha256:49728f6f0e8d [2] Atlantic Council · Maritime trade routes are under threat—and markets still underprice the risks (C) · Tue Aug 25 2026 14:15:06 GMT+0000 (Coordinated Universal Time) · sha256:2740d0a23976 [3] Modern Diplomacy · How Could Iran Retaliate as US Conflict Escalates? (B) · Wed Sep 02 2026 08:17:01 GMT+0000 (Coordinated Universal Time) · sha256:d74581e4ffa5 [4] The National · Two Filipino crew members killed in attack on Saudi vessel blamed on Iran (A) · Wed Sep 02 2026 08:42:39 GMT+0000 (Coordinated Universal Time) · sha256:31d3958e7b07 [5] يمن المستقبل (Yemen Future) · هونغ كاو ومضيق هرمز والبحر الأحمر: هل تستعد الولايات المتحدة لحرب بحرية كبرى مع إيران وأذرعها؟ - يمن المستقبل (D) · Wed Sep 02 2026 08:18:12 GMT+0000 (Coordinated Universal Time) · sha256:f948976150b8 [6] AnewZ · How the Iran Conflict Is Redrawing the Maritime Map (B) · Tue Sep 01 2026 18:56:00 GMT+0000 (Coordinated Universal Time) · sha256:730168e45f3c [7] Al Jazeera (aljazeera.net) · الممرات البحرية وجيوبوليتيك الاختناق: من السيطرة على البحار إلى إدارة التدفقات (B) · Sun Aug 30 2026 21:18:39 GMT+0000 (Coordinated Universal Time) · sha256:1d91e494e891 [8] The National · Scott Bessent says the Strait of Hormuz will be ‘worthless’ in two years. Analysts disagree (A) · Wed Sep 02 2026 14:08:36 GMT+0000 (Coordinated Universal Time) · sha256:b22d1d96ba36 [9] Al Jazeera · Iran war live: US rules out Iran talks until ship attacks stop (A) · Fri Sep 04 2026 00:00:00 GMT+0000 (Coordinated Universal Time) · sha256:b5d7c298fb82 [10] قناة الحدث (Al Hadath) · البحرية اليمنية تعترض قاربا يحمل مكونات مسيرات إيرانية قادمة من جيبوتي لمليشيا الحوثي. التفاصيل مع موفد "الحدث" أحمد بجاتو | قناة الحدث Al Hadath (E) · sha256:4cd81375be13

Source content hashes were computed at collection time; the cited text is preserved unmodified for the life of this product.

TLP:CLEAR