GCP Databricks Outage History

GCP Databricks experienced an issue with their Jobs Service affecting Lakeflow Spark Declarative Pipelines, causing pipeline start and restart failures that would terminate shortly after launch. The incident lasted 1.5 hours and was classified as minor severity. Customers could resolve the issue by manually stopping and restarting their pipelines while the engineering team investigated the root cause.

GCP Databricks Classic Compute experienced cluster startup failures across multiple regions for 3.4 hours starting May 5, 2026 at 03:33 UTC, specifically affecting clusters configured with init scripts. Customers observed clusters failing to initialize, not starting at all, or experiencing extended startup times. The issue was caused by an outage at an external Ubuntu package repository, which was restored by the external provider at 08:06 UTC.

GCP Databricks experienced a major outage starting at 17:20 UTC on April 27, 2026, affecting Classic Compute and Serverless Compute clusters across multiple regions for approximately 1 hour. Customers experienced cluster start failures, unresponsive existing clusters, and inability to connect notebooks, jobs, and SQL workloads to their clusters. The root cause was identified and remediation efforts were underway as of the last update.

GCP Databricks experienced a 4.8-hour service disruption affecting Jobs Service, User Interface, Databricks SQL, MLFlow, and Compute Service due to an expired HashiCorp GPG key used for Terraform binary verification in Declarative Automation Bundles. Customers experienced failures in CI/CD pipelines, GPG checksum verification errors, and widespread inability to perform automated deployments starting April 18, 2026 at 21:50 UTC. The issue was resolved by releasing a fix in Databricks CLI version 0.297.2 that incorporates a new public key to bypass the expired GPG key check, with patch versions being developed for older CLI versions.

GCP Databricks customers in multiple regions experienced delays or failures when launching clusters and running jobs that used init-scripts dependent on Ubuntu package repositories (archive.ubuntu.com and security.ubuntu.com) starting at 01:15 UTC on April 17, 2026. The incident affected the Compute Service, causing cluster launch failures and job execution delays for workloads relying on these package repositories. The issue was stabilizing after 52 minutes with teams actively monitoring for full recovery.

GCP Databricks experienced a compute service issue starting at 05:54 UTC on April 16, 2026, causing cluster launch delays and failures across multiple regions for 1.5 hours. Jobs dependent on affected clusters also failed or experienced delays during this period. The issue appeared to be stabilizing by the end of the incident window, with the team monitoring for full recovery.

From 02:04 to 02:10 UTC on April 13, 2026, GCP Databricks experienced a major authentication system failure affecting all cloud providers across multiple regions for 6 minutes. Customers were unable to log into Databricks workspaces, and all authentication requests through APIs and SDKs failed, impacting the User Interface, Databricks SQL, MLFlow, Jobs Service, and Compute Service. Service was fully restored by 02:10 UTC with no customer action required.