GDELT CloudGDELT Cloud
Connected Situation / Through 2026-09-22

Russian air and drone strikes across Ukraine

stories
29
events
15
entities
115
connections
29
Retained edition
Evidence so far on 2026-09-22 UTC · updated 2026-09-22 20:23 UTC · analysis as of 2026-09-22 02:29 UTCSign in for the live Situation ↗
Narrative

As-of analysis

Carried forward
Situation at a glance

Russia carried out drone strikes across Kyiv region on 2026-09-20, killing four people, in “Russian forces strike Ukraine’s logistics hubs, warehouses and ports overnight.” Russian Armed Forces struck an Eco Market warehouse in Zhytomyr region on 2026-09-20, identifying civilians as the target and reporting no fatalities. Russian drones also struck railway infrastructure in Vinnytsia region on 2026-09-20. On 2026-09-21, Russian Armed Forces struck critical infrastructure in Poltava, a Ukrainian military logistics center in Kyiv Oblast, and an enterprise in Kropyvnytskyi district, where one person was injured. The same day, “Russian strikes hit apartment buildings and shopping center in Zaporizhzhia” and “Russia strikes educational facilities and shopping centers in Zaporizhzhia” described civilian-area damage, while “Attack damages Ukrainian rail infrastructure, delaying 50 train services” described disruption to rail services.

Footnotes[7][2][8][11][10][12][9][1][6][3]
Assessment

The coded Events and linked Stories describe Russian air-and-drone strikes affecting civilians, infrastructure, and Ukrainian military or state-force targets across Ukraine. Same-day links connect the logistics Story with the rail-disruption and Zaporizhzhia civilian-damage Stories. The six coded Events identify Russia or Russian Armed Forces as the source actor. The material includes reported deaths, an injury, rail delays, and strikes on infrastructure and logistics sites; the same-day Stories are not all separate coded Events. The targeting classifications are not uniform: the Zhytomyr warehouse Event marks civilian targeting true, while the Kropyvnytskyi enterprise Event names civilians as the target but marks civilian targeting false.

Footnotes[17][20][22][23][24][8][9]

Explanation originally captured 2026-09-22 · Evidence through 2026-09-22 UTC · Source edition sed_baadb2ffb34d39f9416a0a8221152c93

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 3-day Situation represented by 15 coded Events carried across 29 member Stories.

  • Coded activity

    The coded activity is led by AIR/DRONE STRIKE (9) and SHELLING/ARTILLERY/MISSILE ATTACK (2).

  • Prominent subjects

    Donald Trump is prominent in the retained actor and relationship evidence.

  • Entity coverage

    115 canonical Entities are linked to this edition.

Metric coverage. 15 coded Events · 3 CAMEO+ · 12 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.

Magnitude3
min 2max 4
2 measured
Systemic importance0.34
min 0.28max 0.4
2 measured
Propagation potential0.48
min 0.44max 0.52
2 measured
Market sensitivity0.22
min 0.05max 0.38
2 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

15 coded events — 3 CAMEO+ (1 political) · 12 conflict

  • Significance · 150.31
    min 0.11max 0.52
  • Magnitude · 23
    min 2max 4
  • Systemic · 20.34
    min 0.28max 0.4
  • Propagation · 20.48
    min 0.44max 0.52
  • Market · 20.22
    min 0.05max 0.38
  • Goldstein · 13-8
    min -10max 3
  • Fatalities · 120
    min 0max 4
  • Confidence · 150.77
    min 0.38max 0.98

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

Significance

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

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

across all 15 events

Magnitude

2 measured / 3 eligible · 1 missing · 12 not applicable

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

across the 3 of 15 events coded in the CAMEO+ family; the conflict family has no such column

Systemic

2 measured / 3 eligible · 1 missing · 12 not applicable

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

across the 3 of 15 events coded in the CAMEO+ family; the conflict family has no such column

Propagation

2 measured / 3 eligible · 1 missing · 12 not applicable

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

across the 3 of 15 events coded in the CAMEO+ family; the conflict family has no such column

Market

