Databricks Azure experienced a minor incident on October 1, 2026 affecting Compute and Notebooks and 1 more component, lasting 2h 11m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 01, 2026, 08:19 AM UTC
We are actively investigating an issue affecting Databricks compute. We will provide another update within 1 hour, or sooner if there is a material change in service status.
- investigating Oct 01, 2026, 08:19 AM UTC
We are actively investigating an issue affecting Databricks compute. We will provide another update within 1 hour, or sooner if there is a material change in service status.
- monitoring Oct 01, 2026, 09:56 AM UTC
Impact Summary Between 06:13 UTC and 08:37 UTC October 01, 2026, customers using Azure Databricks may have experienced degraded performance with Classic Compute. Affected customers may have been unable to provision, attach to, or run customer-managed compute-backed workloads during this window. Symptoms • Cluster launch failures due to library installation errors • Library installation failures or timeouts on clusters • Job and notebook run failures for workloads dependent on cluster libraries Current Status The issue has been mitigated and service is operational. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
- monitoring Oct 01, 2026, 09:56 AM UTC
Impact Summary Between 06:13 UTC and 08:37 UTC October 01, 2026, customers using Azure Databricks may have experienced degraded performance with Classic Compute. Affected customers may have been unable to provision, attach to, or run customer-managed compute-backed workloads during this window. Symptoms • Cluster launch failures due to library installation errors • Library installation failures or timeouts on clusters • Job and notebook run failures for workloads dependent on cluster libraries Current Status The issue has been mitigated and service is operational. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
- resolved Oct 01, 2026, 10:31 AM UTC
Impact Summary Between 06:13 UTC and 08:37 UTC on October 01, 2026, customers using Azure Databricks may have experienced degraded availability with Classic Compute. Affected customers may have encountered cluster launch failures, library installation failures, or failures of dependent jobs and notebooks during this window. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Cluster library installation failures • Job and notebook run failures during cluster startup Current Status The issue has been resolved, and all affected services have been restored. Next Update This is the final update for this incident. We apologize for any inconvenience this may have caused. If you require further details about this incident, please submit an Azure support ticket. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription