Conflict · Ukraine intelligence
Zelenskyy Says US Missile Warnings Are Back. The Gaps Remain Unexplained.
Zelenskyy says a vital US warning feed has resumed, but satellite restrictions remain. The cause of the disruptions—and who controlled them—is still unresolved.

Transcript · LOADING
Story trackerDay 6
1 report85 outlets148 sources5 videos
On October 16, we reported the damage Russian missile and drone strikes had inflicted on Kyiv’s buildings and energy infrastructure. The latest development concerns the defenses behind those headlines: President Volodymyr Zelenskyy says American warnings of Russian ballistic-missile launches are working again after a three-day gap. But he says satellite restrictions still limit Ukraine’s military operations. One vital service has returned in his account; another has not fully recovered. 1 4
That is a consequential improvement, not an explanation. The interview aired on NBC’s Meet the Press on October 18, 2026, but neither its recording date nor the exact beginning and end of the warning interruption has been established. October 18 cannot be treated as the day Washington restored the feed. Independent official confirmation of the precise three-day gap and its restoration is also not established in the available reporting. 6 15
And then it was deblocked by the American side. We are very thankful for this. Now it works.
Zelenskyy identified the missing information narrowly: American intelligence warning Ukraine when Russia uses ballistic missiles. He said Ukraine received none during ballistic attacks for three days, while European countries and other partners continued supplying other intelligence. His description of the American capability as unique is his assessment—not evidence that Ukraine had lost every means of detecting an attack. 6
The distinction matters. A launch warning gives people information they can act on before a missile arrives. A country can continue receiving intelligence while losing one specialized stream that makes an immediate difference to its defenses.
A warning gap without an explanation
There is a contemporaneous record behind Zelenskyy’s retrospective account. Ukrainian statements described missing partner warnings for ballistic attacks on Kyiv on the evenings of October 12 and 13. Reporting described explosions preceding some air-raid alerts and missiles being detected late. Those attack nights help explain the alarm, but they do not establish the full three-day timetable. Nor has any particular death or damaged building been shown to result from missing American warnings rather than the Russian attacks themselves. 95 17
Foreign Minister Andrii Sybiha offered a broader description on October 13: intelligence cooperation with the Americans continued. He linked delayed alerts partly to the weapons Russia used. Trump also denied stopping intelligence sharing around October 13–14. Those statements do not necessarily disprove a failure in one particular warning stream; continued cooperation and incomplete delivery can coexist. 126 125
The cause remains unresolved. A Ukrainian official relayed an American explanation that the launch simply had not been seen. The available account does not identify the launch date or establish that explanation as conclusive. Deliberate withholding, a collection failure and a failure to transmit information remain different possibilities, not interchangeable descriptions of a proven suspension. 1
Former US ambassador to Ukraine William Taylor told Global News on October 18 that missile warnings had been interrupted for roughly three days, alongside interruptions to satellite services. He attributed the interruptions to a conscious administration decision. That is Taylor’s assessment, not an on-record admission by a current official or identification of whoever authorized a change. 2
What “restored” leaves out
The satellite dispute has a separate chronology. On October 14, presidential technology and electronic-warfare adviser Serhiy Beskrestnov, known as “Flash,” described unannounced restrictions affecting terminals in motion, with a stated threshold of 100 miles an hour—approximately 160–161 kilometers an hour. That evening, former defense minister Mykhailo Fedorov announced connectivity returning at speeds up to 160 km/h while urging complete removal of Starshield’s speed limit. 141 142
Defense Ministry sources described service in motion working again on October 15. By October 16, however, Zelenskyy was still saying full capability had not returned. Those earlier restoration reports do not settle the later complaint: restoring a connection below a threshold is not the same as removing that threshold. 143 101
In the later NBC interview account, Zelenskyy put the continuing maximum at 160 or 161 km/h. This concerns how fast the connected platform moves, not internet throughput. An earlier account gave approximately 61 km/h amid garbled wording; the later interview account and contemporaneous Ukrainian statements support 160–161 km/h instead. The older figure should not be treated as an equally established current limit. 4 141
Operational reports are less tidy than a single number suggests. The senators’ letter requesting an investigation says Ukrainian military testing found restrictions above approximately 63 mph, roughly 101 km/h, while SpaceX reportedly acknowledged a 100-mph restriction. Seventh Corps accounts described drops lasting 10–20 seconds at 110–120 km/h; other unit observations ranged roughly from 72 to 161 km/h. These are reported experiences under differing conditions, not proof of one universal cutoff for every terminal. 86 73
Zelenskyy says the restriction prevents affected satellite-connected interceptor drones from destroying jet-powered Shahed-type aircraft he estimates travel at 450–550 km/h. That estimate applies to those jet-powered variants, not every Shahed. He also says the services support frontline deliveries of food and water. These accounts explain the military stakes, but the claimed operational effects are not independently confirmed, and officials have not quantified lost interceptions, missions or deliveries. 4
He also describes Ukrainian equipment working at higher speeds during tests in Europe, which he considers evidence of a planned, Ukraine-specific restriction. That is his account and inference, not independent proof of intent. His further request for satellite access over Russian territory to attack ballistic-missile launches remains unmet, he says. Opening that territory would expand geographic permissions, not merely restore existing service inside Ukraine. 73 4
Conflicting claims of access and control
Even the identity of the restricted service is disputed. Starlink is SpaceX’s commercial connectivity service; Starshield is a separate military-grade offering for US government and defense operations. On October 18, NPR reported Zelenskyy’s account that existing Starshield access remained restricted. Fox News that day relayed Secretary of State Marco Rubio’s position that Ukraine was seeking Starshield access but did not have it. The disagreement cannot be resolved by calling everything Starlink: the actual services, equipment and permissions available to Ukraine remain unclear. 3 5
The accounts of responsibility also conflict. Taylor’s October 18 Global News interview attributed the interruptions to an administration decision; Fox’s October 18 report carried Rubio’s denial that the United States ordered Starlink slowed. Zelenskyy believes an American government message prompted SpaceX to impose limits, but explicitly says he does not know who made the decision. 2 5 4
Reuters reported on October 15, citing two American officials and a Western official briefed on the matter, that an order originated inside the White House and reached Defense Department leadership. No individual decision-maker was identified. A senior American official denied that the president made such a request. That is significant anonymously sourced reporting, not a confirmed chain of command. 37
Trump denied interfering and said the system was operating as usual, as far as he understood. Treasury Secretary Scott Bessent repeated the administration’s denial on NBC, calling Zelenskyy’s accusation “very reckless.” But Bessent said he did not know what caused the reported satellite disruption or intelligence-sharing break. His categorical rebuttal addressed the satellite allegation; it supplied no explanation for the missing missile warnings. 3 7
Elon Musk says the US military and ultimately the president decide Starshield’s limits. He distinguishes commercial Starlink as restricted to civilian or defensive uses, excluding offensive military action. That describes who holds authority; it does not establish whether an order was issued in this instance. 67
An accountability request, not findings
Nine senators, led by Jeanne Shaheen and Thom Tillis, asked Defense Department Inspector General Platte B. Moring III to investigate on October 15. Their questions cover communications, intelligence sharing and warning capabilities: who directed, approved or knew about changes; whether SpaceX complied with its contracts; what notifications occurred; and what corrective measures are needed. 55 86
The letter also raises allegations that American diplomatic, military and security personnel could not reach designated bunkers during Russian air raids. Those are concerns for examination, not completed investigative findings. The senators requested written confirmation of the investigation’s status and an initial briefing by November 1, 2026—not a final report. No public confirmation that the inspector general has opened an investigation is established. 86
Zelenskyy’s proposed talks with American negotiators around October 20–21 remain tentative, with no commitment to settle either disruption. For now, his account offers reassurance on the most immediate point: the ballistic-missile warning feed works again. The unfinished task is to establish why it disappeared, what satellite capability remains unavailable, and whether Ukraine can rely on either service staying available when the next attack comes. 6
As aired 28 lines
- On October 16 we reported Kyiv’s strike damage. Zelenskyy says American missile warnings have resumed. Earlier today, we reported that Ukrainian officials had put power losses from earlier attacks at at least 600,000 people. Ukraine’s president now describes three days without American ballistic-missile warnings, while satellite restrictions still hamper defenses in his account. What caused the warning gap, and how much support is working again?
- Zelenskyy says Ukraine received no American warnings during ballistic attacks for three days. He says the Americans then restored the information. In his words, “We are very thankful for this. Now it works.”
- His interview aired October 18. He hasn't given exact dates for the interruption, so the warnings may have resumed before that broadcast. European countries and other partners continued supplying other intelligence during the gap.
- Ukrainian accounts described missing partner warnings for Russian ballistic attacks on Kyiv on the evenings of October 12 and 13. Explosions preceded some air-raid alerts, and missiles were detected late. Those attack nights don't give us the full three-day timetable.
- A launch warning gives people information they can act on before a missile arrives. Zelenskyy calls the American capability unique. Ukraine also had other ways to detect attacks, even while the particular American warning information was missing.
- Foreign Minister Andrii Sybiha said on October 13 that intelligence cooperation with the Americans continued. He linked delayed alerts partly to the weapons Russia used. Cooperation could continue while one specialized stream of launch warnings failed to arrive.
- Trump denied stopping intelligence sharing around October 13 and 14. Former American ambassador William Taylor later described a roughly three-day warning interruption and blamed a conscious administration decision. He also described interruptions to Ukraine’s satellite services.
- A Ukrainian official relayed an American explanation that the launch simply hadn't been seen. That explanation wasn't tied publicly to a specific launch date. Nobody has explained conclusively whether information was withheld, missed by American systems, or lost along the way.
- Zelenskyy says satellite restrictions remain even though the missile-warning information has returned. He believes an American government message prompted SpaceX to impose the limits. He says he doesn't know who made that decision, and has sought Trump’s and Elon Musk’s intervention.
- Ukraine described a partial satellite recovery before Zelenskyy’s interview. On October 14, officials reported unannounced restrictions on moving terminals. Connectivity below a speed threshold began returning that evening. Defense Ministry sources described service in motion working again on October 15.
- Presidential technology adviser Serhiy Beskrestnov, known as Flash, described a restriction around 100 miles an hour. Former defense minister Mykhailo Fedorov announced connectivity returning up to 160 kilometers an hour, while urging complete removal of Starshield’s speed limit.
- By October 16, Zelenskyy was still saying full capability hadn't returned. Restoring a connection below a threshold can leave faster-moving aircraft unable to use it. The restriction concerns how fast the connected platform moves.
- Zelenskyy puts the platform threshold at 160 or 161 kilometers an hour. He says affected interceptor drones can't destroy jet-powered Shahed-type aircraft he estimates fly at 450 to 550 kilometers an hour. That estimate applies to those jet-powered variants.
- Ukrainian military testing found restrictions above about 63 miles an hour, roughly 101 kilometers an hour. The Senate letter says SpaceX reportedly acknowledged 100 miles an hour. Seventh Corps accounts described drops at 110 to 120 kilometers an hour, lasting 10 to 20 seconds.
- Other unit observations ranged from roughly 72 to 161 kilometers an hour, depending on the platform and conditions. Those experiences don't give every terminal the same cutoff. Zelenskyy also says Ukrainian equipment worked at higher speeds during tests in Europe, which he sees as evidence of a deliberate Ukraine-specific restriction.
- Zelenskyy says the connections support frontline deliveries of food and water, as well as interception of Russian weapons. Taylor describes their use against Russian drones and for targeting Russian firing positions. The officials haven't put a number on lost missions or interceptions.
- Ukraine also sought satellite access over Russian territory to attack ballistic-missile launches. Zelenskyy says that request remains unmet. Opening that territory would expand the service’s geographic reach beyond restoring capabilities already used inside Ukraine.
- Officials disagree about what Ukraine has access to. Starlink is SpaceX’s commercial connectivity service. Starshield is a separate military-grade offering for American government and defense operations. Ukrainian accounts describe restricted existing Starshield access, while Rubio says Ukraine is seeking access it doesn't currently have.
- Trump denies interfering and says the system was operating as usual, as far as he understood. Rubio denies a White House order to reduce access or speed to keep certain drones from using it. Treasury Secretary Scott Bessent repeats their denial.
- Bessent calls Zelenskyy’s accusation “very reckless” and warns him to be careful. He says he doesn't know what caused the satellite disruption or the intelligence-sharing break. His categorical rebuttal addresses the satellite allegation and supplies no explanation for the missing missile warnings.
- Musk says the American military and ultimately the president decide Starshield’s limits. He describes commercial Starlink as limited to civilian or defensive activity, excluding offensive military action. His description of control doesn't tell us whether an order was issued in this case.
- Taylor attributes the interruptions to an administration decision. Rubio rejects an American order to slow Starlink. Their positions conflict, and the dispute also reaches the identity of the service, its permissions and the equipment Ukraine could use.
- Two American officials and a Western official briefed on the matter describe an order originating inside the White House and reaching Defense Department leadership. They identify no individual decision-maker. A senior American official denies that the president made such a request. Zelenskyy says the warning feed now works, but the cause of its absence and the extent of restored satellite capability are still unresolved.
- Nine senators asked the Defense Department’s inspector general, Platte Moring the Third, to investigate on October 15. Jeanne Shaheen and Thom Tillis led the bipartisan request. It covers communications, intelligence sharing and warning capabilities, including possible danger to American personnel.
- Dick Durbin, Susan Collins, Jack Reed, John Cornyn, Chris Coons, Lisa Murkowski and Richard Blumenthal also signed. They want to know who directed, approved or knew about changes, whether SpaceX complied with its contracts, what notifications occurred, and what corrective measures are needed.
- The senators also raise allegations that American diplomatic, military and security personnel couldn't reach designated bunkers during Russian air raids. They want the effects on those personnel and Ukraine’s defenses examined. The inspector general hasn't publicly confirmed opening an investigation.
- Zelenskyy says he's ready for talks with American negotiators around October 20 or 21, following an American signal that a meeting could happen. Those dates are tentative, and nobody has committed to resolving either disruption through those talks.
- The senators want written confirmation of the investigation’s status and an initial briefing by November 1, 2026. They asked for an immediate investigation. Their deadline is for that response and briefing, with no promised date for final findings.
Sources
148 sources85 outlets5 videos4 wire copies
Source map
Follow the evidence behind this report. The map shows its connections; the links below open the sources cited in this article.
Source map loads as you read.
Revision log
- r1First published.
