Resolved incident

Confluent Cloud logging degradation - Connect and Flink

Confluent Cloud · None · Started

Duration
< 1m
Severity
None
Status
Resolved

Summary

None · Resolved

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.

View official incident ↗

Event timeline

How this incident unfolded, from the official status page.

  1. Resolved

    Confluent Cloud

    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.