GDELT CloudGDELT Cloud
Connected Situation / Through 2026-10-26

Saudi-Houthi Attacks, Interceptions and Disruption

stories
51
events
18
entities
142
connections
51
Retained edition
Evidence so far on 2026-10-26 UTC · updated 2026-10-26 08:23 UTC · analysis as of 2026-10-25 18:26 UTCSign in for the live Situation ↗
Narrative

As-of analysis

Carried forward
Situation at a glance

On October 22, Houthi forces were coded as striking the Yanbu refinery and causing a fire, while the Saudi-led coalition was coded as intercepting Houthi drones and a ballistic missile. On October 23, the headline “Houthi attack on Saudi Arabia's Dammam airport kills two” reported a deadly airport attack, and “Saudi Aramco evacuates Dhahran headquarters after Houthi attacks” reported an evacuation. Also on October 23, Air France extended its suspension of flights to Riyadh, an action coded as transport disruption. On October 24, the Saudi-led coalition was coded as intercepting two Houthi ballistic missiles, while a separate Event coded a Saudi strike in Hodeida that killed five civilians. Headlines including “Houthis claim attacks on airports and oil facilities in Saudi Arabia” attribute further attacks to Houthi claims, while “Threat lifted for Mecca, Jeddah, Taif and Yanbu” reports that a threat was lifted in those places.

Footnotes[16][18][10][12][15][19][13][5][2]
Assessment

The dated Events and linked headlines establish a sequence of reported attacks, interceptions, operational disruption and strikes in Yemen, but they do not make every headline’s claim independently established. In particular, “Houthi attack on Saudi Arabia's Dammam airport kills two” is linked to an Event titled as a Yanbu refinery strike; the different locations leave that connection unresolved. The October 24 Event reports five civilian deaths in Hodeida, and another reports five civilians killed in a Houthi missile launch failure; these are separate reports, not a reconciled or additive toll. The reported threat being lifted is a distinct account from claims of attacks on Saudi airports and oil facilities; the headlines alone do not establish that they describe the same locations or incidents.

Footnotes[10][16][13][14][2][5]

Explanation originally captured 2026-10-25 · Evidence through 2026-10-26 UTC · Source edition sed_6efbbec67061c5264db92b2b716c196b

What informs this explanation
  • Complete retained Story and Event membership
  • Daily reporting and coded-occurrence time steps
  • Event taxonomies, metrics, units, and denominators
  • Canonical Entities and recorded actor/target bindings
  • Typed reporting, membership, and incident edges
  • Changes against the preceding retained edition
  • Permitted macro, public-record, and asset facts only when they were retained with an explicit source and observation date
Quantitative

Evidence in numbers

This retained edition
  • Scope

    A 5-day Situation represented by 18 coded Events carried across 51 member Stories.

  • Coded activity

    The coded activity is led by DISRUPTED WEAPONS USE (5) and AIR/DRONE STRIKE (3).

  • Prominent subjects

    Houthis, Air France, and Air India are prominent in the retained actor and relationship evidence.

  • Entity coverage

    142 canonical Entities are linked to this edition.

Metric coverage. 18 coded Events · 7 CAMEO+ · 11 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.

Magnitude3.1
min 2max 4
7 measured
Systemic importance0.15
min 0.1max 0.3
7 measured
Propagation potential0.32
min 0.25max 0.39
7 measured
Market sensitivity0.14
min 0.05max 0.6
7 measured

Dot = mean · shaded span = observed range · position uses each metric’s defined scale.

All 8 scores, distributions & definitions

How the coder scored the full retained Event set

18 coded events — 7 CAMEO+ (4 political) · 11 conflict

  • Significance · 180.31
    min 0.21max 0.59
  • Magnitude · 73.1
    min 2max 4
  • Systemic · 70.15
    min 0.1max 0.3
  • Propagation · 70.32
    min 0.25max 0.39
  • Market · 70.14
    min 0.05max 0.6
  • Goldstein · 15-6.2
    min -10max 6
  • Fatalities · 111
    min 0max 5
  • Confidence · 180.66
    min 0.3max 0.89

Quad class over those 15 events · Material Conflict 11 · Verbal Conflict 3 · Material Cooperation 1. 3 sit outside POLITICAL, where Goldstein and quad class are undefined. The four CAMEO+ scores are over the 7 CAMEO+ events only; the 11 conflict events have no such column.

