ChangesStarburstQueries not starting in GCP us-east1 clusters
Starburst: Critical incident: Queries not starting in GCP us-east1 clusters
Summary pending. The diff below shows exactly what changed.
Incident page: the full timeline of updates
What changed
Struck in red is what Starburst removed; blue is what they added. Muted text is unchanged context.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
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.
Rewindex captured this after the last checkpoint; the next run () commits it.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
History of this incident
Thursday, February 19
1 incident change
- OutageCritical incident
Queries not starting in GCP us-east1 clustersthis change
Cite this
Critical incident: Queries not starting in GCP us-east1 clusters on Starburst’s status page, changed 2026-02-19 20:15 UTC (change 1 of 1).
- Title
- Critical incident: Queries not starting in GCP us-east1 clusters
- Vendor
- Starburst
- Date
- URL
- https://rewindex.com/change/i4edc36371bca08