2 measured / 3 eligible · 1 missing · 12 not applicable

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

across the 3 of 15 events coded in the CAMEO+ family; the conflict family has no such column

Goldstein

13 measured / 13 eligible · 0 missing · 2 not applicable

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

across the 13 of 15 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 · 3 not applicable

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

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

Confidence

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

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

across all 15 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 day3 reporting days · click a day to open or close it

2026-09-22from the recordslatest

Chernihivoblenergo reports power outage affecting 100,000 subscribers

23 Stories and 7 coded Events (+17 / +2 against the day before). Widest coverage: Russian strikes hit industrial sites in Dnipro, Kryvyi Rih and Pavlohrad (68 articles).

Chernihivoblenergo reports power outage affecting 100,000 subscribersRussian strikes hit industrial sites in Dnipro, Kryvyi Rih and Pavlohrad
23+17
Stories · vs day before
7+2
Events · vs day before
269
articles
The lay of the land

Situation timeline

Threads
All 3 daysarticlesstoriesevents
09-2009-2109-22
Loading Situation timeline…

What kind of event · 6 coded types

over 15 coded events on this edition

  • Conflict11
    • AIR/DRONE STRIKE9
    • SHELLING/ARTILLERY/MISSILE ATTACK2
  • CAMEO+1
    • CAMEO+1
  • Conflict1
    • OTHER1
  • Infrastructure1
    • IN01 · Energy Infrastructure Event1
  • Political1
    • 027 · Appeal to Settle Dispute1

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
    AnalystRussian air and drone strikes across Ukrainian locations

    Russia or Russian Armed Forces are identified as the source actor in the Kyiv-region, Zhytomyr, Vinnytsia, Poltava, Kyiv-Oblast and Kropyvnytskyi Events.

    Russia or Russian Armed Forces are identified as the source actor in the Kyiv-region, Zhytomyr, Vinnytsia, Poltava, Kyiv-Oblast and Kropyvnytskyi Events.

    Footnotes[7][8][11][10][12][9]
  2. development
    AnalystCivilian deaths, injury and damage to civilian sites

    The Events report four deaths in Kyiv region, one injury in Kropyvnytskyi district and a civilian-targeted warehouse strike in Zhytomyr; the Zaporizhzhia Stories describe apartment buildings, shopping centers and educational facilities.

    The Events report four deaths in Kyiv region, one injury in Kropyvnytskyi district and a civilian-targeted warehouse strike in Zhytomyr; the Zaporizhzhia Stories describe apartment buildings, shopping centers and educational facilities.

    Footnotes[7][9][8][1][6]
  3. development
    AnalystStrikes on logistics, rail and critical infrastructure

    The logistics Story covers warehouses, ports and logistics hubs; coded Events separately identify railway infrastructure in Vinnytsia, critical infrastructure in Poltava and a military logistics center in Kyiv Oblast.

    The logistics Story covers warehouses, ports and logistics hubs; coded Events separately identify railway infrastructure in Vinnytsia, critical infrastructure in Poltava and a military logistics center in Kyiv Oblast.

    Footnotes[2][11][10][12]
  4. development
    AnalystRail delays and power outages in related reporting

    The rail Story reports delays affecting 50 train services, while the power-outage Story attributes outages to a Russian drone attack and bad weather.

    The rail Story reports delays affecting 50 train services, while the power-outage Story attributes outages to a Russian drone attack and bad weather.

    Footnotes[3][5][20][23]

Key actors

  1. DT
    RuleDonald Trump

    Recorded as actor in 1 coded Event, including Trump calls for Ukraine war to end.

    Recorded as actor in 1 coded Event, including Trump calls for Ukraine war to end.

    Footnotes[?]

