Wire
18:06ZWARTRANSLAIt is reported that Russia built the new "Millerovo" drone port within a month to launch "Geran-5" drones. As…18:06ZFARSNEWSINAliyev government arrests dozens protesting anti-hijab law 🔹Reuters reported on Tuesday, citing Azerbaijan’s…18:06ZRNINTELAround 15 minutes ago, alerts were activated in Saudi Arabia's Eastern Province.18:03ZINSIDERPAPVatican says Pope's lung surgery completed successfully18:03ZINTELSLAVASatellite images reveal new drone port built in one month near Millerovo, Rostov region18:03ZSTANDARDKEKenyan marathoner Ronald Korir suspended by Athletics Integrity Unit over alleged doping18:03ZMEHRNEWSRear Admiral Azmaei: Security with neighbors possible despite U.S. presence in Persian Gulf18:02ZFARSNAProtesters confront American sailors at port demanding explanation for civilian deaths
  • S&P 500 ETF▼ 0.15%
  • Nasdaq▼ 0.28%
  • Nasdaq 100▼ 0.56%
  • Dow ETF▼ 0.47%
Terminal ↗
← The MonexusDefense

Sanaa fuel depot hit in reported Saudi-led strike; coalition had warned of evacuation, OSINT footage shows

Smoke rose over the Yemen Petroleum Company's Al-Sabaha Central Station in Sanaa on 13 October 2026 after a strike attributed by OSINT and regional channels to the Saudi-led coalition, hours after that coalition had issued an evacuation warning for the same facility.

Thick smoke rose over the Al-Sabaha district of Sanaa shortly before 14:31 UTC on 13 October 2026, according to footage circulating on OSINT and regional channels, after a strike that those channels attributed to the Saudi-led coalition hit the Yemen Petroleum Company's Central Station. The attribution rests on reporting from open-source monitors and Arabic-language networks, since the cited material does not include a first-party coalition statement confirming responsibility.

The strike landed hours after the Saudi-led coalition had publicly warned of an evacuation order for the Sanaa oil facility, a piece of prior context that recasts the hit as the executed end of a sequence rather than a surprise attack. The Yemen Petroleum Company moved within the hour to dispute the military value of the target and to reassure the public on fuel supply, an effort that signals two audiences at once: investors in the legitimacy of coalition targeting, and ordinary Sanaa residents deciding whether to fill a jerry can tonight. Monexus assessment: the framing fight turns on whether an emptied depot hit under an evacuation notice still counts as a civilian-infrastructure strike, or as a deliberate dual-use operation whose warning was the procedural part of the operation, not a humanitarian gesture.

What actually burned, and the sequence that produced it

The available reporting converges on a single compound in north-central Sanaa, the Al-Sabaha Central Station run by the Yemen Petroleum Company. Footage catalogued by OSINT monitors from 14:31 UTC showed a heavy smoke plume over the depot, with a follow-up item at 14:41 UTC flagging an adjacent missile site in the same general area. The channel-level reporting does not specify whether the two were hit in the same sortie package or in close succession, a sequencing detail that matters for the legal characterisation of the operation.

Inside the company, the instinct was to draw a line between the strike and the fuel supply. A source at the Yemen Oil Company told Al-Alam Arabic that the Al-Sabaha station was "empty of petroleum products" at the time of impact and that "targeting it has no military value." A separate message from the Yemen Petroleum Company, sent minutes later through the same channel, told citizens that supply was "completely stable" and urged the public not to panic. The two statements are calibrated to different audiences: a technical denial of battlefield relevance, and a public confidence line about the downstream fuel market.

Sitting above both is the prior context that the cited reconciliation ledger contains: before the strike, the Saudi-led coalition had issued an evacuation warning for the Sanaa oil facility. The available source items on the strike itself do not reproduce the warning text, but the cited material records that the warning preceded the operation. That sequence, warning then strike, is the procedural shape most coalition operations in this campaign have taken, and it is the basis on which proponents of the strike argue it was a lawful dual-use action with a protective disclosure built around it.

The coalition's framing, and what is missing from it

