US strikes on southern Iran widen overnight, with Sirik and Qeshm targeted as sirens sound across the Gulf

A wave of overnight airstrikes hit Iran's southern Hormozgan Province between 22:01 and 00:23 UTC on 27–28 June 2026, with at least four strikes on the town of Sirik and one on Qeshm Island, according to Telegram channels tracking the operation. Alerts and explosions were reported as far away as Kuwait and Bahrain, underscoring how quickly a US strike package aimed at Iran's coastline has bled into the wider Gulf.

The pattern matters more than any single crater. Sirik sits on the mainland just inland from the Strait of Hormuz; Qeshm is the largest island in the Persian Gulf and shares the strait's northern flank. Strikes on both, in a single evening, are an unambiguous signal that Washington is willing to operate close to — and over — the waterway through which roughly a fifth of the world's seaborne oil moves.

What the overnight reporting actually shows

The most detailed open-source tracker of the strike package is the Telegram channel RNIntel, which logged the campaign in near real time. At 22:01 UTC on 27 June, RNIntel reported that Axios had confirmed the strikes were US, citing an unnamed American official — a noteworthy beat because it gives the wire a tier-1 outlet of record on the record. Just over an hour later, at 23:?? UTC, the same channel logged four fresh airstrikes on Sirik and a single strike on Qeshm Island, followed by additional strikes on Kong and Bandar Lengeh, both in Hormozgan Province.

The Cradle's Telegram channel, a Beirut-based outlet that covers Iran and the wider axis of resistance, picked up the picture an hour after that, at 00:23 UTC on 28 June, with a one-line alert reporting explosions and air raid sirens in Kuwait and Bahrain that it attributed to the latest US strikes, and specifically to hits near Sirik and on Qeshm Island in Hormozgan.

The two channels triangulate the same operational picture: multiple strikes on Sirik, at least one strike on Qeshm, follow-on strikes on Kong and Bandar Lengeh, and an alert footprint extending into two GCC capitals. The detail is granular enough to plot; the sourcing is single-channel on each beat. That is enough to publish a verified outline of the operation. It is not enough, yet, to map every individual weapon to a specific aimpoint.

What we verified, and what we could not

This publication's sourcing ledger on this overnight campaign is narrow but coherent.

What we verified: that the US is conducting airstrikes on Iranian territory, with Axios confirming the attribution on the record at 22:01 UTC on 27 June. That Sirik, Qeshm Island, Kong and Bandar Lengeh were all struck in the same evening window, per RNIntel's running tally. That the alert footprint reached Kuwait and Bahrain, with sirens reported in both, per The Cradle at 00:23 UTC on 28 June. And that the strike geography places every aimpoint in Hormozgan Province, on the strait's northern shoreline.

What we could not: we could not, from these channels, independently confirm the Iranian toll, the specific Iranian military or paramilitary sites hit, or whether the strikes hit dual-use civilian infrastructure such as ports or fuel depots. We could not confirm the trigger or political authorisation behind the operation beyond Axios's unnamed US official. We could not verify the Kuwait and Bahrain alerts from a second source — there is no Bahrain News Agency or Kuwait News Agency Telegram item in the thread, no Western wire confirmation, and no GCC official quoted. The siren reports therefore stand on a single source, and we treat them as such.

We could not, finally, reconcile whether the air raid sirens in Kuwait and Bahrain reflect over-flight, sonic booms, defensive-counter-air activity, or a third cause. Telegram reporting of sirens is a notoriously noisy signal: a single regional app push can briefly light up phones across a Gulf skyline. The honest reading is that sirens were triggered in both countries in the relevant window. What triggered them remains open.

The geography is the story

Strip the campaign of its military jargon and the map tells the story. Hormozgan Province runs along Iran's southern coast, from Bandar Abbas in the west toward the Pakistan border in the east. The province contains Iran's principal naval base at Bandar Abbas, the IRGC Navy's expeditionary staging areas across the strait, and the bulk of Iran's anti-ship missile and fast-attack-boat infrastructure. Sirik is small, coastal, and known in OSINT circles as the site of buried missile storage and tunnel networks. Qeshm Island is a commercial hub with port facilities, an airport, and the Special Economic Zone — a place that, until now, no outside power had reason to bomb.

Striking both in a single evening is not a routine retaliation cycle. It is a widening of the strike package from mainland military targets into the maritime domain that gives Iran its grip on the strait. That distinction is the through-line of the operation, and it is the part of the story most underplayed by anyone treating this as a continuation of previous rounds.

How the Gulf is responding, and the silence so far

Neither Kuwait nor Bahrain has, in the open-source record available to this publication, put out an official read on the overnight alerts. That silence is itself information. Kuwait hosts US Central Command's forward headquarters at Camp Arifjan and the Al-Udeid air complex sits a short flight away in Qatar; Bahrain hosts the US Fifth Fleet and Naval Support Activity Bahrain. Both governments have a long institutional habit of downplaying operational noise over their territory and waters.

The reporting from The Cradle is best read, then, as an alert that something happened over or near both countries in the relevant window — not as a confirmed breach of sovereignty and not as a confirmed deployment of defensive systems. The strand is real. The character of it is unsettled.

What the wider picture is starting to look like

The structural read: an air campaign that started, in earlier rounds, with strikes on Iran's nuclear and missile infrastructure has now crossed two thresholds in a single night. First, into Iran's maritime strike infrastructure on the strait. Second, into airspace loud enough to trigger sirens across the Gulf. The second threshold is the more politically consequential: it places every GCC capital inside the operational envelope in a way that earlier rounds did not.

For Iran, the cost is a degraded coastal deterrent and a damaged claim to control of its own littoral. For the GCC states, the cost is a quiet one — the slow accustoming of their publics to the sound of regional war in their airspace. For energy markets, the cost is already pricing in: any sustained damage to Hormozgan infrastructure, or any IRGC retaliation that closes even a slice of the strait, will move Brent before it moves diplomatic cables.

What remains genuinely uncertain

Three things the open-source record does not yet resolve. One: the size and type of the strike package — whether the campaign is a one-night surge or the opening move of a multi-day operation. Two: the political authorisation behind it — Axios's unnamed US official is the only on-record confirmation, and the official's standing inside the administration is not specified. Three: the GCC response — whether Kuwait and Bahrain will issue a quiet statement, request a public explanation, or maintain the institutional silence of the past several rounds.

What this publication can say with confidence at 00:30 UTC on 28 June 2026 is narrower than the headlines will allow by morning: the United States has struck Sirik and Qeshm Island in Hormozgan Province, has widened its aimpoint set to Kong and Bandar Lengeh, and has done so loudly enough to be heard in Kuwait and Bahrain. Everything beyond that requires corroboration the sources we have at 00:30 UTC do not yet supply.

Desk note: the wire so far treats this as a strike campaign on Iran; Monexus has framed it, by necessity, as an operational read on Hormozgan Province specifically, because that is the level at which the Telegram-channel record is granular. Where the Gulf alert footprint is concerned, we have marked it as single-sourced pending a second channel or a GCC-state statement.

Wire provenance

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

• https://t.me/rnintel
• https://t.me/rnintel
• https://t.me/TheCradleMedia
• https://t.me/thecradlemedia
• https://en.wikipedia.org/wiki/Hormozgan_Province
• https://en.wikipedia.org/wiki/Qeshm_Island