US opens aerial campaign into southern Iran with ATACMS launches from Kuwaiti soil

At 22:14 UTC on 12 July 2026, the Telegram channel Intelslava flagged a possible ATACMS launch from Kuwait toward Iran. Two minutes later, GeoPWatch posted video it said showed ATACMS launches from Kuwait toward Iran. By 22:20 UTC, Intelslava was reporting an ATACMS strike into Iran, corroborated by what it described as a Kuwaiti eyewitness. By 22:32 UTC, the channel RNIntel was calling the operation a "large-scale US aerial campaign against southern Iran ongoing at the moment, including missile launches from Kuwaiti territory." By 22:41 UTC, Intelslava had posted additional launch footage, again from Kuwait, with the same southern Iran heading.

The window is short and the sourcing is narrow, but the picture the OSINT community has assembled in roughly half an hour is unusually coherent: launch tubes on Kuwaiti territory, projectiles on a southern Iran bearing, and the operation continuing rather than tapering. If the early reporting holds, the United States has escalated from the air-and-sea pressure campaign against Iranian nuclear and military infrastructure into a territory-launched ballistic missile strike phase, hosted from a Gulf state that has historically avoided being publicly inside any strike package aimed at Tehran.

What the channels are showing

The four Telegram feeds at the centre of the reporting are Intelslava, RNIntel, GeoPWatch, and the user account @Alsaa_plus_EN, whose launch footage Intelslava reposted. Each has, at different points in the half-hour, used the language of ATACMS, the US Army Tactical Missile System. ATACMS is a 610-millimetre solid-fuel surface-to-surface missile with a range of roughly 300 kilometres in its baseline variants and substantially more in newer block upgrades; it is fired from HIMARS launchers that the US Army and allied forces have operated across the Gulf for years. The implication of consistent ATACMS identification across four independent channels is that the launch tubes are visible on the posted footage and the projectiles are recognisable as ATACMS to operators familiar with the system.

GeoPWatch, which on past nights has paired raw video with corroborating flight-tracker screenshots and infrared satellite passes, was first to publish launch imagery. Intelslava added a Kuwaiti-source confirmation within minutes. RNIntel, which tends to synthesise rather than originate, used the word "campaign" at 22:32 UTC, an editorial signal that the channel's analysts believed the launches were sustained rather than discrete. The pacing is the giveaway: a single retaliatory strike tends to produce one cluster of posts within minutes, then silence. What the channels are documenting is closer to rolling fire.

The Kuwaiti hosting problem

The geographic specificity matters more than the weapon system. Kuwait hosts US Central Forward Operating Locations and has been, since at least the 1990s, one of the quiet pillars of American power projection into the Gulf. But Kuwaiti public opinion has long been uneasy about being visibly inside any operation aimed at Iran. Kuwaiti parliamentary politics has consistently distinguished between allowing US basing on Kuwaiti soil and participating in strikes; the latter has been treated as a red line by successive National Assembly majorities. If the OSINT reporting holds and launches are genuinely coming off Kuwaiti territory, Washington has either secured a level of Kuwaiti acquiescence that has not been publicly disclosed, or is operating in a grey zone that Kuwait will struggle to acknowledge.

There is no Kuwaiti government statement in the open sources reviewed for this article, and no confirmation from the US Department of Defense or Central Command that an aerial campaign is under way. The default assumption among Telegram OSINT analysts is that official acknowledgement will lag the operational reality. The plausible alternative reads: the footage could be older, the projectiles could be defensive intercepts rather than offensive launches, or the geolocation could be wrong. Each of those readings is real, and the absence of any major wire confirmation at the time of writing means the live story remains an OSINT one.

What a "large-scale aerial campaign" actually means

The phrase "aerial campaign" used by RNIntel is doing a lot of work. In US military usage, a campaign implies a planned, sequenced set of strikes with defined targets and an end-state, not a one-off retaliation. Against Iranian nuclear facilities, missile production lines, or Revolutionary Guard Corps command nodes, a campaign implies multiple salvos over hours or days, with Tomahawk land-attack cruise missiles from surface ships and submarines supplementing the land-based ATACMS salvoes. The 22:14 to 22:41 UTC window is consistent with the opening salvos of such a campaign rather than its conclusion.

The structural frame matters here. The United States has spent two decades building a Gulf architecture capable of striking Iran from the air without overflying Iranian airspace for the launch phase: ships in the Gulf of Oman and Arabian Sea, long-range bombers on Diego Garcia or al-Udeid, and land-based fires from Kuwait, Qatar, Bahrain, and the UAE. What the OSINT reporting describes is the land-based leg of that architecture being used in daylight, on the record, with video circulating before any official comment. The pre-2026 norm in US-Iran confrontation was to keep the launch geography ambiguous, with strikes officially unattributed and Tehran left to read the provenance from wreckage analysis. Tonight's reporting suggests that norm has been set aside.

The counter-narrative worth taking seriously is that this is a limited, symbolic demonstration: a salvo calibrated to signal without committing to a broader war, designed to degrade a specific Iranian capability, and intended to be over before sunrise. Iranian retaliation would in that reading be managed through backchannels. The evidence against that reading is the language: "campaign," "ongoing," "more scenes." None of those words belong in a one-shot message.

What the sources do not yet say

Three things remain unverified by anything other than Telegram-channel reporting at the time of publication. First, the target set inside Iran: "southern Iran" is a heading, not a target list. Khuzestan province hosts Iranian missile production, the Bandar Imam Khomeini petrochemical complex, and the bulk of Iranian conventional land forces facing the Gulf. Without corroborating impact geolocation, the target package cannot be reconstructed. Second, the Kuwaiti role: the channels show launches from Kuwaiti territory, but Kuwaiti government silence leaves open whether this was a joint operation with Kuwaiti consent, a unilateral US use of an existing base, or footage of an older event re-circulated under a 12 July timestamp. Third, the casualty and damage picture: no Iranian source, no Reuters or AP field report, no IRNA or Tasnim readout is in the source set reviewed here, and Iranian state media's first instinct on strikes is usually denial followed by controlled acknowledgement hours later.

The reporting here is built entirely on four open-source Telegram feeds and the launch footage they have posted. No major wire service has yet confirmed the campaign, no government has spoken on the record, and the source set does not include satellite imagery from Maxar, Planet, or Sentinel hubs. The pattern across the four channels is consistent, but the OSINT community has been wrong before on launch-attribution, most notably during the 2019 Saudi Aramco strikes when early reporting swung between Yemeni and Iraqi launch origin for almost 48 hours before crater analysis settled the question.

What is clear is the speed. From first possible launch to "campaign, ongoing" in 27 minutes is a reporting cycle that even major wires will struggle to match. By the time this article is read, the picture will have either hardened into a confirmed US strike package against Iranian targets, or complicated into a competing set of claims that the early video showed something else. The next hours will tell. The OSINT reporting has done its job; it has put the question on the wire ahead of any official statement. The burden of confirmation now sits with the governments whose flags are on the rockets.

This piece was assembled from four open-source Telegram channels active between 22:14 and 22:41 UTC on 12 July 2026. Monexus notes that the dominant wire framing of this event is likely to lag the OSINT cycle by several hours and to depend heavily on official US and Kuwaiti readouts that had not been issued at publication time. The framing above treats the OSINT reporting as the operative source until contradicted by primary government statements.

Wire provenance

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

• https://t.me/intelslava
• https://t.me/GeoPWatch
• https://t.me/intelslava
• https://t.me/rnintel
• https://t.me/intelslava
• https://t.me/Alsaa_plus_EN