Significance

18 measured / 18 eligible · 0 missing · 0 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across all 18 events

Magnitude

7 measured / 7 eligible · 0 missing · 11 not applicable

score (0 to 10) · Event-level distribution, not a Situation risk score.

across the 7 of 18 events coded in the CAMEO+ family; the conflict family has no such column

Systemic

7 measured / 7 eligible · 0 missing · 11 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across the 7 of 18 events coded in the CAMEO+ family; the conflict family has no such column

Propagation

7 measured / 7 eligible · 0 missing · 11 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across the 7 of 18 events coded in the CAMEO+ family; the conflict family has no such column

Market

7 measured / 7 eligible · 0 missing · 11 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across the 7 of 18 events coded in the CAMEO+ family; the conflict family has no such column

Goldstein

15 measured / 15 eligible · 0 missing · 3 not applicable

score (-10 to 10) · Event-level distribution, not a Situation risk score.

across the 15 of 18 events Goldstein is defined on — CAMEO+ POLITICAL and the conflict family; the other nine CAMEO+ domains have no Goldstein semantics

Fatalities

11 measured / 11 eligible · 0 missing · 7 not applicable

reported people · Reports may overlap; these are Event-level reports, not an additive unique human toll.

across the 11 of 18 events that report a toll — the conflict family only, and never 0 on a CAMEO+ event

Confidence

18 measured / 18 eligible · 0 missing · 0 not applicable

score (0 to 1) · Event-level distribution, not a Situation risk score.

across all 18 events

Metric definitions and limitations

This retained edition, independent of graph and page limits. Different dimensions, not a blended risk score; reported tolls may overlap.

Day by day5 reporting days · click a day to open or close it

2026-10-26from the recordslatest

Houthis claim attack on Riyadh airport after flights resume

11 Stories and 0 coded Events (-3 / -6 against the day before). Widest coverage: Houthis claim attack on Riyadh airport after flights resume (52 articles).

Houthis claim attack on Riyadh airport after flights resume
11-3
Stories · vs day before
0-6
Events · vs day before
93
articles
The lay of the land

Situation timeline

Threads
All 5 daysarticlesstoriesevents
10-2210-2310-2410-2510-26
Loading Situation timeline…

What kind of event · 7 coded types

over 18 coded events on this edition

  • Conflict6
    • AIR/DRONE STRIKE3
    • SHELLING/ARTILLERY/MISSILE ATTACK3
  • Conflict5
    • DISRUPTED WEAPONS USE5
  • Political4
    • 111 · Criticize or Denounce2
    • 06 · Engage in Material Cooperation1
    • 1123 · Aggression1
  • Infrastructure3
    • IN02 · Transport Disruption3

Countries · where it happened

Countries · who is acting

Salient structure

What holds this Situation together

Selected from the complete retained edition

Key threads

  1. core
    AnalystAttacks and interceptions

    This thread joins the Yanbu strike and Saudi-led coalition interceptions to the Dammam airport report and October 24 accounts of claimed attacks and threat updates. The airport Story’s link to the Yanbu Event remains unresolved.

    This thread joins the Yanbu strike and Saudi-led coalition interceptions to the Dammam airport report and October 24 accounts of claimed attacks and threat updates. The airport Story’s link to the Yanbu Event remains unresolved.

    Footnotes[16][18][19][10][5][2]
  2. development
    AnalystStrikes in Yemen and reported civilian harm

    The Stories report coalition strikes in Yemen and a strike in Hodeida, while coded Events describe a Taiz strike by Yemeni Armed Forces and civilian deaths in Hodeida and a Houthi missile launch failure. These accounts remain distinct.

    The Stories report coalition strikes in Yemen and a strike in Hodeida, while coded Events describe a Taiz strike by Yemeni Armed Forces and civilian deaths in Hodeida and a Houthi missile launch failure. These accounts remain distinct.

    Footnotes[6][3][9][7][17][13][14]
  3. development
    AnalystOperational and travel effects

    Stories report Aramco’s Dhahran headquarters evacuation, efforts to repatriate stranded pilgrims, and flight disruptions; an Event separately codes Air France’s Riyadh suspension. The supplied connections frame several travel and operational effects as consequences of the attacks.

    Stories report Aramco’s Dhahran headquarters evacuation, efforts to repatriate stranded pilgrims, and flight disruptions; an Event separately codes Air France’s Riyadh suspension. The supplied connections frame several travel and operational effects as consequences of the attacks.

    Footnotes[12][11][8][15][26][27][28]

