outages.live
Live
CoreWeave logoCoreWeaveIncident · 2026-11-02 16:59 UTC

Object Storage Service Degradation in US-EAST-04

Partial outageOfficial update
0

CoreWeave Object Storage has a degradation in US-EAST-04. Some customers can see intermittent request failures. CoreWeave reports the status as investigating and states that the team identified the root cause and is working on a fix.

State

Investigating

Started

2 h ago

2026-11-02 16:59 UTC

Ongoing for

1 h 45 min

Worst impact

Partial outage

Timeline

1 update
16:5917:2517:5118:1718:44
Partial outageUpdate postedTimes in UTC

Investigating

1 h 45 min 100%

Updates

Times in UTC

As posted by CoreWeave

Investigating2026-11-02 17:18 UTC

We’re currently experiencing a degradation in the CoreWeave Object Storage Service in US-EAST-04, which may result in intermittent request failures for some customers. Our team has identified the root cause and is actively working on a fix to restore full functionality as quickly as possible. If you have any questions or concerns in the meantime, please don’t hesitate to reach out to us at support@coreweave.com

Affected components

2
CoreWeave Object StorageUS-EAST-04

CoreWeave in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

2

Days with an incident

12

Median duration

Not enough data

This incident

Not comparable

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

11 days
90 days agoToday

Other CoreWeave incidents

All incidents
CoreWeave logo

CoreWeave·Facility power incident impacting services in US-EAST-15A

A facility power incident affects CoreWeave Infrastructure, Object Storage, Services, Inference, and US-EAST-15 in US-EAST-15A. CoreWeave reports that power is restored at the site and that the team is stabilizing it. CoreWeave is still investigating, most affected nodes are back in service, and the remaining nodes are coming back online.

Partial outageupdated 8 d ago

Follow CoreWeave

Your coding agent knows when CoreWeave is down, and tells you when a failure is theirs, not yours. You can also get CoreWeave 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 "coreweave" and tell me if CoreWeave 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=coreweave
Slack
/feed subscribe https://outages.cc/feed.xml?providers=coreweave

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane