rewindex

CompaniesConfluentIncidents

Confluent: Confluent Cloud logging degradation - Connect and Flink

No impact listedStatus: resolvedStarted Resolved (-1130 min)1 updatestspg.io (opens in new tab)

Timeline of updates

  1. 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.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Confluent, started 2026-08-24 15:49 UTC, resolved after -1130 min, 1 update(s).

Title
Confluent Cloud logging degradation - Connect and Flink
Vendor
Confluent
Date
URL
https://rewindex.com/company/confluent/incidents/lgwqzmbrdz8f

Confluent profileRecent Confluent incidentsAll outages on August 24, 2026Confluent in August 2026MarkdownJSON