Changes / Confluent / Some Confluent Cloud customers accessing services in GCP us-south1 region might experience elevated errors rates
Confluent: Major incident: Some Confluent Cloud customers accessing services in GCP us-south1 region might experience elevated errors rates
Summary
Confluent reported a major incident involving elevated error rates for some Confluent Cloud customers in GCP us-south1, with single zone clusters in us-south1 Zone-a impacted. It started 2026-02-25 05:01 UTC and was resolved 2026-02-27 18:16 UTC, lasting 2 days 13 h. GCP identified the issue; a fix was implemented and monitored.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Some Confluent Cloud customers accessing services in GCP us-south1 region might experience elevated errors rates
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-02-25 05:01 UTC
Before: not present
After: 2026-02-27 18:16 UTC
Before: not present
After: Confluent Cloud
Before: not present
After: We are currently investigating the issue
Before: not present
After: GCP has identified the issue and is actively working on applying mitigation.
Before: not present
After: At this time, single zone clusters in us-south1 Zone-a are impacted.
Before: not present
After: A fix has been implemented and we are monitoring the results
Before: not present
After: We are continuing to monitor for any further issues.
Before: not present
After: This incident has been resolved.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Some Confluent Cloud customers accessing services in GCP us-south1 region might experience elevated errors rates (this change) Confluent reported a major incident involving elevated error rates for some Confluent Cloud customers in GCP us-south1, with single zone clusters in us-south1 Zone-a impacted. It started 2026-02-25 05:01 UTC and was resolved 2026-02-27 18:16 UTC, lasting 2 days 13 h. GCP identified the issue; a fix was implemented and monitored. | Major incident |
All Confluent changes → · Confluent profile · Markdown · JSON