US strikes on Iran resume overnight as Tehran fires ballistic missiles toward Jordan
Overnight into 11 June 2026, the United States launched a new round of strikes on targets inside Iran, according to a Reuters wire alert timestamped 02:50 UTC. Within minutes, multiple open-source channels on Telegram reported Iranian ballistic missile launches out of Isfahan in central Iran, with at least one set of projectiles apparently directed toward Jordan rather than Israel — a notable geographic shift from the trajectory pattern of the previous week. The combined reporting, drawn from a single Reuters alert and four independent Telegram posts between 01:51 and 02:46 UTC, points to the most significant horizontal escalation of the air campaign since it began, and to a widening of the Iranian retaliation envelope.
The picture that emerges from the overnight traffic is not a single, contained exchange but a synchronised one: a US strike package hitting Iranian targets at roughly the same moment that Iranian missileers stood up multiple launchers in Isfahan, with projectiles tracked moving west and southwest. Reuters's 02:50 UTC alert is the load-bearing Western-wire confirmation that the US side of the exchange is real and ongoing. The Telegram feed from AMK Mapping and Middle East Spectator supplies the geographic specifics — Isfahan as the launch point, Jordan as a target — that a one-line wire alert cannot carry on its own. Read together, they describe a Middle Eastern night in which two state militaries are no longer simply trading blows across a single border but are reaching for second-tier targets in neighbouring states.
What the reporting actually says
The Reuters alert, carried on the @Reuters X account at 02:50 UTC on 11 June 2026, is short and unbylined: "US launches new strikes on targets in Iran." Reuters does not name the targets, the weapon system, or the basing in the alert itself; readers are pointed to subsequent reporting for the operational detail. The alert is, however, an explicit confirmation that the US air campaign has continued across a calendar-day boundary, which matters for any assessment of Washington's escalation calculus.
Four minutes earlier, at 02:46 UTC, two Telegram channels — AMK Mapping and the Iran-focused account @rnintel — independently reported ballistic missile launches from Isfahan. AMK Mapping's post specifies that the launches took place "around 10 minutes" before the post itself, which places first-launch observations at roughly 02:36 UTC. The corroboration across two channels within the same minute is significant: open-source intelligence of this kind is frequently single-sourced and easy to fake, but two independent geolocated posts on a tightly synchronised event lend one another credibility.
A third AMK Mapping post, timestamped 01:57 UTC, describes "another video" of Iranian ballistic missiles being launched "towards Jordan from northwestern Iran." The phrasing implies multiple launch events across the night, with at least one salvo originating from the northwest of the country rather than the centre. A Middle East Spectator post at 01:51 UTC frames the same activity more cautiously as "ballistic launches from Iran, unknown target" — a useful reminder that, in the first minutes of any such event, target identification is itself a contested claim.
Why the Jordan vector matters
Earlier in the campaign, the Iranian retaliation set was understood, in widely circulated analyses, to be aimed primarily at Israeli targets, with any Iraqi or Syrian vector treated as a margin case. The overnight posts shift that picture. AMK Mapping's reference to launches "towards Jordan" is the first widely circulated indicator in this dataset that Amman is now inside the Iranian targeting envelope. Jordan is a US treaty ally, hosts coalition basing, and has previously been struck by Iranian-proxy projectiles during escalations with Israel. Including it in a formal state-on-state missile salvo is qualitatively different from a drone or rocket straying across a border.
The strategic effect of that shift, if confirmed, is to widen the air-defence burden across the region. Jordanian and US Central Command assets that had been positioned primarily to defend Israeli airspace, or to guard the Strait of Hormuz shipping lanes, would face a new requirement: defending a third national airspace from a peer-approximation missile threat. The sources do not specify whether the projectiles reached Jordanian airspace or were intercepted, and they do not name the specific launch sites beyond Isfahan and a separate "northwestern Iran" reference. That is a real limit on what the open record can support at 03:00 UTC on 11 June.
The structural frame, in plain language
Overnight exchanges of this kind are rarely decided in the moment they happen. They are decided in the days before, in the choice of launcher placement, in the diplomatic cover provided to allies, and in the readiness state of the air-defence network. The relevant pattern is one of widening rather than deepening: each cycle of the air campaign has, on the open record, added a layer of geography to the conflict — from Iranian territory to Iraqi airspace, from Iraqi airspace to the Gulf, and now, per Telegram-channel reporting, from Iranian territory to Jordanian airspace.
The two-track nature of the overnight traffic — US strikes on Iran and Iranian launches outward, in the same hour — is consistent with a logic in which neither side is currently operating under a deconfliction channel. Diplomatic intermediaries, where they are active, are working the daylight hours. The strikes and the launches are happening in the window when those channels are thinnest, which is itself a tell.
What remains uncertain
The open-source record is unusually thin on several points that will matter within hours. The Reuters alert does not specify the targets hit, the number of weapons used, or whether the strikes were launched from air or sea platforms. The Telegram-channel reporting does not specify how many missiles were launched, what type they were, or what the outcome of the launches was — successful impact, mid-course interception, or launch failure. The "towards Jordan" claim comes from a single channel's earlier post (01:57 UTC), with the 02:46 UTC cluster reframing the activity more generically as "from Isfahan." Independent satellite or radar confirmation is not present in this dataset.
The sources also do not address Israeli posture for the night. There is no public reporting in the dataset on whether Israeli air-defence systems were activated, whether Israeli aircraft were involved in the US strike package, or whether the Israeli government has made a public statement. The absence of a publicly known Israeli dimension in the open record is itself a fact about the night's reporting rather than about the night's events.
What this dataset does support, and what it does not, is the line between the verifiable and the inferred. The verifiable: the United States struck targets in Iran overnight, and Iranian missile launches took place from at least Isfahan and possibly a second site in the northwest, with one channel's claim of a Jordan vector. The inferred, and not yet corroborated by the sources in hand: that Jordan was actually the target, that the launches reached the kingdom, that the strikes and the launches were deliberately synchronised, or that the night represents a strategic pivot rather than a tactical one. The 24 hours that follow will, in all likelihood, narrow that gap.
Monexus treated the overnight wire alert as the load-bearing confirmation of US action and the Telegram channels as the load-bearing open-source layer on the Iranian side; the two were cross-checked against one another rather than read in isolation, which is the standard the desk applies to any escalation in which a single-source claim could move markets.
Wire provenance
This editorial synthesis draws on the following public wire/social posts:
- http://reut.rs/4v6PKZc
- https://t.me/AMK_Mapping
- https://t.me/rnintel
- https://t.me/AMK_Mapping
- https://t.me/Middle_East_Spectator