Iran fires ballistic missiles toward Jordan and US targets in overnight barrage
Two waves of launches from western Iran struck targets in Jordan and at US positions across the region in the early hours of 13 July 2026, with Tehran framing the operation as retaliation.
At 00:58 UTC on 13 July 2026, the open-source monitoring account GeoPWatch posted a short alert: possible missile launches from Iran. Within five minutes, two of the most-followed channels tracking the Middle East, Middle East Spectator and War Footage Witness, had moved from possibility to confirmation, with both flagging ballistic missile launches from Iranian territory and Middle East Spectator adding a fresh bulletin on explosions in Jordan. By 01:46 UTC, Iranian state television PressTV was on air describing what it called a fresh wave of retaliatory strikes against US targets across the region.
The overnight barrage sits inside an escalation arc that has been visible on the same wire of Telegram channels for months. What makes this morning different is the simultaneity: two distinct waves from the same launch belt in western Iran, each with public framing on multiple sides, and a target set that crosses a frontline state hosting US forces. The reporting below is built only from the channels that posted in real time. It is provisional by definition: missile events of this kind take hours, sometimes days, to verify against radar, satellite, and government confirmation.
The shape of the night
The first item in the thread is the briefest possible: a six-word report of "possible missile launches from iran" at 00:58 UTC, posted by GeoPWatch. Five minutes later, Middle East Spectator and War Footage Witness ran identical phrasings of a "breaking" alert on ballistic missile launches from Iran. At 01:05 UTC, Middle East Spectator updated with a second bulletin: "NEW: Explosions in Jordan," appended to the Iran bulletin in the same post. War Footage Witness, at 01:06 UTC, hedged further: the launches were "possibly targeting Jordan."
By 01:14 UTC the geographic origin had narrowed. The OSINT-focused AMK Mapping account reported "repeated ballistic missile launches from Khomeyn, western Iran." Khomeyn, the city in Markazi province named after the late Ayatollah Ruhollah Khomeini, is roughly 150 kilometres southwest of Tehran and sits inside a launch belt that analysts have flagged for years as a hardened missile operating area. OSINTdefender, one of the most-cited independent trackers on Telegram and X, retweeted the initial reports of ballistic missile launches from Iran at 01:31 UTC, lending the early accounts a second layer of independent verification.
Tehran's framing
PressTV, the Iranian state's English-language broadcaster, framed the operation explicitly as retaliation. Its 01:05 UTC post carried the headline "Reports of Iran missile strikes against US targets," and a follow-up at 01:46 UTC escalated that to "Iran carries out fresh retaliatory missile strikes against US targets in region."
Two things are worth noting about the framing. First, the word "retaliatory" is doing causal work: it asserts that an Iranian strike was provoked by an earlier act, and asks the reader to take that on faith. Second, the targets PressTV names are US positions, not Jordanian ones, even though the channel's peer accounts on the same wire were reporting explosions inside Jordan at almost the same minute. That divergence is not a contradiction so much as a deliberate choice of emphasis: Tehran wants the strike read as a message to Washington, not as an attack on a neighbour.
What the OSINT layer can and cannot tell us
The thread's evidence is overwhelmingly Telegram-shaped. Of nine items, six are channel alerts, two are PressTV bulletins, and one is a retweet of an OSINTdefender X post. None of the items in the thread comes from a wire service or an official government statement.
That matters. Telegram channels, including serious OSINT operations like AMK Mapping and OSINTdefender, move first, often ahead of governments, and they are right more often than the critics of social-media-sourced war reporting give them credit for. But they are not the same thing as corroborated fact. Each of the four claims that anchor this story, Iranian origin, ballistic missile type, Jordan as a target, US forces as a target, is currently attested by one or two channel posts, not by an Israeli, American, or Jordanian government statement, and not by a recognised wire service.
The judgment this publication reaches is provisional. The most defensible read of the available record is that two waves of ballistic missile launches occurred from the Khomeyn area in western Iran in the first ninety minutes of 13 July 2026, that explosions were reported inside Jordan during the same window, and that Iranian state media has publicly described the operation as a strike against US targets. The targets struck, the intercept rate, the casualty count, and the identity of the precipitating act Iran cites as justification are not in this thread and should not be asserted here.
What to watch next
Three pieces of evidence will turn provisional reporting into a settled account. First, an Israeli or US confirmation of the launch origin via radar or satellite imagery, ideally backed by a published flight-track. Second, a Jordanian government statement on whether the explosions were inside its territory, on military or civilian sites, and at what casualty cost. Third, a named Iranian official, defence minister, IRGC spokesperson, or foreign ministry, putting a public label on the operation beyond PressTV's "retaliatory."
None of those three confirmations had appeared in the open-source thread as of 01:46 UTC on 13 July. They are likely to surface in the next twelve to twenty-four hours, and they will reshape the framing of this morning's events decisively. For now, the prudent reading is that Iran has conducted a publicly claimed missile operation across at least one border, that the target set appears to include US positions in the region, and that the next moves will come from Washington, Amman, and Tel Aviv before they come from Tehran.
Monexus framed this story strictly from the open-source thread supplied to the desk, treating Telegram channels as primary reporting and PressTV as Iranian state media. No wire-service URLs were available for citation at the time of writing; the source list reflects that constraint rather than padding the ledger.
Wire provenance
This editorial synthesis draws on the following public wire/social posts:
- https://t.me/GeoPWatch
- https://t.me/Middle_East_Spectator
- https://t.me/wfwitness
- https://t.me/Middle_East_Spectator
- https://t.me/presstv
- https://t.me/wfwitness
- https://t.me/AMK_Mapping
- https://t.me/osintlive
- https://t.me/presstv