2026-07-22
Ukraine daily situation report — 2026-07-22
- Claim clusters
- 13
- Source families
- 14
- Confirmed / likely
- 11
18 republication chains were detected and grouped.
Daily situation picture
Would you like one calm daily brief?
Only anonymous interest is measured. No email address is collected.
What changed
President Volodymyr Zelenskyy publicly announced Mykhailo Drapatyi as the new Commander-in-Chief in place of Oleksandr Syrskyi and separately said he offered Mykhailo Fedorov an unspecified leadership role.
Day 6 correctly recorded no decree by its cutoff. The announced change occurred after that cutoff and is not a correction of the earlier bounded claim.
The Liberian-flagged LPG tanker Gas Lisbon was struck outside Romanian territorial waters while heading to Ukraine; Romanian rescuers evacuated the full crew and three were injured, while attribution remained under investigation.
The incident occurred shortly before the observation window but became publicly verified during it; it is carried as a late-reported material update.
Zaporizhzhia Oblast authorities reported three civilians killed and 24 injured during the July 21-22 reporting day; the city strike accounted for all three deaths and 13 injuries.
The final roll-up supersedes early reports of one and two deaths and avoids treating the city and regional totals as separate events.
Odesa regional authorities raised the injury count from the July 21 daytime strike to four.
Four supersedes the early counts and is not summed with them.
Kharkiv Oblast authorities reported that a drone struck a moving civilian car on July 21, killing two passengers and injuring the driver.
The event occurred within the observation window and is kept separate from earlier Kharkiv attacks.
Dnipropetrovsk Oblast authorities reported five civilians injured in July 21 daytime attacks in the Nikopol and Synelnykove districts.
The five injured are not merged with two deaths reported from attacks before the window cutoff.
Donetsk Oblast authorities reported at least two civilians killed and seven injured in July 21 attacks, including a strike on a civilian vehicle.
The later two-killed/seven-injured total supersedes an earlier two-killed/three-or-four-injured vehicle report.
Evidence and open questions
Confidence describes evidence quality, not certainty. Reposts are not counted as independent confirmation.
President Volodymyr Zelenskyy publicly announced Mykhailo Drapatyi as the new Commander-in-Chief in place of Oleksandr Syrskyi and separately said he offered Mykhailo Fedorov an unspecified leadership role.Ukraine CONFIRMED · 4.6/5
Rationale
A direct authoritative announcement plus multiple independent editorial confirmations supports CONFIRMED status. Wording is limited to the public announcement and preserves the offer-versus-appointment distinction.
Still unknown
- Formal decree text and effective transition timing
- Fedorov role, acceptance and legal status
- Syrskyi's next assignment
Sources
- Ukrinform — Drapatyi named new Commander-in-Chief ↗
- Ukrinform — Fedorov offered leadership position ↗
- Guardian — Zelenskyy replaces military leader ↗
- Reuters — Ukraine gets new top commander ↗
- ISW — Russian Offensive Campaign Assessment, July 21 ↗
- Guardian — Ukraine war briefing, July 22 ↗
- Liveuamap — July 21 Ukraine event stream ↗
The Liberian-flagged LPG tanker Gas Lisbon was struck outside Romanian territorial waters while heading to Ukraine; Romanian rescuers evacuated the full crew and three were injured, while attribution remained under investigation.Black Sea · off Romania LIKELY · 4.3/5
Rationale
Official rescue action, crew evacuation and independent editorial reporting strongly support the bounded event. Attribution is explicitly held below final confirmation, so LIKELY is appropriate.
Still unknown
- Final forensic attribution
- Weapon type and launch origin
- Final vessel damage and cargo condition
Zaporizhzhia Oblast authorities reported three civilians killed and 24 injured during the July 21-22 reporting day; the city strike accounted for all three deaths and 13 injuries.Zaporizhzhia Oblast · Zaporizhzhia LIKELY · 3.6/5
Rationale
A timely authoritative aftermath source and independent event confirmation support LIKELY, while limited numerical independence prevents CONFIRMED.
Still unknown
- Late hospital revisions
- Final separation of city and other regional incidents
Odesa regional authorities raised the injury count from the July 21 daytime strike to four.Odesa LIKELY · 3.6/5
Rationale
The regional authority is authoritative for immediate medical reporting and the correction is internally traceable; single-origin dependence keeps it LIKELY.
Still unknown
- Later medical revisions
- Full damage assessment
Kharkiv Oblast authorities reported that a drone struck a moving civilian car on July 21, killing two passengers and injuring the driver.Kharkiv Oblast LIKELY · 3.5/5
Rationale
A strong, specific local aftermath source supports LIKELY for the narrow casualties, but limited independence prevents CONFIRMED.
Still unknown
- Independent visual verification
- Final condition of the driver
- Weapon provenance beyond the preliminary local assessment
Dnipropetrovsk Oblast authorities reported five civilians injured in July 21 daytime attacks in the Nikopol and Synelnykove districts.Dnipropetrovsk Oblast LIKELY · 3.4/5
Rationale
A credible regional aftermath source supports the bounded minimum, with conservative separation of cutoffs. Limited independence keeps it LIKELY.
Still unknown
- Late hospital revisions
- Complete period alignment across district updates
Donetsk Oblast authorities reported at least two civilians killed and seven injured in July 21 attacks, including a strike on a civilian vehicle.Donetsk Oblast LIKELY · 3.5/5
Rationale
Traceable local updates and specific aftermath reporting support LIKELY; the exact roll-up remains one official family.
Still unknown
- Late casualty revisions
- Full event list behind the regional minimum
Sumy Oblast's July 22 morning roll-up recorded seven people injured or seeking medical care, but several had been injured in attacks on July 15, 19 or 20 rather than during the latest reporting day.Sumy Oblast LIKELY · 3.5/5
Rationale
The source's explicit date breakdown directly supports the clarification. LIKELY reflects reliance on one reporting chain while preventing a misleading daily sum.
Still unknown
- Whether all seven had previously been counted
- Final medical classifications
Kyiv Oblast authorities reported five people, including three children, injured when a residential building was struck on the morning of July 22.Kyiv Oblast LIKELY · 3.6/5
Rationale
Direct emergency response and a specific official casualty count support LIKELY, with moving-toll risk and limited independence clearly retained.
Still unknown
- Later medical revisions
- Final damage and munition assessment
Geolocated footage supports that Ukrainian strikes hit a Russian fighter aircraft and an air-defense system at an airfield in Kursk Oblast; complete destruction was not independently established.Kursk Oblast LIKELY · 4.1/5
Rationale
Auditable geolocated visual evidence supports the bounded hit claim at LIKELY. The stronger destruction wording is withheld.
Still unknown
- Repairability and final damage
- Whether both systems were operational
- Independent post-strike imagery
A large industrial fire occurred in Lipetsk after a reported Ukrainian strike; Russian local acknowledgement, geolocated imagery and Astra reporting support the fire, while exact site function and damage remain incomplete.Lipetsk LIKELY · 4.1/5
Rationale
Cross-environment acknowledgement and geospatial evidence make the fire and likely strike link LIKELY. The report withholds unsupported target and damage claims.
Still unknown
- Exact facility hit
- Degree of operational disruption
- Final attribution and damage assessment
ISW assessed localized Ukrainian gains in two broad directions and no confirmed Russian advances across several major sectors on July 21; no broad breakthrough was independently established.Ukraine frontline PLAUSIBLE · 3.5/5
Rationale
The bounded no-broad-breakthrough conclusion is credible and evidence-backed, but incomplete map-family independence keeps it PLAUSIBLE.
Still unknown
- Small changes not yet processed
- DeepState's independent 24-hour assessment
- Durability of localized gains
Control of Kostiantynivka remained contested: Russian sources claimed positions and advances, while recently processed footage showed Ukrainian positions in areas where Russian presence had been claimed.Kostiantynivka · Donetsk Oblast CONFLICTED · 3.1/5
Rationale
Credible sources materially disagree and the independent reviewer explicitly says control remains contested, so CONFLICTED overrides the numerical score.
Still unknown
- Citywide control
- Age and completeness of available footage
- Map revisions expected after cutoff