C
Outage recap · Crusoe

Crusoe outage — March 4, 2026

On March 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.

Disruption to Cluster Management Services in us-southcentral Region

minor
Started
Mar 4, 2:36 PM EST
Resolved
Mar 4, 4:25 PM EST
Duration
1h 49m

Crusoe's updates (3)

  1. investigating · Mar 4, 2:36 PM EST

    We are investigating an issue in our US-Southcentral region that may be impacting the ability to manage cluster resources via the API. Our engineering team is actively working to identify the scope and cause. We will provide another update as more information becomes available.

  2. investigating · Mar 4, 4:25 PM EST

    We are pleased to report that this incident is now resolved. We have confirmed that control plane functionality for all impacted clusters in the us-southcentral region has been fully restored. The issue was caused by network congestion on a small number of underlying physical hosts. This has been remediated by isolating the source of the traffic. We will be conducting a full post-mortem to prevent a recurrence and apologize for any disruption this incident caused.

  3. resolved · Mar 4, 4:25 PM EST

    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.