Crusoe

First posted only after it was over

4% 2 of the 50 incidents we have in full detailbetterworse

The first update already said resolved. Typical vendor: 6%.

Crusoe: around the middle.

Time to resolve

3 h 54 min median; 9 in 10 within 4.2 daysbetterworse

From the vendor’s own start and resolve times, last 365 days. Typical vendor: 2 h.

Crusoe: higher than most vendors.

Major or critical incidents

0.9 a month 11 in the last 365 daysbetterworse

Impact as the vendor labels it. Typical vendor: 1.2 a month.

Crusoe: around the middle.

Rewrites caught

None so far

Counts, not a rate: 10-minute tracking began Oct 17, so there are too few events to compare yet.

Crusoe depends on

Runs in (named in its incidents): Google Cloud us-east1 (13), Google Cloud us-east2 (3), AWS us-east-1 (2).

Outage events: Cloudflare, Nov 18, 2025 (timing), Google Cloud, Jun 12, 2025 (timing).

Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.

Full Crusoe change history

No pricing, trust or legal pages tracked for Crusoe.

Each change links to its diff: the changed passages with a few words of context, never a full copy of the page.

Crusoe incidents, last 90 daysJSONMarkdown