Yemeni missile strikes hit Saudi Arabia's Jizan as regional war footing deepens

Smoke was still visible over the Saudi city of Jizan at 05:11 UTC on 25 July 2026, more than three hours after Yemeni forces launched a missile attack that set fire to critical infrastructure inside the border governorate. Iran's Mehr News circulated video of the plumes and impact damage, publishing the footage to its Telegram channel at 04:41 UTC with the label "smoke is still rising from this city" (mehrnews.com, via @Mehrnews, 25 July 2026, 05:11 UTC, https://t.me/mehrnews/399553). The same images were amplified by Iran's Tasnim News Agency, which posted footage of fire columns rising from critical facilities in Jizan at 03:54 UTC and again, two minutes earlier, headlined the attack as a "new Yemeni missile attack on Saudi Arabia" with explosions heard across the city (Tasnim News, 25 July 2026, 03:54 UTC, https://t.me/tasnimnews_en/27812 and 03:11 UTC, https://t.me/tasnimnews_en/27808). The independent conflict monitor Rybar's English-language channel (@rnintel) posted what it described as visual confirmation of Ansarullah missile impacts in Jizan at 02:08 UTC (https://t.me/rnintel/64887).

The strikes are the latest in a campaign that has now produced a publicly circulated count of targets spanning both civilian infrastructure and Saudi military sites. Tasnim's English feed, citing "Yemeni sources," reported at 02:27 UTC that "air bases in Saudi Arabia were targeted" (https://t.me/tasnimnews_en/27804), a scope that, if verified, would extend the Jizan attack beyond the urban infrastructure the earlier video frames show burning. The framing of the strikes as predominantly an air-base operation is sourced through Iranian state media and is not independently corroborated in the materials Monexus reviewed for this article.

What the footage shows

The four pieces of verifiable visual evidence reviewed here are consistent on their central claim, that missile impacts produced fire and smoke in Jizan in the early hours of 25 July 2026, but they diverge on framing. Mehr News and Tasnim both publish video of flames and rising smoke, with Tasnim explicitly identifying the burning installations as "critical facilities" (Tasnim, 03:54 UTC, https://t.me/tasnimnews_en/27812). The two Telegram channels draw on the same pool of footage, and the captions are written in the voice of Iranian state media reporting a friendly or allied power's military operation. These sources are useful for confirming that an attack occurred, where, and approximately when. They are not, on their own, a complete account of what was hit, the scale of damage, or whether there were casualties. The available source items do not specify the type of missile, the number of launches, the number of impacts, the names of the specific facilities, or whether Saudi air defences engaged the projectiles.

The structural frame

Read across the last several attacks attributed to Ansarullah (the official name of the Houthi movement), the Jizan strike sits inside a pattern in which Yemeni forces have shifted the centre of gravity of their long-running confrontation with Saudi Arabia southward, away from the capital and toward the kingdom's south-western border region. Jizan, sitting on the Red Sea coast opposite Eritrea, is the closest major Saudi city to the Yemeni theatre and has been an intermittent target for years. Monexus analysis: the reporting density around the 25 July strikes, four separate Iranian and pro-Iran channels publishing within a three-hour window, is itself a form of information operation. It is a reminder that the Gulf missile front is being fought on two planes simultaneously: the physical exchanges of warhead and air defence, and the controlled release of imagery through state-adjacent media that sets the post-strike narrative before Western outlets have time to file.

The Saudi side has not been visible in the chain of source items Monexus reviewed. The cited posts contain no Saudi defence ministry statement, no spokesman comment, and no official casualty or damage assessment, and this article has not independently established whether Riyadh has issued one. The absence is reported narrowly, as a fact about the source material rather than as an inference about Saudi government behaviour.

What the alternative reads leave us with

The most natural reading of the available material is that Yemeni forces struck targets in or near Jizan in the early hours of 25 July 2026, producing fires that were filmed and circulated by Iranian-aligned media. A second plausible reading is that the air-base claim is a separate, adjacent strike that the same Iranian reporting chain has merged into one event for narrative impact. A third, less parsimonious reading, is that the visible fire columns stem from a single incident, that the air-base claim is a confident paraphrase, and that the discrepancy will resolve once Saudi or independent reporting is in the public record. The honest assessment is that the source material is sufficient to confirm the attack and its location, but not sufficient to characterise its military significance. That work belongs to the Saudi side, which now has the floor.

What to watch next

The next forty-eight hours will determine whether the Jizan strike generates a Saudi response in-kind, whether the ceasefire architecture formally extended earlier in the year holds, and whether the air-base claim survives verification. Watch for a Saudi-led coalition briefing, a UN ceasefire mechanism statement, and any disruption to commercial traffic through the southern Red Sea or the Bab el-Mandeb, the corridor where this same conflict has most directly impinged on global shipping before. The trajectory is not ambiguous; the pace is.

Desk note: Monexus covered this strike as a localised military event inside a documented pattern, sourcing the four cited items directly rather than relaying derivative summaries. Saudi-side reporting has not yet entered the public record Monexus reviewed; the gap is flagged, not papered over.

Wire provenance

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

• https://t.me/mehrnews/399553
• https://t.me/tasnimnews_en/27812
• https://t.me/tasnimnews_en/27808
• https://t.me/tasnimnews_en/27804
• https://t.me/rnintel/64887