U.S. Secretary of State Marco Rubio said on October 17, 2026, that Ukraine did not have access to Starshield and that its request to use the military satellite service was under discussion. His account differed from Ukrainian officials’ descriptions of an existing service affected by new restrictions on moving terminals.
Speaking at Joint Base Andrews, Rubio distinguished commercial Starlink from Starshield, which he described as a U.S. military product. In the State Department transcript, reproduced by Public Technologies, he said Ukraine had requested Starshield for attacks deep inside Russia. He also denied that the White House had ordered slower Starlink service and said his understanding was that connectivity had returned to its previous level.
Rubio’s description of restored service was based on information he said he had received two days earlier. He did not announce a new agreement granting Ukraine Starshield access or explain how his account related to the military service package described by Ukrainian officials.
Different Accounts of Access and Restrictions
Presidential adviser Serhii Beskrestnov had told the Associated Press on October 16 that Ukraine used a Pentagon-managed Starshield package. He said outages had been fixed but a cap affecting terminals above 160 km/h remained. He also said the service was not used inside Russia. That account differs from Rubio’s description of a request for access to conduct deep strikes.
The reported cap concerns the terminal’s physical speed, rather than simply the rate at which it downloads data. A drone can have a functioning terminal and lose its connection when it exceeds the permitted speed. Restoring connectivity for stationary users would not, by itself, describe the operating conditions for those aircraft.
New Space Economy’s coverage of satellite service control explains the relevant distinction between equipment capability and permission to use a managed network. In this case, the disputed operating condition affects airborne use, making a general statement that service has returned insufficient to establish whether the same missions can resume.
Responsibility and Restoration
The disagreement also concerns responsibility for the restrictions. Reuters reported on October 15, in a story updated October 17, that two U.S. officials and a Western official attributed the instruction to the White House. They did not identify the decision-maker or the person responsible for implementation. A senior U.S. official denied that President Donald Trump had requested the restriction. Rubio subsequently denied that anyone in the White House had ordered it.
Ukraine’s chargé d’affaires in the United States, Denys Sienik, offered a narrower account of service recovery. In an October 16 interview reported by The New Voice of Ukraine the following day, he said performance had improved but continued to fluctuate. He said Kyiv was awaiting confirmation from the Pentagon and SpaceX that the problem had been resolved and service fully restored.
The next steps described by the two governments were different: Rubio referred to discussions about access and intended use; Sienik sought confirmation that an existing service was operating normally. Neither statement supplied a jointly confirmed account of the service available to Ukrainian aircraft.
Useful Books Available on Amazon
