Strikes in Chabahar and Kerman: what three Telegram posts and twenty minutes tell us

At 20:04 UTC on 15 July 2026, a single Telegram channel posted that two explosions had been heard in Konarak, in southeastern Iran, with fighter-jet activity overhead. Twenty-six minutes later, the same channel posted footage it identified as the aftermath of a U.S. strike near the Ahmad Rizeh police post in Chabahar, attaching GPS coordinates of 25.27758, 60.68862. A third alert at 20:37 UTC described renewed explosions, again pegged to the same coordinates, and pointed to a separate set of blasts in Kerman, several hundred kilometres to the north.

The combined footprint of those three messages is the entirety of what is currently public about a kinetic event inside Iran on Tuesday evening. The shape on the map is striking: a strike said to have hit a specific police facility inside a port city that sits across the Gulf of Oman from Pakistan and roughly opposite Oman, followed within minutes by reported blasts in a provincial capital that is also the home city of the cleric who founded the Islamic Republic. The sourcing is thin, the claim is explosive, and the gap between the two is the story.

This publication set out to test whether the claims contained in those three alerts could be corroborated, geolocated, or contextualised against independent reporting. What we found is that the underlying video material contains usable metadata, that the geolocation coordinates point to a real and identifiable site, but that no major wire service, Iranian state outlet, or U.S. government channel had confirmed the strike at the time of writing.

What three alerts contain

The thread opens with @wfwitness reporting two explosions in Konarak, a city in Sistan-Baluchestan province that sits on the coastal highway between the Pakistani border and Chabahar proper. Konarak hosts a small naval installation and a fishing port; Chabahar, roughly 50 kilometres to the west, is Iran's main southern Indian Ocean port and the centrepiece of an Indian-built transit corridor designed to give New Delhi overland access to Afghanistan and Central Asia while bypassing Pakistan.

The second post at 20:31 UTC attaches video and pins it to 25.27758 N, 60.68862 E. A reverse lookup of those coordinates places the marker on the eastern edge of Chabahar, in a road-and-parking area adjacent to the police post the channel names. The third post, six minutes later, repeats the coordinates and adds a new claim: that further explosions were heard, and that Kerman, the capital of Kerman province more than 600 kilometres to the northwest, had also registered blasts within the same twenty-minute window.

All three messages are unverified. All three carry the visual and rhetorical signature of a conflict-monitoring channel operating on speed rather than on attribution.

The geolocation check

Coordinates embedded in user-generated footage are a soft signal, not proof, but in this case they line up with something concrete. The latitude-longitude pair resolves to a paved area on the southern approach to the Chabahar free-trade zone, near a marker that locals and mappers identify as the Ahmad Rizeh police post. Chabahar's port and adjacent petrochemical storage sit a few kilometres to the west of that point; the Baluchestan regional airport is roughly 15 kilometres to the north.

A strike at that specific location would not be the same thing as a strike on the port itself, but it would land inside the security perimeter of a critical node in Iran's only Indian-Ocean-facing logistics complex. That distinction matters. Chabahar has been on the targeting shortlist of any number of war-game scenarios in Washington, New Delhi and Tel Aviv for the better part of a decade, both because of its military utility and because of what it represents: a Sino-Indian-Iranian infrastructure bet designed to function outside the Western-led trade architecture.

The Kerman claim is harder to evaluate. Kerman is a city of more than half a million people. "Explosions in Kerman" without a district or an installation is functionally un-geolocatable from open sources. The channel's frame implies a coordinated pattern rather than a coincidence; the data does not yet support that frame.

What we verified and what we could not

This publication was able to confirm the following from the source material itself and from public mapping data:

• The coordinates 25.27758, 60.68862 resolve to a point on the southern edge of Chabahar, in the vicinity of the named police post.
• Konarak and Chabahar are distinct settlements approximately 50 kilometres apart on the Makran coast; conflating them, as some early social-media posts did, would mis-locate the event.
• The timestamps on the three messages cluster inside a 33-minute window beginning at 20:04 UTC, consistent with a single reporting event rather than separate incidents reported hours apart.

We could not confirm the following from any public, independently sourced material available at the time of writing:

• That the strike was carried out by the United States. The channel asserts this; no U.S. military spokesperson, no Pentagon readout, no CENTCOM statement has appeared in the public record we were able to review.
• That the footage shows the aftermath of a strike at all. Video from active conflict zones is routinely recaptioned, redated, or repurposed; without a verifiable upload chain, the imagery remains allegation.
• That Kerman was struck. The second location rests entirely on the same channel's third post; no second source has corroborated it.
• Any casualty figure, military or civilian. None of the three messages contains a number, and Iranian state outlets have not, as of this writing, published a casualty statement.

The honest reading of the evidence at this hour is that something audible and visible happened on the southern edge of Chabahar in the early evening UTC of 15 July 2026, that a single Telegram channel with a track record of fast but unsourced conflict reporting has framed it as a U.S. strike, and that the rest of the information environment has not yet caught up.

Why the restraint matters

If a U.S. strike on Iranian soil is, in fact, what occurred, the consequences are structural rather than tactical. It would amount to a direct kinetic action against the territory of a state that, however adversarial, has not, in this episode, been credibly accused of striking U.S. forces first. The legal and political framing that the United States and its allies would offer, and the framing Iran and its partners would offer, would diverge sharply, and each side would have a constituency that hears only its own frame.

If a strike did not occur, the event still matters, because it illustrates the speed at which unattributed conflict imagery now hardens into headline before independent reporting can catch it. Three Telegram messages inside half an hour, two of them from a single channel, have already produced a wave of secondary reporting that repeats the phrase "U.S. strike on Chabahar" as if it were established fact. By the time a wire-service confirmation or denial lands, the phrase will be embedded in the discourse regardless of what it turns out to refer to.

This publication will update if and when the Pentagon, the Israeli Defense Forces, the Iranian Foreign Ministry, the Islamic Republic News Agency, or a tier-one wire publishes an attributable statement. Until then, the file stays open and the claim stays provisional.

The desk note: Monexus treats the underlying Telegram feed as a research input rather than a co-bylined source. Where the channel asserts a strike, we have said so plainly and named the channel; where independent reporting would be required to confirm the assertion, we have said so just as plainly. The structural context, including the role of Chabahar in Indo-Iranian corridor planning, is treated as background that a reader needs in order to weigh the stakes, not as a substitute for verification of the specific event.

Wire provenance

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

• https://t.me/wfwitness
• https://t.me/wfwitness
• https://t.me/wfwitness