Databricks Azure is currently experiencing a minor incident affecting Compute and Unity Catalog (West US 3) and 1 more component, which began 3h ago. The vendor's full update timeline is below.
Affected components
Update timeline
- investigating Jun 10, 2026, 07:00 AM UTC
We are actively investigating an issue affecting Databricks compute. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
- identified Jun 10, 2026, 07:11 AM UTC
Starting at approximately 3:54 UTC on June 10, 2026, a subset of customers using Azure Databricks may be experiencing failures and errors when attempting to launch or restart Classic Compute clusters. Affected customers may find that their clusters are unable to start successfully, with startup attempts resulting in errors or prolonged failures. This disruption is affecting Classic Compute workloads, and the issue remains ongoing as our engineering teams continue to work toward a resolution. Symptoms • Cluster launch or restart attempts are failing, with errors indicating that the compute instance is unreachable after bootstrap completes • Classic Compute clusters cannot be started or restarted, leaving dependent workloads unavailable • Degraded availability of Classic Compute resources, with cluster startup errors being reported during normal operations Recommendations No customer action is required at this time. Current Status We have identified the root cause and are working on a fix. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
- monitoring Jun 10, 2026, 08:30 AM UTC
Between 3:54 UTC and 7:53 UTC on June 10, 2026, a subset of customers using Azure Databricks may have experienced failures or errors when attempting to launch or restart Classic Compute clusters. Affected customers may have found that cluster startup attempts resulted in errors or prolonged failures, with degraded availability of Classic Compute workloads during this period. Symptoms • Classic Compute cluster launch or restart attempts failed with errors indicating the compute instance was unreachable after bootstrap completed. • Customers were unable to start or restart Classic Compute clusters, leaving dependent workloads unavailable. • Cluster startup errors were reported during normal operations, with some clusters failing intermittently after initial recovery. Current Status The issue has been mitigated and services have been restored. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.