Crusoe reported "Storage issue in eu-norway1" on its status page at 2026-11-09 14:32 UTC. Crusoe reports degraded Shared Disks in eu-norway1. The issue is resolved. It lasted 1 hour and 12 minutes.

Crusoe lists these components: Shared Disks, Storage - Shared Disks.

When did the incident start and end?

It started at 2026-11-09 14:32 UTC and ended at 2026-11-09 15:44 UTC. It lasted 1 h 12 min.

How do I get alerts for Crusoe?

Subscribe to the Crusoe live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Crusoe. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

CrusoeIncident ·

Storage issue in eu-norway1

ResolvedOfficial update

Crusoe reports degraded Shared Disks in eu-norway1. The issue is resolved. It lasted 1 hour and 12 minutes.

State

Resolved

Started

Lasted

1 h 12 min

Worst impact

Degraded

Timeline

2 updates

14:3214:5015:0815:2615:44

DegradedUpdate postedTimes in UTC

Investigating

1 h 12 min 100%

Updates

Times in UTC

As posted by Crusoe

Resolved

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

Investigating

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.

Affected components

Shared DisksStorage - Shared Disks

Crusoe in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

2 h 38 min

This incident

55% shorter than the median

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

3 days

median 2 h 38 min

90 days agoToday

Other Crusoe incidents

All incidents

Crusoe·Compute issue in eu-norway1

A compute issue affects GPU Virtual Machines in eu-norway1. Crusoe has identified the issue and continues work to restore service. Some affected instances are restored.

Partial outage

Crusoe·Facility issue in us-east2-a

This incident has been resolved.

Resolved

Crusoe·Storage accessibility issues in eu-norway1

This incident has been resolved.

Resolved

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

This incident has been resolved.

Resolved

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.

Resolved

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.live/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.live/feed.xml?providers=crusoe

Slack

/feed subscribe https://outages.live/feed.xml?providers=crusoe

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane