Saudi airstrikes hit Houthi positions in al-Jawf and Maarib, monitoring channels report

The Royal Saudi Air Force carried out airstrikes on Houthi positions in Yemen's al-Jawf and Maarib governorates on the morning of 25 July 2026, according to four monitoring channels that relayed the report within minutes of each other. The strike locations sit north of Sana'a, in the same corridor that has hosted repeated Saudi-led operations against the Iranian-aligned movement since the war in Gaza opened a regional front. One of the channels framed the operation as a response to a refinery bombing that preceded it; the others reported the strikes without naming a trigger.

What the cluster establishes is narrow but consistent: Saudi jets hit Houthi territory in the north of the country, the monitoring channels specifically flagged in their early posts that there were no reported strikes on Sana'a or Hudaidah, and one channel linked the operation to a refinery attack whose target it did not name. The harder questions, who was hit, on what scale, and against which named facility, are not fully resolved by the four Telegram items this article is built on. Reporting outside the cluster has identified the refinery as the Aramco facility in Jazan and has carried coalition and Houthi first-party statements; this article's body stays within what the four Telegram posts can support, and the desk note flags the wider public record.

A familiar geography

Al-Jawf is named explicitly in the Telegram posts, along with the location "Jabal al Jurrah" carried by the Middle East Spectator and Geopolitical Watch items. Both are northern sites that fall inside the airspace Riyadh has flown over repeatedly since 2015. Maarib, named by AMK Mapping and the wfwitness feed, sits further south in a governorate that has been one of the most contested pieces of ground in the eight-year war. Striking both governorates in a single morning is an operational tempo signal: the northern corridor, where the Houthis have staged cross-border threats against Saudi territory, is not a sanctuary.

The detail that stands out across the cluster is what the channels did not report striking. Three of the four monitoring posts, including both Middle East Spectator items and the Geopolitical Watch post, state in the same line that there were "no reported strikes on Sana'a or Hudaidah." The fourth and fifth items, AMK Mapping and the wfwitness feed, name Maarib and al-Jawf without the exclusion. The choice to flag both cities' absence, rather than just Sana'a, is the channels' own framing of the operation's limits as of mid-morning UTC.

What the cluster says prompted this

Only the Middle East Spectator post of the four identifies a trigger. That item frames the Saudi operation as a response to "the bombing of a major refinery," without naming the facility or its owner. The other three Telegram items in this cluster do not, in the posts available here, attribute a cause. The cluster is therefore silent on which refinery was hit, who attacked it, and how the attack was delivered. Reporting outside this four-item cluster, carried by Türkiye Today, Daily Pakistan, ABC News, the Palestine Chronicle, and CNBC, identifies the refinery as the Aramco facility in Jazan and frames it as the target of a Houthi missile or drone strike; the Saudi-led coalition's Joint Forces Command and the Houthis' spokesman have publicly addressed the exchange, per Anadolu, the Palestine Chronicle, Al Arabiya, Al Jazeera, the Jerusalem Post and other wires. Those first-party statements sit outside the four Telegram items this article draws on, and the body above does not rely on them; the wider public record is acknowledged here and tracked below in the watch list.

A wider frame, kept narrow

The strikes land inside a regional picture that has hardened since late 2023, when the Houthis widened their target set from Israel-linked shipping to Saudi and Emirati territory as the Gaza war opened a regional front. Saudi Arabia's public posture through 2024 and 2025 has been to remain formally on the diplomatic back foot while continuing to underwrite the Yemeni government's fight against the movement in the country's east and south. A northern Saudi operation of the kind the channels reported on 25 July reads, in Monexus analysis, as the air force running a familiar task: hitting Houthi concentrations in territory the coalition has bombed repeatedly for a decade, framed this time by one of the four channels as a direct response to a strike on Saudi energy infrastructure. The refinery dimension, where the one Middle East Spectator post places it, raises the political cost of restraint, which is the standard Saudi calculus in this war.

Two cautions keep the framing honest. First, this article is built on four Telegram monitoring channels whose reporting converges on location and timing; their statements are relays, not first-party Saudi or Houthi statements, and the certainty of any claim about what was struck and why is correspondingly lower than a coalition or Houthi spokesperson briefing would support. Second, the channel-level framing in this cluster does not by itself settle who struck which refinery; that identification, per the contradiction search, comes from wires and outlets outside the four Telegram items.

What to watch next

Three indicators will tell readers whether this is a one-day exchange or the start of a sharper cycle. First, a Saudi Press Agency statement that puts a name and a number on the strikes, formal confirmation that the four Telegram items relay but do not contain. Second, a Houthi response through spokesman Yahya Saree or the movement's al-Masirah satellite channel, claiming the refinery strike or warning of retaliation; the public record already carries such a response, per Anadolu and the Palestine Chronicle, but a renewed cycle of statements after the morning's exchanges would be the signal to watch. Third, any movement on the UN special envoy's stalled mediation track; strikes in al-Jawf and Maarib do not by themselves break that track, but a refinery strike that prompts them tends to push it further onto the back burner.

For now, the picture is what the four monitoring channels describe: jets over al-Jawf and Maarib, with three of the posts flagging no reported strikes on Sana'a or Hudaidah as of mid-morning UTC, and one channel placing the operation in response to a refinery attack whose target the cluster does not name. The wider pattern, an air force with deep familiarity operating in a war zone it has flown over for a decade, is consistent with everything publicly known about how this conflict runs; the specific refinery target and the coalition-Houthi exchange of statements belong to a wider public record this article does not extend to.

This article is built on four Telegram monitoring channels whose reporting converges on location and timing. The Saudi-led coalition's own statement and the Houthis' response, as well as the identification of the refinery as the Aramco facility in Jazan, are not contained in the four Telegram items; the body of the article stays within what those items can support.

Wire provenance

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

• https://t.me/Middle_East_Spectator/35463
• https://t.me/Middle_East_Spectator/35462
• https://t.me/GeoPWatch/37839
• https://t.me/AMK_Mapping/34607
• https://t.me/wfwitness/104849