This website uses cookies

Read our Privacy policy and Terms of use for more information.

AI-assisted content

Three tankers were struck off Oman's coast in 24 hours this week, and Iran never formally claimed any of them. This issue shows you how a broadcaster's own words, a maritime advisory's timestamps, and one free satellite pass can build a record that a non-claim cannot survive. The ceasefire that framed those strikes is now over, in President Trump's own words, and the technique does not depend on what replaces it.

Intercept

Three tankers were struck in the Strait of Hormuz inside 24 hours, all on the same contested route Iran had already warned ships off. Was this a surprise attack, or a warning carried out?

Signal

A free satellite pass will not tell you who fired. It will tell you whether the pattern on the ground matches the story you are being told. Here is how to read it.

Shadow

Iran never claimed the strikes. Its own broadcaster and its own prior warning already did the claiming for it. This section shows you how to build that into a file that does not depend on a formal admission.

• • •
Section 01 of 03 · Intercept
01

Three tankers were struck on the exact route Iran's own broadcaster had already warned ships to avoid.

On Monday night into Tuesday, three commercial vessels were struck in the Strait of Hormuz within 24 hours. UKMTO, Britain's maritime security monitor, reported the first strike at 21:19 UTC Monday, eight nautical miles east of Limah, Oman: a projectile hit the LNG carrier M/T Al Rekayyat on its port side, igniting an engine-room fire. The crew sent a mayday call and evacuated safely. The second vessel, the Saudi crude supertanker M/T Wedyan, was struck roughly sixteen nautical miles east of Khor Fakkan. The third, the Liberia-flagged M/T Cyprus Prosperity, was hit by a drone, per UKMTO, and continued under its own power. No casualties were reported on any of the three. CENTCOM later confirmed all three vessel names in its own statement.

M/T Al Rekayyat · LNG carrier · struck 21:19 UTC Mon, 8nm E of Limah, Oman
M/T Wedyan · crude supertanker · struck Tue, 16nm E of Khor Fakkan
M/T Cyprus Prosperity · struck by drone, Tue, per UKMTO
All three transiting the southern route along Oman's coast

Here is what the open record held before the first strike. Iran's IRGC-affiliated broadcaster IRIB had already posted a warning on X telling ships to use its declared northern route, closer to Iran's coast, instead of the Oman-side route. UKMTO's own weekend advisory noted that risk in the strait remained elevated despite the June ceasefire. None of that required insider access. It was sitting in public advisories and a broadcaster's own social feed before any ship was hit.

The practitioner question is not whether Iran struck these ships. The pattern is consistent with a warning being carried out, not a surprise attack. The question is at what point the record made that legible, and the answer is the IRIB warning itself, timestamped and public days before the first UKMTO advisory came through.

Do this now

Subscribe to UKMTO's free advisory feed before you need it, not after. Cross-reference any Hormuz incident's stated position against Iran's most recent public route warnings on X. If the strike sits inside a zone Iran already named, the "surprise" framing does not hold.

The broader pattern matters beyond this week. Iran has enforced a version of this route logic since the war's opening weeks, turning back or striking vessels that use the Oman-side passage. Each new Hormuz "incident" is best read as the latest instance of a standing policy, not an isolated event, until the record shows otherwise.

As of press time, that pattern has deepened rather than resolved. CENTCOM confirmed a second round of strikes on 8 July, saying it hit ninety targets to further degrade the threat to shipping. Iranian state media reported explosions in Bandar Abbas and Sirik, and Iran's Revolutionary Guard said it struck US bases in Kuwait and Bahrain in response. President Trump has called the ceasefire over. None of that changes the verification method below, only the stakes of applying it correctly.

• • •

Subscribe to keep reading

This content is free, but you must be subscribed to Signal & Shadow to continue reading.

I consent to receive newsletters via email. Terms of use and Privacy policy.

Already a subscriber?Sign in.Not now

Reply

Avatar

or to participate

Keep Reading