Starburst: Slow logins and query failures for some Galaxy clusters
Timeline of updates
- resolved
Between 03:20 and 07:20 UTC on October 13, 2026, some Starburst Galaxy users experienced degraded performance when connecting to their clusters. Password-based and token-based logins from Trino clients were very slow. Some queries failed with server errors (HTTP 500/504) while waiting for authentication. Logins through SSO and existing Galaxy UI sessions were largely unaffected.
The cause was a slow response from an external dependency used during password-based authentication. The slow responses tied up our authentication service, and it could not keep up with incoming requests. We deployed a fix that restored normal login performance at 07:20 UTC. A permanent fix with additional safeguards was released later the same day and has been running without issue.
No action is required from customers. We apologize for the inconvenience.
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.galaxy.starburst.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Starburst, started 2026-10-13 05:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Slow logins and query failures for some Galaxy clusters
- Vendor
- Starburst
- Date
- URL
- https://rewindex.com/company/starburst/incidents/8206ss1269kp
Starburst profileRecent Starburst incidentsAll outages on October 13, 2026Starburst in October 2026MarkdownJSON