Coreweave Scheduled Cooling System Maintenance - US-EAST-02A
We will perform preventive maintenance on cooling systems in US-EAST-02A, starting November 30, 2026, at 13:30 UTC to December 11, 2026, at 21:00 UTC. Work is expected to take approximately two weeks. Impact: No customer service interruption or disruption to CDU operation is expected. Cooling systems will remain operational, and no shutdowns are planned. We will actively monitor systems throughout the maintenance. If you have questions or require assistance, please contact our support team at support@coreweave.com. This activity is deemed Planned Maintenance under the CoreWeave Terms of Service Maintenance Policy (docs.coreweave.com/policies/terms-of-service/maintenance-policy).
The latest update from CoreWeave.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by CoreWeave
We will perform preventive maintenance on cooling systems in US-EAST-02A, starting November 30, 2026, at 13:30 UTC to December 11, 2026, at 21:00 UTC. Work is expected to take approximately two weeks. Impact: No customer service interruption or disruption to CDU operation is expected. Cooling systems will remain operational, and no shutdowns are planned. We will actively monitor systems throughout the maintenance. If you have questions or require assistance, please contact our support team at support@coreweave.com. This activity is deemed Planned Maintenance under the CoreWeave Terms of Service Maintenance Policy (docs.coreweave.com/policies/terms-of-service/maintenance-policy).
We will perform preventive maintenance on cooling systems in US-EAST-02A, starting November 30, 2026, at 13:30 UTC to December 11, 2026, at 21:00 UTC. Work is expected to take approximately two weeks. No service interruption is expected. Cooling systems will remain operational, and no shutdowns are planned. We will provide updates if the schedule or expected service impact changes.
Affected components
2CoreWeave in the last 90 days
Full historyIncidents in 90 days
3
Days with an incident
22
Median duration
11 days
This incident
Not comparable
Other CoreWeave incidents
All incidents
CoreWeave·Storage Service Degradation
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.
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.
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