‘Software Glitch’ Costs a Life: US Again Failed to Warn Kyiv of Ballistic Strike
Russia struck Kyiv with ballistic missiles on the night of October 19, killing a 21-year-old woman and damaging a residential tower, a medical center, and the Chernihivska metro station. The US, which had resumed intelligence sharing hours earlier, again gave no advance warning — and Secretary of State Marco Rubio blamed a “software problem.”
1 / 4The facts: On the night of October 19, Russia launched ballistic missiles at Kyiv. A 21-year-old woman was killed. At least three people were injured. A 25-story residential building in the Solomianskyi district, a medical center, and the Chernihivska metro station on the red line were damaged. The Chernihivska and Lisova stations are temporarily closed; trains run only to Darnytsia.
But the main story of this night is not just the destruction. It’s that Ukraine could have known about it in advance — and didn’t.
Just hours earlier, on October 18, President Zelenskyy told NBC’s “Meet the Press” that the U.S. had resumed intelligence sharing after a three-day pause. “Now everything is working,” he said. Then Russia launched its ballistic missiles — and again, no warning came.
Bloomberg and RFE/RL, citing sources, confirmed that the U.S. did not warn Ukraine of the ballistic launch. RFE/RL journalist Oleksiy Raufoğlu wrote: “Again, there was no advance notification about the ballistic attack on Kyiv.”
Marco Rubio offered an explanation. The U.S. Secretary of State said a “software problem” in the early warning system was to blame. The U.S. European Command (EUCOM) is investigating. But that brings no comfort to the family of the dead woman, to the residents of the damaged building, or to the metro passengers who couldn’t get to work this morning.
This is not the first time. On October 12 and 13, ballistic missiles also struck Kyiv without prior warning from allies. Zelenskyy then publicly stated that the U.S. had threatened to cut off intelligence sharing because of Ukraine’s strikes on Russian oil refineries. A three-day pause followed. Then the resumption. And then — another “software problem.”
The logical question: if the early warning system fails every time ballistic missiles are headed for Kyiv, is it really a “software problem” — or something else? Rubio could not confirm whether Ukraine received any warning. But the fact remains: no warning came. And a person died.
Zelenskyy himself confirmed on October 19 that partners again failed to warn Ukraine of the ballistic attack, as Hromadske reported.
Could the 21-year-old woman have been saved if the warning system had worked? Technically, yes. Ballistic missiles have a short flight time, but even a few minutes allow people to take cover. The issue is not technical. It’s whether Washington truly intends to warn Kyiv every time — not just in words.
“Software problem” is a convenient phrase. It shifts responsibility from specific people onto an impersonal system. But behind every such “problem” are real lives. Today — one. How many more before the system is fixed?
While EUCOM investigates, Kyiv continues to live under ballistic strikes without warnings. And any night could be the last for someone who simply happened to be in the wrong place.
Primary sources
Documents and statements this story is based on.
- TSN — US again failed to warn Kyiv of ballistic attack
- Glavred — Russia struck Kyiv with ballistic missiles
- EuroPravda — Zelenskyy confirmed resumption of intelligence sharing
- Hromadske — Zelenskyy on the absence of warning
- Today.ua — Rubio named the cause
- RBC-Ukraine — US fails to warn Ukraine
- NV — Ballistic strike on Kyiv: US failed to warn
- LIGA.net — Sources: Ukraine again received no warning
- UNN — Rubio unable to confirm warning
- The Kyiv Independent — US resumes intel sharing



