Confluent: Potential Metrics Impact in AWS/Frankfurt
Timeline of updates
- resolved
We have determined the level of impact was Confluent-only internal metrics loss, some of which are exposed to customers, who may see missing or unusual metrics from UTC 15:40 to 16:30. We see no evidence of data or service loss.
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: minor) posted by Confluent, started 2019-04-25 16:35 UTC, resolved after 29 min, 1 update(s).
- Title
- Potential Metrics Impact in AWS/Frankfurt
- Vendor
- Confluent
- Date
- URL
- https://rewindex.com/company/confluent/incidents/lmb9p6fmtktk
Confluent profileRecent Confluent incidentsAll outages on April 25, 2019Confluent in April 2019MarkdownJSON