Databricks Azure experienced a minor incident on August 4, 2026 affecting Compute and Lakeflow and 1 more component, lasting 1h 41m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 04, 2026, 08:26 PM UTC
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.
- investigating Aug 04, 2026, 08:26 PM UTC
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.
- investigating Aug 04, 2026, 08:32 PM UTC
Starting at approximately 20:00 UTC on August 4, 2026, customers using Azure Databricks may be experiencing failures or errors when using Classic Compute or Notebooks services. Some operations may fail, time out, or be delayed. We are actively investigating the issue. Symptoms • Failures or errors when starting or running Classic Compute clusters • Notebooks may fail to load, execute commands, or respond slowly • Intermittent API request failures affecting compute and notebook operations Recommendations No customer action is required at this time. Current Status The incident is in the Investigating stage; teams have identified a likely correlated deployment and are actively rolling it back while confirming root cause. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
- investigating Aug 04, 2026, 08:32 PM UTC
Starting at approximately 20:00 UTC on August 4, 2026, customers using Azure Databricks may be experiencing failures or errors when using Classic Compute or Notebooks services. Some operations may fail, time out, or be delayed. We are actively investigating the issue. Symptoms • Failures or errors when starting or running Classic Compute clusters • Notebooks may fail to load, execute commands, or respond slowly • Intermittent API request failures affecting compute and notebook operations Recommendations No customer action is required at this time. Current Status The incident is in the Investigating stage; teams have identified a likely correlated deployment and are actively rolling it back while confirming root cause. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.
- monitoring Aug 04, 2026, 09:08 PM UTC
Between 20:00 UTC and 20:56 UTC on August 4, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors with Classic Compute, Jobs, and Notebooks services. Affected customers may have seen failures, timeouts, or delays when starting or running compute clusters, executing notebook commands, or running jobs dependent on clusters. The disruption has since been mitigated. Symptoms • Failures or errors when starting or running Classic Compute clusters • Notebooks failed to load, execute commands, or responded slowly • Jobs experienced failures due to their dependency on affected clusters 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 04, 2026, 09:08 PM UTC
Between 20:00 UTC and 20:56 UTC on August 4, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors with Classic Compute, Jobs, and Notebooks services. Affected customers may have seen failures, timeouts, or delays when starting or running compute clusters, executing notebook commands, or running jobs dependent on clusters. The disruption has since been mitigated. Symptoms • Failures or errors when starting or running Classic Compute clusters • Notebooks failed to load, execute commands, or responded slowly • Jobs experienced failures due to their dependency on affected clusters 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 04, 2026, 10:08 PM UTC
Between 20:00 UTC and 20:56 UTC on August 4, 2026, a subset of customers using Azure Databricks may have experienced degraded availability or errors with Classic Compute, Jobs, and Notebooks services. Affected customers may have seen failures, timeouts, or delays when starting or running compute clusters, executing notebook commands, or running jobs dependent on clusters. The disruption was resolved by the end of the impact window. Symptoms • Failures or errors when starting or running Classic Compute clusters • Notebooks failed to load, execute commands, or responded slowly • Jobs experienced failures due to their dependency on affected clusters 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