Tankers hit off Oman as Strait of Hormuz corridor reopens to projectiles

Two merchant vessels reported being struck by projectiles in the Gulf of Oman on the morning of 17 July 2026, in two separate incidents roughly 100 nautical miles apart. The first advisory, issued by the United Kingdom Maritime Trade Operations centre (UKMTO) at 11:10 UTC, placed the hit on a tanker 19 nautical miles east of Khasab, at the mouth of the Strait of Hormuz, with minor damage to the vessel's port side and all crew reported safe. A second UKMTO notice at 11:40 UTC described a further incident about 100 nautical miles east of Duqm, on Oman's Arabian Sea coast, involving a merchant vessel and unspecified military forces. Both advisories were relayed in real time by the Open Source Intel channel on Telegram, which framed the second strike as part of a continuing pattern by the "Islamic regime." No party has claimed responsibility; the wording of the Khasab advisory attributes the projectile to "unknown" actors.

Whatever the launcher, the geography is the story. The Strait of Hormuz carries roughly a fifth of global seaborne oil; the Arabian Sea corridor east of Oman carries the rest of Gulf exports once they clear the strait. Strikes 19 nautical miles off Khasab and 100 nautical miles off Duqm sit on the same tanker lane, on the same morning, after months in which commercial shipping through these waters has been treated as a permissible target. The shipping insurers and the oil traders will price that within hours; the politicians will take weeks.

The Khasab hit

The Khasab incident is the easier of the two to read. A single projectile, port-side damage, crew safe, vessel continuing under its own power. The pattern matches the spate of small-boat and drone attacks on tankers that have punctuated the Gulf since late 2024, the difference being that the projectiles here appear to have come from the shore or from a fast inshore craft rather than from a limpet mine or a UAV. UKMTO's standard language, "unknown projectile," is a deliberate diplomatic cushion: it preserves the legal option for the vessel's flag state and its insurers to file a claim without prejudging attribution. The cushion is also the news, because it tells the reader that the Royal Navy's liaison office in Dubai does not yet know, or will not yet say, who fired.

The Duqm incident, and what "military forces" means at sea

The Duqm advisory is the harder one. UKMTO's wording, "merchant vessel and military forces," is unusual. UKMTO advisories typically describe weather, suspicious approaches, or the aftermath of an attack; they rarely identify the other party as a military formation unless the facts are unambiguous. The phrase carries two readings. The first is that a naval vessel, almost certainly Iranian Revolutionary Guard Corps Navy given the location and the pattern of past confrontations off Duqm and Musandam, intercepted or hailed the merchant ship and the encounter escalated. The second is that a projectile, again of unknown origin, struck the vessel and the military contact is incidental. The Open Source Intel framing, "Islamic regime firing at tankers again," picks the first reading. UKMTO's own wording leaves both on the table.

The honest answer, given only the two advisories as published, is that this publication does not know which is correct. The available reporting names no flag state, no owner, no casualty count, and no confirmed launcher; it places two incidents on a single morning inside a corridor the world's tanker fleet cannot route around.

Why the corridor matters more than the launcher

The structural point is bigger than either incident. Roughly a fifth of seaborne crude transits Hormuz, and almost all of that barrels east past Duqm after clearing the strait. A shipping lane that can be struck twice in a single morning, with the strikes unclaimed and the launchers unidentified, is a lane that the Lloyd's-listed war-risk underwriters will reprice by Monday and that the major charterers, including the state oil buyers of Asia, will start routing around. There is no overland substitute at scale. The East-West Pipeline from Abu Dhabi to Fujairah can bypass Hormuz, but its nameplate capacity is a fraction of total Gulf exports, and the Saudi Petroline to Yanbu carries Saudi crude only. Routing around Hormuz by sea, via the Cape of Good Hope, adds roughly two weeks per voyage and lifts bunker-fuel costs across the wet market.

This is the asymmetry the firing party, whoever it is, is exploiting. The marginal cost of a single projectile on a merchant hull is low; the marginal cost of even a partial reroute across the global tanker fleet is enormous, and it shows up first in insurance premiums, then in delivered crude prices in Singapore and Rotterdam, and only afterwards in headline diplomacy. The pattern matters more than the launcher because the pattern is what gets priced.

What remains contested, and what to watch next

Three things are unresolved at the time of writing. First, attribution: UKMTO has not named a launcher for either strike, the Khasab advisory attributes the hit to an "unknown projectile," and the Duqm advisory refers generically to "military forces." Second, the second vessel's condition: the Duqm notice published via Open Source Intel does not state damage or crew status. Third, the wider naval posture: neither the Royal Navy's Combined Maritime Forces headquarters in Bahrain nor the U.S. Fifth Fleet has been quoted in the available advisories, and their silence, or their next statement, will be the next data point. Watch for a UKMTO update notice within 24 hours, for any flag-state statement from the vessels' registries (Marshall Islands and Liberia cover most of the relevant tanker tonnage), and for any change to the Joint Maritime Information Centre's transit advisories. If a third strike lands before the close of the week, the pricing is no longer incremental; it is a regime change for the corridor.

Desk note: this publication is reporting the two UKMTO advisories as published, attributing the broader pattern framing to the Open Source Intel Telegram channel that relayed them. Where the channel's editorial line and UKMTO's diplomatic wording diverge, both are named.

Wire provenance

This editorial synthesis draws on the following public wire/social posts:

• https://t.me/s/osintlive
• https://t.me/s/osintlive
• https://t.me/s/osintlive