Wire
22:02ZALALAMFATwelve killed, 309 injured in attack at King Khalid Airport, Saudi Arabia confirms22:02ZBBC NEWSFour dead and thousands without power after Hurricane Isaias lashes US22:01ZTASNIMPLUSAt least 12 killed, 50 injured in Yemeni forces attack on Riyadh airport22:00ZJAHANTASNIYemen missile attack on Riyadh airport kills 12, New York Times reports22:00ZFARSNAAmerican diplomat says Iran may launch preemptive attack22:00ZENGLISHABUAt least 12 killed, 50 wounded in Houthi strike on Riyadh airport22:00ZABUALIEXPRAt least 12 dead, 50 injured in Houthi attack on King Khalid Airport in Riyadh21:58ZCLASHREPORIran preserved missile, drone production capacity despite U.S., Israeli strikes
  • S&P 500 ETF▲ 0.60%
  • Nasdaq▲ 0.64%
  • Nasdaq 100▲ 0.51%
  • Dow ETF▲ 0.87%
Terminal ↗
← The MonexusBusiness · Economy

Vessels off UAE ordered from anchorage as UKMTO logs VHF warnings

UKMTO logged VHF warnings to commercial vessels at anchorage near Ras Al Khaimah on 10 October 2026. Iran-aligned channels named the IRGC Navy as the source; UKMTO's own wording did not.

Commercial ships at anchorage off the UAE emirate of Ras Al Khaimah were told to leave the area on the evening of 10 October 2026, after VHF radio broadcasts instructed them to depart, according to notices carried by the UK Maritime Trade Operations. The Jerusalem Post's Telegram channel relayed UKMTO at 20:46 UTC the same day, reporting that the agency had "received reports from several ship captains that they had been instructed" to leave their anchorages.

Al Alam Arabic had broken the news on its channel earlier the same evening, quoting UKMTO that "several ships off Ras Al Khaimah in the UAE" had been directed to leave their anchorages. The Iran-aligned outlets IntelSlava and Tasnim News carried the same UKMTO wording but added an attribution that the source of the transmissions was the IRGC Navy. UKMTO's own bulletin, as carried by the outlets in this thread, did not name an actor.

What the cited sources actually say

Reading the five Telegram items together produces a narrow, defensible record. Al Alam Arabic posted at 19:41:20 UTC on 10 October 2026, quoting UKMTO's wording that ships off Ras Al Khaimah had been directed to leave their anchorages. Mehr News and Tasnim News English both ran the bulletin in the same hour, using the same core wording. The Jerusalem Post relay followed at 20:46 UTC, attributing the report to UKMTO and noting that ship captains had reported the instructions. IntelSlava, which watches Iranian military traffic, posted at 20:18 UTC that the warnings had come "from the IRGC Navy."

The distinction matters. UKMTO's role, as reflected in the wording the outlets carried, is to log what mariners report, not to assign responsibility for it. Of the five sources in this thread, only IntelSlava and Tasnim News explicitly named the IRGC Navy as the transmitting party. Tasnim is an outlet affiliated with the IRGC; IntelSlava is an open-source intelligence channel that monitors Iranian naval movements. The Jerusalem Post, Al Alam Arabic and Mehr News reproduced UKMTO's wording without naming a source. UKMTO's own attribution, beyond the bulletin wording, is not visible in these items.

The most defensible read of the public record on this thread is therefore narrower than either the Iranian-aligned or the Western framing: UKMTO logged the warnings; Iran-aligned channels named the IRGC Navy; UKMTO itself did not name an actor in the wording reproduced here.

Where it happened, and what geography implies

Ras Al Khaimah is the northernmost of the seven UAE emirates, sitting on the southern side of the Strait of Hormuz, the seaway that links the Persian Gulf to the Gulf of Oman. The strait is the transit route for a substantial share of seaborne crude leaving the Gulf. The four cited regional outlets placed the incident off Ras Al Khaimah specifically, which is the part of the UAE coast closest to the strait and the Iranian side.

The geography also explains why the wording matters. UKMTO advisories are read by ship operators, insurers and naval liaison officers across the region. An advisory of this shape, in which the issuing party is unnamed but the location and the instruction are specific, is the kind of bulletin that prompts masters to weigh their next move without yet requiring formal diversion.

The available source items do not specify how many vessels received the warnings, which flags they were flying, or whether any complied. Independent confirmation of the transmissions, beyond UKMTO's log and the Iran-aligned outlets that named the IRGC, is not present in this thread.

Two readings of the warnings

The Western-aligned reading, implicit in the Jerusalem Post's relay, treats the bulletin as an incident to be logged and reported: a fact on the water that operators and analysts should weigh. The Iran-aligned reading, present in IntelSlava and Tasnim, treats the warnings as a deliberate signal from the IRGC Navy directed at commercial traffic off the UAE coast.

Both readings are consistent with the same set of source items. The bulletins are identical in their core wording; the difference is in what is added. The simplest editorial test is provenance: UKMTO logs what mariners say; Iran-aligned channels name a transmitter. On this thread, only the latter carries an attribution.

Monexus analysis: the operational signal carried by UKMTO's wording, with no actor named, is consistent with a calibrated warning rather than the prelude to an interception. That reading is not entailed by the source items; it is a hypothesis on which the next 12 to 24 hours of reporting will be the first test.

What remains uncertain

The five source items in this thread do not specify the number of vessels warned, the vessel flags, the content of the VHF message beyond the instruction to depart, or whether any ship complied. They do not specify whether the IRGC Navy issued any public statement beyond the framing carried by Tasnim. Independent wire confirmation from Reuters, Associated Press, the BBC or other tier-one outlets is not visible in the thread, and the search layer did not surface a contradiction to the specific 10 October 2026 advisory. The next bulletin from UKMTO, or its absence, will determine whether this is logged as a single warning or as the opening move in a longer sequence.


This desk held the UKMTO wording as the spine of the article and treated the IRGC attribution carried by Iran-aligned channels as one of two competing readings, not as established fact. Historical context that would require sources outside this thread was deliberately omitted.

Wire provenance

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

  • https://t.me/The_Jerusalem_Post/17815
  • https://t.me/alalamarabic/509531
  • https://t.me/intelslava/96094
  • https://t.me/tasnimnews_en/42219
  • https://t.me/mehrnews/421278

At the source.

Open the posts cited in this article.

Telegram postOpen original ↗

Live content may have changed since this article was published. Loading it contacts Telegram.

Telegram postOpen original ↗

Live content may have changed since this article was published. Loading it contacts Telegram.

Telegram postOpen original ↗

Live content may have changed since this article was published. Loading it contacts Telegram.

© 2026 Monexus Media · AI-native reporting from public-source material
The Monexus

Read with context.

Using this article and its related event records

Find the evidence behind a claim, inspect a dated position, or pick up the thread.

Source lookup is available to everyone. Members can request an AI explanation grounded in the retrieved material.

Browse event files →
Vessels off UAE ordered from anchorage as UKMTO logs VHF warnings - The Monexus