Is GCP Databricks down?

We are actively investigating an issue with the Databricks service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Starting at 26 May 2026 17:14 UTC, customers using Lakeflow Spark Declarative Pipelines may experience pipeline start and restart failures. Symptoms Customers may observe: - Pipelines failing to start or restart - Pipeline updates terminating shortly after launch Recommendations Manually stopping and restarting Pipelines is expected to succeed. Current Status Our engineering team is actively investigating the issue and working to identify the cause. We will share more information as it becomes available. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Between 26 May 2026 17:14 UTC and 26 May 2026 20:53 UTC, customers using Lakeflow Spark Declarative Pipelines may have experienced pipeline start and restart failures. Symptoms Customers may have observed: - Pipelines failing to start or restart - Pipeline updates terminating shortly after launch Recommendations No customer action is required at this time. Current Status A fix has been applied and service has been restored. We are actively monitoring to confirm stability. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Starting at 05 May 2026 03:33 UTC, Classic Compute in multiple regions may fail to start clusters when init scripts are configured. There was brief recovery observed at 05:55 UTC. Some customers may continue to observe failures starting 06:10 UTC Symptoms Customers may observe: Clusters failing to initialize or not starting Extended cluster start times when init scripts are configured Recommendations No customer action is required at this time. Current Status We have identified the root cause as an outage affecting an external Ubuntu package repository. The external provider has reported service restoration as of 05 May 2026 05:55 UTC. Some customers may continue to observe delays in cluster initialization while we confirm full recovery. We are actively monitoring and continuing to investigate residual impact. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Starting at 05 May 2026 03:33 UTC, Classic Compute in multiple regions may fail to start clusters when init scripts are configured. There was brief recovery observed at 05:55 UTC. Some customers may continue to observe failures starting 06:10 UTC Symptoms Customers may observe: Clusters failing to initialize or not starting Extended cluster start times when init scripts are configured Recommendations No customer action is required at this time. Current Status We have identified the root cause as an outage affecting an external Ubuntu package repository. The external provider has reported service restoration as of 05 May 2026 08:06 UTC. Some customers may continue to observe delays in cluster initialization while we confirm full recovery. We are actively monitoring and continuing to investigate residual impact. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Between 03:33 UTC and 08:06 UTC on 05 May 2026 , Classic Compute in multiple regions may have failed to start clusters when init scripts configured. There was brief recovery observed at 05:55 UTC. Full recovery was observed at 08:06 UTC. Symptoms Customers may observe: Clusters failing to initialize or not starting Extended cluster start times when init scripts are configured Recommendations No customer action is required at this time. Current Status The issue has been mitigated. We are continuing to monitor for any residual impact. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.