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

Affected components

• Confluent Cloud

1. resolvedFeb 27, 2026, 18:16 UTC

   This incident has been resolved.

2. monitoringFeb 27, 2026, 03:25 UTC

   We are continuing to monitor for any further issues.

3. monitoringFeb 26, 2026, 17:41 UTC

   A fix has been implemented and we are monitoring the results

4. identifiedFeb 26, 2026, 01:11 UTC

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

5. identifiedFeb 25, 2026, 12:02 UTC

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

6. investigatingFeb 25, 2026, 05:01 UTC

   We are currently investigating the issue

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Confluent Cloud's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• GitBook: Site wide outageCritical · Feb 26, 2026, 17:15 UTC
• PyPI: Python Infrastructure OutageCritical · Feb 26, 2026, 20:40 UTC
• Mailgun: Intermittent Email Validation ErrorsMajor · Feb 25, 2026, 19:10 UTC
• LaunchDarkly: Investigating Issues with LaunchDarkly Application and AuthenticationMajor · Feb 26, 2026, 15:43 UTC
• npm: Degraded performance with package installationMinor · Feb 25, 2026, 18:43 UTC
• Cloudinary: Saved search fails for SMDs with spaces in name.Minor · Feb 26, 2026, 12:50 UTC
• Miro: MCP server performance degradedMinor · Feb 26, 2026, 13:27 UTC
• MongoDB Atlas: DataDog Integration Degraded ExperienceMinor · Feb 26, 2026, 19:21 UTC

How often does Confluent Cloud have incidents?

Confluent Cloud reported 13 incidents in the last 90 days, 8 of them major or critical. A typical incident lasted 7h 3m. See Confluent Cloud's uptime and incident history