Key actors

  1. H
    AnalystHouthis

    The Houthis are the target of the coded Yemeni Armed Forces strike at a Taiz hotel.

    The Houthis are the target of the coded Yemeni Armed Forces strike at a Taiz hotel.

    Footnotes[21][17]
  2. AF
    AnalystAir France

    Air France is the actor in the Event coding an extended suspension of flights to Riyadh.

    Air France is the actor in the Event coding an extended suspension of flights to Riyadh.

    Footnotes[22][15]

Key Events

  1. contextAnalystHouthi forces strike Yanbu refinery, causing a fire

    On October 22, Houthi forces were coded as striking the Yanbu refinery and causing a fire; the linked Story headline instead names an attack on Dammam airport.

    On October 22, Houthi forces were coded as striking the Yanbu refinery and causing a fire; the linked Story headline instead names an attack on Dammam airport.

    Footnotes[16][10]
  2. contextAnalystSaudi-led coalition intercepts Houthi drones and ballistic missile

    On October 22, the Saudi-led coalition was coded as intercepting Houthi drones and a ballistic missile.

    On October 22, the Saudi-led coalition was coded as intercepting Houthi drones and a ballistic missile.

    Footnotes[18]
  3. contextAnalystAir France extends suspension of flights to Riyadh

    On October 23, Air France was coded as extending its suspension of flights to Riyadh.

    On October 23, Air France was coded as extending its suspension of flights to Riyadh.

    Footnotes[15][8]
  4. contextAnalystYemeni Armed Forces strike Houthi positions at Taiz hotel

    On October 23, Yemeni Armed Forces were coded as striking Houthi positions at a Taiz hotel; the Event reports zero fatalities.

    On October 23, Yemeni Armed Forces were coded as striking Houthi positions at a Taiz hotel; the Event reports zero fatalities.

    Footnotes[17][7]
  5. contextAnalystSaudi-led coalition intercepts two Houthi ballistic missiles

    On October 24, the Saudi-led coalition was coded as intercepting two Houthi ballistic missiles.

    On October 24, the Saudi-led coalition was coded as intercepting two Houthi ballistic missiles.

    Footnotes[19]

Notable connections

Evidenced relationships involving significant participants beyond the central cast.

  1. The Dammam airport Story is linked to an Event titled as a Yanbu refinery strike, but the different locations leave… · reporting linkAnalystHouthi attack on Saudi Arabia's Dammam airport kills two → Houthi forces strike Yanbu refinery, causing a fire

    The Story and Event are linked, but their titles name different locations.

    The Story and Event are linked, but their titles name different locations.

    Footnotes[10][16]
  2. The Houthis are the target of the Yemeni Armed Forces strike at the Taiz hotel. · recorded participationAnalystHouthis → Yemeni Armed Forces strike Houthi positions at Taiz hotel

    The Event binds the Houthis as its target.

    The Event binds the Houthis as its target.

    Footnotes[21][17]
  3. Air France is the actor extending its suspension of flights to Riyadh. · recorded participationAnalystAir France → Air France extends suspension of flights to Riyadh

    The Event binds Air France as its actor.

    The Event binds Air France as its actor.

    Footnotes[22][15]

Current related Situations

Explore all →

Finding connected developments…

Compared with currently maintained Situation membership; this list is not part of the retained edition above.

How a Situation is put together51 Stories · 18 Events · 51 membership connections · 586 graph edges

A retained time step

This edition freezes the complete served membership and analysis available through its UTC cutoff. Later repairs or identity changes do not rewrite what this edition showed.

Stories, Events, and cast

Stories are reporting clusters. Events are coded occurrences within that reporting. The cast contains 142 canonical people and organizations linked to the retained evidence.

Typed connections

Story-to-Event edges identify supporting reporting. Entity-to-Event edges identify recorded actor or target participation. Mentions and analytical roles stay visibly distinct from recorded participation.

Core, precursor, and continuation labels organize the reading. They do not by themselves establish causation. Collapsed graph groups and paginated evidence change presentation only; counts use the complete retained edition.