Confluent: Some GCP peering status is incorrectly reported as FAILED
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: minor) posted by Confluent, started 2024-05-03 18:04 UTC, resolved after 5.3 h, 1 update(s).
- Title
- Some GCP peering status is incorrectly reported as FAILED
- Vendor
- Confluent
- Date
- URL
- https://rewindex.com/company/confluent/incidents/895wlsky1yv3
Confluent profileRecent Confluent incidentsAll outages on May 3, 2024Confluent in May 2024MarkdownJSON