Starburst Galaxy Outage History

Started Oct 20, 2026, 08:10 AM UTC· resolved Oct 20, 2026, 03:53 PM UTC

1. investigating Oct 20, 2026, 08:10 AM UTC

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

2. identified Oct 20, 2026, 09:51 AM UTC

   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.

3. monitoring Oct 20, 2026, 11:57 AM UTC

   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.

4. resolved Oct 20, 2026, 03:53 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 13, 2026, 03:20 AM UTC· resolved Oct 13, 2026, 07:20 AM UTC

1. 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.

Read the full incident report →

Started Sep 14, 2026, 05:09 PM UTC· resolved Sep 14, 2026, 08:06 PM UTC

1. investigating Sep 14, 2026, 05:09 PM UTC

   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.

2. investigating Sep 14, 2026, 05:09 PM UTC

   We are continuing to investigate this issue.

3. identified Sep 14, 2026, 06:58 PM UTC

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

4. monitoring Sep 14, 2026, 07:26 PM UTC

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

5. resolved Sep 14, 2026, 08:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 09, 2026, 12:02 PM UTC· resolved Sep 09, 2026, 08:42 PM UTC

1. identified Sep 09, 2026, 12:02 PM UTC

   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.

2. identified Sep 09, 2026, 02:37 PM UTC

   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.

3. resolved Sep 09, 2026, 08:42 PM UTC

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

Read the full incident report →

Started Aug 18, 2026, 07:31 PM UTC· resolved Aug 20, 2026, 04:45 PM UTC

1. investigating Aug 18, 2026, 07:31 PM UTC

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

2. investigating Aug 18, 2026, 07:32 PM UTC

   We are continuing to investigate this issue.

3. monitoring Aug 19, 2026, 02:32 AM UTC

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

4. resolved Aug 20, 2026, 04:45 PM UTC

   The rollback of the impacted service resolved the issue.

Read the full incident report →

Started Aug 13, 2026, 02:05 PM UTC· resolved Aug 13, 2026, 03:39 PM UTC

1. identified Aug 13, 2026, 02:05 PM UTC

   We are investigating an issue causing clusters and pipelines connected via AWS/Azure PrivateLink to fail to start, with queries timing out. Clusters using standard (non-PrivateLink) connectivity are not affected. Our team has identified the likely area (an Istio/networking change) and is working to confirm and remediate. We will post updates as we learn more.

2. monitoring Aug 13, 2026, 02:30 PM UTC

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

3. resolved Aug 13, 2026, 03:39 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 03, 2026, 05:56 PM UTC· resolved Aug 03, 2026, 08:24 PM UTC

1. investigating Aug 03, 2026, 05:56 PM UTC

   We are investigating errors while starting Starburst Galaxy clusters.

2. investigating Aug 03, 2026, 05:57 PM UTC

   We are continuing to investigate this issue.

3. investigating Aug 03, 2026, 06:17 PM UTC

   We are continuing to investigate this issue.

4. identified Aug 03, 2026, 06:29 PM UTC

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

5. monitoring Aug 03, 2026, 06:46 PM UTC

   We have mitigated the issue and we are monitoring the results.

6. monitoring Aug 03, 2026, 06:59 PM UTC

   All impacted clusters are fully operational now. We are continuing to monitor.

7. resolved Aug 03, 2026, 08:24 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 15, 2026, 01:09 PM UTC· resolved Jun 15, 2026, 02:20 PM UTC

1. investigating Jun 15, 2026, 01:09 PM UTC

   We are investigating degraded performance affecting customers using the spooling protocol. We will provide an update as we learn more.

2. identified Jun 15, 2026, 01:50 PM UTC

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

3. monitoring Jun 15, 2026, 02:14 PM UTC

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

4. resolved Jun 15, 2026, 02:20 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 15, 2026, 11:22 AM UTC· resolved Jun 15, 2026, 11:35 AM UTC

1. investigating Jun 15, 2026, 11:22 AM UTC

   We are actively investigating the issue

