Ukrainian monitors report one Russian ballistic missile over Brovary, east of Kyiv, on 22 October
What happened
Ukrainian air monitoring channel @war_monitor on Telegram reported one Russian ballistic missile descending over Brovary, a settlement in Kyiv Oblast just east of the capital, at 09:40 UTC on 22 October 2026. The original post is a short Ukrainian-language alert, 'Бровари — спуск балістики!', which translates roughly as 'Brovary — ballistic descent!' The wording describes a missile's reported descent phase rather than a confirmed impact, so the report says nothing about strike points, damage, or casualties. No other outlet in the dataset carries the report. The event is logged as a ballistic missile attack with Russia named as actor and no origin location recorded. It follows a cluster of activity over Kyiv earlier that night and a cruise missile reported heading toward Brovary the previous evening.
Context and assessment
Brovary lies on the eastern approach to the Ukrainian capital, so air alerts there typically track missiles moving toward Kyiv or its surrounding districts. The related events show a sequence over roughly fifteen hours. At 19:10 UTC on 21 October, a Russian Zircon or Oniks-type cruise missile was reported passing Nizhyn, a town to the north in Chernihiv Oblast, and heading toward Brovary. Three minutes later a ballistic missile was reported over Kyiv, followed by further ballistic reports over Kyiv at 00:06 and 00:09 on 22 October. Two entries share the 00:09 timestamp and wording, so they may be duplicates rather than separate missiles. Taken together, the pattern suggests a multi-type salvo using a northern approach and varied trajectories, with the Kyiv area as the main focus and eastern suburbs such as Brovary crossed or targeted as well. The data does not establish intent. A missile reported over Brovary could be on a path to Kyiv, could be a deliberate secondary target, or could be a misreported position. Monitoring reports of this kind are most useful for tracking flight paths and alert timing rather than for judging what was hit.
Sources and confidence
Only one channel, Telegram @war_monitor, reported this event, and no second source is listed. The confidence score of 6.0 reflects that single-source status, a clear Ukrainian-language original, and a specific settlement-level location. It is not higher because the channel's track record is not documented in the data, and the report describes a descent rather than an impact. Confidence would rise with corroboration from official Ukrainian Air Force alerts, regional military administration statements, or geolocated imagery. It would fall if the feed were shown to duplicate earlier entries or if the report were corrected or withdrawn.
Location
The location is recorded at settlement level for Brovary, Kyiv Oblast, with coordinates of about 50.511 N, 30.791 E. The location confidence is rated high because the place name is explicit in the original post. The town sits on the eastern edge of the Kyiv metropolitan area, in flat lowland terrain of the Dnipro basin. The landscape here includes river floodplains, farmland, and forest belts typical of northern Kyiv Oblast. The point is a town centre estimate, not a specific facility or impact site.
Related events nearby
- Ukrainian air monitoring: 1 Russian Zircon/Oniks missile passing Nizhyn, heading toward Brovary.2026-10-21 19:10 UTC · Cruise Missile · Brovary, Ukraine
- Ukrainian air monitoring: 1 Russian ballistic missile over Kyiv.2026-10-22 00:09 UTC · Ballistic Missile · Kyiv, Ukraine
- Ukrainian air monitoring: 1 Russian ballistic missile over Kyiv.2026-10-22 00:09 UTC · Ballistic Missile · Kyiv, Ukraine
- Ukrainian air monitoring: 1 Russian ballistic missile over Kyiv.2026-10-22 00:06 UTC · Ballistic Missile · Kyiv, Ukraine
- Ukrainian air monitoring: 1 Russian ballistic missile over Kyiv.2026-10-21 19:13 UTC · Ballistic Missile · Kyiv, Ukraine
▶ View this event on the live map
Intel Mapper aggregates open-source reports from monitored Telegram and X channels, geolocates them, cross-checks duplicates across sources and assigns a confidence score. Entries are updated as new confirmations arrive. Read how we verify events.