Planned maintenanceOpen · vendor status “scheduled”Official status API

Scheduled Power Infrastructure Maintenance - CA-EAST-01A

Reported by CoreWeave · AI & ML · source last read 5 min ago

Official source (opens in a new tab)
Vendor start
Nov 9, 2026, 23:30 UTC
Vendor's clock
Resolved
Not yet
Still open
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
Not available
This source does not publish reliable durations

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • CoreWeave reports planned maintenance: "Scheduled Power Infrastructure Maintenance - CA-EAST-01A".[E1, E2]
  • It is not resolved yet (vendor status "scheduled").[E3, E7]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Which components are affected: the vendor did not say.[E6]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.
  • When it will be resolved: no estimate is shown unless the vendor publishes one on its page.

Last update in these facts: 2026-11-09 23:30 UTC · summary s1, evidence f25124a3bc66d1eb

Evidence (7)
  1. E1CoreWeave reports planned maintenance. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Scheduled Power Infrastructure Maintenance - CA-EAST-01A". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "scheduled". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-11-09 23:30 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Not resolved by the vendor yet. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: not stated by the vendor

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

CoreWeave is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

What to check on your side

Verification steps only. Statuswall cannot see your systems.

  • Watch 5xx, 429 (rate limit) and timeout rates on calls to the CoreWeave API.
  • If you route to more than one model or provider, check whether fallback traffic is behaving.
  • Check retry queues and background jobs that call the API, which can back up quietly.
  • Check error rates, latency and timeouts in your own monitoring for requests that depend on CoreWeave.
  • Look at synthetic checks and alerts that exercise CoreWeave.
  • Compare with recent deploys on your side, so a coincidental change is not blamed on the vendor.
  • Follow the vendor's official incident page for scope changes and resolution.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Nov 9, 2026, 23:30 UTCVendor-reported startVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.