Open-source trackers log ten impacts in Kyiv by 22:41 UTC, with another in western Kyiv forty minutes later

Open-source tracking accounts recorded a salvo that left ten impact points logged across the Ukrainian capital by 22:41 UTC on 31 July 2026, with fires reported as growing in size and water service disrupted in some districts by 23:08 UTC, and a further impact in western Kyiv recorded at 00:20 UTC on 1 August. Between those bookends the same set of channels produced a minute-by-minute reconstruction that also forced Kyiv residents into shelter.

The source material is fragmentary by design. Read together, the posts construct a coherent chronology of arrival and aftermath; they do not reconstruct launch. What the open-source trail establishes is the impact floor as logged by citizen trackers. What the available items do not establish is the missile type, the launching unit, the casualty picture, or the air-defence interception count. On casualty reporting in particular, Ukrainian wire reporting from the same night describes wounded persons and fires across multiple districts; this article confines itself to the open-source-tracker record and does not aggregate that reporting into the chronology below.

A granular timeline

At 22:38 UTC on 31 July, the AMK_Mapping channel flagged two projectiles on a Kyiv-bound trajectory. By 22:41 UTC the same account reported ten impact sites, hedged with the qualifier "so far." That hedge matters: the count was a snapshot at that moment, not a final tally. At 23:08 UTC, AMK_Mapping reported that fires in the city were growing in size, while correspondent Andriy Tsaplienko separately logged, in a post framed as hearsay ("They write that…"), that water had disappeared in some districts of Kyiv. The two non-mapping posts sit inside that spine. At 00:18 UTC on 1 August, AMK_Mapping posted "1 min from Kyiv." A minute later, the operational Telegram channel operativnoZSU issued a shelter order, and AMK_Mapping posted "10 seconds from Kyiv" in the same minute, with a further post at 00:20 UTC logging "1 impact in western Kyiv." By 00:56 UTC, the war_monitor channel had returned online with an apology to subscribers that attributed its absence to its operator's "personal factor" rather than to the strike itself. The 00:18-00:19-00:20 UTC cluster is unusually compressed, with an inbound-missile warning, a shelter instruction and a western-Kyiv impact logged inside roughly two minutes.

What the posts do not establish

The available source items do not specify the missile type or model, the military unit responsible for the launch, casualty figures, or whether the strikes targeted military infrastructure, energy infrastructure or residential blocks. They record fires and water-disruption reports as observable effects, not as adjudicated damage assessments. The Tsaplienko water-loss post is presented in the source as received information ("They write that…"), not as a personal observation; this article preserves that framing. Ukrainian air-defence interception activity, which often accompanies morning-after official reporting on overnight strikes, is not in this source set. The total number of missiles launched is also not in the source set; only that at least ten impacts were logged by 22:41 UTC, that two additional projectiles were observed inbound at 22:38 UTC, and that a further impact in western Kyiv was logged at 00:20 UTC.

Reading the timing

Monexus assessment: the cluster of posts around 00:18-00:20 UTC on 1 August is the densest data point in the record, with a "1 min from Kyiv" warning, a shelter order, a "10 seconds from Kyiv" warning and a western-Kyiv impact all logged within roughly two minutes of one another. The compressed interval between warning and shelter instruction, combined with the simultaneous reporting of multiple impacts, is consistent with the short flight window characteristic of ballistic missiles rather than the longer approach profile of cruise missiles. The simultaneous reporting of growing fires and water-service disruption in the same minute at 23:08 UTC is consistent with critical-infrastructure effects inside the impact zone. None of these readings is a confirmed attribution; each is an inference from the timing pattern in the open-source record.

The variable to watch in the hours ahead is the official morning tally. Ukrainian air-force briefings typically publish interception counts, launch vectors and missile-type breakdowns within twelve to twenty-four hours of a major overnight strike, and city-administration utility updates typically follow within hours. If interception rates were low, the salvo will be read in Kyiv and in Western capitals as a successful operational test of ballistic-saturation pressure on the capital. If they were high, the framing shifts to one of defensive competence under pressure. Both readings are available on the timing evidence in the source set; the data to choose between them is not. Casualty reporting from Ukrainian wire services, which began appearing during the same attack window, sits outside the open-source-tracker record this article draws on and is flagged here so the reader can calibrate.

What can be said without overreach: on the night of 31 July to 1 August 2026, open-source tracking accounts logged an attack on Kyiv that produced a "so far" count of ten impact points by 22:41 UTC on 31 July, an additional recorded impact in western Kyiv at 00:20 UTC on 1 August, growing fires and water-service disruption in some districts by 23:08 UTC, and a shelter order issued within a minute of impact-warning posts. That is the floor of what the evidence supports. Everything else belongs to the morning's official reporting and to the Ukrainian wire coverage already in the public record.

Desk note: this article is built from open-source Telegram trackers (AMK_Mapping, operativnoZSU, war_monitor, Andriy Tsaplienko) operating in real time during a live strike. The chronology is granular, but the casualty, weapon-type and interception questions are deferred to official reporting and to Ukrainian wire coverage of the same attack window. Where the wire will lead with confirmed numbers and named officials, Monexus leads with the timeline that only citizen-tracker accounts produce in the first hours of an event.

Wire provenance

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

• https://t.me/war_monitor/42137
• https://t.me/AMK_Mapping/35203
• https://t.me/operativnoZSU/217373
• https://t.me/AMK_Mapping/35197
• https://t.me/AMK_Mapping/35194
• https://t.me/AMK_Mapping/35164
• https://t.me/Tsaplienko/96613
• https://t.me/AMK_Mapping/35127
• https://t.me/AMK_Mapping/35121