Explosions reported across northern Iraq as details remain thin
Tasnim's English and Farsi channels carried parallel reports of blasts in Erbil and Sulaymaniyah within minutes of each other on 25 July 2026; cause, casualty count and responsibility have not been established in the available reporting.
Two explosions were reported across Iraqi Kurdistan in the space of roughly half an hour late on 25 July 2026, according to parallel posts from Iran's state-aligned Tasnim news agency. The first alert, logged at 22:51 UTC on the Farsi-language Jahan Tasnim channel, said an explosion had been heard in Sulaymaniyah. A second English-language Tasnim post followed at 22:53 UTC, repeating the Sulaymaniyah line. A third alert, at 23:10 UTC on the same network's English feed, extended the geography: an explosion had also been heard in Erbil. By 23:17 UTC the Farsi-language Tasnim Plus channel had carried a separate item on the Erbil blast, still without further detail.
Taken together, the available source items describe two separate loud noises, in two cities, with no confirmed cause, no casualty figure and no claim of responsibility. The reporting exists, in other words, as a sequence of alerts rather than a story.
What Tasnim actually posted
The five source items, all drawn from Tasnim's Telegram channels, share a near-identical structure: a one-line statement that an explosion was heard, the city name, and an acknowledgment that further details have not been published. The Sulaymaniyah alerts appear three times across two channels (Jahan Tasnim at 22:51 UTC and 23:10 UTC, Tasnim English at 22:53 UTC). The Erbil alert appears twice, on Tasnim English at 23:11 UTC and on Tasnim Plus at 23:17 UTC.
That distribution matters for how the rest of this piece should be read. Tasnim is an Iranian state news outlet, headquartered in Tehran and editorially aligned with the Islamic Republic's security establishment. Its choice to relay these alerts at all, and the speed at which they did so, is itself a piece of information: Iraqi Kurdistan has been the site of repeated Iranian operations against opposition Kurdish groups, Israeli strikes on Iranian-linked logistics in Syria that occasionally extend into Iraqi air space, and US military presence in and around Erbil. Any loud noise in either city has a non-trivial chance of being read, in Tehran, through one of those lenses.
The reporting Tasnim actually carried, however, stops at the fact of the sound. The available items do not specify whether the blast was a strike, an accident, a detonation of cached munitions, or something else. They do not name a casualty count. They do not identify a perpetrator, a target or a weapon. They do not cite Iraqi Kurdish officials, the Kurdistan Regional Government, or any Western military spokesperson.
Why this matters editorially
The temptation, when a wire alert flashes, is to fill the gap with pattern recognition. Erbil has hosted US forces at al-Harir airbase and the consulate complex that Iran-aligned militias have previously targeted with rockets and drones. Sulaymaniyah is the political heartland of the PUK, and the PUK's relationship with Tehran has historically been transactional rather than hostile. A strike on either city would, in previous reporting cycles, have carried a fairly predictable attribution window.
But this article is being filed from the alert phase, not the confirmation phase. Pattern-matching on a still-unexplained blast, before Iraqi Kurdish authorities, Iraqi federal authorities, the US-led coalition or any claimant has spoken, would convert an alert into a story that the evidence does not yet support. The honest ledger is narrower: two cities, two loud noises, two windows of time, and no confirmed cause. That is what Tasnim reported. It is also all that Tasnim reported.
What remains to be established
The open questions fall into three sets. First, the operational question: what exploded, in which district of each city, at what magnitude. The available items give city names and nothing finer-grained. Second, the casualty question: whether anyone was killed or injured, and whether critical infrastructure was hit. The Tasnim posts do not address this at all. Third, the political question: who is claiming, who is denying, and what the Iraqi federal government in Baghdad and the Kurdistan Regional Government in Erbil are saying in parallel.
For each of these, the credible next reads are first-party statements from the KRG's interior ministry, Iraqi federal interior spokespeople, the US-led Combined Joint Task Force – Operation Inherent Resolve (which has previously commented on incidents in and around Erbil), and any Iranian or Israeli official channel that may choose to weigh in. Iranian state outlets other than Tasnim, IRNA, Mehr, PressTV, would be a secondary check on whether the story is being amplified or quietly downplayed inside Iran itself.
What Tasnim's reporting does establish, plainly, is that within the hour before midnight UTC on 25 July 2026, two loud explosions were audible in two separate cities in Iraqi Kurdistan, and that the Iranian state news agency considered the fact worth relaying twice in English and three times in Farsi before any further detail had emerged. The rest, for now, is silence.
Monexus note: this article has been filed at the alert stage. It reports what Iranian state-aligned channels carried and refuses to attribute the blasts to any actor in the absence of a first-party claim or an official Iraqi or coalition statement. Where Western wires or Iraqi Kurdish officials subsequently publish, a follow-up will integrate their findings against the same evidentiary ledger.
Wire provenance
This editorial synthesis draws on the following public wire/social posts:
- https://t.me/tasnimnews_en/27927
- https://t.me/tasnimnews_en/27928
- https://t.me/JahanTasnim/226846
- https://t.me/JahanTasnim/226848
- https://t.me/tasnimplus/115810