2. monitoring Jun 15, 2026, 11:29 AM UTC

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

3. resolved Jun 15, 2026, 11:35 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 01, 2026, 09:40 PM UTC· resolved Apr 01, 2026, 10:57 PM UTC

1. investigating Apr 01, 2026, 09:40 PM UTC

   We are currently investigating an issue causing query failures across multiple regions in Galaxy

2. investigating Apr 01, 2026, 09:54 PM UTC

   We are continuing to investigate this issue.

3. investigating Apr 01, 2026, 10:24 PM UTC

   We are continuing to investigate this issue.

4. monitoring Apr 01, 2026, 10:30 PM UTC

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

5. resolved Apr 01, 2026, 10:57 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 16, 2026, 10:06 PM UTC· resolved Mar 18, 2026, 03:50 PM UTC

1. investigating Mar 16, 2026, 10:06 PM UTC

   We care currently investigating intermittent query failures in AWS us-east-1 and AWS us-east-2.

2. monitoring Mar 16, 2026, 11:54 PM UTC

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

3. resolved Mar 18, 2026, 03:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 11, 2026, 04:21 PM UTC· resolved Mar 16, 2026, 06:17 AM UTC

1. investigating Mar 11, 2026, 04:21 PM UTC

   We are currently experiencing intermittent galaxy outage in us-east-1 and us-east-2 that is leading to query failures

2. investigating Mar 11, 2026, 05:30 PM UTC

   Right now both the regions continue to operate normally. We are still investigating the root cause to prevent future failures

3. investigating Mar 11, 2026, 07:48 PM UTC

   Services continue to operate normally, we are still investigating the root cause

4. investigating Mar 11, 2026, 09:25 PM UTC

   We have a short term mitigation in place as we continue to investigate further

5. monitoring Mar 12, 2026, 04:03 PM UTC

   We continue to monitor the pods after our short term mitigation

6. resolved Mar 16, 2026, 06:17 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 19, 2026, 06:40 PM UTC· resolved Feb 19, 2026, 08:15 PM UTC

1. investigating Feb 19, 2026, 06:40 PM UTC

   We are investigating an issue that prevents queries from being run in GCP us-east1

2. identified Feb 19, 2026, 07:04 PM UTC

   The issue has been identified and we are working on a fix

3. monitoring Feb 19, 2026, 07:46 PM UTC

   A fix has been implemented and we are monitoring functionality.

4. resolved Feb 20, 2026, 02:49 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 02, 2026, 08:59 PM UTC· resolved Feb 03, 2026, 02:41 PM UTC

1. investigating Feb 02, 2026, 08:59 PM UTC

   Several Galaxy accounts are experiencing issues restarting Azure clusters across multiple regions. The team is actively investigating the root cause and working to restore normal operations as quickly as possible.

2. identified Feb 02, 2026, 09:40 PM UTC

   According to Azure status page https://azure.status.microsoft/en-us/status "Active - Virtual Machine service management issues - Multiple regions Impact statement: We are aware of an ongoing issue causing customers to receive error notifications when performing service management operations - such as create, delete, update, scaling, start, stop - for Virtual Machines (VMs). These issues are also causing impact to services with dependencies on these operations, including Azure Arc Enabled Servers, Azure Batch, Azure DevOps, and GitHub. For details on the latter, please see https://www.githubstatus.com. Current status: We have determined that these issues were caused by a recent configuration change that affected public access to certain Microsoft‑managed storage accounts, used to host extension packages. We are actively working on mitigation, including updating configuration to restore relevant access permissions. Our next update will be provided by 22:30 UTC, approximately 60 minutes from now. This message was last updated at 21:35 UTC on 02 February 2026"

