Is Databricks Azure down?

Impact Summary Starting at 04:51 UTC September 12, 2026, customers using Azure Databricks in West Europe may experience failures or degraded availability with Classic Compute, and with Jobs, Declarative Pipelines, and notebooks that depend on those clusters. Affected customers may encounter cluster launch failures, cloud provider errors, or allocation timeouts. Symptoms • Cluster launch failures with cloud provider error messages • Cluster allocation timeouts during compute startup • Failed or delayed jobs, pipelines, and notebook execution dependent on affected clusters Recommendations No customer action is required at this time. Current Status The issue is under active investigation in coordination with the cloud provider. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

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.

Impact Summary Starting at 04:51 UTC September 12, 2026, customers using Azure Databricks in West Europe may experience failures or degraded availability with Classic Compute, and with Jobs, Declarative Pipelines, and notebooks that depend on those clusters. Affected customers may encounter cluster launch failures, cloud provider errors, or allocation timeouts. Symptoms • Cluster launch failures with cloud provider error messages • Cluster allocation timeouts during compute startup • Failed or delayed jobs, pipelines, and notebook execution dependent on affected clusters Recommendations No customer action is required at this time. Current Status The issue is under active investigation in coordination with the cloud provider. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Starting at 05:06 UTC September 12, 2026, customers using Azure Databricks in West Europe may experience failures or degraded availability with Classic Compute, and with Jobs, Declarative Pipelines, and notebooks that depend on those clusters. Affected customers may encounter cluster launch failures, cloud provider errors, or allocation timeouts. Symptoms • Cluster launch failures with cloud provider error messages • Cluster allocation timeouts during compute startup • Failed or delayed jobs, pipelines, and notebook execution dependent on affected clusters Recommendations No customer action is required at this time. Current Status The issue is under active investigation in coordination with the cloud provider. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Starting at 04:51 UTC September 12, 2026, customers using Azure Databricks in West Europe may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, clusters remaining in a pending state, and failed or terminated job and pipeline runs. Symptoms • Cluster launch failures and clusters stuck in Pending or Starting • Notebook attach failures on customer-managed compute • Jobs and pipeline runs failing, terminating during cluster startup, or not progressing Recommendations No customer action is required at this time. Current Status The issue has been identified and mitigation efforts are in progress in coordination with the cloud provider. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Starting at 04:51 UTC September 12, 2026, customers using Azure Databricks in West Europe may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, clusters remaining in a pending state, and failed or terminated job and pipeline runs. Symptoms • Cluster launch failures and clusters stuck in Pending or Starting • Notebook attach failures on customer-managed compute • Jobs and pipeline runs failing, terminating during cluster startup, or not progressing Recommendations No customer action is required at this time. Current Status The issue has been identified and mitigation efforts are in progress in coordination with the cloud provider. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Between 04:51 UTC and 07:55 UTC September 12, 2026, customers using Azure Databricks in West Europe may have experienced degraded availability with Classic Compute and Jobs. Affected customers may have encountered cluster launch failures, clusters remaining in a pending state, and job or pipeline runs failing during cluster startup within this window. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Notebook attach failures on affected clusters • Job and pipeline runs failing, terminating, or not progressing during cluster startup Current Status The issue has been mitigated and service is operational. Mitigation was carried out in coordination with the cloud provider. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Between 04:51 UTC and 07:55 UTC September 12, 2026, customers using Azure Databricks in West Europe may have experienced degraded availability with Classic Compute and Jobs. Affected customers may have encountered cluster launch failures, clusters remaining in a pending state, and job or pipeline runs failing during cluster startup within this window. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Notebook attach failures on affected clusters • Job and pipeline runs failing, terminating, or not progressing during cluster startup Current Status The issue has been mitigated and service is operational. Mitigation was carried out in coordination with the cloud provider. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Between 04:51 UTC and 07:55 UTC September 12, 2026, customers using Azure Databricks in West Europe may have experienced degraded availability with Classic Compute and Jobs. Affected customers may have encountered cluster launch failures, clusters remaining in a pending state, and job or pipeline runs failing during cluster startup within this window. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Notebook attach failures on affected clusters • Job and pipeline runs failing, terminating, or not progressing during cluster startup Current Status The issue has been resolved, and all affected services have been restored. Follow-up analysis is being conducted in coordination with the cloud provider. Next Update This is the final update for this incident. 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

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.

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.

