Azure Databricks Outage History

Azure Databricks experienced a major incident starting at 17:20 UTC on April 27, 2026, affecting Classic Compute and Serverless Compute clusters across multiple regions for approximately 1 hour. Customers encountered 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.

Azure Databricks experienced compute service failures in the East US region for 10.9 hours, affecting Classic Compute, Jobs Compute, and later Serverless Compute workloads. Customers encountered cluster launch failures, job run failures during startup, and Serverless workloads failing to start. The incident was caused by an underlying Azure cloud provider issue, with Databricks engineering working directly with Azure to implement mitigations and achieve partial recovery.

Azure Databricks customers using Declarative Automation Bundles experienced CI/CD pipeline failures and deployment issues for 4.8 hours due to an expired GPG key from HashiCorp that prevented proper Terraform binary verification. The incident affected multiple components including the User Interface, Databricks SQL, Account Console, Compute Service, and Jobs Service, causing widespread inability to perform automated deployments. 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.

Azure 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 issue affected the Compute Service and caused cluster launch failures and job execution delays for workloads relying on these package repositories. The incident lasted 1.1 hours with the team actively investigating and monitoring for full recovery as the issue appeared to be stabilizing.

Azure Databricks experienced a compute service issue lasting 1.6 hours where customers across multiple regions encountered cluster launch delays and failures starting at 05:54 UTC on April 16, 2026. Jobs dependent on the affected clusters also failed or experienced delays as a result. The issue appeared to be stabilizing by the end of the incident period with the team monitoring for full recovery.

Azure Databricks experienced a 32-minute incident affecting Serverless Compute in the westcentralus region, where customers encountered failures when starting or provisioning compute resources and errors when running workloads. The engineering team identified the root cause and worked with the cloud provider to restore service functionality.

Azure Databricks experienced a service incident affecting the Compute Service, Jobs Service, Databricks SQL, and Account Console components. The incident lasted 32 minutes and was classified as minor severity. The service team actively investigated the platform issue, though the specific resolution details were not provided in the available updates.

Azure Databricks experienced a compute service outage in the West US 3 region lasting 2.9 hours, affecting Serverless Compute and SQL Warehouses. Customers encountered failures when starting compute clusters, connection timeouts, and SQL Warehouse query execution failures. A mitigation was applied and service levels improved, with the team continuing to monitor for full restoration.

Azure Databricks experienced degraded availability with Serverless Compute starting at 11:00 UTC on March 24, 2026, lasting 2.9 hours. Customers encountered cluster launch failures with driver unreachable errors, job execution failures with DRIVER_UNRESPONSIVE errors, clusters stuck in restart loops, and failed new cluster creation during spin-up. The incident was classified as minor and the service was actively investigating the compute service issues.

Azure Databricks experienced a compute service issue affecting Classic Compute in the Azure US Gov Virginia region, where customers encountered failures when creating or starting clusters. The incident lasted 2.9 hours and was linked to an underlying cloud provider issue. The service was actively investigating the cluster failures with no customer action required during the incident.