Confluent incident

Confluent Cloud logging degradation - Connect and Flink

Notice Resolved View vendor source →

Confluent experienced a notice incident on August 24, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Aug 24, 2026, 03:49 PM UTC
Resolved
Aug 23, 2026, 09:00 PM UTC
Duration
—
Detected by Pingoru
Aug 24, 2026, 03:49 PM UTC

Update timeline

  1. resolved Aug 24, 2026, 03:49 PM 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.