Coreweave status history
Current state: maintenance — “Planned Maintenance” per https://status.coreweave.com (Status.io), checked 2026-09-16 12:28 UTC.
4incidents, last 30 days
4incidents, last 90 days
4incidents on record
Status.io only exposes incidents that are open right now, so this history starts on 2026-09-04, the day we first watched Coreweave. It fills in from here.
Incidents on record (4)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-10 15:15 UTC | Scheduled CoreWeave Maintenance - US-WEST-04A | maintenance | maintenance | open |
| 2026-09-03 01:26 UTC | Scheduled CoreWeave Maintenance - US-EAST-06A | maintenance | maintenance | open |
| 2026-08-28 18:15 UTC | Scheduled CoreWeave Electrical Maintenance - US-EAST-04A | maintenance | maintenance | 7 d 11 h (approx.) |
| 2026-08-19 14:44 UTC | Scheduled CoreWeave Maintenance - US-EAST-08A | maintenance | maintenance | 22 d 21 h (approx.) |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Coreweave with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"coreweave"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}