Confluent: We are investigating reports that users with aggressive ad blockers aren’t able to access or use parts of the Confluent Cloud UI resulting in error 424 being shown on the UI.
Timeline of updates
- resolved
This incident has been resolved.
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 2020-07-29 15:59 UTC, resolved after 2.5 h, 1 update(s).
- Title
- We are investigating reports that users with aggressive ad blockers aren’t able to access or use parts of the Confluent Cloud UI resulting in error 424 being shown on the UI.
- Vendor
- Confluent
- Date
- URL
- https://rewindex.com/company/confluent/incidents/m7q33xgyjwfr
Confluent profileRecent Confluent incidentsAll outages on July 29, 2020Confluent in July 2020MarkdownJSON