Storage Incident
CoreWeave Object Storage shows degraded performance in US-EAST-04A. Some customers can see elevated error rates (HTTP 500) or timeouts on object storage requests, especially uploads. CoreWeave reports that it is investigating.
State
Investigating
Started
Ongoing for
1 h 4 min
Worst impact
Degraded
Timeline
1 updateInvestigating
1 h 4 min 100%
Updates
Times in UTCAs posted by CoreWeave
Hello, We are investigating degraded performance with CoreWeave AI Object Storage in US-EAST-04A. Some customers may see elevated error rates (HTTP 500) or timeouts on object storage requests, especially uploads. Our engineering teams are actively working on it. We will provide an update as soon as we have more information. 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
2CoreWeave in the last 90 days
Full historyIncidents in 90 days
4
Days with an incident
23
Median duration
10 days
This incident
100% shorter than the median
Other CoreWeave incidents
All incidents
CoreWeave·Storage Service Degradation
CoreWeave Premium Shared Filesystem Volumes in US-EAST-13 do not fully work. CoreWeave reports that the incident is resolved. The outage lasted from 5 November 2026 to 12 November 2026.
CoreWeave·Object Storage Service Degradation in US-EAST-04
CoreWeave Object Storage in US-EAST-04 had a partial outage. Some customers saw intermittent request failures. CoreWeave reports that the issue is resolved, and it lasted from November 2 to November 12, 2026.
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.
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.
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.
https://outages.live/feed.xml?providers=coreweave/feed subscribe https://outages.live/feed.xml?providers=coreweaveFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane