Confluent: Some requests may have experienced latency in Basic and Standard clusters in GCP Asia-Southeast2
Timeline of updates
- resolved
On Friday, August 5th between approximately 8:00 and 18:00 UTC, customers may have experienced elevated request latency or failure to connect to Basic and Standard clusters in GCP Asia-Southeast2. This incident is now 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 2022-08-05 18:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Some requests may have experienced latency in Basic and Standard clusters in GCP Asia-Southeast2
- Vendor
- Confluent
- Date
- URL
- https://rewindex.com/company/confluent/incidents/vfb1gzh1sg6b
Confluent profileRecent Confluent incidentsAll outages on August 5, 2022Confluent in August 2022MarkdownJSON