Kyiv under the barrage: what the open-source record actually shows

Ten documented impact points across the Ukrainian capital, water service cut in some districts, fires growing in size, and a fresh wave closing in after midnight. That is the documented state of Kyiv between 22:38 UTC on 31 July and 00:20 UTC on 1 August 2026, according to the open-source monitor AMK_Mapping and the war correspondent Andriy Tsaplienko, both posting into the small hours as the strikes piled up.

Monexus assessment: the framing of each Russian strike on Kyiv as a discrete escalation has itself become part of the problem. Read in sequence, the Telegram posts trace an unmistakable tempo. At 22:38 UTC on 31 July, AMK_Mapping posted that two missiles were approaching Kyiv (AMK_Mapping/35121). By 22:41 UTC, the same channel had logged ten impacts in the city (AMK_Mapping/35127). At 23:03 UTC, another wave was approaching the city (AMK_Mapping/35155). By 23:08 UTC, fires were growing in size across the impact sites, and Tsaplienko reported that water had disappeared in some districts of Kyiv (AMK_Mapping/35164; Tsaplienko/96613). Just after midnight on 1 August, AMK_Mapping reported a wave one minute from Kyiv at 00:18 UTC, then approaching Brovary and Kyiv at 00:19 UTC, then ten seconds out at 00:19 UTC, and one impact recorded in western Kyiv at 00:20 UTC (AMK_Mapping/35194, /35195, /35197, /35203). The arithmetic is what the wireframe is struggling to absorb.

The vocabulary problem

Western wire copy routinely reaches for the word "strike" and then moves on. A strike implies an action with a defined beginning and end, something that can be condemned in a paragraph and then forgotten by the morning bulletin. The Kyiv timeline from 31 July into the early hours of 1 August is closer to a siege economy: at least two distinct approach reports (AMK_Mapping/35121 and /35155), ten impacts confirmed within minutes of the first report (AMK_Mapping/35127), documented infrastructure damage already in the first hour, and a fresh wave crossing the final minute-countdown thresholds in the early minutes of 1 August (AMK_Mapping/35194, /35195, /35197, /35203).

The pattern is not new. What the open-source record shows on this occasion is the speed. AMK_Mapping logged two missiles approaching Kyiv at 22:38 UTC on 31 July (AMK_Mapping/35121), ten impacts inside the city by 22:41 UTC (AMK_Mapping/35127), and a further approach at 23:03 UTC (AMK_Mapping/35155). A subsequent sequence at 00:18 UTC, 00:19 UTC and 00:19 UTC tracked a wave down to ten seconds from impact, followed by one logged impact in western Kyiv at 00:20 UTC on 1 August (AMK_Mapping/35194, /35195, /35197, /35203). That is a documented tempo, and it sits inside an established pattern of multi-wave attacks on Kyiv rather than a one-off incident.

What the source record actually establishes

The available posts are precise about effect and silent about intent. AMK_Mapping documents ten impacts inside the city by 22:41 UTC on 31 July, growing fires at 23:08 UTC, and four additional countdown-and-impact messages between 00:18 UTC and 00:20 UTC on 1 August. Tsaplienko adds the civilian-infrastructure consequence: water service disrupted in some districts of the capital as of 23:08 UTC. The channel does not specify what category of facility each warhead struck, only where the impacts registered.

Monexus analysis: the loss of water service in some districts of a capital city under active bombardment is operationally significant regardless of the specific target of each missile. Cutting water degrades a city's ability to coordinate air defence, to keep hospitals running, and to maintain the symbolic centre of national resistance. That is a structural reading of the consequence, not a claim about which building was hit. The source items do not specify operational intent; they document effect.

The counter-claim and why it does not hold

Moscow's framing, when it bothers to acknowledge strikes on Kyiv at all, treats them as responses to alleged Ukrainian long-range operations against Russian territory. That rebuttal deserves to be reported, not because it is persuasive but because it is the only counter-position on offer and the absence of engagement with it would weaken the argument. The rebuttal fails on its own terms: a state engaged in punitive infrastructure attacks on a third-tier European capital, repeatedly, across multiple waves inside a single night, cannot credibly cast itself as the victim. The documented sequence of approach and impact posts between 22:38 UTC on 31 July and 00:20 UTC on 1 August is not in dispute; the political interpretation is.

What the wireframes leave out

Three things. First, the open-source monitors doing the real-time mapping work (AMK_Mapping, Tsaplienko) are operating at a tempo and a granularity that the wire services cannot match. Western outlets tend to publish one packaged story the next morning; the monitors publish the wave-by-wave reality as it happens. Second, the human cost of the strikes is concentrated in the responders, the on-call water engineers, the night-shift nurses, the people who keep a damaged city functional. Their names rarely make it into the wire. Third, the framing of "Russian missile strike on Kyiv" is now so familiar that it has lost its descriptive power. Each strike is the same strike. Each sentence about it becomes interchangeable with the last. That is the point.

Monexus analysis: the structural pattern is one of attrition normalised by repetition. The West's appetite for sustained attention on this war is finite; Moscow's appetite for sustained pressure on Kyiv is, on present evidence, not. The longer the framing fails to name that asymmetry, the more it concedes it.

The night ahead

What remains uncertain is whether the 1 August strikes represent the opening of a new, more intense campaign or the continuation of an existing tempo. The available source items do not specify operational intent; they document effect. The two pre-midnight approach reports (AMK_Mapping/35121, /35155), ten confirmed impacts by 22:41 UTC (AMK_Mapping/35127), and the four countdown-and-impact posts in the first twenty minutes of 1 August (AMK_Mapping/35194, /35195, /35197, /35203) suggest the latter, but the data here is thin. Watch for additional waves on the evening of 1 August, and for the first aggregated official read of the night's damage. The open-source monitors are, for now, the closest thing the public has to a real-time ledger of what is being done to one European capital by another. They should be treated as primary evidence, not as colour.

Desk note: Monexus has framed this overnight sequence as a single continuous campaign rather than as discrete events, on the basis that the source items document multiple approach and impact posts inside a roughly 100-minute window and cumulative infrastructure damage. Where Ukrainian open-source monitors are the only available sources for a specific timing claim, that provenance is stated explicitly above. No Russian-side confirmation or denial has been cited as evidence; the counter-claim is engaged with as argument, not as reportage. The available source items do not specify the targets of individual missiles or the operational intent behind the sequencing.

Wire provenance

This editorial synthesis draws on the following public wire/social posts:

• https://t.me/AMK_Mapping/35121
• https://t.me/AMK_Mapping/35127
• https://t.me/AMK_Mapping/35155
• https://t.me/AMK_Mapping/35164
• https://t.me/Tsaplienko/96613
• https://t.me/AMK_Mapping/35194
• https://t.me/AMK_Mapping/35195
• https://t.me/AMK_Mapping/35197
• https://t.me/AMK_Mapping/35203