Impact Summary Starting at 10:16 UTC September 11, 2026, customers using Azure Databricks in West Europe may experience degraded availability with Serverless Compute. Affected customers may be unable to start or run Databricks-managed serverless workloads for notebooks, workflows, and Lakeflow pipelines. Symptoms • Serverless workloads failing to start • Unexpected termination of running workloads • Errors returned when attempting to execute serverless workloads Recommendations No customer action is required at this time. Current Status The issue is under active investigation, in coordination with the cloud provider. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Starting at 10:16 UTC September 11, 2026, customers using Azure Databricks in West Europe may experience degraded availability with Serverless Compute. Affected customers may be unable to start or run Databricks-managed serverless workloads for notebooks, workflows, and Lakeflow pipelines. Symptoms • Serverless workloads failing to start • Unexpected termination of running workloads • Errors returned when attempting to execute serverless workloads Recommendations No customer action is required at this time. Current Status The issue is under active investigation, in coordination with the cloud provider. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Starting at 09:07 UTC September 11, 2026, customers using Azure Databricks in West Europe may experience degraded availability with Serverless Compute. Affected customers may be unable to start or run Databricks-managed serverless workloads for notebooks, workflows, and Lakeflow pipelines, and may encounter errors or unexpected workload termination. Symptoms • Serverless workloads failing to start or terminating unexpectedly • Cluster allocation timeouts during workload startup • Errors returned when attempting to execute serverless notebooks, workflows, or Lakeflow pipelines Recommendations No customer action is required at this time. Current Status The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact is continuing at a reduced level while the investigation remains ongoing. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Starting at 09:07 UTC September 11, 2026, customers using Azure Databricks in West Europe may experience degraded availability with Serverless Compute. Affected customers may be unable to start or run Databricks-managed serverless workloads for notebooks, workflows, and Lakeflow pipelines, and may encounter errors or unexpected workload termination. Symptoms • Serverless workloads failing to start or terminating unexpectedly • Cluster allocation timeouts during workload startup • Errors returned when attempting to execute serverless notebooks, workflows, or Lakeflow pipelines Recommendations No customer action is required at this time. Current Status The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact is continuing at a reduced level while the investigation remains ongoing. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Between 09:07 UTC and 13:23 UTC on September 11, 2026, customers using Azure Databricks in West Europe may have experienced degraded availability with Serverless Compute. Affected customers may have been unable to start or run Databricks-managed serverless workloads for notebooks, workflows, and Lakeflow pipelines during this window. Symptoms • Serverless workloads failing to start or terminating unexpectedly • Errors returned when attempting to execute serverless workloads • Cluster allocation timeouts and driver connectivity failures Current Status The issue has been mitigated, and service is operational. Investigation is continuing in coordination with the cloud provider. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Between 09:07 UTC and 13:23 UTC on September 11, 2026, customers using Azure Databricks in West Europe may have experienced degraded availability with Serverless Compute. Affected customers may have been unable to start or run Databricks-managed serverless workloads for notebooks, workflows, and Lakeflow pipelines during this window. Symptoms • Serverless workloads failing to start or terminating unexpectedly • Errors returned when attempting to execute serverless workloads • Cluster allocation timeouts and driver connectivity failures Current Status The issue has been mitigated, and service is operational. Investigation is continuing in coordination with the cloud provider. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Between 09:07 UTC and 13:23 UTC on September 11, 2026, customers using Azure Databricks in West Europe may have experienced degraded availability with Serverless Compute. Affected customers may have been unable to start or run Databricks-managed serverless workloads for notebooks, workflows, and Lakeflow pipelines, and may have encountered errors or unexpected workload termination during this window. Symptoms • Serverless workloads failing to start or terminating unexpectedly • Cluster allocation timeouts during workload startup • Errors returned when attempting to execute serverless notebooks, jobs, or pipelines Current Status The issue has been resolved, and all affected services have been restored. Follow-up analysis is being conducted in coordination with the cloud provider. Next Update This is the final update for this incident. 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

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.

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.

