Vendor reports: partial outageResolved · vendor status “resolved”Official status API

Cluster operations impaired

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

Vendor start
Jul 3, 2025, 16:58 UTC
Vendor's clock
Resolved
Jul 3, 2025, 17:39 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
41 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 partial outage: "Cluster operations impaired".[E1, E2]
  • The vendor marked it resolved at 2025-07-03 17:39 UTC.[E3, E7]

Affected products and regions

  • Components: CockroachDB Basic/Standard, CockroachDB Advanced.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2025-07-03 17:39 UTC · summary s1, evidence 7f5187f8aba278f7

Evidence (7)
  1. E1CockroachDB Cloud reports partial outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Cluster operations impaired". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2025-07-03 16:58 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: CockroachDB Basic/Standard, CockroachDB Advanced. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2025-07-03 17:39 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: CockroachDB Basic/Standard, CockroachDB Advanced

The vendor's feed gives no region for this incident. It is not assumed to be global.

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. Jul 3, 2025, 16:58 UTCVendor-reported startVendor time
  2. Jul 3, 2025, 17:39 UTCVendor-reported resolutionVendor time

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