Crusoe incident

Disruption to Cluster Management Services in us-southcentral Region

Minor Resolved View vendor source →

Crusoe experienced a minor incident on March 4, 2026 affecting API, lasting 1h 49m. The incident has been resolved; the full update timeline is below.

Started
Mar 04, 2026, 07:36 PM UTC
Resolved
Mar 04, 2026, 09:25 PM UTC
Duration
1h 49m
Detected by Pingoru
Mar 04, 2026, 07:36 PM UTC

Affected components

API

Update timeline

  1. investigating Mar 04, 2026, 07:36 PM UTC

    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 04, 2026, 09:25 PM UTC

    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 04, 2026, 09:25 PM UTC

    This incident has been resolved.