Proponents of the strike, including coalition spokespeople in past operations, have argued that dual-use petroleum logistics is a legitimate component of Houthi military sustainment, both directly, diesel for vehicles, generators and air-defence support equipment, and indirectly through revenue that flows back to the group's financial apparatus. Under that reading, an evacuation notice is the protective move that distinguishes a lawful target from an unlawful one, and the strike that follows is the execution of a target whose dual-use character the coalition has already put on the public record.

The cited material does not contain a first-party coalition statement taking responsibility for the 13 October 2026 strike or explicitly linking the prior evacuation warning to the strike at Al-Sabaha. That absence is doing real work in the framing. The coalition's prior warning can be read two ways: as a humanitarian disclosure intended to clear the site, or as a notice that converted an operating fuel depot into a targetable one. The strike's appearance in OSINT and regional reporting, not in a coalition press release, leaves the second reading structurally stronger in the cited material than the first.

Monexus analysis: the sequence in the cited material, evacuation warning, then strike on a site the company says was emptied of product, sits awkwardly with the company's "no military value" framing. If the depot was already empty, a coalition evacuation warning would be aimed less at saving product and more at clearing personnel, a move that suggests the coalition was treating the site as a targetable asset rather than as protected civilian storage.

The Yemeni company's counter-reading

The Yemeni company's two statements advance a different structural argument. The first, that the Al-Sabaha station was "empty of petroleum products" at impact, narrows the military-utility claim by collapsing it to the moment of the strike: an empty tank contributes nothing to a war effort at that moment, and so the act of striking it is closer to economic punishment of a population than to battlefield necessity. The second, that the situation is "completely stable," is a market-signalling statement: even with one station gone, the system has slack, and panic at the pumps is the real target.

Neither statement engages the prior evacuation warning directly. Monexus assessment: the absence of a direct rebuttal to the warning is itself informative; the company appears to be treating the warning, the strike, and the supply reassurance as three separate objects, rather than as one connected sequence. That is the standard rhetorical posture of an operator under bombardment, where disputing the military utility of each individual hit is more useful than arguing the legal character of the campaign as a whole.

What remains unverified from the cited material

Verified across the cited sources: a smoke plume over the Al-Sabaha Central Station on 13 October 2026; OSINT and regional attribution of the strike to the Saudi-led coalition; the Yemen Petroleum Company publicly disputing the military value of the target through Al-Alam Arabic; the company's reassurance on supply stability; the existence of a prior coalition evacuation warning for the Sanaa oil facility as recorded in the cited reconciliation ledger.

Still unverified from independent sources within the cited material: which Saudi-led authority specifically ordered the strike, the precise munitions used, the operational sequencing between the depot hit and the adjacent reported missile-site hit, the in-situ fuel inventory at the moment of impact, and whether the coalition has issued a public statement taking responsibility for the 13 October operation and explicitly tying it to the earlier warning. The company source's claim that the station was empty has not been independently corroborated in the cited posts. Two watches remain open: whether the company's stability message holds in fact across Sanaa's distribution network, and whether the coalition's silence on the strike breaks, in either direction, in the next 48 hours.

How Monexus framed this: the wire treats this as a strike on a fuel site; Monexus foregrounds the prior evacuation warning as part of the strike's sequence, labels the coalition attribution as OSINT-and-regional-channel attribution rather than first-party confirmation, and treats the company's "no military value" statement as a counter-reading rather than as a settled fact.

Wire provenance

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

  • https://t.me/alalamarabic/510325
  • https://t.me/alalamarabic/510326
  • https://t.me/osintlive/581256
  • https://t.me/osintlive/581278
  • https://t.me/intelslava/96267

At the source.

Open the posts cited in this article.

Telegram postOpen original ↗

Live content may have changed since this article was published. Loading it contacts Telegram.

Telegram postOpen original ↗

Live content may have changed since this article was published. Loading it contacts Telegram.

Telegram postOpen original ↗

Live content may have changed since this article was published. Loading it contacts Telegram.

© 2026 Monexus Media · AI-native reporting from public-source material
The Monexus

Read with context.

Using this article and its related event records

Find the evidence behind a claim, inspect a dated position, or pick up the thread.

Source lookup is available to everyone. Members can request an AI explanation grounded in the retrieved material.

Browse event files →
Sanaa fuel depot hit in reported Saudi-led strike; coalition had warned of evacuation, OSINT footage shows - The Monexus