Significance
12 measured / 12 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 12 events
Connected Situation / Through 2026-09-22
Russian Air and Ground Attacks Across Ukraine and Reciprocal Strikes
- stories
- 13
- events
- 12
- entities
- 51
- connections
- 13
Evidence so far on 2026-09-22 UTC · updated 2026-09-22 05:21 UTC · analysis as of 2026-09-22 02:26 UTCSign in for the live Situation ↗
Narrative
As-of analysis
Situation at a glance
On 2026-09-20, Russia carried out drone strikes across the Kyiv region that killed four civilians, including three children and a woman, as described in “Russian drone attack kills three children and a woman in Kyiv.” [citations omitted] Russian Armed Forces also struck railway infrastructure in Vinnytsia on 2026-09-20, while Ukraine was coded as striking a Russian oil refinery in the event titled “Ukraine strikes Russian oil refinery despite Trump appeal.” On 2026-09-21, Russian Armed Forces struck critical infrastructure in Poltava and a Ukrainian military logistics center, developments covered by “Russian forces strike Ukraine’s logistics hubs, warehouses and ports overnight.” The same date brought coded Russian attacks near Dobropillia against Ukrainian Armed Forces and Russian air-defense interceptions over Kaluga, while “Russia vows harsh retaliation for Ukrainian drone attacks, targeting Kyiv” linked the cross-border activity to a retaliation narrative. “Russian strikes hit apartment buildings and shopping center in Zaporizhzhia” added reported damage and injuries within the wider Ukrainian strike wave.
Footnotes[8][4][12][15][11][13][2][14][16][3][1]Assessment
The strongest supported picture is a geographically broad Russian strike campaign affecting civilian-linked sites, logistics, rail and critical infrastructure in Ukraine, alongside ground fighting near Dobropillia. The Kyiv event provides the clearest civilian toll, while the Vinnytsia rail story reports delays affecting 50 train services; the power-outage account also names bad weather as a contributing factor, so it does not isolate the Russian attack as the sole cause. The reciprocal-strike interpretation is supported by the coded Ukraine-to-Russia refinery event, the unidentified-drone event in Rostov and Russian air-defense interceptions over Kaluga, but the refinery event carries low confidence and the Rostov attacker is unidentified. Vladimir Putin, Volodymyr Zelenskyy and the Armed Forces of the Russian Federation are mentioned in associated Stories, but the supplied entity records do not bind them to the coded Events as participating actors.
Footnotes[8][12][7][1][6][5][15][16][8][11][17][18]Explanation originally captured 2026-09-22 · Evidence through 2026-09-22 UTC · Source edition sed_e121298c24b96b02e4f8a1f28cc32bdc
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 12 coded Events carried across 13 member Stories.
- Coded activity
The coded activity is led by AIR/DRONE STRIKE (9) and ARMED CLASH (1).
- Prominent subjects
🇺🇦Ukraine, 🇷🇺Russia, and 🇵🇱Poland are prominent in the retained actor and relationship evidence.
- Entity coverage
51 canonical Entities are linked to this edition.
Metric coverage. 12 coded Events · 0 CAMEO+ · 12 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.
Magnitude—
Systemic importance—
Propagation potential—
Market sensitivity—
Dot = mean · shaded span = observed range · position uses each metric’s defined scale.
All 4 scores, distributions & definitions
How the coder scored the full retained Event set
12 coded events — 12 conflict
- Significance · 120.31min 0.11max 0.52
- Goldstein · 12-8.7min -10max -2
- Fatalities · 120min 0max 4
- Confidence · 120.81min 0.42max 0.96
Quad class over those 12 events · Material Conflict 11 · Verbal Conflict 1.
Goldstein
12 measured / 12 eligible · 0 missing · 0 not applicable
score (-10 to 10) · Event-level distribution, not a Situation risk score.
across the 12 of 12 events Goldstein is defined on — CAMEO+ POLITICAL and the conflict family; the other nine CAMEO+ domains have no Goldstein semantics
Fatalities
12 measured / 12 eligible · 0 missing · 0 not applicable
reported people · Reports may overlap; these are Event-level reports, not an additive unique human toll.
across the 12 of 12 events that report a toll — the conflict family only, and never 0 on a CAMEO+ event
Confidence
12 measured / 12 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 12 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-22from the recordslatest
Poland issues border alert as fighter jets scramble and defenses activate
1 Story and 0 coded Events (-11 / -7 against the day before). Widest coverage: Poland issues border alert as fighter jets scramble and defenses activate (5 articles).
- 1-11
- Stories · vs day before
- 0-7
- Events · vs day before
- 5
- articles
The lay of the land
Situation timeline
Threads
All 3 daysarticlesstoriesevents
09-2009-2109-22
Loading Situation timeline…
What kind of event · 4 coded types
over 12 coded events on this edition
- Conflict9
- AIR/DRONE STRIKE9
- Conflict2
- DISRUPTED WEAPONS USE1
- OTHER1
- Conflict1
- ARMED CLASH1
Countries · where it happened
Countries · who is acting
Salient structure
What holds this Situation together
Selected from the complete retained edition
Key threads
- core
AnalystRussian air and drone strikes across Ukraine
Russian strikes span Kyiv, Vinnytsia, Poltava and Ukrainian logistics and civilian-linked sites, while the Stories “Russian forces strike Ukraine’s logistics hubs, warehouses and ports overnight” and “Russian strikes hit apartment buildings and shopping center in Zaporizhzhia” connect multiple locations to the same overnight wave.
Russian strikes span Kyiv, Vinnytsia, Poltava and Ukrainian logistics and civilian-linked sites, while the Stories “Russian forces strike Ukraine’s logistics hubs, warehouses and ports overnight” and “Russian strikes hit apartment buildings and shopping center in Zaporizhzhia” connect multiple locations to the same overnight wave.
Footnotes[8][12][11][13][2][1] - development
AnalystCivilian casualties and infrastructure effects
The Kyiv strike killed four civilians, while the rail account reports delays affecting 50 train services and the Zaporizhzhia Story reports damage to apartment buildings and a shopping center.
- development
AnalystCross-border strikes and Russian retaliation claims
Ukraine was coded as striking a Russian oil refinery on 2026-09-20; unidentified drones were coded in Rostov, and Russian air defenses were coded as destroying 13 drones over Kaluga on 2026-09-21. “Russia vows harsh retaliation for Ukrainian drone attacks, targeting Kyiv” presents the associated retaliation claim.
Ukraine was coded as striking a Russian oil refinery on 2026-09-20; unidentified drones were coded in Rostov, and Russian air defenses were coded as destroying 13 drones over Kaluga on 2026-09-21. “Russia vows harsh retaliation for Ukrainian drone attacks, targeting Kyiv” presents the associated retaliation claim.
Footnotes[15][16][3] - development
AnalystRussian attacks near Dobropillia
Russian Armed Forces were coded as intensifying attacks near Dobropillia against Ukrainian Armed Forces on 2026-09-21, covered by “Russian forces intensify glide-bomb attacks near Dobropillia in Donetsk.”
Key actors
Key Events
turning pointAnalystRussia kills four in drone strikes across Kyiv region
Russia was coded as carrying out drone strikes across the Kyiv region on 2026-09-20, with four civilian fatalities; the event is described by “Russian drone attack kills three children and a woman in Kyiv.”
contextAnalystUkraine strikes Russian oil refinery despite Trump appeal
Ukraine was coded as striking a Russian oil refinery on 2026-09-20; the event has confidence 0.42 and no reported fatalities.
Ukraine was coded as striking a Russian oil refinery on 2026-09-20; the event has confidence 0.42 and no reported fatalities.
Footnotes[15]
contextAnalystRussian drones strike railway infrastructure in Vinnytsia region
Russian Armed Forces were coded as striking railway infrastructure in Vinnytsia on 2026-09-20, while “Attack damages Ukrainian rail infrastructure, delaying 50 train services” reports the infrastructure impact.
contextAnalystRussian forces strike critical infrastructure in Poltava
Russian Armed Forces were coded as striking critical infrastructure in Poltava on 2026-09-21, with no reported fatalities.
Russian Armed Forces were coded as striking critical infrastructure in Poltava on 2026-09-21, with no reported fatalities.
Footnotes[11]contextAnalystRussian drones strike Ukrainian military logistics center
Russian Armed Forces were coded as striking a Ukrainian military logistics center in Kyiv Oblast on 2026-09-21, targeting Ukrainian Armed Forces.
Russian Armed Forces were coded as striking a Ukrainian military logistics center in Kyiv Oblast on 2026-09-21, targeting Ukrainian Armed Forces.
Footnotes[13]
Notable connections
Evidenced relationships involving significant participants beyond the central cast.
describes the same overnight Russian strike wave with additional logistics, warehouse and port details · reporting linkAnalystRussian forces strike Ukraine’s logistics hubs, warehouses and ports overnight → Russian drone attack kills three children and a woman in Kyiv
The logistics-hubs Story and the Kyiv-casualty Story are connected as accounts of the same overnight incident.
adds Zaporizhzhia apartment-building and shopping-center damage to the overnight Russian strike-wave account · reporting linkAnalystRussian strikes hit apartment buildings and shopping center in Zaporizhzhia → Russian forces strike Ukraine’s logistics hubs, warehouses and ports overnight
The Zaporizhzhia Story is linked to the logistics-hubs Story as the same incident, with different location and damage details.
is the Kyiv-region strike described by the Kyiv casualty Story · reporting linkAnalystRussia kills four in drone strikes across Kyiv region → Russian drone attack kills three children and a woman in Kyiv
The Kyiv-region Event and “Russian drone attack kills three children and a woman in Kyiv” share the Kyiv location and four civilian fatalities.
is the Poltava critical-infrastructure strike included in the logistics-hubs Story · reporting linkAnalystRussian forces strike critical infrastructure in Poltava → Russian forces strike Ukraine’s logistics hubs, warehouses and ports overnight
The Poltava Event is linked to “Russian forces strike Ukraine’s logistics hubs, warehouses and ports overnight.”
is mentioned in coverage of the Russian strikes · reporting linkAnalystVladimir Putin → Russian forces strike Ukraine’s logistics hubs, warehouses and ports overnight
Vladimir Putin is mentioned in “Russian forces strike Ukraine’s logistics hubs, warehouses and ports overnight,” but his entity record has no supporting Event participation.
How a Situation is put together13 Stories · 12 Events · 13 membership connections · 95 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 51 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.