Impact Summary Starting at 06:03 UTC September 11, 2026, customers using Azure Databricks may experience degraded availability with cluster launch and cluster termination operations. Affected customers may encounter cloud provider launch failures, network health check failures, and delays or errors when starting or terminating compute. Symptoms • Cluster launch failures with cloud provider launch errors • Failed or delayed cluster termination requests • Network check failures during compute startup Recommendations No customer action is required at this time. Current Status The issue is under active investigation in coordination with the cloud provider. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Starting at 06:03 UTC September 11, 2026, customers using Azure Databricks may experience degraded availability with cluster launch and cluster termination operations. Affected customers may encounter cloud provider launch failures, network health check failures, and delays or errors when starting or terminating compute. Symptoms • Cluster launch failures with cloud provider launch errors • Failed or delayed cluster termination requests • Network check failures during compute startup Recommendations No customer action is required at this time. Current Status The issue is under active investigation in coordination with the cloud provider. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Starting at 06:03 UTC on September 11, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch and termination failures, clusters remaining in a pending state, and job runs that fail to start or terminate unexpectedly. Symptoms • Cluster launch failures and clusters stuck in Pending or Starting • Cluster termination requests failing or delayed • Jobs failing to start on schedule, remaining pending, or failing during cluster startup Recommendations No customer action is required at this time. Current Status The issue has been identified and mitigation efforts are in progress in coordination with the cloud provider. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Starting at 06:03 UTC on September 11, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch and termination failures, clusters remaining in a pending state, and job runs that fail to start or terminate unexpectedly. Symptoms • Cluster launch failures and clusters stuck in Pending or Starting • Cluster termination requests failing or delayed • Jobs failing to start on schedule, remaining pending, or failing during cluster startup Recommendations No customer action is required at this time. Current Status The issue has been identified and mitigation efforts are in progress in coordination with the cloud provider. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Between 06:03 UTC and 09:30 UTC September 11, 2026, customers using Azure Databricks may have experienced degraded availability with Classic Compute and Jobs. Affected customers may have encountered cluster launch and termination failures, delayed or failed job runs, and pipeline runs that did not complete during this window. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Cluster termination failures and notebook attach failures • Jobs and pipeline runs failing, remaining pending, or not progressing Current Status The issue has been mitigated and service is operational. Mitigation was confirmed in coordination with the cloud provider. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Between 06:03 UTC and 09:30 UTC September 11, 2026, customers using Azure Databricks may have experienced degraded availability with Classic Compute and Jobs. Affected customers may have encountered cluster launch and termination failures, delayed or failed job runs, and pipeline runs that did not complete during this window. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Cluster termination failures and notebook attach failures • Jobs and pipeline runs failing, remaining pending, or not progressing Current Status The issue has been mitigated and service is operational. Mitigation was confirmed in coordination with the cloud provider. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Between 06:03 UTC and 09:30 UTC on September 11, 2026, customers using Azure Databricks may have experienced degraded availability with Classic Compute, Declarative Pipelines, and Jobs. Affected customers may have encountered cluster launch and termination failures, along with delayed or failed job and pipeline runs during this window. Symptoms • Cluster launch failures or clusters remaining in Pending or Starting states • Cluster termination failures or delays • Jobs failing to start on schedule, remaining pending, or failing immediately • Pipeline runs failing to complete or not progressing Current Status The issue has been resolved, and all affected services have been restored. Recovery was confirmed in coordination with the cloud provider. Next Update This is the final update for this incident. 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

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.

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.

