Critical incident

Desktop Commander: Devices unable to connect to Remote Desktop Commander

Current status of Desktop Commander: Operational — live Desktop Commander status

Timeline

1. Oct 13, 2026, 13:01 UTC
   investigating
   Some devices can’t connect to Remote Desktop Commander, and tool calls to those devices are timing out. We’re investigating.
2. Oct 13, 2026, 13:10 UTC
   identified
   The cause is overload on a realtime service run by our infrastructure provider. They are reducing the load and adding capacity.
3. Oct 13, 2026, 19:16 UTC
   identified
   Our provider is setting up a new cluster for our traffic. Devices that are already connected mostly work, but new connections still fail for many users. We’ll post an update before we move to the new cluster.
4. Oct 13, 2026, 22:34 UTC
   identified
   We’re moving to the new cluster now. Expect a full interruption of 5 to 15 minutes.
5. Oct 13, 2026, 22:42 UTC
   identified
   The move is complete and devices are reconnecting. We’re monitoring.
6. Oct 13, 2026, 23:33 UTC
   monitoring
   Connections are back to normal. We’re keeping an eye on it.
7. Oct 14, 2026, 11:19 UTC
   resolved
   Connections have been stable since the move to the new cluster. This incident is resolved. If a device still can’t connect, please contact support.

Updates as published by Desktop Commander.