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

Some Confluent Cloud customers accessing services in GCP us-south1 region might experience elevated errors rates

Reported by Confluent Cloud · Data & Analytics · source last read 2 min ago

Official source (opens in a new tab)
Vendor start
Feb 25, 2026, 05:01 UTC
Vendor's clock
Resolved
Feb 27, 2026, 18:16 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
2 d 13 h
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

  • Confluent Cloud reports partial outage: "Some Confluent Cloud customers accessing services in GCP us-south1 region might experience elevated errors rates".[E1, E2]
  • The vendor marked it resolved at 2026-02-27 18:16 UTC.[E3, E7]

Affected products and regions

  • Regions: us-south1 (read from the title, so inferred).[E5]
  • Components: Confluent Cloud.[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-02-27 18:16 UTC · summary s1, evidence a5f81b43d4dbeabb

Evidence (7)
  1. E1Confluent Cloud reports partial outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Some Confluent Cloud customers accessing services in GCP us-south1 region might experience elevated errors rates". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-02-25 05:01 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): us-south1. (Statuswall) source (opens in a new tab)
  6. E6Components the vendor attached: Confluent Cloud. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-02-27 18:16 UTC. (vendor) source (opens in a new tab)

Affected scope

us-south1

Components: Confluent Cloud

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

Potential relevance

Confluent 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. Feb 25, 2026, 05:01 UTCVendor-reported startVendor time
  2. Feb 27, 2026, 18:16 UTCVendor-reported resolutionVendor time

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