Vendor reports: degradedResolved · vendor status “resolved”Official status API

Stock out issues in GCP us-central1

Reported by CockroachDB Cloud · Databases · source last read 13 min ago

Official source (opens in a new tab)
Vendor start
Oct 6, 2026, 21:21 UTC
Vendor's clock
Resolved
Oct 7, 2026, 19:33 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
22 h 12 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • CockroachDB Cloud reports degraded: "Stock out issues in GCP us-central1".[E1, E2]
  • The vendor marked it resolved at 2026-10-07 19:33 UTC.[E3, E7]

Affected products and regions

  • Regions: us-central1 (read from the title, so inferred).[E5]
  • Components: CockroachDB Advanced, Continuum Mission Critical.[E6]

What is unknown

  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-10-07 19:33 UTC · summary s1, evidence 9f3db2b31d2e2d13

Evidence (7)
  1. E1CockroachDB Cloud reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Stock out issues in GCP us-central1". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-10-06 21:21 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): us-central1. (Statuswall) source (opens in a new tab)
  6. E6Components the vendor attached: CockroachDB Advanced, Continuum Mission Critical. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-10-07 19:33 UTC. (vendor) source (opens in a new tab)

Affected scope

us-central1

Components: CockroachDB Advanced, Continuum Mission Critical

Read from region codes written in the incident title, so treat it as inferred.

Potential relevance

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

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. Oct 6, 2026, 21:21 UTCVendor-reported startVendor time
  2. Oct 7, 2026, 19:33 UTCVendor-reported resolutionVendor time

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