Two missiles out of Tabriz: what the open-source feed says, and what it doesn't

At 17:57 UTC on 20 July 2026, the open-source channel AMK Mapping posted a brief, hedged line: "Possible ballistic missile launch from Tabriz, northwestern Iran." Two minutes later, the conflict-monitoring account rnintel reported "at least two missiles detected." By 18:01 UTC, the war-tracking channel wfwitness was already naming a destination: two Iranian ballistic missiles launched from Tabriz toward Jordan. None of the three posts carried imagery, radar data, or an attribution to an Iranian or Jordanian official. They carried something else, equally real: a live, time-stamped record of how the early hours of a Middle Eastern missile incident propagate through the open-source intelligence ecosystem, long before any government has decided what to call it.

The question is not whether something left Tabriz. Three independent open-source channels logged launches within a four-minute window. The question is what the launch was, who ordered it, and why an Iranian trajectory would point at Jordan rather than at Israel, where most recent Iranian missile activity has been directed. On every one of those points, the open feed is silent.

What the three channels actually said

Read closely, the three posts disagree more than they agree. AMK Mapping, the earliest by two minutes, used the word "possible" and gave only a launch location. rnintel, the next to post, gave a count ("at least two") but no destination. wfwitness, the latest, was the only one to assert a direction: toward Jordan.

That escalation of specificity over four minutes is typical of how open-source feeds assemble themselves in real time. A first observer catches the launch plume or the heat signature, files a tentative post; a second, working the same imagery or a complementary sensor feed, confirms the count; a third, drawing on prior incidents or pattern recognition, layers in a likely target. Each step adds confidence. Each step also adds a layer of inference that is not in the underlying observation. wfwitness's "toward Jordan" is, on the available evidence, an inference from trajectory or from prior context. The channel did not cite radar, Iranian statements, or Jordanian confirmation.

Open-source intelligence is genuinely useful here: it compresses the time between an event and a public record of it from hours into minutes, and it does so without waiting on official spokespeople. It is also genuinely fragile at the same moment. The same feeds that catch the first plume are the feeds that will, if the situation escalates, be the ones cited retrospectively as evidence of what "everyone knew" in the first hour. That retrospective weight is not warranted by what the posts actually contain.

Why Tabriz, and why now

Tabriz sits in Iran's East Azerbaijan province, in the northwest of the country, several hundred kilometres from the Persian Gulf coast and from the Iraqi Kurdistan border. It is not the launch site most associated with Iranian missile activity in recent memory; that label belongs to sites in western Iran, closer to Iraq and the Levant, or to underground facilities near the Gulf. A launch from Tabriz, if confirmed, suggests either a mobile launcher moving through the northwest, a test of dispersal tactics that put Iran's ballistic assets further from any single targeted air-defence envelope, or a signal to a specific audience.

The audience question is the one the wires will spend the next 24 hours answering. A trajectory toward Israel from western Iran is the established pattern of the past two years. A trajectory toward Jordan is rarer, and politically loaded in a different direction. Jordan is a US treaty ally, a neighbour of both Israel and Iraq, and host to a substantial refugee population from the Syrian and earlier Iraqi wars. A missile incident directed at Jordanian airspace, even if intercepted or off-course, would draw Washington into the immediate conversation in a way that an Israeli-targeting incident, however serious, no longer does by default. Whether that is the signal Tehran intends, or whether the apparent trajectory is a function of booster staging, target packages, or a test profile, is not in the open-source feed.

The OSINT layer and the official layer

Three layers of information are now racing. At the bottom: the raw sensor data, satellite heat traces, radar returns and eyewitness accounts that the open-source channels are themselves drawing on. In the middle: the channels themselves, each with its own editorial judgement about how much to assert and how fast. At the top: official statements from Tehran, Amman, Washington, and any other capital with a stake in the answer.

The top layer has, as of the time of writing, not arrived. No wire service had reported the launches by the time wfwitness posted its destination line. No Iranian outlet cited in the open-source feed had claimed responsibility or described the launch. No Jordanian or US military spokesperson had acknowledged the incident. That absence is itself part of the story. The OSINT layer functions as a real-time tip line for journalists and analysts; it does not, on its own, substitute for confirmation.

This is the structural problem with reading live OSINT as if it were a wire report. The incentives of the channels reward speed and specificity. The incentives of an official confirmation reward caution and political cover. The two timelines rarely meet in the first hour. Readers who encounter the open-source version first, as many will, will carry it forward as the baseline against which later official statements are judged. That asymmetry of attention is now a permanent feature of how Middle Eastern military incidents enter public record.

What the sources do not say

The three posts do not specify the missile type. They do not give an impact point, an interception result, or a casualty figure. They do not name an Iranian unit, commander, or political authority. They do not record any claim of responsibility from Tehran. They do not record any statement from Amman or Washington. They do not establish whether the trajectory described by wfwitness reflects an intended target, an early-stage booster path, or a pattern-matching inference from prior incidents.

In other words, the open feed establishes that something was launched from Tabriz on the evening of 20 July 2026, and that at least two missiles were involved. Everything else is the work of the next several hours of reporting, much of which will be done by the same channels that posted the first lines, and much of which will be done by outlets that have not yet weighed in.

The stakes if the trajectory holds

If the destination line survives the next round of reporting, the incident would sit inside an already crowded summer of escalation between Tehran and the wider Middle East, with Jordan pulled into a frame it has spent two years trying to avoid. Jordan's airspace has been a working channel for Israeli operations in the past, and an Iranian missile directed at Jordanian territory would complicate that arrangement immediately, regardless of where the warhead was ultimately intended to land.

If the destination line does not survive, the incident still matters, because the open-source record will be cited, screenshotted, and reframed in the days ahead as evidence of how the early hours of an escalation actually looked. The technical question of where the missiles were going will be answered one way. The question of who got to define the first hour of the story may already have been answered another.

This article draws only on three open-source channels active between 17:57 and 18:01 UTC on 20 July 2026. No official statement had been published at the time of filing. Monexus will update as wire confirmation arrives.

Wire provenance

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

• https://t.me/wfwitness
• https://t.me/rnintel
• https://t.me/AMK_Mapping
• https://en.wikipedia.org/wiki/Tabriz