Crusoe outage history

We hold 52 Crusoe incidents from Crusoe's status page, the newest from Nov 9, 2026. 52 of the 52 listed carry Crusoe's own update timeline. Each one links to a page with the vendor's updates and what our five-minute checks recorded while it was open.

Uptime & history

Tracking since Jun 22, 2026
Currently up for 8d 6h since the last recorded problem.
Operational · 24h
100%
0 incidents · no downtime
288 checks
Operational · 7d
98.81%
0 incidents · no downtime
2015 checks
Operational · 30d
93.22%
2 incidents · ≈1d 10h degraded
8638 checks
Operational · since Jun 22, 2026
86.37%
10 incidents · ≈5d 17h degraded
41572 checks

% of our checks that found Crusoe fully operational — a degraded check counts against it, because a slow or partly-broken service is not a working one. Down and degraded time are counted at our 5-minute check resolution, so both are approximate. Longer windows fill in as data accrues — we never show uptime we haven't measured.

Recent checks
oldernow
Past incidents

How Crusoe fails

Since Jul 1, 2026, Crusoe's status page has marked 5 Crusoe components as impaired, across 2,071 of our five-minute readings. us-east2 accounts for the most: 966 readings (about 81 hours) on 5 days, 307 of them marked as an outage rather than degraded, most recently on Oct 18, 2026. Next is Datacenter Networking, with 444 readings on 3 days. We hold 52 Crusoe incidents from Crusoe's status page, the earliest from May 30, 2025. Of the 50 that Crusoe closed with an end time, the median lasted 3 h 50 min.

ComponentOutageDegradedMaint.DaysLast
us-east2307659105Oct 18, 2026
Datacenter Networking307137—3Oct 16, 2026
eu-norway1—404102Nov 10, 2026
Container Registry—1961651Nov 12, 2026
Shared Disks4615—3Nov 9, 2026
eu-iceland1——346313Oct 6, 2026
VPC Networking——45211Nov 10, 2026
Wide Area Networking (WAN)——42610Oct 20, 2026

Incidents by month: May 2026: 8 · Jun 2026: 5 · Jul 2026: 2 · Sep 2026: 4 · Oct 2026: 1 · Nov 2026: 2

Counts are five-minute readings of Crusoe's own component statuses, recorded only when a component is not operational. Hours are readings times five minutes, so a gap in our recording would undercount, never overcount.

Every recorded incident

November 2026 · 2

October 2026 · 1

September 2026 · 4

June 2026 · 5

May 2026 · 8

April 2026 · 2

February 2026 · 5

December 2025 · 3

November 2025 · 1

October 2025 · 4

September 2025 · 4

August 2025 · 1

June 2025 · 3

May 2025 · 1

Incidents and their updates are Crusoe's own words from its status page, recorded every five minutes; we never add an inferred cause. AIDownCheck is independent and not affiliated with Crusoe.