Impact Summary: Starting at 11:27 UTC September 07, 2026, customers using Azure Databricks may experience failures or degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, clusters remaining in a pending state, or job runs failing or terminating during compute startup. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Notebook attach failures and unexpected cluster terminations • Jobs failing to start, remaining pending, or failing during cluster startup Recommendations: No customer action is required at this time. Current Status: The issue is under active investigation in coordination with the cloud provider. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary: Starting at 11:27 UTC September 07, 2026, customers using Azure Databricks may experience failures or degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, clusters remaining in a pending state, or job runs failing or terminating during compute startup. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Notebook attach failures and unexpected cluster terminations • Jobs failing to start, remaining pending, or failing during cluster startup Recommendations: No customer action is required at this time. Current Status: The issue is under active investigation in coordination with the cloud provider. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary: Starting at 11:27 UTC September 07, 2026, customers using Azure Databricks may be experiencing degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, clusters remaining in a pending state, or job runs failing during cluster startup. Symptoms: • Cluster launch failures or unexpected launch errors • Clusters stuck in Pending or Starting, and notebook attach failures • Jobs failing to start, or failing and terminating during cluster startup Recommendations: No customer action is required at this time. Current Status: The issue has been identified and mitigation efforts are in progress in coordination with the cloud provider. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary: Starting at 11:27 UTC September 07, 2026, customers using Azure Databricks may be experiencing degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, clusters remaining in a pending state, or job runs failing during cluster startup. Symptoms: • Cluster launch failures or unexpected launch errors • Clusters stuck in Pending or Starting, and notebook attach failures • Jobs failing to start, or failing and terminating during cluster startup Recommendations: No customer action is required at this time. Current Status: The issue has been identified and mitigation efforts are in progress in coordination with the cloud provider. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary: Between 11:27 UTC and 14:52 UTC September 07, 2026, customers using Azure Databricks may have experienced intermittent failures and degraded availability with Classic Compute, Serverless Compute, Databricks Apps, Declarative Pipelines, and Jobs. Affected customers may have encountered cluster launch failures, allocation timeouts, and elevated latency or delayed completion of job and pipeline runs during this window. Symptoms: • Cluster launch failures, clusters stuck in Pending or Starting, and terminations during startup • Serverless workloads failing to start, allocation timeouts, or unexpected workload termination • Jobs and pipeline runs remaining pending, failing, or completing with elevated latency; Databricks Apps slow to scale or returning errors Current Status: The issue has been mitigated and service is operational. Monitoring continues in coordination with the cloud provider. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary: Between 11:27 UTC and 14:52 UTC September 07, 2026, customers using Azure Databricks may have experienced intermittent failures and degraded availability with Classic Compute, Serverless Compute, Databricks Apps, Declarative Pipelines, and Jobs. Affected customers may have encountered cluster launch failures, allocation timeouts, and elevated latency or delayed completion of job and pipeline runs during this window. Symptoms: • Cluster launch failures, clusters stuck in Pending or Starting, and terminations during startup • Serverless workloads failing to start, allocation timeouts, or unexpected workload termination • Jobs and pipeline runs remaining pending, failing, or completing with elevated latency; Databricks Apps slow to scale or returning errors Current Status: The issue has been mitigated and service is operational. Monitoring continues in coordination with the cloud provider. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary: Between 11:27 UTC and 14:52 UTC on September 07, 2026, customers using Azure Databricks may have experienced degraded availability across Classic Compute, Serverless Compute, Databricks Apps, Declarative Pipelines, and Jobs. Affected customers may have encountered intermittent cluster launch failures, allocation timeouts, and elevated latency or delayed completion of job and pipeline runs during this window. Symptoms: • Cluster launch failures or clusters remaining stuck in Pending or Starting • Serverless workloads failing to start, allocation timeouts, or unexpected workload termination • Jobs and pipeline runs delayed, remaining pending, or failing to complete • Apps failing to launch or responding slowly due to delayed instance scaling Current Status: The issue has been resolved, and all affected services have been restored. Resolution was confirmed in coordination with the cloud provider. Next Update: This is the final update for this incident. 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

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.

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.

Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks in East US 2 may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job runs that fail or terminate during compute startup. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cloud provider launch failure and launch timeout terminations • Job runs failing to start or terminating during cluster startup Recommendations: No customer action is required at this time. Current Status: The issue is under active investigation, in coordination with the cloud provider. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks in East US 2 may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job runs that fail or terminate during compute startup. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cloud provider launch failure and launch timeout terminations • Job runs failing to start or terminating during cluster startup Recommendations: No customer action is required at this time. Current Status: The issue is under active investigation, in coordination with the cloud provider. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may be experiencing failures or degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, cluster allocation timeouts, or unexpected termination of workloads requiring new compute. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster allocation timeouts and unexpected cluster terminations during startup • Job runs failing to start, remaining pending, or terminating during cluster startup Recommendations: No customer action is required at this time. Current Status: The issue has been identified and mitigation efforts are in progress in coordination with the cloud provider. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may be experiencing failures or degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, cluster allocation timeouts, or unexpected termination of workloads requiring new compute. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster allocation timeouts and unexpected cluster terminations during startup • Job runs failing to start, remaining pending, or terminating during cluster startup Recommendations: No customer action is required at this time. Current Status: The issue has been identified and mitigation efforts are in progress in coordination with the cloud provider. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may be experiencing failures or degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, cluster allocation timeouts, or unexpected termination of workloads requiring new compute. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster allocation timeouts and unexpected cluster terminations during startup • Job runs failing to start, remaining pending, or terminating during cluster startup Recommendations: No customer action is required at this time. Current Status: The issue has been identified and mitigation efforts are in progress in coordination with the cloud provider. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may be experiencing failures or degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, cluster allocation timeouts, or unexpected termination of workloads requiring new compute. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster allocation timeouts and unexpected cluster terminations during startup • Job runs failing to start, remaining pending, or terminating during cluster startup Recommendations: No customer action is required at this time. Current Status: The issue has been identified and mitigation efforts are in progress in coordination with the cloud provider. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may be experiencing failures or degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, cluster allocation timeouts, or unexpected termination of workloads requiring new compute. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster allocation timeouts and unexpected cluster terminations during startup • Job runs failing to start, remaining pending, or terminating during cluster startup Recommendations: No customer action is required at this time. Current Status: The issue has been identified and mitigation efforts are in progress in coordination with the cloud provider. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may be experiencing failures or degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, cluster allocation timeouts, or unexpected termination of workloads requiring new compute. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster allocation timeouts and unexpected cluster terminations during startup • Job runs failing to start, remaining pending, or terminating during cluster startup Recommendations: No customer action is required at this time. Current Status: The issue has been identified and mitigation efforts are in progress in coordination with the cloud provider. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may be experiencing failures or degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, cluster allocation timeouts, or unexpected termination of workloads requiring new compute. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster allocation timeouts and unexpected cluster terminations during startup • Job runs failing to start, remaining pending, or terminating during cluster startup Recommendations: No customer action is required at this time. Current Status: The issue has been identified and mitigation efforts are in progress in coordination with the cloud provider. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may be experiencing failures or degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, cluster allocation timeouts, or unexpected termination of workloads requiring new compute. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster allocation timeouts and unexpected cluster terminations during startup • Job runs failing to start, remaining pending, or terminating during cluster startup Recommendations: No customer action is required at this time. Current Status: The issue has been identified and mitigation efforts are in progress in coordination with the cloud provider. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may be experiencing failures or degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, cluster allocation timeouts, or unexpected termination of workloads requiring new compute. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster allocation timeouts and unexpected cluster terminations during startup • Job runs failing to start, remaining pending, or terminating during cluster startup Recommendations: No customer action is required at this time. Current Status: The issue has been identified and mitigation efforts are in progress in coordination with the cloud provider. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may be experiencing failures or degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, cluster allocation timeouts, or unexpected termination of workloads requiring new compute. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster allocation timeouts and unexpected cluster terminations during startup • Job runs failing to start, remaining pending, or terminating during cluster startup Recommendations: No customer action is required at this time. Current Status: The issue has been identified and mitigation efforts are in progress in coordination with the cloud provider. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, or unexpected termination of workloads during cluster startup. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cloud provider launch failure and launch timeout terminations • Job runs failing, remaining pending, or terminating during cluster startup Recommendations: No customer action is required at this time. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, or unexpected termination of workloads during cluster startup. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cloud provider launch failure and launch timeout terminations • Job runs failing, remaining pending, or terminating during cluster startup Recommendations: No customer action is required at this time. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to Serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to Serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Starting around 14:28 UTC, the Cloud Provider has applied a mitigation, and we noticed improvements in East US 2, UAE North, Sweden Central, and West Europe regions, while North Central US continues to be unstable. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Starting around 14:28 UTC, the Cloud Provider has applied a mitigation, and we noticed improvements in East US 2, UAE North, Sweden Central, and West Europe regions, while North Central US continues to be unstable. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Starting around 14:28 UTC, the Cloud Provider has applied a mitigation, and we noticed improvements in East US 2, UAE North, Sweden Central, and West Europe regions, while North Central US continues to be unstable. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Starting around 14:28 UTC, the Cloud Provider has applied a mitigation, and we noticed improvements in East US 2, UAE North, Sweden Central, and West Europe regions, while North Central US continues to be unstable. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Starting around 14:28 UTC, the Cloud Provider has applied a mitigation, and we noticed improvements in East US 2, UAE North, Sweden Central, and West Europe regions, while North Central US continues to be unstable. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Starting around 14:28 UTC, the Cloud Provider has applied a mitigation, and we noticed improvements in East US 2, UAE North, Sweden Central, and West Europe regions, while North Central US continues to be unstable. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Starting around 14:28 UTC, the Cloud Provider has applied a mitigation, and we noticed improvements in East US 2, UAE North, Sweden Central, and West Europe regions, while North Central US continues to be unstable. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Starting around 14:28 UTC, the Cloud Provider has applied a mitigation, and we noticed improvements in East US 2, UAE North, Sweden Central, and West Europe regions, while North Central US continues to be unstable. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Starting around 14:28 UTC, the Cloud Provider has applied a mitigation, and we noticed improvements in East US 2, UAE North, Sweden Central, and West Europe regions, while North Central US continues to be unstable. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC on September 07, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute and Jobs. Affected customers may encounter cluster launch failures, launch timeouts, and job or pipeline runs that fail or do not complete. Starting around 14:28 UTC, the Cloud Provider has applied a mitigation, and we noticed improvements in East US 2, UAE North, Sweden Central, and West Europe regions, while North Central US continues to be unstable. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Impact remains ongoing, and the incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC on September 07, 2026, some Azure Databricks customers experienced degraded availability with Classic Compute and Jobs. Impact included cluster launch failures and timeouts, as well as job or pipeline runs that failed or did not complete. At approximately 14:28 UTC, the cloud provider applied a mitigation. Service availability has improved in East US 2, UAE North, Sweden Central, and West Europe, and recovery has also begun in North Central US. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. We are continuing to monitor the recovery closely, and service availability is now significantly improved compared with earlier in the incident. The incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.

