Databricks Azure experienced a minor incident on August 9, 2026 affecting Compute and Databricks SQL and 1 more component, lasting 1h 52m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 09, 2026, 03:23 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 09, 2026, 03:23 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.
- monitoring Aug 09, 2026, 04:17 AM UTC
Between 02:35 UTC and 03:35 UTC on August 9, 2026, a subset of customers using Azure Databricks may have experienced failures or errors with Classic Compute, Serverless Compute, Databricks SQL, Declarative Pipelines, and Jobs. Affected workloads may have seen unresponsive clusters, cluster connectivity issues, or failures when starting or running jobs and pipelines. Symptoms • Clusters became unresponsive or failed to launch • Jobs and pipelines failed due to lost cluster communication • Errors occurred when connecting to Databricks SQL endpoints or compute resources 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.
- monitoring Aug 09, 2026, 04:17 AM UTC
Between 02:35 UTC and 03:35 UTC on August 9, 2026, a subset of customers using Azure Databricks may have experienced failures or errors with Classic Compute, Serverless Compute, Databricks SQL, Declarative Pipelines, and Jobs. Affected workloads may have seen unresponsive clusters, cluster connectivity issues, or failures when starting or running jobs and pipelines. Symptoms • Clusters became unresponsive or failed to launch • Jobs and pipelines failed due to lost cluster communication • Errors occurred when connecting to Databricks SQL endpoints or compute resources 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.
- resolved Aug 09, 2026, 05:16 AM UTC
Between 02:35 UTC and 03:35 UTC on August 9, 2026, a subset of customers using Azure Databricks may have experienced failures or errors with Classic Compute, Serverless Compute, Databricks SQL, Declarative Pipelines, and Jobs. Affected workloads may have seen unresponsive clusters, cluster connectivity issues, or failures when starting or running jobs and pipelines. Symptoms • Clusters became unresponsive or failed to launch • Jobs and pipelines failed due to lost cluster communication • Errors occurred when connecting to Databricks SQL endpoints or compute resources 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