Confluent: Confluent Cloud Metrics API Delay
Timeline of updates
- resolved
On May 1st, 2025 between 17:00 and 17:45 UTC, the Confluent Cloud Metrics API experienced ingestion delay for the "io.confluent.kafka.server/retained_bytes" metric for some customers. As a result, queries for this specific metric may have yielded incomplete, undercounted, or missing data.
From Confluent’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
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.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.confluent.cloud (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Confluent, started 2025-05-01 17:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Confluent Cloud Metrics API Delay
- Vendor
- Confluent
- Date
- URL
- https://rewindex.com/company/confluent/incidents/qxdp1nc6zv0z
Confluent profileRecent Confluent incidentsAll outages on May 1, 2025Confluent in May 2025MarkdownJSON