Incidentsby GlyphConfluent Cloud logging degradation - Connect and Flink
Aug 23, 21:00 UTCAug 23, 21:00 UTC
Duration
0m
Impact
Informational
Root cause
Not disclosed
Confluent, 90 days
20 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 historyKafka - Increased latency and connectivity issues - Azure - brazilsouthlasted 2h 9mMultiple Confluent Cloud services are in a degraded state - GCP EU-West2lasted 10h 25mDelay in Kafka cluster provisioninglasted 7h 18mConfluent Cloud Console (UI) degraded functionalitylasted 2h 45mPossible outage in AWS us-east-1lasted 56mExperiencing high error rate in AZURE in West Europe regionlasted 20h 2m