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

GCP cluster creations issues in us-central1

Reported by Redpanda Cloud · Databases · source last read just now

Official source (opens in a new tab)
Vendor start
Nov 11, 2025, 12:21 UTC
Vendor's clock
Resolved
Nov 11, 2025, 19:39 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
7 h 18 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

  • Redpanda Cloud reports operational: "GCP cluster creations issues in us-central1".[E1, E2]
  • The vendor marked it resolved at 2025-11-11 19:39 UTC.[E3, E7]

Affected products and regions

  • Regions: us-central1 (read from the title, so inferred).[E5]

What is unknown

  • 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.

Last update in these facts: 2025-11-11 19:39 UTC · summary s1, evidence cb6267efe6815a18

Evidence (7)
  1. E1Redpanda Cloud reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "GCP cluster creations issues in 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: 2025-11-11 12:21 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): us-central1. (Statuswall)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2025-11-11 19:39 UTC. (vendor)

Affected scope

us-central1

Components: not stated by the vendor

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

Potential relevance

Redpanda 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. Nov 11, 2025, 12:21 UTCVendor-reported startVendor time
  2. Nov 11, 2025, 19:39 UTCVendor-reported resolutionVendor time

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