outages.live
Live
CrusoeIncident · 2026-09-29 20:38 UTC

Storage accessibility issues in eu-norway1

ResolvedOfficial update

This incident has been resolved.

The latest update from Crusoe.

State

Resolved

Started

33 d ago

2026-09-29 20:38 UTC

Lasted

3 h 54 min

until 2026-09-30 00:32 UTC

Worst impact

Major outage

Timeline

4 updates
20:3821:3722:3523:3300:32
Major outageUpdate postedTimes in UTC

Investigating

40 min 17%

Identified

2 h 25 min 62%

Monitoring

49 min 21%

Updates

Times in UTC

As posted by Crusoe

Resolved2026-09-30 00:32 UTC

This incident has been resolved.

Monitoring2026-09-29 23:43 UTC

Shared Storage, Object Storage and Crusoe Container Registry in eu-norway1 are available again. We have put a fix in place with our storage vendor and are monitoring the results. We will share another update once we confirm the service is stable.

Identified2026-09-29 21:18 UTC

We are seeing early signs of recovery for Shared Storage, Object Storage and Crusoe Container Registry in eu-norway1. We are still working closely with our storage vendor to fully restore service and will share another update as progress continues.

Investigating2026-09-29 20:38 UTC

We are currently investigating storage accessibility issues when using Shared Storage, Object Storage and Crusoe Container Registry in eu-norway1. We are working with our storage vendor to resolve the issue as soon as possible and will keep you posted on further developments.

Affected components

2
Shared DisksStorage - Shared Disks

Crusoe in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

5

Days with an incident

9

Median duration

3 h 54 min

This incident

About the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

3 days
median 3 h 54 min
90 days agoToday

Other Crusoe incidents

All incidents

Crusoe·Facility issue in us-east2-a

This incident has been resolved.

Resolvedresolved 14 d ago

Crusoe·A subset of VMs are showing as UNSPECIFIED in our us-east2 region

This incident has been resolved.

Resolvedresolved 53 d ago

Crusoe·Networking issue affecting service connectivity

We identified general network errors affecting service connectivity in our us-east1 region. The issue has been resolved and services are operating normally.

Resolvedresolved 59 d ago

Crusoe·VM and CMK cluster creation issue in us-east2 region

This incident has been resolved.

Resolvedresolved 60 d ago

Follow Crusoe

Your coding agent knows when Crusoe is down, and tells you when a failure is theirs, not yours. You can also get Crusoe incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "crusoe" and tell me if Crusoe has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=crusoe
Slack
/feed subscribe https://outages.cc/feed.xml?providers=crusoe

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane