ES-1974209

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.

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.