Confluent incident

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

Resolved after 2 days 13 hours, affecting Confluent Cloud, on February 25, 2026.

monitoring Feb 27, 2026, 03:25 AM UTC

We are continuing to monitor for any further issues.

Started
Feb 25, 2026, 05:01 AM UTC
Resolved
Feb 27, 2026, 06:16 PM UTC
Duration
2d 13h
Detected by Pingoru
Feb 25, 2026, 05:01 AM UTC

Affected components

Confluent Cloud

Update timeline

  1. investigating Feb 25, 2026, 05:01 AM UTC

    We are currently investigating the issue

  2. identified Feb 25, 2026, 12:02 PM UTC

    GCP has identified the issue and is actively working on applying mitigation.

  3. identified Feb 26, 2026, 01:11 AM UTC

    At this time, single zone clusters in us-south1 Zone-a are impacted.

  4. monitoring Feb 26, 2026, 05:41 PM UTC

    A fix has been implemented and we are monitoring the results

  5. monitoring Feb 27, 2026, 03:25 AM UTC

    We are continuing to monitor for any further issues.

  6. resolved Feb 27, 2026, 06:16 PM UTC

    This incident has been resolved.

Your product runs on more than Confluent

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →