# Confluent Cloud logging degradation - Connect and Flink

- Provider: [Confluent Cloud](https://down.guide/providers/confluent)
- Confidence: Confirmed
- Impact: Operational
- lasted 0m
- started 2026-08-24 15:49 UTC
- id: DWN-2057d5d838
- Official page: https://stspg.io/1vjp6vl24zps

## Updates from Confluent Cloud
### 2026-08-23 21:00 UTC: 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.

From the builder: does your app depend on Confluent Cloud? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=confluent) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Confluent Cloud.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-2057d5d838), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.