outages.live
Live
CoreWeave logoCoreWeaveIncident ·

Storage Service Degradation

DegradedOfficial update
0

CoreWeave Premium Shared Filesystem Volumes do not fully work in US-EAST-13. CoreWeave reports that the issue is under investigation. CoreWeave later reports that the issue is mitigated and monitoring continues.

State

Investigating

Started

Ongoing for

1 h 29 min

Worst impact

Partial outage

Timeline

2 updates
15:1315:3515:5816:2016:42
Partial outageDegradedUpdate postedTimes in UTC

Investigating

1 h 29 min 100%

Updates

Times in UTC

As posted by CoreWeave

Investigating

We believe the issue has been mitigated, and we are continuing to monitor the affected services. If you are experiencing an issue or have any further questions please reach out to support@coreweave.com.

Investigating

Investigating Hello, We are actively investigating an issue that is impacting our storage services in US-EAST-13A. As the situation evolves, we will continue to update our customers on the matter. If you have any questions, we encourage you to reach out to support by email: support@coreweave.com We apologize for any inconvenience this may cause and thank you for your patience while we work to resolve the matter in a timely manner. Thank you, CoreWeave Support

Affected components

2
CoreWeave Premium Shared Filesystem VolumesUS-EAST-13

CoreWeave in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

3

Days with an incident

15

Median duration

11 days

This incident

99% shorter than the median

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

11 days
median 11 days
90 days agoToday

Other CoreWeave incidents

All incidents
CoreWeave logo

CoreWeave·Object Storage Service Degradation in US-EAST-04

CoreWeave Object Storage has degraded performance in US-EAST-04. Some customers may see intermittent request failures. CoreWeave reports that the issue is mitigated and requests complete normally again while the team finishes a configuration fix and monitors stability.

Partial outage
CoreWeave logo

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

A facility power incident affected CoreWeave Infrastructure, Object Storage, Services, and Inference in the US-EAST-15 region. CoreWeave reports that the incident is resolved. It lasted from 22 October 2026 to 3 November 2026.

Resolved

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.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 "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.live/feed.xml?providers=coreweave
Slack
/feed subscribe https://outages.live/feed.xml?providers=coreweave

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane