Databricks Azure incident

ES-2126410

Minor Resolved View vendor source →

Databricks Azure experienced a minor incident on August 12, 2026 affecting Compute and Lakeflow and 1 more component, lasting 1h 32m. The incident has been resolved; the full update timeline is below.

Started
Aug 12, 2026, 06:11 PM UTC
Resolved
Aug 12, 2026, 07:44 PM UTC
Duration
1h 32m
Detected by Pingoru
Aug 12, 2026, 06:11 PM UTC

Affected components

ComputeLakeflowUnity Catalog (Central India)

Update timeline

  1. investigating Aug 12, 2026, 06:11 PM 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.

  2. investigating Aug 12, 2026, 06:11 PM 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.

  3. investigating Aug 12, 2026, 06:21 PM UTC

    Starting at approximately 17:56 UTC on August 12, 2026, customers using Azure Databricks may be experiencing failures or terminations of Serverless Compute workloads, along with degraded availability. Symptoms • Serverless Compute clusters terminating unexpectedly • Errors when starting or running Serverless Compute workloads • Degraded availability of Serverless Compute Recommendations No customer action is required at this time. Current Status Databricks engineering teams are actively investigating a Sev1 incident impacting Serverless Compute availability. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

  4. investigating Aug 12, 2026, 06:21 PM UTC

    Starting at approximately 17:56 UTC on August 12, 2026, customers using Azure Databricks may be experiencing failures or terminations of Serverless Compute workloads, along with degraded availability. Symptoms • Serverless Compute clusters terminating unexpectedly • Errors when starting or running Serverless Compute workloads • Degraded availability of Serverless Compute Recommendations No customer action is required at this time. Current Status Databricks engineering teams are actively investigating a Sev1 incident impacting Serverless Compute availability. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

  5. monitoring Aug 12, 2026, 06:42 PM UTC

    Between 17:56 UTC and 18:20 UTC on August 12, 2026, a subset of customers using Azure Databricks may have experienced failures or terminations of Serverless Compute workloads along with degraded availability. This disruption also affected related Jobs and Pipelines services during the same window. Symptoms • Serverless Compute clusters terminated unexpectedly • Errors occurred when starting or running Serverless Compute workloads • Jobs and Pipelines experienced degraded availability 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.

  6. monitoring Aug 12, 2026, 06:42 PM UTC

    Between 17:56 UTC and 18:20 UTC on August 12, 2026, a subset of customers using Azure Databricks may have experienced failures or terminations of Serverless Compute workloads along with degraded availability. This disruption also affected related Jobs and Pipelines services during the same window. Symptoms • Serverless Compute clusters terminated unexpectedly • Errors occurred when starting or running Serverless Compute workloads • Jobs and Pipelines experienced degraded availability 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.

  7. resolved Aug 12, 2026, 07:44 PM UTC

    Between 17:56 UTC and 18:20 UTC on August 12, 2026, a subset of customers using Azure Databricks may have experienced failures or terminations of Serverless Compute workloads, along with degraded availability. This disruption also affected related Jobs and Pipelines services during the same window. Symptoms • Serverless Compute clusters terminated unexpectedly • Errors occurred when starting or running Serverless Compute workloads • Jobs and Pipelines experienced degraded availability 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