C
Outage recap · Crusoe

Crusoe outage — November 9, 2026

On November 9, 2026, Crusoe had 2 reported incidents on Crusoe's official status page. Below is what was reported — impact, timing, and the AI services the same upstream outage could affect.

Storage and Compute issue in eu-norway1

minor
Started
Nov 9, 9:32 AM EST
Resolved
Nov 9, 10:44 AM EST
Duration
1h 12m

Crusoe's updates (2)

  1. investigating · Nov 9, 9:32 AM EST

    We are investigating an issue in eu-norway-1 that may impact storage. We are not aware of any data loss. We will provide updates as more information becomes available.

  2. resolved · Nov 9, 10:44 AM EST

    This issue is resolved. If you are still seeing issues, please contact support.

What our checks recorded

We checked Crusoe 14 times from Crusoe's start time to its resolution, once every five minutes. Every one of them reached Crusoe's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 648 ms, against 646 ms over the 24 hours before. Crusoe posted the incident at Nov 9, 9:32 AM EST.

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

Compute issue in eu-norway1

major
Started
Nov 9, 10:49 AM EST
Resolved
Nov 10, 8:24 PM EST
Duration
33h 35m

Crusoe's updates (3)

  1. identified · Nov 9, 10:49 AM EST

    We have identified an issue in eu-norway-1 impacting compute and are working to restore service. We will provide updates as more information becomes available.

  2. identified · Nov 9, 5:05 PM EST

    We are continuing to work to restore service. Recovery is progressing; some affected instances are restored. We will provide updates as recovery progresses.

  3. resolved · Nov 10, 8:24 PM EST

    This issue is resolved. If you are still seeing issues, please contact support.

What our checks recorded

We checked Crusoe 403 times from Crusoe's start time to its resolution, once every five minutes. Every one of them reached Crusoe's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 648 ms, against 643 ms over the 24 hours before. Crusoe posted the incident at Nov 9, 10:49 AM EST.

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.