Scheduled Power Infrastructure Maintenance - US-EAST-18A
CoreWeave will perform scheduled power infrastructure maintenance in US-EAST-18A between November 17, 2026 at 13:00 UTC and November 18, 2026 at 22:00 UTC. Work will occur in two separate maintenance periods: - November 17: 13:00–22:00 UTC - November 18: 13:00–22:00 UTC Location: US-EAST-18A Impact: No customer service interruption is expected, and no customer action is required. Power redundancy will be temporarily reduced during the work. Customer workloads are expected to remain available throughout the maintenance. 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 (https://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
CoreWeave will perform scheduled power infrastructure maintenance in US-EAST-18A between November 17, 2026 at 13:00 UTC and November 18, 2026 at 22:00 UTC. Work will occur in two separate maintenance periods: - November 17: 13:00–22:00 UTC - November 18: 13:00–22:00 UTC Location: US-EAST-18A Impact: No customer service interruption is expected, and no customer action is required. Power redundancy will be temporarily reduced during the work. Customer workloads are expected to remain available throughout the maintenance. 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 (https://docs.coreweave.com/policies/terms-of-service/maintenance-policy).
Affected components
2CoreWeave in the last 90 days
Full historyIncidents in 90 days
4
Days with an incident
23
Median duration
9 days
This incident
Not comparable
Other CoreWeave incidents
All incidents
CoreWeave·Storage Incident
CoreWeave Object Storage in US-EAST-04 was degraded. Some customers saw HTTP 500 errors or timeouts on object storage requests, especially uploads. CoreWeave reports that the incident is resolved. It lasted about 5 hours and 54 minutes.
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