Databricks Azure experienced a minor incident on August 3, 2026 affecting Compute and Lakeflow and 1 more component, lasting 3h 19m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 03, 2026, 02:07 AM UTC
We are actively investigating an issue with the Databricks service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
- investigating Aug 03, 2026, 02:07 AM UTC
We are actively investigating an issue with the Databricks service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
- identified Aug 03, 2026, 02:31 AM UTC
Starting at approximately 00:42 UTC on August 3, 2026, customers using Azure Databricks may be experiencing failures or delays when launching clusters, running jobs, or using Serverless Compute. Affected services include Classic Compute, Serverless Compute, and Jobs, with symptoms such as cluster launch failures and job termination errors. We are actively investigating the issue. Symptoms • Cluster launch failures and unexpected cluster terminations • Job runs terminating unexpectedly or failing to start • Delayed or failed startup of Serverless Compute workloads Recommendations No customer action is required at this time. Current Status We are actively investigating the incident affecting Classic Compute, Serverless Compute, and Jobs, caused by an issue with our cloud provider, and are working closely with them to restore full service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
- identified Aug 03, 2026, 02:31 AM UTC
Starting at approximately 00:42 UTC on August 3, 2026, customers using Azure Databricks may be experiencing failures or delays when launching clusters, running jobs, or using Serverless Compute. Affected services include Classic Compute, Serverless Compute, and Jobs, with symptoms such as cluster launch failures and job termination errors. We are actively investigating the issue. Symptoms • Cluster launch failures and unexpected cluster terminations • Job runs terminating unexpectedly or failing to start • Delayed or failed startup of Serverless Compute workloads Recommendations No customer action is required at this time. Current Status We are actively investigating the incident affecting Classic Compute, Serverless Compute, and Jobs, caused by an issue with our cloud provider, and are working closely with them to restore full service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
- identified Aug 03, 2026, 03:27 AM UTC
Starting at approximately 00:42 UTC on August 3, 2026, some customers using Azure Databricks in the regions may be experiencing failures or delays when launching clusters, running jobs, or using Serverless Compute. Affected services include Classic Compute, Serverless Compute, and Jobs. Symptoms • Cluster launch failures and unexpected cluster terminations • Job runs terminating unexpectedly or failing to start • Delayed or failed startup of Serverless Compute workloads Recommendations No customer action is required at this time. Current Status We have identified the issue affecting some customers in the regions and are working closely with our cloud provider to restore full service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
- identified Aug 03, 2026, 03:27 AM UTC
Starting at approximately 00:42 UTC on August 3, 2026, some customers using Azure Databricks in the regions may be experiencing failures or delays when launching clusters, running jobs, or using Serverless Compute. Affected services include Classic Compute, Serverless Compute, and Jobs. Symptoms • Cluster launch failures and unexpected cluster terminations • Job runs terminating unexpectedly or failing to start • Delayed or failed startup of Serverless Compute workloads Recommendations No customer action is required at this time. Current Status We have identified the issue affecting some customers in the regions and are working closely with our cloud provider to restore full service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
- monitoring Aug 03, 2026, 04:05 AM UTC
Between 0:42 UTC and 3:43 UTC on August 3, 2026, a subset of customers using Azure Databricks may have experienced failures or delays when launching clusters, running jobs, or using Serverless Compute. Affected services included Classic Compute, Serverless Compute, and Jobs, with symptoms such as cluster launch failures, job termination errors, and delayed startup of Serverless Compute workloads. Symptoms • Cluster launch failures and unexpected cluster terminations • Job runs terminating unexpectedly or failing to start • Delayed or failed startup of Serverless Compute workloads Current Status The issue has been mitigated and services have been restored. Next Update We will provide another update within 2 hour, or sooner if there is a material change in service status.
- monitoring Aug 03, 2026, 04:05 AM UTC
Between 0:42 UTC and 3:43 UTC on August 3, 2026, a subset of customers using Azure Databricks may have experienced failures or delays when launching clusters, running jobs, or using Serverless Compute. Affected services included Classic Compute, Serverless Compute, and Jobs, with symptoms such as cluster launch failures, job termination errors, and delayed startup of Serverless Compute workloads. Symptoms • Cluster launch failures and unexpected cluster terminations • Job runs terminating unexpectedly or failing to start • Delayed or failed startup of Serverless Compute workloads Current Status The issue has been mitigated and services have been restored. Next Update We will provide another update within 2 hour, or sooner if there is a material change in service status.
- resolved Aug 03, 2026, 05:27 AM UTC
Between 0:42 UTC and 3:43 UTC on August 3, 2026, a subset of customers using Azure Databricks may have experienced failures or delays when launching clusters, running jobs, or using Serverless Compute. Affected services included Classic Compute, Serverless Compute, and Jobs, with symptoms such as cluster launch failures, job termination errors, and delayed startup of Serverless Compute workloads. Symptoms • Cluster launch failures and unexpected cluster terminations • Job runs terminating unexpectedly or failing to start • Delayed or failed startup of Serverless Compute workloads Current Status This incident has been resolved. 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