3. identified Feb 03, 2026, 12:03 AM UTC

   Current status from Azure team( https://azure.status.microsoft/en-us/status) : "We have determined that these issues were caused by a recent configuration change that affected public access to certain Microsoft‑managed storage accounts, used to host extension packages. We are actively working to mitigate impact, by updating our configuration to restore relevant access permissions. After applying this update in one region, we validated that it mitigates the issues customers were experiencing - we are making good progress applying this same mitigation across all impacted regions, in parallel where possible. We still expect that this will be completed across all impacted regions by approximately 00:00 UTC, approximately one hour from now. Our next update will be provided by then, or sooner if we have progress to share. This message was last updated at 22:59 UTC on 02 February 2026"

4. identified Feb 03, 2026, 02:39 PM UTC

   We are continuing to work on a fix for this issue.

5. resolved Feb 03, 2026, 02:41 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 05, 2025, 09:25 AM UTC· resolved Dec 05, 2025, 10:05 AM UTC

1. monitoring Dec 05, 2025, 09:25 AM UTC

   Galaxy was temporarily unavailable due to an external connectivity disruption. During this time, users may have been unable to access or interact with the service. The issue is the result of a broader Cloudflare service incident.

2. resolved Dec 05, 2025, 10:05 AM UTC

   The Galaxy availability issue caused by the Cloudflare incident has been resolved, and the service is now fully operational.

Read the full incident report →

Started Nov 13, 2025, 01:54 PM UTC· resolved Nov 13, 2025, 08:15 PM UTC

1. monitoring Nov 13, 2025, 01:54 PM UTC

   We are experiencing elevated error rates and latency due to a database upgrade. We are currently mitigating the issue and it should resolve shortly.

2. resolved Nov 13, 2025, 08:15 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 04, 2025, 08:17 PM UTC· resolved Nov 04, 2025, 10:18 PM UTC

1. identified Nov 04, 2025, 08:17 PM UTC

   Data ingest live table creation and modification including starting/stopping are currently not working. We have identified the issue and are working on a fix. Data ingestion is unaffected and is continuing to work normally.

2. monitoring Nov 04, 2025, 09:04 PM UTC

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

3. resolved Nov 04, 2025, 10:18 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 20, 2025, 09:42 AM UTC· resolved Oct 20, 2025, 10:50 PM UTC

1. identified Oct 20, 2025, 09:42 AM UTC

   We are currently experiencing a service outage caused by an ongoing incident affecting our cloud provider, Amazon Web Services (AWS). Our teams are actively monitoring the situation and are in close contact with AWS as they work to resolve the issue. We will continue to provide updates and confirm once all services are fully restored.

2. identified Oct 20, 2025, 01:10 PM UTC

   Although some AWS services have been restored, others continue to fail, and we are still impacted. In particular, any Galaxy service tied to the AWS region us-east-1 is currently not functioning properly. This includes creating new clusters and modifying RBAC permissions. We will continue to work with AWS to restore our full functionality and provide updates here.

3. identified Oct 20, 2025, 03:18 PM UTC

   We are still affected by residual AWS outages, with many Galaxy functions affected (e.g., creating new clusters, result-set caching, modifying RBAC permissions, etc.). We continue to work with AWS to address the problems and will update the status here when we have new information to share.

4. identified Oct 20, 2025, 07:08 PM UTC

   We have put in some temporary mitigations to help alleviate the cluster startup problems in us east 1. At the same time we are still actively monitoring the AWS outage. Along with cluster startup, we think customers using galaxy telemetry and managed data ingestion may also experience data staleness. We are working with AWS to mitigate this and will provide more updates when there is new information to share.

5. monitoring Oct 20, 2025, 08:51 PM UTC

   AWS services are slowly getting restored. We are actively monitoring our services to ensure they recover as well

6. resolved Oct 20, 2025, 10:50 PM UTC

   All galaxy services affected by AWS outage should be operational at this point.

Read the full incident report →

Started Oct 14, 2025, 06:29 PM UTC· resolved Oct 14, 2025, 08:03 PM UTC

1. identified Oct 14, 2025, 06:29 PM UTC

   We have identified an issue affecting customers who are using Tabular connector which has been deprecated by Tabular. Customers using this connector may encounter failures when issuing queries. As a workaround, customers need to unregister the Tabular connector in order to mitigate the issue.

2. resolved Oct 14, 2025, 08:03 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 06, 2025, 02:27 PM UTC· resolved Oct 06, 2025, 02:54 PM UTC

1. investigating Oct 06, 2025, 02:27 PM UTC

   We are currently investigating this issue.

2. resolved Oct 06, 2025, 02:54 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 10, 2025, 07:00 PM UTC· resolved Sep 10, 2025, 08:17 PM UTC

1. investigating Sep 10, 2025, 07:00 PM UTC

   We are currently investigating an issue that prevents clusters from starting.

2. identified Sep 10, 2025, 07:16 PM UTC

   We have identified the issue and are working on mitigating it.

3. monitoring Sep 10, 2025, 07:24 PM UTC

   A fix has been implemented and service should be fully restored. We will continue to monitor the situation.

4. monitoring Sep 10, 2025, 08:09 PM UTC

   We are continuing to monitor for any further issues.

5. resolved Sep 10, 2025, 08:17 PM UTC

   The incident has been resolved.

Read the full incident report →

Started Sep 10, 2025, 10:37 AM UTC· resolved Sep 13, 2025, 10:52 PM UTC

1. monitoring Sep 10, 2025, 10:37 AM UTC

   We are aware of some users getting the `Failed fetching Arrow chunk` error when querying Snowflake tables for larger result sets. We have a fix and are testing it in our staging environment. Production should receive this fix in a matter of hours.

2. monitoring Sep 11, 2025, 08:37 AM UTC

   The fix was successfully tested in staging and is ready to be pushed into production soon.

3. monitoring Sep 11, 2025, 09:10 PM UTC

   The fix has been deployed to production.

4. resolved Sep 13, 2025, 10:52 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 21, 2025, 05:58 PM UTC· resolved Aug 21, 2025, 08:01 PM UTC

1. investigating Aug 21, 2025, 05:58 PM UTC

   We are currently investigating this issue.

2. investigating Aug 21, 2025, 06:39 PM UTC

   We are continuing to investigate this issue.

3. resolved Aug 21, 2025, 08:01 PM UTC

   This incident has been resolved. Galaxy was affected by upstream network issues from our provider Cloudflare. We will be investigating ways to make our systems more resilient during future network disruptions. (See https://www.cloudflarestatus.com/incidents/d9n3g1vnxdd2 for details of the upstream issue.)

Read the full incident report →

Started Aug 13, 2025, 06:53 PM UTC· resolved Aug 14, 2025, 06:30 PM UTC

1. identified Aug 13, 2025, 06:53 PM UTC

   We have identified an issue with the Galaxy Autoscaler where the recommendation engine is not detecting increased workloads (for scale-ups only, scale-downs are working as expected) which can lead to Trino clusters not being autoscaled to match the workload. We recommend to scale up the clusters manually as we work towards a permanent fix.

2. resolved Aug 14, 2025, 06:30 PM UTC

   Our investigation revealed that the autoscaling has been working as expected -- with that we're closing this incident.

Read the full incident report →

Started Aug 01, 2025, 08:08 AM UTC· resolved Aug 03, 2025, 06:33 AM UTC

1. investigating Aug 01, 2025, 08:08 AM UTC

   We are investigating the problem.

2. identified Aug 01, 2025, 11:21 AM UTC

   We have reported the problem to Snowflake.

3. identified Aug 01, 2025, 11:43 AM UTC

   We have escalated the problem with Snowflake.

4. identified Aug 01, 2025, 01:06 PM UTC

   We have a potential workaround for the issue and are working on a plan to release it to Production.

5. monitoring Aug 02, 2025, 08:43 AM UTC

   The fix has been deployed to Production. We are monitoring the change.

6. resolved Aug 03, 2025, 06:33 AM UTC

   This incident has been resolved.

Read the full incident report →