17AUG

Two tanker claims, one logged blast

2 min read

15:37UTC

Houthi spokesman Yahya Saree claimed strikes on two tankers on 5 August, off Yanbu and in the Gulf of Aden. Only the Gulf of Aden explosion reached the incident log.

← Back to A 35-party Iran action, invisible to search Jump to analysis ↓

ConflictDeveloping

Key takeaway

The Houthis claimed two tanker strikes; UKMTO logged one explosion, and the vessel identification remains unconfirmed.

Houthi military spokesman Yahya Saree made two separate claims on Wednesday 5 August: a ballistic-missile strike on the tanker Wafaa off Yanbu on Saudi Arabia's Red Sea coast, and a strike on the tanker Daisy in the Gulf of Aden ¹. Several wires merged them into a single vessel of disputed name ². Yanbu and the Gulf of Aden sit more than 800 nautical miles apart, at opposite ends of the Red Sea, so evidence for one strike is no evidence at all for the other.

UKMTO (United Kingdom Maritime Trade Operations), the Royal Navy cell to which merchant captains report incidents at sea, recorded one event: a loud explosion 95 nautical miles south-east of Aden at 14:30 UTC, crew accounted for, no environmental impact ³. As of Thursday 6 August its record held nothing matching the Yanbu claim. A UKMTO log entry and a Saree announcement carry different evidential weight. A master reporting to UKMTO is describing something that happened to their own ship; a belligerent announcing a hit has every reason to claim ones it did not land. Cutting the other way, vessels in this corridor routinely run dark or decline to report, so an unlogged claim is weaker evidence of nothing having happened than an absent satellite fire signature would be. The Yanbu claim should be held open, not dismissed.

Naming the vessel rests on thinner ground still. The open-source analyst AtlasObserver tentatively named the Gulf of Aden vessel as the Dominica-flagged product tanker Daisy, International Maritime Organization (IMO) number 9516545, and no flag state, owner, insurer or official body has confirmed it ⁴.

The "eighth tanker since 22 July" figure now circulating is the movement's own running count, not a verified total, and that distinction carries a price. War-risk underwriters set premiums off demonstrated capability, and the Houthis have moved rates before by announcing intent, widening their target set to Yanbu and Jazan Aramco sites in late July and claiming strikes on crude transport infrastructure days later . An unverified claim, repeated widely enough, costs shipowners money whether or not a missile ever flew. Riyadh struck Houthi-held military sites near Hodeidah after the NCC Masa was hit off Al-Shuqaiq in July , , which is what turns a second unconfirmed claim into something more consequential than a bookkeeping dispute.

Deep Analysis

In plain English

A Houthi military spokesman said the group had struck two oil tankers, named Wafaa and Daisy, in the Gulf. The UK's maritime monitoring body, UKMTO, only recorded one explosion, and has not confirmed which ship, if either, was actually hit. Houthi claims about ship strikes have often run ahead of what can be independently verified.

Deep Analysis

Root Causes

Houthi strike claims have historically outpaced what UKMTO can independently confirm within the same window, and this claim follows that pattern: one explosion logged against two claimed strikes, with vessel identification still pending.

UKMTO's logging depends on vessel operators reporting in, and neither the Wafaa nor Daisy operator has yet confirmed which, if either, was hit.

What could happen next?

Risk
A doubled claim against a single confirmed incident risks becoming the reported figure in wire coverage before either vessel operator responds, inflating the apparent tempo of Gulf strikes.

Sources:gCaptain·CNN

Mentions:Yahya Saree →Wafaa →Daisy →UKMTO →Yanbu →Gulf of Aden →NCC Masa →Hodeidah →Houthis →Riyadh →Red Sea →United Kingdom →International Maritime Organization →Saudi Arabia →Royal Navy →Al-Shuqaiq →Jazan →

First Reported In

Update #166 · Two Hormuz deals, neither one published

gCaptain· 6 Aug 2026

Read original →

Causes and effects

This Event

Two tanker claims, one logged blast

War-risk premiums are being set off a tally the attacking party maintains, with no independent reconciliation of what was actually hit.

Led to

Houthis claim an oil transport strike

Extends the Houthi campaign against Red Sea shipping tracked since late July.

Occurred 26 Jul 2026

Read story →

Yemen's front began with a blocked flight

The reported Yemen casualties and tanker decline followed earlier Houthi attacks on shipping.

Occurred 6 Aug 2026

Read story →

Different Perspectives

Shipping and insurance underwriters

Kpler counted five Hormuz transits on 16 August against 31 the previous weekend, while Windward logged four vessels going AIS-dark for up to a month; underwriters price both the attacks and a sanctions register that names their counterparties in unreadable scanned images. Two trackers now measure only the ships that consent to be seen.

China

China sits at the end of the payment chain the 14 August designation targets: Iran's shadow banking network exists to convert sanctioned oil sales, much of it to Chinese refiners, into usable funds. Beijing has previously refused to recognise OFAC's jurisdiction over its own entities buying Iranian crude, leaving this designation to test compliance rather than change trade.

Qatar

Qatar's foreign ministry denied on 16 August holding any Iranian pilots alive, contradicting Iranian General Mohammad Bagherzadeh's claim that Doha holds three Su-24 aircrew, and said it had recovered only one set of remains. Qatar carries Iran's messages to Washington, and this is a public break with Tehran over a fact only one aircrew inquiry can settle.

Oman

Oman's shipping-map talks, covering monitoring, environment and maritime services, were publicly decoupled from any Hormuz reopening by Iran's own foreign minister on 17 August. Muscat's mediation channel keeps functioning on the narrow file it was given, while the political decision it hoped to unlock stays with Iran's security council.

Saudi Arabia

Saudi Arabia separately called the recurrence of tanker attacks on Emirati shipping a dangerous escalation, breaking from the UAE's repeated formula. Riyadh speaking in its own name over an attack on another state's vessels signals it reads the pattern differently from Abu Dhabi's flat statements.

United Arab Emirates

The UAE foreign ministry condemned a third ADNOC-linked tanker attack on 15 August in language identical, word for word, to its statement the day before. Three consecutive strikes on Emirati shipping have not moved Abu Dhabi's public wording by a single adjective.