Significance
29 measured / 29 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 29 events
Connected Situation / Through 2026-09-17
Russian Strikes in Ukraine and Related Security Measures
- stories
- 53
- events
- 29
- entities
- 233
- connections
- 53
Frozen through 2026-09-17 UTC · published 2026-09-18 00:28 UTC · analysis as of 2026-09-17 18:30 UTCSign in for the live Situation ↗
Narrative
As-of analysis
Situation at a glance
The Situation concerns reported Russian strikes in several Ukrainian locations, including civilian, transport and industrial or energy impacts, together with Ukrainian protection and aid requests and related Polish security measures.
Footnotes[1][5][8][4][6][3][13][14]Assessment
The retained evidence links reports of strikes in Ukraine with Ukrainian protection and assistance measures and Polish security actions. It does not establish that every reported incident belongs to one independently verified attack.
Footnotes[5][6][3][2][16][15][17][13]Explanation originally captured 2026-09-17 · Evidence through 2026-09-17 UTC · Source edition sed_98a2de3f5e263fa2edbeace8b33478ac
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 3-day Situation represented by 29 coded Events carried across 53 member Stories.
- Coded activity
The coded activity is led by AIR/DRONE STRIKE (7) and SHELLING/ARTILLERY/MISSILE ATTACK (4).
- Prominent subjects
Volodymyr Zelenskyy, Władysław Kosiniak-Kamysz, and Ukrainian Railways are prominent in the retained actor and relationship evidence.
- Entity coverage
233 canonical Entities are linked to this edition.
Metric coverage. 29 coded Events · 12 CAMEO+ · 17 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.
Magnitude4.2
min 2max 7
Systemic importance0.28
min 0.1max 0.67
Propagation potential0.41
min 0.24max 0.56
Market sensitivity0.11
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
29 coded events — 12 CAMEO+ (11 political) · 17 conflict
- Significance · 290.33min 0.08max 0.56
- Magnitude · 124.2min 2max 7
- Systemic · 120.28min 0.1max 0.67
- Propagation · 120.41min 0.24max 0.56
- Market · 120.11min 0.05max 0.6
- Goldstein · 28-5.5min -10max 3
- Fatalities · 170min 0max 5
- Confidence · 290.73min 0.35max 0.91
Quad class over those 28 events · Material Conflict 17 · Verbal Conflict 6 · Verbal Cooperation 5. 1 sit outside POLITICAL, where Goldstein and quad class are undefined. The four CAMEO+ scores are over the 12 CAMEO+ events only; the 17 conflict events have no such column.
Magnitude
12 measured / 12 eligible · 0 missing · 17 not applicable
score (0 to 10) · Event-level distribution, not a Situation risk score.
across the 12 of 29 events coded in the CAMEO+ family; the conflict family has no such column
Systemic
12 measured / 12 eligible · 0 missing · 17 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 12 of 29 events coded in the CAMEO+ family; the conflict family has no such column
Propagation
12 measured / 12 eligible · 0 missing · 17 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 12 of 29 events coded in the CAMEO+ family; the conflict family has no such column
Market
12 measured / 12 eligible · 0 missing · 17 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across the 12 of 29 events coded in the CAMEO+ family; the conflict family has no such column
Goldstein
28 measured / 28 eligible · 0 missing · 1 not applicable
score (-10 to 10) · Event-level distribution, not a Situation risk score.
across the 28 of 29 events Goldstein is defined on — CAMEO+ POLITICAL and the conflict family; the other nine CAMEO+ domains have no Goldstein semantics
Fatalities
17 measured / 17 eligible · 0 missing · 12 not applicable
reported people · Reports may overlap; these are Event-level reports, not an additive unique human toll.
across the 17 of 29 events that report a toll — the conflict family only, and never 0 on a CAMEO+ event
Confidence
29 measured / 29 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 29 events
This retained edition, independent of graph and page limits. Different dimensions, not a blended risk score; reported tolls may overlap.
Day by day3 reporting days · click a day to open or close it
2026-09-17from the recordslatest
Poland issues air-raid alert after drone nears border
31 Stories and 15 coded Events (+9 / +7 against the day before). Widest coverage: Ballistic attack hits Kyiv, damaging civilian sites and injuring four (114 articles). Recorded acting: Radosław Sikorski, NATO, Security Service of Ukraine, Polish Armed Forces.
- 31+9
- Stories · vs day before
- 15+7
- Events · vs day before
- 426
- articles
The lay of the land
Situation timeline
Threads
All 3 daysarticlesstoriesevents
09-1509-1609-17
Loading Situation timeline…
What kind of event · 17 coded types
over 29 coded events on this edition
- Conflict11
- AIR/DRONE STRIKE7
- SHELLING/ARTILLERY/MISSILE ATTACK4
- Political11
- 111 · Criticize or Denounce2
- 01 · Make Public Statement1
- 0212 · Military1
- 0214 · Intelligence1
- 023 · Appeal for Aid1
Countries · where it happened
Countries · who is acting
Salient structure
What holds this Situation together
Selected from the complete retained edition
Key threads
- core
AnalystUkraine strike impacts
This is the core thread because it joins reports and coded records of strikes affecting civilians, industrial and energy facilities, transport, Kyiv and Odesa sites, and other Ukrainian locations.
- development
AnalystUkrainian rail protection and aid
This thread records Zelenskyy’s review of railway and fuel-station protection needs and Ukraine’s appeal to allies after attacks were reported to deplete its locomotive fleet.
- development
AnalystCross-border security measures
This thread groups Polish border, observation-post, fighter and airport security reporting associated with the retained evidence; these links do not by themselves establish a single underlying incident.
Key actors
- VZ
- WK
AnalystWładysław Kosiniak-Kamysz
Władysław Kosiniak-Kamysz is recorded as the source actor for announcing reinforced border guard activity along the Ukraine frontier.
- UR
- PA
AnalystPolish Armed Forces
The Polish Armed Forces are recorded as the source actor for scrambling fighter jets over Poland; a related coded record names the Polish Army as the source actor for building observation posts.
Key Events
contextAnalystRussian forces kill one and injure five in Kherson strikes
The coded record attributes a Kherson strike to Russian Armed Forces and records one fatality and five injuries among civilians.
The coded record attributes a Kherson strike to Russian Armed Forces and records one fatality and five injuries among civilians.
Footnotes[13]
contextAnalystRussia strikes industrial and energy facilities in Poltava region
The coded record describes a Russian air or drone strike on industrial and energy facilities in the Poltava region.
The coded record describes a Russian air or drone strike on industrial and energy facilities in the Poltava region.
Footnotes[14]
contextAnalystUkraine seeks allied help as attacks deplete locomotive fleet
The coded record describes Ukraine seeking allied help after attacks reportedly depleted its locomotive fleet.
The coded record describes Ukraine seeking allied help after attacks reportedly depleted its locomotive fleet.
Footnotes[15]
contextAnalystKosiniak-Kamysz announces reinforced border guard along Ukraine frontier
The coded record describes Władysław Kosiniak-Kamysz announcing reinforced border guard activity along the Ukraine frontier.
The coded record describes Władysław Kosiniak-Kamysz announcing reinforced border guard activity along the Ukraine frontier.
Footnotes[12]contextAnalystPolish Army builds observation posts after Russian attacks
The coded record describes the Polish Army building observation posts after Russian attacks.
The coded record describes the Polish Army building observation posts after Russian attacks.
Footnotes[17]
Notable connections
Evidenced relationships involving significant participants beyond the central cast.
supports the coded consultation about railway and fuel-station protection needs · reporting linkAnalystRussia strikes passenger train near Polish border, diplomats endangered → Zelenskyy reviews railway and fuel station protection needs
The event is linked to the story reporting the passenger-train attack and related railway protection decisions.
supports the coded appeal for allied locomotive assistance · reporting linkAnalystRussia strikes passenger train near Polish border, diplomats endangered → Ukraine seeks allied help as attacks deplete locomotive fleet
The event is linked to the story reporting attacks on passenger trains and Ukraine’s request for locomotive support.
has Volodymyr Zelenskyy as source actor · recorded participationAnalystZelenskyy reviews railway and fuel station protection needs → Volodymyr Zelenskyy
The event record binds Volodymyr Zelenskyy to the source-actor field.
has Ukrainian Railways as target actor · recorded participationAnalystZelenskyy reviews railway and fuel station protection needs → Ukrainian Railways
The event record binds Ukrainian Railways to the target-actor field.
mentions the Ministry of National Defence (Poland) in reporting about border reinforcement · reporting linkAnalystPoland reinforces Ukraine border after Russian drone strikes → Ministry of National Defence (Poland)
The entity is a mention-only contextual connection in the story and is not recorded as an event participant.
How a Situation is put together53 Stories · 29 Events · 53 membership connections · 564 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 233 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.