Significance
13 measured / 13 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 13 events
Connected Situation / Through 2026-10-25
Saudi-Houthi Attacks, Interceptions and Disruption
- stories
- 35
- events
- 13
- entities
- 113
- connections
- 35
Evidence so far on 2026-10-25 UTC · updated 2026-10-25 10:26 UTC · analysis as of 2026-10-24 20:27 UTCSign in for the live Situation ↗
Narrative
As-of analysis
Situation at a glance
On October 22, Houthi forces were coded as striking a Yanbu refinery and causing a fire, while the Saudi-led coalition was coded as intercepting Houthi drones and a ballistic missile; Saudi Arabian air defenses were separately coded as intercepting two Houthi drones. [citations carried in evidence_ids]
Footnotes[12][14][15]Assessment
The coded October 22 conflict Events report zero fatalities, while the October 23 airport headlines give different casualty accounts: “Houthi attack on Saudi Arabia's Dammam airport kills two” reports two deaths, and “Attack on Saudi airport kills Indian national and injures two others” reports one death and two injuries. A separate single-article headline, “Yemeni attacks kill 45 Saudi troops in Saudi Arabia’s Asir and Najran regions,” makes a further casualty claim; the material here does not reconcile these claims or establish that the two airport headlines describe the same incident. The Yanbu Event’s location and title do not align with the Dammam airport headline it supports. The accounts of evacuation, flight cancellations, pilgrim return and political responses are connected to the attacks, but do not establish that each consequence arose from one specific incident. No supplied change record establishes an addition, correction or membership change since the prior explanation.
Footnotes[12][14][15][3][10][9][21][22][23][25][19]Explanation originally captured 2026-10-24 · Evidence through 2026-10-25 UTC · Source edition sed_84dc783fcdd03bbcb53d78f028374808
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
- Scope
A 4-day Situation represented by 13 coded Events carried across 35 member Stories.
- Coded activity
The coded activity is led by DISRUPTED WEAPONS USE (4) and AIR/DRONE STRIKE (3).
- Prominent subjects
Houthis, Air India, and Air France are prominent in the retained actor and relationship evidence.
- Entity coverage
113 canonical Entities are linked to this edition.
Metric coverage. 13 coded Events · 5 CAMEO+ · 8 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.
Magnitude3
min 2max 4
Systemic importance0.16
min 0.1max 0.3
Propagation potential0.35
min 0.26max 0.39
Market sensitivity0.16
min 0.05max 0.6
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
13 coded events — 5 CAMEO+ (3 political) · 8 conflict
- Significance · 130.32min 0.21max 0.59
- Magnitude · 53min 2max 4
- Systemic · 50.16min 0.1max 0.3
- Propagation · 50.35min 0.26max 0.39
- Market · 50.16min 0.05max 0.6
- Goldstein · 11-5.9min -10max 6
- Fatalities · 81min 0max 5
- Confidence · 130.69min 0.37max 0.89
Quad class over those 11 events · Material Conflict 8 · Verbal Conflict 2 · Material Cooperation 1. 2 sit outside POLITICAL, where Goldstein and quad class are undefined. The four CAMEO+ scores are over the 5 CAMEO+ events only; the 8 conflict events have no such column.
Magnitude
5 measured / 5 eligible · 0 missing · 8 not applicable
score (0 to 10) · Event-level distribution, not a Situation risk score.
across the 5 of 13 events coded in the CAMEO+ family; the conflict family has no such column
Systemic
5 measured / 5 eligible · 0 missing · 8 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 5 of 13 events coded in the CAMEO+ family; the conflict family has no such column
Propagation
5 measured / 5 eligible · 0 missing · 8 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 5 of 13 events coded in the CAMEO+ family; the conflict family has no such column
Market
5 measured / 5 eligible · 0 missing · 8 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 5 of 13 events coded in the CAMEO+ family; the conflict family has no such column
Goldstein
11 measured / 11 eligible · 0 missing · 2 not applicable
score (-10 to 10) · Event-level distribution, not a Situation risk score.
across the 11 of 13 events Goldstein is defined on — CAMEO+ POLITICAL and the conflict family; the other nine CAMEO+ domains have no Goldstein semantics
Fatalities
8 measured / 8 eligible · 0 missing · 5 not applicable
reported people · Reports may overlap; these are Event-level reports, not an additive unique human toll.
across the 8 of 13 events that report a toll — the conflict family only, and never 0 on a CAMEO+ event
Confidence
13 measured / 13 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 13 events
This retained edition, independent of graph and page limits. Different dimensions, not a blended risk score; reported tolls may overlap.
Day by day4 reporting days · click a day to open or close it
2026-10-25from the recordslatest
Air India suspends flights to three Saudi cities
9 Stories and 1 coded Event (-7 / -4 against the day before). Widest coverage: Houthis claim attacks on Saudi airports and oil refineries (56 articles). Recorded acting: Air India.
- 9-7
- Stories · vs day before
- 1-4
- Events · vs day before
- 120
- articles
The lay of the land
Situation timeline
Threads
All 4 daysarticlesstoriesevents
10-2210-2310-2410-25
Loading Situation timeline…
What kind of event · 7 coded types
over 13 coded events on this edition
- Conflict4
- AIR/DRONE STRIKE3
- SHELLING/ARTILLERY/MISSILE ATTACK1
- Conflict4
- DISRUPTED WEAPONS USE4
- Political3
- 06 · Engage in Material Cooperation1
- 111 · Criticize or Denounce1
- 1123 · Aggression1
- Infrastructure2
- IN02 · Transport Disruption2
Countries · where it happened
Countries · who is acting
Salient structure
What holds this Situation together
Selected from the complete retained edition
Key threads
- core
AnalystAttacks and air-defense interceptions
This thread brings together the Dammam airport casualty report, the two distinct October 22 interception Events, and the Yanbu refinery Event linked to the airport story; the location mismatch remains unresolved.
- development
AnalystPolitical responses
The UN chief condemned the attacks and urged a political horizon for Yemen; Rashad Mohammed al-Alimi said Houthi attacks would not derail state efforts.
- development
AnalystOperational and travel effects
Stories describe Saudi Aramco evacuating its Dhahran headquarters, IndiGo extending flight cancellations, and India working to repatriate stranded pilgrims; a separate Event codes India’s foreign ministry coordinating pilgrims’ return.
- development
AnalystMarket coverage
“Brent crude jumps 4% to $113, its highest price since May” links market coverage to the attacks, but the headline alone does not establish causation.
Key actors
- H
RuleHouthis
Recorded as target in 1 coded Event, including Yemeni Armed Forces strike Houthi positions at Taiz hotel.
Recorded as target in 1 coded Event, including Yemeni Armed Forces strike Houthi positions at Taiz hotel.
Footnotes[?] - AI
RuleAir India
Recorded as actor in 1 coded Event, including Air India suspends flights to three Saudi cities.
Recorded as actor in 1 coded Event, including Air India suspends flights to three Saudi cities.
Footnotes[?] - AF
RuleAir France
Recorded as actor in 1 coded Event, including Air France extends suspension of flights to Riyadh.
Recorded as actor in 1 coded Event, including Air France extends suspension of flights to Riyadh.
Footnotes[?]
Key Events
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 is titled as a Dammam airport attack.
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[14]contextAnalystSaudi air defenses intercept two Houthi drones headed south
On October 22, Saudi Arabian air defenses were coded as intercepting two Houthi drones headed south.
On October 22, Saudi Arabian air defenses were coded as intercepting two Houthi drones headed south.
Footnotes[15]
contextAnalystIndia’s foreign ministry coordinates stranded pilgrims’ return
On October 22, India’s Ministry of External Affairs was coded as coordinating the return of stranded Indian Umrah pilgrims.
contextAnalystYemen’s Al-Alimi says Houthi attacks will not derail state efforts
On October 22, Rashad Mohammed al-Alimi was coded as criticizing Houthi militia attacks and saying they would not derail state efforts.
Notable connections
Evidenced relationships involving significant participants beyond the central cast.
The Aramco Dhahran headquarters evacuation is linked as a consequence of the Houthi attacks covered by the Dammam story. · reporting linkAnalystHouthi attack on Saudi Arabia's Dammam airport kills two → Saudi Aramco evacuates Dhahran headquarters after Houthi attacks
The connection describes the evacuation as following the attacks; it does not identify a specific attack as its cause.
The stories are linked by a same-day edge concerning flight cancellations and stranded pilgrims; that edge does not by [ · reporting linkAnalystIndiGo extends Riyadh flight cancellations through October 31 amid security concerns → India works to repatriate thousands of Muslim pilgrims stranded in Saudi Arabia
The supplied edge identifies the Stories as same-day coverage; it does not establish causation or participation.
The entity “Houthis” is mentioned in the Dammam airport Story; this is not an actor-participation link. · reporting linkAnalystHouthis → Houthi attack on Saudi Arabia's Dammam airport kills two
The entity is marked as mention-only and has no supporting Events.
The UN chief’s condemnation is linked as a political response to the attacks covered by the Dammam story. · reporting linkAnalystHouthi attack on Saudi Arabia's Dammam airport kills two → UN chief urges a political horizon for Yemen, condemns Houthi attacks on Saudi Arabia
The connection identifies the condemnation as a response to the attacks.
How a Situation is put together35 Stories · 13 Events · 35 membership connections · 340 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 113 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.