Kyiv under fire: tracking the overnight missile wave on 20 August 2026
Tracking channels reported six groups of Kh-101s and four groups of Kh-59/69s closing on Kyiv in the early hours of 20 August 2026, with TSN_ua saying the casualty toll was rising.
At 02:25 UTC on 20 August 2026, the AMK_Mapping tracking channel posted that six groups of Kh-101s and four groups of Kh-59/69s were inbound on Kyiv. One minute later, at 02:26 UTC, the same feed put the first missiles 75 kilometres from the city. By 02:27 UTC, the channel wrote that the salvos were approaching the capital. Earlier, at 01:48 UTC, AMK_Mapping had reported that the last group was approaching Kyiv from the south and had then disappeared from track. The TSN_ua news desk posted at 02:14 UTC that the number of dead and injured from a "massive missile attack" on Kyiv was growing rapidly. The war_monitor channel flagged the Kyiv region as an area of intelligence interest at 23:59 UTC on 19 August.
The plain reading of the cluster is straightforward. Ukraine's open-source tracking ecosystem logged a multi-group air-launched cruise and tactical missile package on Kyiv in the early hours of 20 August, and a major Ukrainian TV news desk warned within minutes that the civilian toll was climbing. Everything beyond that sequencing, the weapon designations, the launch geography, the casualty breakdown, the district-by-district impact pattern, sits outside the cited posts and has to wait for the morning's official briefings.
What the cited posts actually say
The clearest evidentiary anchor is the 02:25 UTC AMK_Mapping post naming the salvo composition: six groups of Kh-101s and four groups of Kh-59/69s on a vector toward Kyiv. The 02:26 UTC post specifies the first missiles at 75 kilometres out. The 02:27 UTC post reports them approaching. The 01:48 UTC pair of AMK_Mapping posts describe the last group as approaching from the south and then as having disappeared. The TSN_ua post, timestamped 02:14 UTC, describes a "massive missile attack on Kyiv" with a rising count of dead and injured and notes that the picture was still being assembled at that hour; the cited item does not contain a final toll. The war_monitor post at 23:59 UTC on 19 August flagged the Kyiv region as an area of intelligence interest, with no further detail in the cited item.
That is the full evidentiary footprint the cluster provides. There is no official air force confirmation of intercepts, no impact-site list, no district-by-district damage map, and no final casualty count in the cited material. The sources that would normally supply those details later in the day, namely the Ukrainian Air Force operational press service and the Kyiv City Military Administration, are not represented in the cited posts.
Analysis: what the cluster tells us, and what it does not
Monexus analysis: read together, the AMK_Mapping sequence reads as a live tracking of a single overnight wave, with the 01:48 UTC southern approach and disappearance post preceding the 02:25–02:27 UTC run on the city. Monexus finds that the salvo composition, cruise missiles paired with shorter-range tactical airframes in the same package, and the time of arrival are consistent with the broader pattern of stand-off strikes on Kyiv that have been a recurring feature of the war since 2022, but the cited sources do not specify a launch location, a launch platform, an intercept count, or an impact geography, and Monexus has not independently established any of those details in this piece. The earlier post from war_monitor, at 23:59 UTC on 19 August, suggests that intelligence indicators on the Kyiv region had begun accruing several hours before the inbound wave was tracked on radar.
The same restraint has to apply to the casualty line. TSN_ua's 02:14 UTC post said the count of dead and injured was growing rapidly; that is the only casualty statement in the cited material. Any specific toll figure, any named district, any named facility would have to come from later official briefings and is not in the source set.
What the morning will bring
The next hours will produce the figures the cluster cannot. The Ukrainian Air Force typically publishes an overnight strike summary within hours, naming missile and drone types tracked, the count it attributes to incoming formations, and the count it claims to have intercepted. The Kyiv City Military Administration typically publishes a district-level damage and casualty update. The Office of the President and the Cabinet ministers usually issue parallel statements. None of those briefings is in the cited set. Monexus will update this piece or file a follow-on when those primary records are available.
The salient point for 20 August 2026 is that the capital woke under another overnight air attack, that the open tracking ecosystem gave the city roughly an hour of warning from the first southern approach post at 01:48 UTC to the 02:27 UTC "approaching" call, and that the rest of the morning's picture, casualties, intercepts, damage geography, will be set by the official briefings, not by the tracking feeds.
Desk note: Monexus framed this on the basis of the cited Ukrainian-tracking and Ukrainian-news posts. The piece deliberately stops where the cited sources stop: no casualty figure, no district list, no intercept count, no launch-location claim. Where the editorial voice reads pattern, it is labelled as Monexus analysis rather than asserted as fact.
Wire provenance
This editorial synthesis draws on the following public wire/social posts:
- https://t.me/AMK_Mapping/36236
- https://t.me/AMK_Mapping/36237
- https://t.me/AMK_Mapping/36238
- https://t.me/AMK_Mapping/36220
- https://t.me/AMK_Mapping/36221
- https://t.me/TSN_ua/586011
- https://t.me/war_monitor/42776
Follow the event.
These dated source records provide context. They do not retrospectively verify this archive article.
A dated voting record is evidence of one decision. Use the original UN record before turning it into an alignment label.
Visual explainer · historical vote of 2022-03-02 →