TLP:CLEAR · Disclosure is not limited.

Red Sea Shipping Disruption: Transit Continues, Risk Remains Elevated, 20 October 2026

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

BLUF

A broad physical closure of Bab al-Mandab is very unlikely over the next 0-14 days, although commercial shipping risk is likely to remain elevated. New reporting describes a skiff firing at an LNG tanker near Al Mukalla, but does not identify the attacker; reported Bab al-Mandab passages and partial Suez traffic recovery show that shipping continues.

Executive summary

The reporting indicates continued, fluctuating traffic through Bab al-Mandab, not a confirmed closure. A UK Maritime Trade Operations report describes a skiff firing two shots at an LNG tanker southeast of Al Mukalla in the Gulf of Aden; the tanker’s security team returned fire, and tracking data indicate the Poland-bound carrier continued its journey. The attacker is unidentified. Separately, a Qatari LNG cargo was reported moving north through the Red Sea. Container traffic through Suez has recovered from its 2024 to mid-2026 trough, but remains below 2023 levels. Houthi threats and reported attempts to restrict Saudi-linked shipping, alongside fighting by Yemeni government forces and the Southern Giants Brigades near Bab al-Mandab, sustain exposure to disruption.

Change from previous assessment

Initial assessment of this topic. Since the prior brief, the record adds a report of a skiff firing at an LNG tanker near Al Mukalla and tracking data indicating the Poland-bound carrier continued its journey. This is a reported vessel-level security incident, but it does not establish Houthi responsibility or a Bab al-Mandab attack. The brief also adds specific Bab al-Mandab passage counts and October Suez traffic figures, which strengthen the assessment that shipping continues while recovery remains partial.

Key judgments

1. A broad physical closure of Bab al-Mandab is very unlikely over the next 0-14 days. Reported passages included 35 vessels on 8 October, 39 on 10 October, 46 on 11 October and 32 on 12 October; a Qatari LNG cargo was also reported moving north through the Red Sea on 19 October. The supplied reporting says no broad closure has been confirmed. These reports establish continued passage, but do not provide a complete or current daily transit count. (Confidence: medium · ASSESSED)
   • I&W: Confirm: AIS-based reporting records commercial vessels passing Bab al-Mandab on each day monitored. (0-14 days)
   • I&W: Break: a maritime notice reports closure, or AIS records show no commercial passages for 48 consecutive hours. (0-14 days)
2. The reported skiff incident southeast of Al Mukalla establishes a security incident involving an LNG tanker, but does not establish Houthi responsibility or an attack in Bab al-Mandab. UK Maritime Trade Operations reported that the skiff fired two shots and the tanker’s security team returned fire. The report did not name the vessel; separate tracking data identify a Poland-bound LNG carrier as the only LNG tanker in the area at the time and indicate that it continued its journey. Confidence is medium because the incident details derive from a limited reporting chain and the attacker remains unidentified. (Confidence: medium · REPORTED)
   • I&W: Confirm: UK Maritime Trade Operations or ship-tracking updates link the incident to the Poland-bound LNG carrier and record its continued passage. (0-14 days)
   • I&W: Break: a UK Maritime Trade Operations follow-up identifies Houthi responsibility, or reports that the tanker was damaged, boarded or stopped. (0-14 days)
3. Suez container traffic has partially recovered, but remains below its 2023 level. Clarksons Research reported about 753,000 TEUs in weekly container transits in the first two weeks of October, compared with 1.457 million TEUs in the same period of 2023; it put Suez’s share of relevant container capacity at 36 per cent in early October, against 80 per cent before the attacks. BIMCO reported 16 container service return announcements since early July, and Linerlytica reported that more than 140 ships, with over 2 million TEUs of capacity, had switched away from Cape routing since May. Confidence is high because multiple shipping and research sources report a recovery, while the figures show it remains incomplete. (Confidence: medium · REPORTED)
   • I&W: Confirm: Clarksons Research reports weekly Suez container transits at or above the early-October level and BIMCO records further service returns. (1-3 months)
   • I&W: Break: weekly Suez container transits fall below the reported early-October level and carriers announce cancellations of returned services. (1-3 months)
4. Commercial shipping exposure at Bab al-Mandab is likely to remain elevated over the next 0-14 days, even as vessels continue to pass. The Houthis have threatened shipping and reportedly attempted to restrict Saudi-linked traffic; Yemeni government forces and the Southern Giants Brigades have reported fighting along the Red Sea coast near the strait. War-risk insurance premiums for Bab al-Mandab transits were reported at roughly 3 per cent from early September. The evidence supports heightened exposure, not an effective blockade or confirmed Houthi attack on a merchant vessel during this reporting window. (Confidence: medium · ASSESSED)
   • I&W: Confirm: UK Maritime Trade Operations reports a verified attack, attempted strike or obstruction involving a commercial vessel at Bab al-Mandab. (0-14 days)
   • I&W: Break: daily AIS-based passages remain at or above the reported 35-vessel low, and Bab al-Mandab war-risk premiums fall below 3 per cent without a new maritime incident. (1-3 months)

Outlook & scenarios

Continued passage with elevated exposure (65%)

This is the likely near-term course. Commercial vessels continue passing Bab al-Mandab, while carriers retain caution over the reported skiff incident, Houthi threats and fighting on the Yemeni coast. Suez traffic recovery remains partial rather than returning to 2023 levels.

Escalation reverses some Suez returns (25%)

This is an unlikely but plausible course. A confirmed attack on merchant shipping or an intensification of fighting near Bab al-Mandab prompts carriers to suspend additional Suez services and favour Cape of Good Hope routing. The immediate observable effects are reduced vessel counts and cancelled service returns.

Sustained interruption of commercial passage (10%)

A sustained interruption is very unlikely, but would have high impact. A successful blockade effort or repeated attacks on commercial vessels halt passages through Bab al-Mandab, reversing the Suez recovery and forcing renewed Cape routing. Current reporting does not establish that the strait is closed.

Recommendations

1. Maintain a daily watch of AIS-based Bab al-Mandab passages and UK Maritime Trade Operations notices. Record passage counts by date so a short-term interruption is distinguishable from a broad closure.
2. Seek a UK Maritime Trade Operations follow-up on the Al Mukalla skiff incident. Confirm the tanker identity, its track, any damage and whether authorities identify the attacker before attributing the incident to the Houthis.
3. Track weekly Clarksons Suez container-transit figures alongside BIMCO service-return announcements and the reported Bab al-Mandab war-risk premium. Keep each source’s measurement period and metric explicit.
4. Describe the waterway as open with elevated shipping exposure unless verified transit data or an authoritative maritime notice establishes a closure. Keep Gulf of Aden incidents distinct from Bab al-Mandab incidents.

Confidence & uncertainty

Overall confidence is high for the broad assessment that commercial passage continues and Suez traffic has partially recovered. Wire-service and trade reporting, including figures attributed to Clarksons Research, BIMCO and Linerlytica, supports that assessment. The Al Mukalla incident rests on a more limited reporting chain, its vessel identification is indirect, and the attacker is unknown. Transit figures also cover different dates and measures, so they do not establish a complete picture of daily traffic.

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 · PARTIAL] 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 · PARTIAL] 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.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.2 · PARTIAL] War-risk and hull insurance coverage changes: issuance refusals, premium increases for Red Sea transits, or explicit route exclusions by underwriters (policy notices or market rate data with dates). Recommended collection: commercial/insurance_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

Red cell review: PARTIAL DISSENT, KJ-3 downgraded HIGH→MEDIUM (estimative_mismatch)

TLP:CLEAR