ES-1945162

Update timeline

1. investigating May 29, 2026, 05:59 AM 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.

2. investigating May 29, 2026, 05:59 AM 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.

3. investigating May 29, 2026, 06:19 AM UTC

   Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We are actively investigating failures affecting Classic Compute, Serverless Compute, and Databricks Apps in collaboration with our cloud provider, and are working to restore full service availability as quickly as possible. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. investigating May 29, 2026, 06:19 AM UTC

   Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We are actively investigating failures affecting Classic Compute, Serverless Compute, and Databricks Apps in collaboration with our cloud provider, and are working to restore full service availability as quickly as possible. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

5. identified May 29, 2026, 07:37 AM UTC

   Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. For live updates on the underlying infrastructure status, customers can refer to the Azure status page at https://azure.status.microsoft/en-us/status. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue and are actively working with our cloud provider to restore full service availability as quickly as possible. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

6. identified May 29, 2026, 07:37 AM UTC

   Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. For live updates on the underlying infrastructure status, customers can refer to the Azure status page at https://azure.status.microsoft/en-us/status. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue and are actively working with our cloud provider to restore full service availability as quickly as possible. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

7. identified May 29, 2026, 08:49 AM UTC

   Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue and are actively working with our cloud provider to restore full service availability as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

8. identified May 29, 2026, 08:49 AM UTC

   Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue and are actively working with our cloud provider to restore full service availability as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

9. identified May 29, 2026, 09:57 AM UTC

   Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue and are actively working with our cloud provider to restore full service availability as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

10. identified May 29, 2026, 09:57 AM UTC

    Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue and are actively working with our cloud provider to restore full service availability as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

11. identified May 29, 2026, 11:37 AM UTC

    Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute appears to be showing partial recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

12. identified May 29, 2026, 11:37 AM UTC

    Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute appears to be showing partial recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

13. identified May 29, 2026, 01:07 PM UTC

    Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute, Serverless Compute, appear to be showing recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

14. identified May 29, 2026, 01:07 PM UTC

    Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute, Serverless Compute, appear to be showing recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

15. identified May 29, 2026, 03:38 PM UTC

    Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute, Serverless Compute, appear to be showing recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

16. identified May 29, 2026, 03:38 PM UTC

    Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute, Serverless Compute, appear to be showing recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

17. identified May 29, 2026, 04:39 PM UTC

    Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute, Serverless Compute, and other Databricks services appear to be showing recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

18. identified May 29, 2026, 04:39 PM UTC

    Starting at approximately 05:25 UTC on May 29, 2026, a subset of customers using Azure Databricks may be experiencing failures or degraded availability when launching or running workloads on Classic Compute, Serverless Compute, and Databricks Apps. Customers using Unity Catalog may also be experiencing errors or degraded availability. Symptoms • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute, Serverless Compute, and other Databricks services appear to be showing recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

19. monitoring May 29, 2026, 06:16 PM UTC

    Impact Summary From 29 May 2026 05:00 UTC to 29 May 2026 16:40 UTC, customers using Databricks in the West US 2 region experienced disruptions to compute startup, query execution, and data access. Service has been restored. Symptoms Customers experienced: • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute, Serverless Compute, and other Databricks services appear to be showing recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status. Next Update We will provide another update within 2 hours, or sooner if there is a material change in service status.

20. monitoring May 29, 2026, 06:16 PM UTC

    Impact Summary From 29 May 2026 05:00 UTC to 29 May 2026 16:40 UTC, customers using Databricks in the West US 2 region experienced disruptions to compute startup, query execution, and data access. Service has been restored. Symptoms Customers experienced: • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident as a cloud provider infrastructure issue. Classic Compute, Serverless Compute, and other Databricks services appear to be showing recovery; we are continuing to work with our cloud provider to restore full service availability for all impacted services, as quickly as possible. For live updates on the underlying infrastructure status, customers can monitor the Azure status page at https://azure.status.microsoft/en-us/status. Next Update We will provide another update within 2 hours, or sooner if there is a material change in service status.

21. resolved May 29, 2026, 08:35 PM UTC

    Impact Summary From 29 May 2026 05:00 UTC to 29 May 2026 16:40 UTC, customers using Databricks in the West US 2 region experienced disruptions to compute startup, query execution, and data access. Service has been restored. Symptoms Customers experienced: • Cluster launches failing or terminating unexpectedly when starting Classic Compute or Serverless Compute workloads • Jobs and runs failing to start or complete due to compute unavailability • Databricks Apps and Unity Catalog experiencing degraded availability or errors Current Status This incident has been fully resolved as of 29 May 2026 16:40 UTC. We apologize for the disruption. This incident was related to a cloud provider issue. Additional information is available on the cloud provider's status page: https://azure.status.microsoft.com/en-us/status/ If you require further details about this incident, please submit an Azure support ticket. Next Update No further updates are planned for this incident. 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