Scheduled CoreWeave Maintenance - RNO2A
CoreWeave will perform scheduled maintenance to update CNI networking in CoreWeave-managed clusters in RNO2A beginning Thursday, November 5, 2026, at 9:00 AM ET (2:00 PM UTC) and continuing through Friday, November 20, 2026, at 5:00 PM ET (10:00 PM UTC). Location: RNO2A We will be actively monitoring the situation during this time. We appreciate your patience and understanding. If you have any further questions or require assistance, please don't hesitate to reach out to our support team at support@coreweave.com This activity is deemed Planned Maintenance under the CoreWeave Terms of Service Maintenance Policy ( https://docs.coreweave.com/policies/terms-of-service/maintenance-policy)
The latest update from CoreWeave.
State
Scheduled
Starts
in 3 d
2026-11-05 14:00 UTC
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by CoreWeave
CoreWeave will perform scheduled maintenance to update CNI networking in CoreWeave-managed clusters in RNO2A beginning Thursday, November 5, 2026, at 9:00 AM ET (2:00 PM UTC) and continuing through Friday, November 20, 2026, at 5:00 PM ET (10:00 PM UTC). Location: RNO2A We will be actively monitoring the situation during this time. We appreciate your patience and understanding. If you have any further questions or require assistance, please don't hesitate to reach out to our support team at support@coreweave.com This activity is deemed Planned Maintenance under the CoreWeave Terms of Service Maintenance Policy ( https://docs.coreweave.com/policies/terms-of-service/maintenance-policy)
Affected components
2CoreWeave in the last 90 days
Full historyIncidents in 90 days
2
Days with an incident
12
Median duration
Not enough data
This incident
Not comparable
Other CoreWeave incidents
All incidents
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 it is investigating and is working on a fix.
CoreWeave·Facility power incident impacting services in US-EAST-15A
CoreWeave reports a partial outage in US-EAST-15A. The incident affects CoreWeave Infrastructure, Object Storage, Services, Inference, and US-EAST-15. CoreWeave reports that power is restored and that it is investigating and stabilizing the site.
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