Starburst Galaxy incident
Slow logins and query failures for some Galaxy clusters
Resolved after 4 hours, on October 13, 2026.
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.
Update timeline
- resolved Oct 14, 2026, 11:22 AM UTC
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.
Your product runs on more than Starburst Galaxy
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services