Scheduled Power Infrastructure Maintenance - CA-EAST-01A
Details: CoreWeave will perform scheduled power infrastructure maintenance in CA-East-01A between 2 November 2026 at 11:30 UTC and 5 November 2026 at 01:00 UTC. Work will occur in separate maintenance periods within this overall window. Location: CA-East-01A Scope: Install permanent power quality meters and branch circuit monitoring, and complete associated corrective work on Optistax power distribution unit 11E and 11F. Each unit will be isolated individually for up to two days, including overnight isolation where required. Power will be restored and equipment validated before work begins on the next unit. Impact: No customer service interruption or disruption to CDU operation is expected. Equipment supplied by the unit under maintenance will temporarily operate on its remaining redundant power sources. Power redundancy will be reduced during each isolation period and restored after that unit’s work is complete. We will actively monitor systems throughout the maintenance. If you have
The latest update from CoreWeave.
State
Scheduled
Starts
in 23 h
2026-11-02 23:30 UTC
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by CoreWeave
Details: CoreWeave will perform scheduled power infrastructure maintenance in CA-East-01A between 2 November 2026 at 11:30 UTC and 5 November 2026 at 01:00 UTC. Work will occur in separate maintenance periods within this overall window. Location: CA-East-01A Scope: Install permanent power quality meters and branch circuit monitoring, and complete associated corrective work on Optistax power distribution unit 11E and 11F. Each unit will be isolated individually for up to two days, including overnight isolation where required. Power will be restored and equipment validated before work begins on the next unit. Impact: No customer service interruption or disruption to CDU operation is expected. Equipment supplied by the unit under maintenance will temporarily operate on its remaining redundant power sources. Power redundancy will be reduced during each isolation period and restored after that unit’s work is complete. We will actively monitor systems throughout the maintenance. If you have
Affected components
2CoreWeave in the last 90 days
Full historyIncidents in 90 days
1
Days with an incident
12
Median duration
Not enough data
This incident
Not comparable
Other CoreWeave incidents
All incidentsFollow 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