Key Events

  1. contextAnalystRussia kills four in drone strikes across Kyiv region

    On 2026-09-20, Russia carried out drone strikes across Kyiv region that killed four people.

    On 2026-09-20, Russia carried out drone strikes across Kyiv region that killed four people.

    Footnotes[7][18]
  2. contextAnalystRussian forces strike Eco Market warehouse in Zhytomyr region

    On 2026-09-20, Russian Armed Forces struck an Eco Market warehouse in Zhytomyr region, with civilians identified as the target and no fatalities reported.

    On 2026-09-20, Russian Armed Forces struck an Eco Market warehouse in Zhytomyr region, with civilians identified as the target and no fatalities reported.

    Footnotes[8][18]
  3. contextAnalystRussian drones strike railway infrastructure in Vinnytsia region

    On 2026-09-20, Russian drones struck railway infrastructure in Vinnytsia region, with Ukrainian state forces identified as the target.

    On 2026-09-20, Russian drones struck railway infrastructure in Vinnytsia region, with Ukrainian state forces identified as the target.

    Footnotes[11][18]
  4. contextAnalystRussian forces strike critical infrastructure in Poltava

    On 2026-09-21, Russian Armed Forces struck critical infrastructure in Poltava; no fatalities or injuries were reported.

    On 2026-09-21, Russian Armed Forces struck critical infrastructure in Poltava; no fatalities or injuries were reported.

    Footnotes[10][19]
  5. contextAnalystRussian drones strike Ukrainian military logistics center

    On 2026-09-21, Russian drones struck a Ukrainian military logistics center in Kyiv Oblast, with the Ukrainian Armed Forces identified as the target.

    On 2026-09-21, Russian drones struck a Ukrainian military logistics center in Kyiv Oblast, with the Ukrainian Armed Forces identified as the target.

    Footnotes[12][19]

Notable connections

Evidenced relationships involving significant participants beyond the central cast.

  1. same-day logistics and rail-impact reporting · reporting linkAnalystRussian forces strike Ukraine’s logistics hubs, warehouses and ports overnight → Attack damages Ukrainian rail infrastructure, delaying 50 train services

    The logistics Story and the rail Story are connected by a same-day link; the rail Story reports damage and delays affecting 50 train services.

    The logistics Story and the rail Story are connected by a same-day link; the rail Story reports damage and delays affecting 50 train services.

    Footnotes[20][21][3]
  2. same-day logistics and Zaporizhzhia civilian-damage reporting · reporting linkAnalystRussian forces strike Ukraine’s logistics hubs, warehouses and ports overnight → Russian strikes hit apartment buildings and shopping center in Zaporizhzhia

    The logistics Story and the Zaporizhzhia Story are connected by a same-day link, with the Zaporizhzhia Story describing apartment buildings and a shopping center.

    The logistics Story and the Zaporizhzhia Story are connected by a same-day link, with the Zaporizhzhia Story describing apartment buildings and a shopping center.

    Footnotes[22][24][2][1]
  3. same-day infrastructure reporting · reporting linkAnalystUkraine suffers power outages after Russian drone attack and bad weather → Russian forces strike Ukraine’s logistics hubs, warehouses and ports overnight

    The power-outage Story is linked to the logistics Story as same-day infrastructure reporting; it attributes outages to a Russian drone attack and bad weather and has no linked coded Event.

    The power-outage Story is linked to the logistics Story as same-day infrastructure reporting; it attributes outages to a Russian drone attack and bad weather and has no linked coded Event.

    Footnotes[23][5][2]
  4. supports the Kyiv-Oblast military logistics-center strike · reporting linkAnalystRussian forces strike Ukraine’s logistics hubs, warehouses and ports overnight → Russian drones strike Ukrainian military logistics center

    The Kyiv-Oblast military logistics-center Event lists the logistics Story among its linked Stories.

    The Kyiv-Oblast military logistics-center Event lists the logistics Story among its linked Stories.

    Footnotes[2][12]
  5. supports the Vinnytsia railway-infrastructure strike · reporting linkAnalystAttack damages Ukrainian rail infrastructure, delaying 50 train services → Russian drones strike railway infrastructure in Vinnytsia region

    The Vinnytsia railway-infrastructure Event lists the rail Story among its linked Stories.

    The Vinnytsia railway-infrastructure Event lists the rail Story among its linked Stories.

    Footnotes[3][11]

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 together29 Stories · 15 Events · 29 membership connections · 292 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 115 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.