Confluent Cloud logging degradation - Connect and Flink
Aug 24, 15:49 UTCAug 23, 21:00 UTC
Duration
0m
Impact
Informational
Root cause
Not disclosed
Confluent, 90 days
16 incidents
Affected
Not listed by the vendor.
Final update
Between 21:15 – 22:30 UTC and 00:05 – 01:15 UTC on Aug 23–24, 2026, Confluent Cloud logging service was degraded. Customers may notice missing Connect and Flink logs in the Confluent Cloud UI, the Confluent CLI, and configured logging integration destinations during these windows. Other log types and the Connect / Flink workloads themselves were unaffected. The issue has been mitigated.
Timeline
- Resolved · Aug 23, 21:00 UTC
Between 21:15 – 22:30 UTC and 00:05 – 01:15 UTC on Aug 23–24, 2026, Confluent Cloud logging service was degraded. Customers may notice missing Connect and Flink logs in the Confluent Cloud UI, the Confluent CLI, and configured logging integration destinations during these windows. Other log types and the Connect / Flink workloads themselves were unaffected. The issue has been mitigated.
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.