Wire
10:25ZCLASHREPORNetanyahu:I spoke yesterday with Secretary of State Marco Rubio, and once again he reaffirmed to me the Unite…10:25ZTASNIMNEWSImages of al-Rahma Mosque in the south of Nablus, which was set on fire by Israel10:24ZTWOMAJORSStrike hits Epicenter construction hypermarket in Kryvyi Rih10:24ZMEHRNEWSDowning of the drone of the Saudi enemy over Al-Jawf, Yemen. The Yemeni armed forces announced that a drone m…10:24ZTASNIMPLUSIsrael's Channel 14 claims: Iran has issued an order to stop all attacks on Arab countries. Tasnim Plus10:23ZDDGEOPOLITMissile strike hits Kharkov10:23ZCLASHREPORNetanyahu to travel to Washington to meet President Trump10:22ZTASNIMNEWS181 of 518 Tehran shelters can be restored, official says
  • S&P 500 ETF 0.10%
  • Nasdaq 0.64%
  • Nasdaq 100 1.15%
  • Dow ETF 0.48%
Terminal ↗
← The MonexusGeopolitics

Explosions reported in Bandar Abbas; US denial circulates through Telegram channels

Two explosions were reported in Bandar Abbas on the evening of 25 July 2026, with the first Telegram notice timestamped at 21:16 UTC. Iranian-aligned channels floated an anti-ship-missile launch toward the Strait of Hormuz; American officials denied any US strike, in a line relayed through a single channel.

A graphic displays two circular portraits—a blonde woman beside an EU flag and a dark-haired man beside an Iranian flag—flanking a yellow phone icon on a blue patterned background, with the Iranian presidential emblem and Persian text at top.
A graphic displays two circular portraits—a blonde woman beside an EU flag and a dark-haired man beside an Iranian flag—flanking a yellow phone icon on a blue patterned background, with the Iranian presidential emblem and Persian text at top. @presstv · Telegram

Two explosions were reported in Bandar Abbas, southern Iran, in a Telegram cluster whose first item is timestamped 21:16:49 UTC on 25 July 2026. Within twelve minutes, the same set of channels was circulating competing frames: one suggested the blasts may have been the launch of anti-ship missiles toward the Strait of Hormuz; another said the explosions might not be related to an attack at all. By 21:45 UTC, the @wfwitness channel had packaged the story with an American denial attached.

The cluster is small, contradictory, and entirely open-source-channel-relayed. That is worth saying plainly: this is a developing story sourced from Telegram posts rather than from primary statements, and the accounts involved carry track records that any reader should hold in mind.

What was posted, and when

The earliest item in the cluster came from @rnintel at 21:16:49 UTC on 25 July 2026, posting that "two explosions" had been heard in Bandar Abbas. At 21:17:39 UTC and 21:17:40 UTC, the @IntelSlava channel reposted the same line in near-identical form. At 21:21 UTC, @wfwitness carried the "explosions in Bandar Abbas" notice on its own channel. At 21:28 UTC, @IntelSlava reframed the event, writing that "the explosions might be the launch of anti-ship missiles towards the Strait of Hormuz." At 21:28 UTC the same minute, @FotrosResistancee posted that the blasts "might not be related to an attack" and said verification was pending. At 21:45 UTC, @wfwitness carried the original explosions notice again, this time paired with the line that "American officials deny striking Bandar Abbas."

Monexus analysis: the sequence is worth attention because the Iranian-aligned frame (an Iranian missile launch rather than an incoming strike) appeared in the same channels that first reported the explosions, and before any American denial had been processed into the thread. Whether that reflects ground truth, fog of war, or the politics of the channels themselves is not something the cited posts establish.

The three explanations now in circulation

Three readings of what happened sit in the public cluster. The first, associated with @IntelSlava, is that Iran itself fired the ordnance, anti-ship missiles moving out toward the Strait of Hormuz from a coastal launch area. The second, pushed by @FotrosResistancee, is that the explosions were unrelated to any attack. The third, attached to the @wfwitness post at 21:45 UTC, is an American denial: US officials, unnamed in the cited post, said no US strike had hit Bandar Abbas.

Two of the three on-ground-reporting channels carry visible alignment. @IntelSlava publishes from a Russian-aligned visual-intelligence angle and has a track record of coverage sympathetic to the Moscow framing of the war in Ukraine. @FotrosResistancee publishes from an Iranian-opposition frame. Neither affiliation disqualifies their reporting, but each is worth holding in mind when weighing the cluster. The American denial, in turn, comes in this cluster as a line of text relayed through @wfwitness rather than as a primary statement. The cited posts do not specify which US official spoke, in which venue, or with what authority.

Why the channel-level framing matters

The Strait of Hormuz reading propagates fast partly because the geography fits. Bandar Abbas sits on the southern Iranian coast where anti-ship activity would be staged from if staged at all; the city and its surrounding province are referenced in the @IntelSlava and @FotrosResistancee posts as the locus of the reported blasts. Beyond that, the cited thread says nothing about oil traffic, seaborne crude share, naval posture, or the operational status of any base. Monexus assessment: the geographic and infrastructure claims that often sit in coverage of this corridor are not in the cited cluster and have been kept out of this article on that basis.

A second-order point concerns the channel mix. The American denial is the only line in the cluster that originates from outside the open-source-intelligence ecosystem, and it arrives at the end of a thirty-minute chain of Telegram reposts. That is procedurally how Telegram clusters often work: a single relayed line gets bundled into the headline of a later post, then circulated as if it were the channel's own reporting. The reader should treat the US denial as text in the cluster, not as a verified primary statement by a named official.

What remains unsettled

This article has not independently established what detonated in Bandar Abbas on the evening of 25 July 2026. The cited thread contains no imagery, no seismic data, no Iranian state-media confirmation, and no US Central Command or State Department statement. Iranian state media PressTV, Tasnim, and IRNA were not in the cluster at the time of writing; the cited posts do not specify whether they have since carried their own line. The American denial is short, anonymous, and relayed.

Two corroborations would change the picture. First, a primary statement from a named Pentagon or State Department voice would let the denial be weighed against the weight of office. Second, commercial-ship AIS data, satellite thermal signatures from the launch area, or Iranian state confirmation would let the missile-launch reading be tested against the ground. Until one of those lands, Bandar Abbas at 21:17 UTC on 25 July 2026 is a live, unresolved event, and the channel-level frames around it tell the reader as much about who reports what first as they do about what actually happened.

How Monexus framed this: the cluster contained only Telegram-channel output, so the article has stayed close to the source-of-origin on each item rather than inferring institutional or geographic claims the posts do not contain. Where the cluster invites inference (missile direction, US denial substance), the inference is labelled as analysis rather than reporting.

Wire provenance

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

  • https://t.me/wfwitness/104907
  • https://t.me/intelslava/91501
  • https://t.me/FotrosResistancee/23332
  • https://t.me/wfwitness/104905
  • https://t.me/intelslava/91499
  • https://t.me/intelslava/91498
  • https://t.me/rnintel/64928
Intelligence ThreadFollow on terminal ↗
© 2026 Monexus Media · AI-native reporting from public-source material