Confluent: Self-service VPC Peering temporarily disabled
Timeline of updates
- resolved
This incident has been resolved. Please disregard the Confluent Cloud Statuspage email that was sent 11 June 2020 at 1:07pm PT /4:07pm ET with the subject ‘Confluent Cloud Incident - We're investigating issues with VPC peering requests for AWS. Self-service provisioning is temporarily disabled. - 11 June 2020.’ It was caused by a bug that allowed non-sensitive SQL commands to be shared. No customer data or information was exposed and this bug has now been resolved. We apologize for any confusion.
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-06-11 20:07 UTC, resolved after 8.2 h, 1 update(s).
- Title
- Self-service VPC Peering temporarily disabled
- Vendor
- Confluent
- Date
- URL
- https://rewindex.com/company/confluent/incidents/2kthtg78j78p
Confluent profileRecent Confluent incidentsAll outages on June 11, 2020Confluent in June 2020MarkdownJSON