CoreWeave uptime
From vendor reports Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours.
72.46%free of major or critical incidents, last 30 days
77.34%free of major or critical incidents, last 90 days*
77.34%free of any incident, last 90 days
5incidents started, last 90 days
* Our archive of CoreWeave’s status page starts , so the window is shorter.
Last 90 days, by UTC day
Aug 7 (UTC day): before our archive of this status page startsAug 8 (UTC day): before our archive of this status page startsAug 9 (UTC day): before our archive of this status page startsAug 10 (UTC day): before our archive of this status page startsAug 11 (UTC day): before our archive of this status page startsAug 12 (UTC day): before our archive of this status page startsAug 13 (UTC day): before our archive of this status page startsAug 14 (UTC day): before our archive of this status page startsAug 15 (UTC day): before our archive of this status page startsAug 16 (UTC day): before our archive of this status page startsAug 17 (UTC day): before our archive of this status page startsAug 18 (UTC day): before our archive of this status page startsAug 19 (UTC day): before our archive of this status page startsAug 20 (UTC day): before our archive of this status page startsAug 21 (UTC day): before our archive of this status page startsAug 22 (UTC day): before our archive of this status page startsAug 23 (UTC day): before our archive of this status page startsAug 24 (UTC day): before our archive of this status page startsAug 25 (UTC day): before our archive of this status page startsAug 26 (UTC day): before our archive of this status page startsAug 27 (UTC day): before our archive of this status page startsAug 28 (UTC day): before our archive of this status page startsAug 29 (UTC day): before our archive of this status page startsAug 30 (UTC day): before our archive of this status page startsAug 31 (UTC day): before our archive of this status page startsSep 1 (UTC day): before our archive of this status page startsSep 2 (UTC day): before our archive of this status page startsSep 3 (UTC day): before our archive of this status page startsSep 4 (UTC day): before our archive of this status page startsSep 5 (UTC day): before our archive of this status page startsSep 6 (UTC day): before our archive of this status page startsSep 7 (UTC day): before our archive of this status page startsSep 8 (UTC day): before our archive of this status page startsSep 9 (UTC day): before our archive of this status page startsSep 10 (UTC day): before our archive of this status page startsSep 11 (UTC day): before our archive of this status page startsSep 12 (UTC day): before our archive of this status page startsSep 13 (UTC day): before our archive of this status page startsSep 14 (UTC day): before our archive of this status page startsSep 15 (UTC day): before our archive of this status page startsSep 16 (UTC day): before our archive of this status page startsSep 17 (UTC day): before our archive of this status page startsSep 18 (UTC day): before our archive of this status page startsSep 19 (UTC day): before our archive of this status page startsSep 20 (UTC day): before our archive of this status page startsSep 21 (UTC day): before our archive of this status page startsSep 22 (UTC day): before our archive of this status page startsSep 23 (UTC day): before our archive of this status page startsSep 24 (UTC day): before our archive of this status page startsSep 25 (UTC day): before our archive of this status page startsSep 26 (UTC day): before our archive of this status page startsSep 27 (UTC day): before our archive of this status page startsSep 28 (UTC day): no vendor-reported incident openSep 29 (UTC day): no vendor-reported incident openSep 30 (UTC day): no vendor-reported incident openOct 1 (UTC day): no vendor-reported incident openOct 2 (UTC day): no vendor-reported incident openOct 3 (UTC day): no vendor-reported incident openOct 4 (UTC day): no vendor-reported incident openOct 5 (UTC day): no vendor-reported incident openOct 6 (UTC day): 42 min with a major or critical incident open, 42 min with any incident open, 1 incident startedOct 7 (UTC day): no vendor-reported incident openOct 8 (UTC day): no vendor-reported incident openOct 9 (UTC day): no vendor-reported incident openOct 10 (UTC day): no vendor-reported incident openOct 11 (UTC day): no vendor-reported incident openOct 12 (UTC day): 4 h 28 min with a major or critical incident open, 4 h 28 min with any incident open, 1 incident startedOct 13 (UTC day): 1 h 6 min with a major or critical incident open, 1 h 6 min with any incident open, 1 incident startedOct 14 (UTC day): no vendor-reported incident openOct 15 (UTC day): no vendor-reported incident openOct 16 (UTC day): no vendor-reported incident openOct 17 (UTC day): no vendor-reported incident openOct 18 (UTC day): no vendor-reported incident openOct 19 (UTC day): no vendor-reported incident openOct 20 (UTC day): no vendor-reported incident openOct 21 (UTC day): no vendor-reported incident openOct 22 (UTC day): 2 h 28 min with a major or critical incident open, 2 h 28 min with any incident open, 1 incident startedOct 23 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openOct 24 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openOct 25 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openOct 26 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openOct 27 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openOct 28 (UTC day): 24 h with a major or critical incident open, 24 h with any incident openOct 29 (UTC day): 21 h 32 min with a major or critical incident open, 21 h 32 min with any incident openOct 30 (UTC day): no vendor-reported incident openOct 31 (UTC day): no vendor-reported incident openNov 1 (UTC day): no vendor-reported incident openNov 2 (UTC day): 7 h 1 min with a major or critical incident open, 7 h 1 min with any incident open, 1 incident startedNov 3 (UTC day): 16 h 59 min with a major or critical incident open, 16 h 59 min with any incident openNov 4 (UTC day): no vendor-reported incident open
Aug 7today
no incident minor incident minor, 6 h+ major/critical major/critical, 6 h+ before archive
Last 7 days, by hour
now
Numbers
| Window | Free of major/critical | Free of any incident | Outage time | Incident time | Incidents |
|---|---|---|---|---|---|
| Last 30 days | 72.46% | 72.46% | 8.3 days | 8.3 days | 5 |
| Last 90 days* | 77.34% | 77.34% | 8.3 days | 8.3 days | 5 |
This is what CoreWeave itself reported, so it can miss outages the vendor never posted and overstate ones where an incident was left open. Regional or single-component incidents count the same as global ones. Recomputed .
See the incidents: CoreWeave status history · last 90 days · CoreWeave status page (opens in new tab) · Markdown