503 errors when accessing the Crusoe Compute Console and API

Event timeline

How this incident unfolded, from the official status page.

1. Monitoring

   6 months ago

   Crusoe

   We are investigating an issue causing 503 errors when accessing the Crusoe Compute Console and API. Users may currently be unable to list instances or manage infrastructure resources. Our engineering team is actively working to identify the root cause. Further updates will be provided as soon as they are available.

2. Monitoring

   6 months ago

   Crusoe

   The issues affecting the Crusoe Compute Console, API, and CLI have been fully resolved. Impact Window: The service interruption lasted from 2:42 PM PDT to 3:16 PM PDT. During this window, users may have experienced 503 errors and were unable to view or manage resources via the web console, CLI, or API. Our engineering team identified the issue and implemented a fix to restore all management services. We have verified that all systems are now performing as expected. We are continuing to monitor the platform and will implement additional safeguards and alerting to improve our response and stability moving forward. Note: Active customer workloads and existing infrastructure remained operational and were not impacted by this management-layer interruption.

3. Resolved

   6 months ago

   Crusoe

   This incident has been resolved.