Some Confluent Cloud customers accessing services in GCP us-south1 region might experience elevated errors rates
Feb 25, 05:01 UTCFeb 27, 18:16 UTC
Duration
2d 13h
Impact
Major
Root cause
Not disclosed
Confluent, 90 days
16 incidents
Affected
Confluent Cloud
Final update
This incident has been resolved.
Timeline
- Resolved · Feb 27, 18:16 UTC
This incident has been resolved.
- Monitoring · Feb 27, 03:25 UTC
We are continuing to monitor for any further issues.
- Monitoring · Feb 26, 17:41 UTC
A fix has been implemented and we are monitoring the results
- Identified · Feb 26, 01:11 UTC
At this time, single zone clusters in us-south1 Zone-a are impacted.
- Identified · Feb 25, 12:02 UTC
GCP has identified the issue and is actively working on applying mitigation.
- Investigating · Feb 25, 05:01 UTC
We are currently investigating the issue
More from Confluent
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2311:47 UTC | Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2 | major | 11h 30m |
| Sep 2215:09 UTC | Elevated error rates in Azure Germany West Central region | major | 4h 50m |
| Sep 2116:15 UTC | Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2 | major | 9h 16m |
| Sep 1717:49 UTC | Confluent Cloud Metrics API experienced elevated latency and error rates | none | 0m |
| Sep 1523:59 UTC | Multiple Confluent Cloud services are in a degraded state - All regions | major | 1h 22m |
| Sep 820:01 UTC | Connectivity degradation - AWS us-east-1 | major | 17h |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.