← Live dashboard

Confluent Cloud logging degradation - Connect and Flink

ResolvedminorOfficial source confirmedFirst recorded update Aug 23, 2026, 09:00 PM · Resolved Aug 23, 2026, 09:00 PM

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.

Confluent Cloud live status →

Free for 3 services · Pro adds recovery alertsAdd to Chrome

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with Confluent Cloud now? Check the current status

Updates (1)

  1. Aug 24, 2026, 03:49 PM
    Confluent Cloud logging degradation - Connect and Flink

    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.

    Confluent Cloud ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow Confluent Cloud's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.