Azure Databricks Outage History

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.