A Man to
End All Wars?

Ukraine · the ceasefire claim and the satellite restrictions

While Trump pursued recognition, Ukraine’s connection faltered.

For Ukrainian troops, satellite connection is part of the machinery of survival. It carries orders, links operators to drones, and helps units communicate under fire.

Before those connections faltered, Trump had struck a diesel deal with Putin, announced an energy ceasefire that surprised Kyiv, and insisted it existed while Russian attacks continued. Ukraine was being pressed to stop hitting the refineries that helped finance its invader. Then came restrictions on the service its own forces needed to fight.

1. October 9–10, 2026

   Ukraine hit Russian oil. Trump opened the market for Russian diesel.

   Ukrainian drones had been reaching deep into Russia’s oil industry. Strikes on the Omsk and Ukhta refineries were reported on October 8 and 9; an attack on the Novoshakhtinsk oil terminal followed on October 10. These were blows against the infrastructure behind Russia’s war economy.

   On October 9, the US Treasury authorized transactions in Russian diesel that sanctions had previously prohibited. Trump’s administration was easing pressure on Russian fuel sales just as Ukraine was trying to increase it.

   At home, high fuel prices were a political liability with the midterms approaching. AP reported that Trump blamed Ukrainian refinery attacks for record US diesel prices and made the Russian deal in an attempt to bring them down. Zelensky disputed that explanation, pointing instead to the blockade of the Strait of Hormuz. The president’s search for cheaper fuel had put him at odds with Ukraine’s campaign against Russian oil.

2. October 11, 2026

   A ceasefire announced before Kyiv knew about it.

   Trump went on Truth Social to announce an immediate energy ceasefire. His post said Russia and Ukraine had both agreed. A senior Ukrainian official told the Kyiv Independent that Kyiv had no information about it. Zelensky said Ukraine was ready to accept a deal if Trump had negotiated one with Putin, and asked when it would begin.

   Within hours, Russia struck a power plant in Kharkiv. Zelensky also reported attacks on a gas production facility and a civilian gas station. Ukraine had held back its own attacks, he said. Russia had not. The Kremlin subsequently declined to confirm the agreement Trump had announced.

3. October 12, 2026

   “Because I said they agreed.”

   On the White House South Lawn, before boarding Marine One, Trump was asked about the gap between his announcement and what the two countries were saying. His answer was extraordinary: “Because I said they agreed.”

   Pressed about Russian attacks, he said he would have to look into them, then referred to violations on both sides. He offered no evidence for that claim. Ukrainian energy facilities had been hit after his announcement; his public answer was to insist that his own declaration settled whether there was a deal.

   ▶Play: Trump answers reporters before boarding Marine One

4. October 12–13, 2026

   The pressure was on Kyiv to stop firing back.

   The Kyiv Independent reported a more direct message behind the scenes. Two Ukrainian officials said their American counterparts had threatened intelligence sharing and the PURL program if Ukraine struck Russian energy infrastructure. PURL supplies American weapons financed by European and other NATO partners. The threat therefore reached beyond information: it concerned the arms Ukraine could obtain through its allies.

   Those officials spoke anonymously. On October 13, Trump publicly said the United States was still sharing intelligence with Ukraine. Asked whether Russian diesel revenue could pay for more bombs, he sidestepped the question and defended releasing the fuel onto the world market.

5. October 14, 2026

   Then the connections faltered. Musk pointed to Washington.

   Ukrainian officials sought the removal of new restrictions affecting military satellite use, including a speed limit that interfered with drones. The dispute concerned military operations, not a documented shutdown of every Starlink terminal in Ukraine.

   Starlink is SpaceX’s satellite network. Starshield is its government and defense offering, whose use in Ukraine is subject to American government control. Musk said the Starshield systems belonged to the US government and rejected responsibility for the restrictions.

   “Any limits on speed or usage are decided by the US military and ultimately POTUS,” he wrote on X. His answer directed the question of responsibility straight back to the American government, including the president.

6. October 15–16, 2026

   An order from inside the White House. An explanation still missing.

   Reuters reported on October 15 that the order to limit Starshield service came from inside the White House, citing two US officials and a Western official. A senior US official, also speaking anonymously, denied that Trump had requested it. The reporting did not identify who issued the order. Reuters did not establish whether Musk had proposed the restrictions.

   There were signs of recovery, but no clear all-clear. On October 15, a Ukrainian Defense Ministry source told the Kyiv Independent that mobile Starshield service had been restored; the source did not say whether every restriction had gone. Reuters’ October 16 reporting described disruption felt on the front line and Zelensky’s assessment that service had improved without fully recovering.

   Ukraine, meanwhile, resumed strikes on Russian refineries. An October 15 drone attack started a fire at the Ryazan refinery, according to Russian authorities cited by AP, after Zelensky abandoned the energy truce that Moscow had failed to honor.