Impact Summary: Starting at 06:03 UTC on September 07, 2026, some Azure Databricks customers experienced degraded availability with Classic Compute and Jobs. Impact included cluster launch failures and timeouts, as well as job or pipeline runs that failed or did not complete. At approximately 14:28 UTC, the cloud provider applied a mitigation. Service availability has improved in East US 2, UAE North, Sweden Central, and West Europe, and recovery has also begun in North Central US. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Cluster terminations with cloud provider launch failure or launch timeout errors • Job and pipeline runs failing, remaining pending, or terminating during cluster startup Recommendations: Customers experiencing classic compute launch failures in the affected Azure regions should, if possible, switch to AMD SKUs or switch impacted workloads to serverless compute where available. Current Status: The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. We are continuing to monitor the recovery closely, and service availability is now significantly improved compared with earlier in the incident. The incident continues to be actively monitored. Next Update: We will provide another update within 2 hours, or sooner if there is a material change in service status.

Impact Summary: Between 06:03 UTC September 07, 2026 and 03:33 UTC September 08, 2026, customers using Azure Databricks may have experienced degraded availability with Classic Compute and Jobs. Affected customers may have encountered cluster launch failures, cluster startup timeouts, and failed or delayed job and pipeline runs during this window. Symptoms: • Cluster launch failures or clusters remaining in Pending or Starting states • Notebook attach failures and workload terminations during cluster startup • Jobs and pipeline runs failing to start, remaining pending, or failing to progress Current Status: The issue has been mitigated and service is operational. Mitigation was completed in coordination with the cloud provider, and recovery continues to be monitored. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary: Between 06:03 UTC September 07, 2026 and 03:33 UTC September 08, 2026, customers using Azure Databricks may have experienced degraded availability with Classic Compute and Jobs. Affected customers may have encountered cluster launch failures, cluster startup timeouts, and failed or delayed job and pipeline runs during this window. Symptoms: • Cluster launch failures or clusters remaining in Pending or Starting states • Notebook attach failures and workload terminations during cluster startup • Jobs and pipeline runs failing to start, remaining pending, or failing to progress Current Status: The issue has been mitigated and service is operational. Mitigation was completed in coordination with the cloud provider, and recovery continues to be monitored. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary: Between 06:03 UTC September 07, 2026 and 03:33 UTC September 08, 2026, customers using Azure Databricks may have experienced degraded availability with Classic Compute and Jobs. Affected customers may have encountered cluster launch failures, cluster startup timeouts, and failed or delayed job and pipeline runs during this window. Symptoms: • Cluster launch failures or clusters remaining in Pending or Starting states • Notebook attach failures and workload terminations during cluster startup • Jobs and pipeline runs failing to start, remaining pending, or failing to progress Current Status: The issue has been resolved, and all affected services have been restored. Resolution was confirmed in coordination with the cloud provider. Next Update: This is the final update for this incident. We apologise 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