Live / Providers / CoreWeave
CoreWeave
coreweave.comReporting incidents
Cloud & hosting · SquidGrid tracks CoreWeave’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.
Public — what CoreWeave is reporting
Current & recent incidents
ResolvedStorage Incident
2026-11-13 05:47 UTC
ResolvedStorage Service Degradation
2026-11-05 15:13 UTC
ResolvedObject Storage Service Degradation in US-EAST-04
2026-11-02 16:59 UTC
ResolvedFacility power incident impacting services in US-EAST-15A
2026-10-22 21:32 UTC
ResolvedKubeconfig download failures
2026-10-13 21:18 UTC
ResolvedObject Storage and Shared File System volumes unavailable in US-CENTRAL-08A
2026-10-12 16:45 UTC
ResolvedGlobal CKS Console Outage
2026-10-06 18:40 UTC
Track record
SquidGrid has archived 13 incidents from CoreWeave’s own status page since 2026-09-11.
- Median time from first post to resolved: 28 min (last 180 days)
- Longest in the last 90 days: 3.2 h
- Most recent incident: today
- 1 open right now
- Status page last checked 2026-11-16 01:44 UTC
Recent incidents in the archive
With SquidGrid — where the route changes
Independent path health
A status page tells you what CoreWeave has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.
CoreWeave runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of CoreWeave is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.
🔒 Sign in to see
Incident track record: 90-day trend, median and worst time to fix
What tends to break, from their own incident write-ups
Recent public reports of problems with this service
Included with any paid plan.
See the full report →