7. October 16, 2026 · New reporting

   Musk pointed to Washington. Sources say the proposal began with him.

   Musk had pointed to Washington. On October 16, The Telegraph reported that four sources familiar with the discussions said he had approached Trump with the proposal to restrict Ukraine’s satellite service. One source said Trump agreed, clearing the way for the Pentagon to act on Starshield.

   That account puts Musk at the start of a decision he had publicly attributed to the US military and ultimately the president. Trump denied responsibility that day and said he did not think Musk was responsible either. The Pentagon had not publicly explained the restrictions; The Telegraph said it had approached SpaceX for comment.

   The speed limit concerned how fast a connected terminal could move — a crucial constraint for drones — rather than simply slower downloads. For Ukrainian forces, the consequences were immediate. The dispute over responsibility was still unresolved.

8. October 20, 2026 · New reporting

   Musk pointed to Washington. The reporting points back to him.

   Musk said the president controlled the service. New reporting puts Musk himself behind the restrictions.

   On October 20, The Wall Street Journal reported that Musk ordered the restrictions. Its sources described conversations with Trump after the disruption became public; one said Musk had discussed Ukraine with Trump and senior officials beforehand. Others said he acted independently. The report did not establish that Trump ordered the restrictions.

   CBS separately reported that Musk made the decision, citing informed sources.

   

   Speaking on CNN, Journal reporter Alexander Ward said his team did not know what was said in the conversation before the decision. He also described SpaceX approaching the White House after the restrictions became public to coordinate their response. Some officials had believed Musk acted alone.

   The Telegraph had reported four days earlier that Musk proposed the restrictions and Trump agreed. The newer accounts add to the questions about Trump’s involvement. Musk’s role is coming into sharper focus. What Trump knew, and what he authorized, still needs an answer.

9. October 21, 2026 · The unanswered questions

   Washington calls it a company decision. Senators want the records.

   The administration’s explanation shifted again. On October 20, Defense Secretary Pete Hegseth pointed to SpaceX’s terms of service and denied that the Pentagon had issued a directive. The following day in Mumbai, Secretary of State Marco Rubio called the restrictions a private company’s decision and denied that the government had directed them or known about them in advance.

   Rubio also acknowledged that Starshield supplied under a US military contract was a different matter. Senators are asking what those contracts allow SpaceX to change, and who is authorized to approve it.

   Four Democratic senators had already asked SpaceX to hand over the records. Their October 19 letter sought the names of the decision-makers, the restrictions imposed between October 10 and 15, the company’s communications with the US government and the contracts governing Ukraine’s access. They set a November 2 deadline. Those records could show who had the authority to act, who used it and who was told.

   Meanwhile, Kyiv was still asking for the service back. Zelensky’s office said his October 20 call with Rubio covered restoring Starlink and Starshield, alongside interceptors and early warnings of Russian missile attacks. That statement did not announce a full restoration of the satellite service. Ukrainian forces needed working equipment while Washington argued over responsibility.

10. October 22, 2026 · New reporting

    Witkoff praised Putin. Hours later, missiles hit Kyiv.

    On October 21, Steve Witkoff sat with Vladimir Putin in St. Petersburg and called him a humanitarian. Trump’s envoy was thanking Putin for releasing Stephen Hubbard, a 75-year-old American teacher held in a Russian prison. “You are a humanitarian also, sir, and I salute that,” Witkoff told him.

    The Kremlin said Putin was willing in principle to resume talks with Ukraine and the United States in November. The meeting also covered the Russian diesel deal Trump had struck with Putin on October 9. No date for the peace talks was set.

    Hours later, Russia bombarded Kyiv. Zelensky said 21 ballistic missiles arrived in three waves, hitting homes, energy facilities and transport infrastructure. By October 22, Ukrainian officials reported at least four people killed across the country and dozens wounded. Putin had offered more talks; Ukrainians were pulling people from another night of wreckage.

    Follow the wider record: Russia and the Trump circle →︎ · The military decisions behind the diplomacy →︎.

11. October 23, 2026 · New reporting

    Trump said Musk had restored the service. Ukraine said the limits remained.

    Trump was ready to call the problem solved. On October 22, he told reporters that Musk had restored Ukraine’s military satellite service: “I guess the bottom line is he put it back.” He declined to say whether he had personally asked Musk to act.

    The Wall Street Journal reported that Trump called Musk on October 21 and asked him to lift the restrictions, citing US officials. Some US and Ukrainian officials reported better performance after the call, the paper said, but not a full restoration.

    By October 23, Ukrainian officials were still reporting failures. Presidential adviser Serhiy Beskrestnov said he had seen no lifting of the restrictions. A Ukrainian Defense Ministry source told CNN that connections were still dropping when equipment moved faster than 100 mph. A Ukrainian officer described outages of 10 to 15 seconds that disrupted coordination, and unusually heavy losses of drones and other equipment. The service Trump said was back was still failing the people who needed it.

Russia received sanctions relief. Ukraine was asked to spare Russian energy sites while its own were still being attacked, faced reported threats to weapons and intelligence support, and then had to seek the restoration of military satellite service. That sequence explains why restoring the connection would not settle the argument. The restrictions had exposed how much of Ukraine’s defense depended on decisions made in Washington and inside SpaceX.