DTDumpTrumpVerified facts, not vibes.
Election Day is Tuesday, November 3.I'm a voter. Make my plan →
The record

Musk's SpaceX throttled Ukraine's Starlink from Oct. 14; CBS photos show air-defense radars at 0.1 Mbps the day a Russian drone killed five in Kharkiv

The 30-second version

On the night of October 14, 2026, SpaceX restricted Ukraine's use of Starlink and of Starshield, the military version that runs on the same satellites, without warning Ukraine's armed forces; Ukrainian units reported drones losing their link at speeds as low as 90 km/h [2][5].

People familiar with the matter told CBS News the restriction followed a decision by Elon Musk, made after he spoke with administration officials several times seeking clarity on the president's thinking [2].

On October 24 Musk confirmed it, writing that Ukraine's military had "violated Starlink terms of service and used it for offensive drone strikes to kill people" and that "that loophole was closed last week" [1][3].

Numbers in brackets are the sources, listed at the end.

CBS photos show Ukraine's air-defense radar Starlink links at 0.1 Mbps on Oct. 19, the day a Russian drone killed five in Kharkiv; Musk admits SpaceX throttled service from Oct. 14. Pentagon denies ordering it; probes requested.

About this story Reporting · October 19, 2026 · rev. 1
People and organizations
Elon Musk, SpaceX, Department of Defense, Pete Hegseth, Marco Rubio, Volodymyr Zelensky, Government of Ukraine, Government of Russia, Trump administration, United States Congress
Places
United States, Ukraine, Russia
Evidence label
Reporting — Original reporting by an identified news organization that we opened and dated. Investigative findings are attributed to the outlet, not asserted as adjudicated fact. More

What happened

On the night of October 14, 2026, SpaceX restricted Ukraine's use of Starlink and of Starshield, the military version that runs on the same satellites, without warning Ukraine's armed forces; Ukrainian units reported drones losing their link at speeds as low as 90 km/h [2][5]. People familiar with the matter told CBS News the restriction followed a decision by Elon Musk, made after he spoke with administration officials several times seeking clarity on the president's thinking [2]. On October 24 Musk confirmed it, writing that Ukraine's military had "violated Starlink terms of service and used it for offensive drone strikes to kill people" and that "that loophole was closed last week" [1][3].

On October 19, a Russian Geran-4 jet-powered drone hit a park in the Kharkiv region, killing five people, among them a 34-year-old makeup artist and a one-year-old girl [1]. Photographs obtained by CBS News show the Starlink connection for Ukraine's ground-based air-defense radars at 0.1 megabytes per second that day, a speed a source familiar with the technology said "would not be enough to load a webpage, let alone power air defense radars" [1].

Why it matters

Ukrainian officials told CBS the restrictions affected air-defense radars and drone interceptors and hindered the military's ability to stop incoming strikes [1]. Vadym Ivchenko, a member of parliament on the National Security, Defense and Intelligence Committee, called the link "an essential part of the air defense infrastructure" while adding, "I couldn't say that all other air defenses stopped working, no" [1]. CBS does not claim the throttling caused the Kharkiv deaths, and neither does this story [1].

Response and counterpoints

The question Congress is now asking is who decided. Defense Secretary Pete Hegseth said the Pentagon "has not manipulated the service," and officials inside the administration told CBS that neither President Trump nor the Pentagon ordered limits meant to disrupt Ukraine's operations [2]. Secretary of State Marco Rubio said on October 25 that "nobody ordered that Starlink speed to be slowed down. It sort of happened" [4]. Musk, for his part, said the U.S. government controls whatever changes happen to Starshield [1]. A bipartisan group of senators has asked the Pentagon's inspector general to investigate whether officials directed or authorized the changes [2], and Republican Rep. Mike Turner of the House Armed Services Committee said on CBS's "Face the Nation" that "there needs to be a congressional investigation" [6].

The evidence

The core record is CBS reporting from Kyiv and Washington over October 20 to 27: sourced accounts that Musk's decision led to the throttling, Musk's own public admission, and photographs of radar-link speeds on the day of the Kharkiv strike [1][2][3]. Zelenskyy said on October 24 that speeds had been restored, while Ukraine's top diplomat in Washington said the same day that Kyiv had received no response from the Pentagon or SpaceX and "cannot confirm that these capabilities have been fully restored" [3][4].

A related but separate claim is that U.S. intelligence warnings of Russian strikes stopped arriving around October 13 and 14. Ukrainian officials told CBS they received no warning before strikes that killed six and cut power to 600,000 people, and sources said the warnings may have been deliberately withheld; CBS reported that this had not been established, and a senior Pentagon official said there had been "no change to Department of War policy regarding intelligence sharing" [5][4].

What remains uncertain

Fundraising messages circulating this week say a CBS investigation found the Department of War is deliberately disabling Starlink ahead of Russian strikes and that the U.S. is coordinating with Russian military intelligence. The CBS reporting cited here does not say that: it attributes the throttling to a Musk decision, records denials from the Pentagon, the White House and Rubio, and treats the intelligence-warning gap as reported but unproven [2][4][5]. What is established is narrower and still serious: the service was throttled for more than a week, Ukraine's radar links were near zero on a day civilians died, Musk has admitted the throttling, and both the Pentagon inspector general and members of Congress are being asked who authorized it [1][2][3][6].

Sources cited