C
Outage recap · Crusoe

Crusoe outage — May 4, 2026

On May 4, 2026, Crusoe had a reported incident on Crusoe's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

503 errors when accessing the Crusoe Compute Console and API

minor
Started
May 4, 6:26 PM EDT
Resolved
May 4, 7:29 PM EDT
Duration
1h 3m

Crusoe's updates (3)

  1. monitoring · May 4, 6:26 PM EDT

    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 · May 4, 6:26 PM EDT

    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 · May 4, 7:29 PM EDT

    This incident has been resolved.

Updates are Crusoe's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗

AIDownCheck is not affiliated with Crusoe. This recap summarizes incidents published on Crusoe's official status page.