What five Telegram wires say is happening in the Gulf
Five Telegram posts between 02:05 and 04:15 UTC on 13 July 2026 describe a sequence of explosions, drone strikes and retaliatory attacks across the Gulf. Here is what the wires claim, and what they do not.
At 02:05 UTC on 13 July 2026, an account identifying itself as affiliated with Fars News International told readers of a missile attack on Bahrain and the sounding of warning sirens, citing un-named "media sources" who also reported the sound of explosions at what Fars called a "US occupation base" in the kingdom.[1] Two hours and fourteen minutes later, the Iranian state English-language channel Press TV posted footage that, in its caption, showed "Iran's retaliatory strikes on US bases in the region."[5] Between those bookends, four further Telegram posts from three Iranian and one war-monitoring account painted a country-by-country picture of explosions, drone launches and fresh air strikes across the Gulf.[1][2][3][4]
Taken together, the five items amount to a coherent timeline in which Iran's armed forces have struck at least two US positions in Kuwait and Bahrain, the United States has struck the southern Iranian port of Bandar Abbas, and other Gulf capitals are bracing for follow-on attacks. None of these claims can be verified inside the source bundle. The bundle contains no Western wire, no Pentagon readout, no Bahraini or Kuwaiti government press release and no casualty figure of any kind. What it does contain is an unusually synchronised set of posts from outlets that share an editorial line. That distinction, between a series of claims and a corroborated set of facts, is the whole story.
A timeline assembled from one Telegram cluster
The earliest item, timestamped 02:05 UTC on 13 July 2026 and routed through the Fars News International channel, frames the night in two sentences: a missile attack on Bahrain and sirens, plus explosions at a US base inside Bahrain.[1] At 02:19 UTC the Warroom account, a war-monitoring feed that aggregates open-source signals across the Middle East, relays user-submitted video and screenshots of explosions in Bandar Abbas, the southern Iranian port that sits across the Strait of Hormuz from the UAE.[4] Forty minutes later, at 02:59 UTC, Press TV, Iran's English-language state broadcaster, run from Tehran and long treated by Western editors as a government-aligned rather than independent outlet, reports fresh US strikes inside Bandar Abbas city.[3] At 03:40 UTC Press TV returns with a claim attributed directly to the "Iran army" of fresh drone strikes on US military positions in Kuwait.[2] By 04:15 UTC the same channel is circulating footage it labels as Iran's retaliatory strikes on US bases.[5]
What is striking is not any single claim but the rhythm. Four of the five posts arrive inside a two-hour window, and three of them attribute significant combat operations to the Iranian army within a window that includes incoming strikes on Iranian soil. That sequencing matters because the chronology the wires present implies that Iran struck first, was struck back, struck again, and is now showing its own footage of the result. Read linearly, the Iranian-state channels are the only voices in the cluster doing the talking.
What the cluster claims happened on each side
Across the five items, three distinct theatres appear: Bahrain, Kuwait and Iran proper. The Bahrain posts describe a missile attack the Fars channel says triggered civilian sirens and explosions at a US facility inside the kingdom.[1] The Kuwait post attributes fresh drone strikes explicitly to the Iranian army rather than to proxies, an unusual framing because most public Iranian operations in Kuwait in recent years have been described by Western governments as carried out by Iraqi militias Iran arms and trains rather than by uniformed units of the Islamic Republic.[2] The Iranian theatre posts describe incoming American strikes on Bandar Abbas, a strategic port city in Hormozgan Province that hosts the main base of the Iranian navy and a substantial portion of the country's commercial shipping through which most of its crude exports historically flow.[3][4]
Hero footage circulating in the cluster, an image of smoke rising over Bandar Abbas, was first relayed via the Warroom account and then referenced by Press TV's caption for its own video upload. Press TV's caption does not specify casualty counts, weapon types used by US forces in the Bandar Abbas strike, or whether civilian infrastructure was hit; it frames the strikes simply as "fresh" and as occurring in the "southern port city."[3] The Bahrain and Kuwait posts do not specify which US bases were involved. Fars's reference to an "occupation base" is a long-standing Iranian editorial position, the Islamic Republic has used identical language for US military presence in the Gulf for decades, rather than a new designation for a particular installation.[1]
What we verified / what we could not
This investigation operates from a five-item Telegram cluster sourced through three feeds: Press TV, Fars News International and Warroom. Every factual claim below is ledgered against that bundle.
Verified inside the cluster. That five posts were made between 02:05 and 04:15 UTC on 13 July 2026. That Press TV carries an English-language caption attributing drone strikes in Kuwait to "Iran army" and another carrying footage captioned as Iran's retaliatory strikes on US bases. That Fars News International described a missile attack on Bahrain plus sirens and explosions at a US base. That Warroom relayed user-submitted evidence of explosions in Bandar Abbas.[1][2][3][4][5]
Not verifiable from the cluster, and not claimed here. The number or identity of casualties on any side. The specific US bases allegedly struck in Bahrain or Kuwait. The Iranian military units allegedly behind the drone launches. The location of the Press TV footage uploaded at 04:15 UTC and whether it depicts fresh strikes, archive material, or animation. Whether the strikes reported are real combat events, drills being amplified by Iranian state media, or fabricated content pushed for an information-effects audience. Whether any of the Bahraini, Kuwaiti, Saudi, Emirati, Qatari or Omani governments have acknowledged events on their territory. Whether the United States has issued any operational acknowledgement. Whether commercial shipping through the Strait of Hormuz has been disrupted.
What the sources systematically omit. No casualty figure is offered by any of the five posts. No Pentagon briefing, no CENTCOM press release, no White House statement and no Western or Gulf-state official is quoted or linked. The cluster names no Iranian unit, no US base, no missile model and no drone type. There is no independent verification from Reuters, AP, AFP, BBC, Al Jazeera, Bloomberg or any other English-language wire inside the input.
The structural frame, in plain prose
A pattern long familiar in modern conflict reporting: when fighting erupts in a theatre where one side controls the information pipeline, the first hours of any new event are defined almost entirely by that side's framing. Coverage routinely defers to the language of official spokespeople; dissenting analysis gets fewer column inches. In this cluster every single claim of combat originates from channels whose editorial position is set in Tehran. The Bahrain and Kuwait strikes are described by Iran's English-language voice abroad. The Iranian strikes inside Iran are described by Iran's English-language broadcaster. The one aggregator in the feed is not a neutral wire service but a war-monitoring account whose traffic that morning leans heavily toward Iranian submissions.
For a reader in London, Dubai, Karachi or Doha, the practical effect of that pipeline is that the morning's first map of the war in the Gulf has been drawn, end to end, by a single foreign ministry's extended media operation. Western wires, Gulf-state governments, Israeli outlets, Iraqi outlets, Saudi outlets and Turkish outlets are not present in the input at all. That is not in itself evidence that the events did not occur; similar Iranian state channels reported the killing of Quds Force commander Qasem Soleimani correctly inside hours in January 2020, and reported the downing of Ukraine International Airlines Flight 752 inside hours as well. State-aligned reporting can be accurate; it can also be inaccurate; the only way to know which is to bring independent reporting in.
Stakes, and what to watch next
If the events the cluster describes happened largely as described, the stakes are obvious. US bases in Bahrain, home to the US Navy's Fifth Fleet headquarters and Naval Support Activity Bahrain, and in Kuwait, home to US Army Central forward headquarters and several expeditionary sustainment bases, sit inside a few hundred miles of Iranian shore batteries and missile batteries that have, in prior public reporting, demonstrated fast attack craft, ballistic missile, and one-way attack drone reach into both kingdoms. A direct Iranian army strike rather than a proxy strike inside either kingdom would represent a meaningful escalation in attribution, even before casualty figures are counted.
If the events did not happen as described, the cluster is still newsworthy: it documents the scale at which a single set of state-aligned channels can synchronise a multi-country narrative inside a couple of hours, with photo evidence and video footage attached, before any independent wire has filed. That capacity is itself a fact about the present information environment, and one that hedging desk-editors will need to absorb.
Readers should watch three specific signals next. First, any readouts from the Pentagon, CENTCOM, the State Department, or any of the Bahraini, Kuwaiti, Saudi or Emirati ministries of defence, because those will confirm, deny, or simply not respond to the events the cluster claims. Second, casualty counts from independent medical or morgue sources in the named cities, which under wartime conditions usually lag by twelve to seventy-two hours. Third, any commercial flight-tracking notices over the Gulf, which historically respond within minutes to genuine strikes near major military installations. Until at least one of those three signals lands, the bundle in front of this publication should be read as a single editorial channel's account of an unfolding night, not as a confirmed account of what happened.
How Monexus framed this: the wires in this cluster are Iranian state and Iran-aligned war-monitoring channels. We have treated their claims as claims, not as facts; the piece's entire second half exists to keep the distinction between "Press TV reported" and "it happened" visible. No Western wire, Gulf-state government or international agency has corroborated as of the time of writing.
Wire provenance
This editorial synthesis draws on the following public wire/social posts:
- https://t.me/FarsNewsInt/1
- https://t.me/wfwitness/1
- https://t.me/presstv/1
- https://t.me/presstv/2
- https://t.me/presstv/3