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.
State
Investigating
Started
10 d ago
2026-10-22 21:32 UTC
Ongoing for
10 days
Worst impact
Partial outage
Timeline
1 updateInvestigating
10 days 100%
Updates
Times in UTCAs posted by CoreWeave
Power has been restored at US-EAST-15A, and we're working to stabilize the site. Most affected nodes are back in service, and we're bringing the remaining nodes back online. We'll continue to monitor the site and share updates as recovery progresses.
Affected components
5CoreWeave in the last 90 days
Full historyIncidents in 90 days
1
Days with an incident
11
Median duration
Not enough data
This incident
Not comparable
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.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.
https://outages.cc/feed.xml?providers=coreweave/feed subscribe https://outages.cc/feed.xml?providers=coreweaveFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane