Is Starburst Galaxy down?

Google Cloud provider is experiencing issues in europe-west2 region. We are working to mitigate the issues. Other regions in Europe are heathy.

GCP europe-west2 region is experiencing issues and our services in the region are directly impacted. If feasible, the impacted customer may try to migrate their workload impacted to another available region.

GCP europe-west2 region experienced a power outage, it has been mitigated. Update from Google: "Partial mitigation to infrastructure services will be observed within the next 30 minutes and the remaining services will be mitigated there after." We are closely monitoring the situation. If feasible, the impacted customers may try to migrate their impacted workloads to another available region.

This incident has been 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.

We are investigating an issue where users viewing Cluster Activity for a running cluster are redirected to an authentication page and cannot proceed. This is limited to the Cluster Activity view in the Galaxy UI; running queries and other cluster operations are not affected. We'll post updates as we learn more.

We are continuing to investigate this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Starburst Galaxy's MCP server is returning an error for every tool call from MCP clients using the newest protocol revision, 2026-07-28. Sign-in, discovery and tool listing are unaffected, and clients on revision 2025-11-25 are not affected. Workaround: pin your MCP client to protocol revision 2025-11-25, which has been confirmed to restore tool calls. We are investigating and will post an update as soon as we have one.

We've identified an issue causing MCP tool calls to fail with a protocol error for Galaxy MCP users (both mcp-starburst and mcp-starburst-public, all auth methods). A fix is in progress. Workaround (Claude Code users): setting "MCP_PROTOCOL_NEGOTIATION": "legacy" in ~/.claude/settings.json mitigates the issue. Other MCP clients (Gemini CLI, Cursor, Continue.dev, Cline) aren't currently affected, since they default to an older protocol revision.

This incident is now resolved. All impacted MCP calls should now be operating as expected.

We're currently investigating an intermittent issue where the full list of catalogs and schemas is not being returned

We are continuing to investigate this issue.

We are in a mitigated state and will continue monitoring for any issues

The rollback of the impacted service resolved the issue.