outages.live
Live
CrusoeIncident · 2026-09-03 12:30 UTC

Networking issue affecting service connectivity

ResolvedOfficial update

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

The latest update from Crusoe.

State

Resolved

Started

59 d ago

2026-09-03 12:30 UTC

Lasted

1 min

until 2026-09-03 12:30 UTC

Worst impact

Notice

Timeline

1 update
12:3012:3012:3012:3012:31
NoticeUpdate postedTimes in UTC

Resolved

1 min 100%

Updates

Times in UTC

As posted by Crusoe

Resolved2026-09-03 12:30 UTC

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

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

100% shorter than 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·Storage accessibility issues in eu-norway1

This incident has been resolved.

Resolvedresolved 33 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·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