Crusoe experienced a minor incident on October 9, 2025 affecting us-east1 and us-northcentral1 and 1 more component, lasting 5d 2h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 09, 2025, 09:37 PM UTC
We have identified an issue that is preventing new or restarted Virtual Machines from booting successfully. Existing, currently running VMs are operational. We advise customers to avoid rebooting critical workloads until a resolution is in place. Our engineering teams are actively investigating the root cause and are working to restore normal provisioning operations as quickly as possible.
- investigating Oct 09, 2025, 09:38 PM UTC
We are continuing to investigate this issue.
- investigating Oct 10, 2025, 01:59 AM UTC
We have determined that the problem is sporadic and limited to a specific subset of our host nodes. Existing, currently running VMs are operational. We still strongly recommend customers avoid rebooting critical workloads until the permanent fix is confirmed to be fully deployed. If you are currently experiencing issues with starting or restarting VMs, please open a support ticket so we can immediately address your specific host. We will provide another update once the targeted fix has been deployed to the identified hosts and we have confirmed stability.
- investigating Oct 10, 2025, 02:02 AM UTC
We are continuing to investigate this issue.
- investigating Oct 14, 2025, 11:42 PM UTC
We are continuing to investigate this issue.
- resolved Oct 14, 2025, 11:43 PM UTC
Update: The issue is now resolved. The engineering team has implemented a fix and confirmed that normal provisioning operations have been restored.