Iran fires ballistic missiles from Tabriz toward Jordan, sirens in Amman

At approximately 18:07 UTC on 20 July 2026, at least two ballistic missiles were launched from Tabriz in northwestern Iran, according to multiple open-source intelligence channels monitoring the launch. Sirens sounded in Amman as the projectiles tracked across Jordanian airspace, and interception attempts were reported over the kingdom within minutes of the launch.

The trajectory matters. A launch from Tabriz toward Jordan is not a strike on Israel by the most direct route. It is a flight path that runs along, then over, Jordanian territory before any further leg, and one that puts a US-allied Arab monarchy directly inside the missile envelope of an Iran-Israel exchange. The reporting window is narrow: launch reports from Tabriz began appearing in real-time intelligence feeds at 18:07 UTC, and corroborating launch footage from the Urmia area, further west, was circulating within the hour.

What the open-source picture shows

Three independent Telegram channels dedicated to tracking Middle East air activity reported the Tabriz launch within the same hour. RN Intel, an OSINT feed, logged the launch first at 18:07 UTC and counted "at least two missiles detected" heading toward Jordan. Within minutes, the @wfwitness channel posted footage described as showing ballistic projectiles over Urmia, and the @abualiexpress feed confirmed launches from Tabriz and reported interception attempts underway in Jordanian airspace. A follow-up bulletin from @englishabuali roughly an hour later added that sirens had been activated inside Jordan and that multiple launches had been observed.

The pattern across the four feeds is consistent on the basic facts: origin Tabriz, direction toward Jordan, multiple projectiles, sirens in Amman, and ongoing interception activity. The number of missiles launched, the identities of any impact points, and the outcome of the interception attempts were not specified in the available reporting.

Why Tabriz, and why Jordan

Tabriz sits in East Azerbaijan province in northwestern Iran, hundreds of kilometres from Iran's western missile garrisons along the Iraq border. A launch from Tabriz toward Jordan is unusual on its face: the standard Iranian ballistic-missile axis toward Israel runs west, through Kermanshah or western Kurdistan, not northwest. Two readings are plausible, and the open-source record does not yet let a desk distinguish cleanly between them.

The first reading is operational. A Tabriz launch toward Jordan puts Iranian missiles on a flight path that crosses over a US-allied Arab state before any further transit, a posture that compresses Jordan's decision time and forces the kingdom's air defence network into the engagement. If the intent was to strike Israel, the launch axis is inefficient. If the intent was to force a Jordanian interception and a regional airspace crisis, it is pointedly efficient. The second reading is deception: a Tabriz-origin launch may have been designed to be mis-attributed, or to seed confusion inside early-warning systems, with the actual terminal trajectory still undetermined in the open-source record.

The escalation warning sitting underneath

Roughly forty minutes before the Tabriz launch, the Middle East Spectator feed carried an Israeli warning that Israel was "preparing for an imminent escalation with Iran." The phrasing of that warning, and the timing relative to the Tabriz launch, frame the Jordan-bound missiles either as the first operational move of that escalation, or as a probing action meant to test reaction time before the main exchange. Both readings are consistent with the public reporting; neither has been confirmed by an Israeli, Iranian, or Jordanian official statement in the materials available to this publication.

What is confirmed is the sequence. Warning of imminent escalation, then launch from Tabriz, then sirens in Amman. The causal arrow between the two is not established. The temporal proximity is.

Stakes and the contested record

If the missiles were headed for Israel and were intercepted or fell short inside Jordan, the immediate consequence is a kinetic expansion of the Iran-Israel front into a third country's airspace, with Jordan now formally inside the engagement envelope and the kingdom's US-supplied air-defence systems publicly tested. If the missiles were intended as a signal to Amman rather than Tel Aviv, the consequence is a calibrated escalation designed to extract a political price without crossing the Israeli nuclear threshold. Either outcome reshapes the regional air-defence geometry for the next round.

What remains contested or uncorroborated: the exact number of missiles launched, the point of impact or intercept, the Israeli response posture, and any Iranian official statement on the launch. The open-source channels that reported the launch are not state actors, and the footage from Urmia and Amman has not yet been independently geolocated by established wire reporting in the materials available to this publication. The reporting here treats the launch itself as established on the strength of four concurring feeds, and treats trajectory, intent, and outcome as open.

The next watch points are narrow. An Israeli strike-package launch would be visible in the same OSINT feeds inside twenty minutes. An Iranian official statement from the IRGC or Foreign Ministry would reset the political framing. A Jordanian government statement would clarify whether the kingdom is treating the launches as a hostile act or as overflight without hostile intent. None of those statements had been posted to the feeds available at the time of writing.

Desk note: Monexus has treated the four concurring OSINT feeds as sufficient to establish the launch itself, and has declined to attribute trajectory or intent beyond what the feeds state explicitly. Where wire reporting later specifies outcome, that reporting will update the picture; the open-source record on its own does not yet close the loop.

Wire provenance

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

• https://t.me/Middle_East_Spectator
• https://t.me/englishabuali
• https://t.me/abualiexpress
• https://t.me/rnintel
• https://t.me/wfwitness