outages.live
Live
CoreWeave logo

CoreWeave

CoreWeave is reporting partial outage

Checked 2 min ago Partial outage

Partial Service Disruption

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.

Partial outageupdated 7 d ago

History

90 days agoToday

Incidents in 90 days

1

Days with an incident

11

Median duration

No data

Longest incident

No data

Components

13
CoreWeave Cloud Operational
90 days agoNo incidentsToday
CoreWeave Infrastructure Partial outage
90 days ago11 days with an incidentToday
CoreWeave Premium Shared Filesystem Volumes Operational
90 days agoNo incidentsToday
CoreWeave Object Storage Partial outage
90 days ago11 days with an incidentToday
CoreWeave Services Partial outage
90 days ago11 days with an incidentToday
CoreWeave Logging Operational
90 days agoNo incidentsToday
CoreWeave Inference Partial outage
90 days ago11 days with an incidentToday
CoreWeave Shared Filesystem Volumes Operational
90 days agoNo incidentsToday
CoreWeave Block Storage Volumes Operational
90 days agoNo incidentsToday
Coreweave Network Operational
90 days agoNo incidentsToday
CoreWeave Bare Metal Operational
90 days agoNo incidentsToday
CoreWeave Networking Operational
90 days agoNo incidentsToday
CoreWeave Cloud Console Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

No incident in the last 90 days.

Affected components

4
  • CoreWeave InfrastructurePartial outage
  • CoreWeave Object StoragePartial outage
  • CoreWeave ServicesPartial outage
  • CoreWeave InferencePartial outage

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.

Prompt
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.

RSS
https://outages.cc/feed.xml?providers=coreweave
Slack
/feed subscribe https://outages.cc/feed.xml?providers=coreweave

Go from tracking outages to fixing production issues with Polylane.

Try Polylane