Databricks Azure Outage History

Started Nov 05, 2026, 07:30 PM UTC· resolved Nov 05, 2026, 08:46 PM UTC

1. investigating Nov 05, 2026, 07:30 PM UTC

   Impact Summary Starting at 18:35 UTC on November 05, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute, Serverless Compute, Databricks SQL, Declarative Pipelines, and Jobs. Affected customers may encounter cluster launch failures, cluster allocation timeouts, or unexpected termination of workloads. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Serverless workloads and SQL warehouses failing to start or terminating unexpectedly • Job and pipeline run failures or allocation timeouts 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.

2. identified Nov 05, 2026, 07:55 PM UTC

   Impact Summary Starting at 18:35 UTC November 05, 2026, customers using Azure Databricks may experience degraded availability with Classic Compute, Serverless Compute, Databricks SQL, Declarative Pipelines, and Jobs. Affected customers may encounter cluster launch failures, serverless allocation timeouts, query failures, or failed job and pipeline runs. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Serverless workloads failing to start or cluster allocation timeouts • Job and pipeline run failures and SQL query or connection errors 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.

3. monitoring Nov 05, 2026, 08:10 PM UTC

   Impact Summary Between 18:35 UTC and 19:55 UTC on November 05, 2026, customers using Azure Databricks may have experienced degraded availability with Classic Compute, Serverless Compute, Databricks SQL, Declarative Pipelines, and Jobs. Affected customers may have encountered cluster launch failures, serverless workload start failures, and failed or delayed job, pipeline, and SQL query runs during this window. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Serverless workloads failing to start or terminating unexpectedly • Job, pipeline, and SQL query failures or delays Current Status The issue has been mitigated and service is operational. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. resolved Nov 05, 2026, 08:46 PM UTC

   IImpact Summary Between 18:35 UTC and 19:55 UTC on November 05, 2026, customers using Azure Databricks may have experienced degraded availability with Classic Compute, Serverless Compute, Databricks SQL, Declarative Pipelines, and Jobs. Affected customers may have encountered cluster launch failures, serverless workload start errors, or failed job, pipeline, and SQL query runs during this window. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Serverless workloads failing to start or cluster allocation timeouts • Job, pipeline, and SQL query failures or BI tool connection timeouts Current Status The issue has been resolved, and all affected services have been restored. 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.

Read the full incident report →

Started Nov 05, 2026, 05:46 PM UTC· resolved Nov 05, 2026, 07:32 PM UTC

1. investigating Nov 05, 2026, 05:46 PM UTC

   Impact Summary Starting at 17:08 UTC November 05, 2026, customers using Azure Databricks in North Europe may experience degraded availability with AI/BI, Databricks SQL, and Notebooks. Affected customers may encounter query failures, slow query execution, or errors when loading dashboards and running notebook commands. Symptoms • SQL queries failing, timing out, or running significantly slower than expected • AI/BI dashboards failing to load or refresh, or showing empty or partial results • Notebook commands failing with errors, and BI tool connections timing out Recommendations No customer action is required at this time. Current Status The issue is under active investigation. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

2. identified Nov 05, 2026, 06:10 PM UTC

   Impact Summary Starting at 17:08 UTC November 05, 2026, customers using Azure Databricks in North Europe may experience degraded availability with AI/BI, Databricks SQL, and Notebooks. Affected customers may encounter failed or slow SQL queries, SQL warehouse start or creation failures, dashboards that fail to load or refresh, and BI tool connection errors. Symptoms • SQL warehouse requests, creation, or startup failing with temporarily unavailable errors • SQL queries, dashboard refreshes, and JDBC/ODBC connections failing or timing out • Intermittent notebook command failures Recommendations No customer action is required at this time. Current Status The issue has been identified and mitigation efforts are in progress. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

3. monitoring Nov 05, 2026, 06:15 PM UTC

   Impact Summary Between 17:08 UTC and 18:07 UTC November 05, 2026, customers using Azure Databricks in North Europe may have experienced degraded availability with AI/BI, Databricks SQL, and Notebooks. Affected customers may have encountered errors when running SQL queries, starting or creating SQL warehouses, loading dashboards, or connecting BI tools during this window. Symptoms • SQL warehouse creation or start requests failing with temporarily unavailable errors • SQL queries and JDBC/ODBC BI tool connections failing or timing out • AI/BI dashboards failing to load or refresh, and intermittent notebook command failures Current Status The issue has been mitigated and service is operational. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. resolved Nov 05, 2026, 07:32 PM UTC

   Impact Summary Between 17:08 UTC and 18:07 UTC on November 05, 2026, customers using Azure Databricks in North Europe may have experienced degraded availability with AI/BI, Databricks SQL, and Notebooks. Affected customers may have encountered errors when running SQL queries, creating or managing SQL warehouses, connecting BI tools, loading dashboards, or executing notebook commands during this window. Symptoms • SQL warehouse creation and management requests failing with temporarily unavailable errors • SQL queries and JDBC/ODBC connections failing or timing out • Dashboards and notebook commands failing to return results Current Status The issue has been resolved, and all affected services have been restored. 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.

Read the full incident report →

Started Nov 05, 2026, 12:29 PM UTC· resolved Nov 05, 2026, 02:23 PM UTC

1. investigating Nov 05, 2026, 12:29 PM UTC

   We are actively investigating an issue with the Databricks service. We will provide another update within 1 hour, or sooner if there is a material change in service status.

2. identified Nov 05, 2026, 12:38 PM UTC

   Impact Summary Starting at 11:18 UTC November 05, 2026, customers using Azure Databricks in Brazil South may experience degraded availability with Classic Compute, Serverless Compute, Databricks SQL, Jobs, and Notebooks. Affected customers may encounter cluster launch failures, job run failures, or SQL queries that fail or return incomplete results. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Job run failures, unexpected terminations, or errors retrieving run output • SQL warehouses failing to start and queries returning empty or partial results 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.

3. monitoring Nov 05, 2026, 01:24 PM UTC

   Impact Summary Between 11:18 UTC and 13:20 UTC November 05, 2026, customers using Azure Databricks in Brazil South may have experienced degraded availability with Classic Compute, Serverless Compute, Databricks SQL, Jobs, and Notebooks. Affected customers may have encountered cluster launch failures, job run failures, query errors, or notebook execution issues during this window. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Job runs failing during startup or terminating unexpectedly • SQL warehouses failing to start and queries failing or returning no results Current Status The issue has been mitigated in coordination with the cloud provider, and service is operational. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. resolved Nov 05, 2026, 02:23 PM UTC

   Impact Summary Between 11:18 UTC and 13:20 UTC on November 05, 2026, customers using Azure Databricks in Brazil South may have experienced degraded availability with Classic Compute, Serverless Compute, Databricks SQL, Jobs, and Notebooks. Affected customers may have encountered cluster launch failures, failed or incomplete SQL queries, and job or notebook execution errors during this window. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • SQL warehouses failing to start and queries failing or returning no results • Job runs failing to start or terminating unexpectedly, and notebook commands failing Current Status The issue has been resolved, and all affected services have been restored. 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.

Read the full incident report →

Started Nov 04, 2026, 08:48 PM UTC· resolved Nov 04, 2026, 10:53 PM UTC

1. investigating Nov 04, 2026, 08:48 PM UTC

   Impact Summary Starting at 20:16 UTC November 04, 2026, customers using Azure Databricks in Brazil South may be experiencing degraded availability with Classic Compute, Serverless Compute, Declarative Pipelines, Jobs, and Notebooks. Affected customers may encounter cluster launch failures, job run failures, or errors when starting workloads. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Job and pipeline runs failing or not progressing • Notebook attach failures and serverless workloads failing to start Recommendations No customer action is required at this time. Current Status The issue is under active investigation. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

2. identified Nov 04, 2026, 09:19 PM UTC

   Impact Summary Starting at 20:16 UTC on November 04, 2026, customers using Azure Databricks in Brazil South may experience degraded availability with Classic Compute, Serverless Compute, Databricks SQL, Declarative Pipelines, Jobs, Notebooks, and Unity Catalog. Affected customers may encounter cluster launch failures, job and pipeline run failures, or errors when running SQL queries and notebook commands. Symptoms • Cluster and SQL warehouse launch failures or clusters stuck in Pending or Starting • Jobs and pipeline runs failing, remaining pending, or not triggering on file arrival • SQL queries and notebook commands failing, timing out, or running slowly 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.

3. monitoring Nov 04, 2026, 10:19 PM UTC

   Impact Summary Between 20:16 UTC and 22:09 UTC November 04, 2026, customers using Azure Databricks in Brazil South may have experienced degraded availability with Classic Compute, Serverless Compute, Databricks Apps, Databricks SQL, Declarative Pipelines, Jobs, Notebooks, and Unity Catalog. Affected customers may have encountered cluster and SQL warehouse launch failures, job and pipeline run failures, or errors accessing governed data during this window. Symptoms • Cluster, SQL warehouse, and serverless workload launch failures or delays • Job and pipeline runs failing, remaining pending, or not progressing • Query, notebook command, and Unity Catalog request 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.

4. resolved Nov 04, 2026, 10:53 PM UTC

   Impact Summary Between 20:16 UTC and 22:09 UTC November 04, 2026, customers using Azure Databricks in Brazil South may have experienced degraded availability with Classic Compute, Serverless Compute, Databricks Apps, Databricks SQL, Declarative Pipelines, Jobs, Notebooks, and Unity Catalog. Affected customers may have encountered cluster and SQL warehouse launch failures, job and pipeline run failures, or errors accessing catalog data during this window. Symptoms • Clusters, SQL warehouses, and serverless workloads failing to start or stuck in Pending • Job and pipeline runs failing, not triggering, or not progressing • Errors or delays with SQL queries, notebook commands, and Unity Catalog requests Current Status The issue has been resolved, and all affected services have been restored. 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.

Read the full incident report →

Started Oct 26, 2026, 08:33 AM UTC· resolved Oct 26, 2026, 10:02 AM UTC

1. investigating Oct 26, 2026, 08:33 AM UTC

   We are actively investigating an issue with the Databricks service. We will provide another update within 1 hour, or sooner if there is a material change in service status.

2. identified Oct 26, 2026, 08:57 AM UTC

   Impact Summary Starting at 07:40 UTC on October 26, 2026, customers using Azure Databricks in East US 2 may experience degraded availability with Databricks SQL and Jobs. Affected customers may encounter query failures, delays starting SQL warehouses, unreliable BI tool connections, or job runs that fail or do not start as expected. Symptoms • SQL warehouses stuck in Starting or Resuming state • SQL queries failing or running significantly slower, and BI tool connections timing out • Jobs remaining pending, failing to start on schedule, or terminating unexpectedly 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.

3. monitoring Oct 26, 2026, 09:20 AM UTC

   Impact Summary Between 07:40 UTC and 08:58 UTC on October 26, 2026, customers using Azure Databricks in East US 2 may have experienced degraded availability with Databricks SQL and Jobs. Affected customers may have encountered failed or slow queries, unreliable BI tool connections, or job runs that failed or did not start as expected during this window. Symptoms • SQL warehouses stuck in Starting or Resuming, with failed or slow queries • Dashboards showing empty or partial results and BI tool connection timeouts • Job runs failing, remaining pending, or terminating unexpectedly Current Status The issue has been mitigated in coordination with the cloud provider, and service is operational. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. resolved Oct 26, 2026, 10:02 AM UTC

   Impact Summary Between 07:40 UTC and 08:58 UTC on October 26, 2026, customers using Azure Databricks in East US 2 may have experienced degraded availability with Databricks SQL and Jobs. Affected customers may have encountered failed or slow SQL queries, unreliable BI tool connections, or unexpected job run failures during this window. Symptoms • SQL queries failing with internal errors or running significantly slower than expected • SQL warehouse and BI tool connections timing out or failing intermittently • Job runs failing or terminating unexpectedly with an unknown termination reason Current Status The issue has been resolved, and all affected services have been restored. 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.

Read the full incident report →

Started Oct 16, 2026, 07:41 PM UTC· resolved Oct 16, 2026, 08:55 PM UTC

1. investigating Oct 16, 2026, 07:41 PM UTC

   Impact Summary Starting at 18:24 UTC on October 16, 2026, customers using Azure Databricks in China East 2 may experience unavailability . Affected customers may encounter cluster launch failures, delayed or failed job runs, or intermittent errors when accessing workloads. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Jobs not starting on schedule, remaining pending, or failing during cluster startup • Intermittent request or authentication errors Recommendations No customer action is required at this time. Current Status The issue is under active investigation. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

2. investigating Oct 16, 2026, 07:44 PM UTC

   Impact Summary Starting at 18:24 UTC on October 16, 2026, customers using Azure Databricks in China East 2 may experience degraded availability across services. Affected customers may encounter authentication failures, errors accessing workspaces and APIs, and failures launching clusters. Symptoms • Intermittent failures accessing workspaces, APIs, and the UI • Authentication failures when using Azure Active Directory or personal access tokens • Classic compute cluster launch failures with control plane connectivity errors Recommendations No customer action is required at this time. Current Status The issue is under active investigation. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

3. identified Oct 16, 2026, 08:07 PM UTC

   Impact Summary Starting at 18:24 UTC October 16, 2026, customers using Azure Databricks in China East 2 may experience degraded availability across all services. Affected customers may encounter request failures, authentication errors, or failures launching compute clusters. Symptoms • Failed or timed-out API and workspace requests • Authentication errors when accessing workspaces • Job and cluster launch failures, including NETWORK_CHECK_CONTROL_PLANE_FAILURE errors Recommendations No customer action is required at this time. Current Status The issue has been identified and mitigation efforts are in progress. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. monitoring Oct 16, 2026, 08:25 PM UTC

   Impact Summary Between 18:24 UTC and 20:04 UTC on October 16, 2026, customers using Azure Databricks in China East 2 may have experienced degraded availability across Azure Databricks services. Affected customers may have encountered request failures, authentication errors, Jobs and Notebook disruptions, or cluster launch failures during this window. Symptoms • Failed or timed-out API, UI, and authentication requests • Jobs and Notebook operations failing or not progressing • Classic compute cluster launches failing with NETWORK_CHECK_CONTROL_PLANE_FAILURE errors Current Status The issue has been mitigated and service is operational. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

5. resolved Oct 16, 2026, 08:55 PM UTC

   Impact Summary Between 18:24 UTC and 20:04 UTC on October 16, 2026, customers using Azure Databricks in China East 2 may have experienced degraded availability across all services. Affected customers may have encountered request failures, authentication errors, or cluster launch failures during this window. Symptoms • Failed or timed-out requests to the workspace UI and APIs • Authentication and authorization errors • Job and notebook execution failures and classic compute cluster launch failures with NETWORK_CHECK_CONTROL_PLANE_FAILURE errors Current Status The issue has been resolved, and all affected services have been restored. 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.

Read the full incident report →

Started Oct 16, 2026, 03:29 PM UTC· resolved Oct 16, 2026, 04:36 PM UTC

1. investigating Oct 16, 2026, 03:29 PM UTC

   We are actively investigating an issue with the Databricks service. We will provide another update within 1 hour, or sooner if there is a material change in service status.

2. monitoring Oct 16, 2026, 04:03 PM UTC

   Impact Summary Between 15:07 UTC and 15:49 UTC on October 16, 2026, customers using Databricks may have experienced degraded availability with Serverless Compute, Databricks Apps, Databricks SQL, Jobs, Notebooks, and Genie One. Affected customers may have encountered errors, unavailable workspace UI features, or failures when starting or running workloads during this window. Symptoms • Genie One, the workspace app switcher, and other workspace UI features unavailable or returning errors • Serverless workloads, jobs, and SQL queries failing to start or returning errors • Notebooks and Databricks Apps failing to load or execute Current Status The issue has been mitigated and service is operational. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

3. resolved Oct 16, 2026, 04:36 PM UTC

   Impact Summary Between 15:07 UTC and 15:49 UTC on October 16, 2026, customers using Databricks may have experienced degraded availability with Serverless Compute, Databricks Apps, Databricks SQL, Jobs, Notebooks, and Genie One. Affected customers may have encountered errors, unavailable workspace UI features, or failures when starting or running workloads during this window. Symptoms • Genie One, the workspace app switcher, and other workspace UI features are unavailable or returning errors • Serverless workloads, jobs, and SQL queries failing to start or returning errors • Notebooks and Databricks Apps failing to load or execute Current Status The issue has been mitigated, and service is operational. 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 a support ticket or contact [email protected].

Read the full incident report →

Started Oct 01, 2026, 10:15 AM UTC· resolved Oct 01, 2026, 03:46 PM UTC

1. investigating Oct 01, 2026, 10:15 AM UTC

   We are actively investigating an issue affecting Databricks compute. We will provide another update within 1 hour, or sooner if there is a material change in service status.

2. identified Oct 01, 2026, 10:38 AM UTC

   Impact Summary Starting at 09:49 UTC on October 1, 2026, customers using Azure Databricks in West Europe may experience degraded availability with Serverless Compute. Affected customers may be unable to start or run serverless workloads for notebooks, workflows, and Lakeflow pipelines, and may encounter cluster allocation timeouts or errors. Symptoms • Serverless workloads failing to start • Cluster allocation timeouts when launching serverless workloads • Unexpected termination of serverless workloads Recommendations No customer action is required at this time. Current Status The issue is under active investigation. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

3. identified Oct 01, 2026, 11:26 AM UTC

   Impact Summary Starting at 09:49 UTC on October 01, 2026, customers using Azure Databricks in West Europe may experience degraded availability with Serverless Compute, AI/BI, Databricks SQL, Declarative Pipelines, Jobs, and Notebooks. Affected customers may encounter workload start failures, cluster allocation timeouts, or errors when running queries, notebooks, jobs, and pipelines. Symptoms • Serverless workloads failing to start or encountering cluster allocation timeouts • Jobs and pipeline runs failing, remaining pending, or not progressing • SQL queries, dashboards, and notebook commands failing or timing out 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.

4. identified Oct 01, 2026, 12:25 PM UTC

   Impact Summary Starting at 09:49 UTC October 01, 2026, customers using Azure Databricks in West Europe may experience degraded availability or failures with Serverless Compute, AI/BI, Databricks Apps, Databricks SQL, Declarative Pipelines, Jobs, and Notebooks. Affected customers may encounter errors when starting workloads, cluster allocation timeouts, or failures when running queries, dashboards, and pipelines. Symptoms • Serverless workloads failing to start or encountering cluster allocation timeouts • Jobs and pipeline runs remaining pending, failing, or not progressing • SQL warehouses, AI/BI dashboards, and notebooks failing to start, load, or execute 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.

5. identified Oct 01, 2026, 01:25 PM UTC

   Impact Summary Starting at 09:49 UTC on October 01, 2026, customers using Azure Databricks in West Europe may experience failures or degraded availability with Serverless Compute, Databricks SQL (including Serverless SQL warehouses), AI/BI, Databricks Apps, Lakeflow Declarative Pipelines, Jobs, and Notebooks. Affected customers may see errors when starting workloads, cluster allocation timeouts, or unexpected workload terminations. Symptoms • Serverless workloads fail to start or hit cluster allocation timeouts. • Jobs and pipeline runs stay pending, fail, or end unexpectedly. • SQL warehouses, dashboards, notebooks, and apps fail to start, load, or run. Recommendations No customer action is required at this time. Current Status We have identified the cause. An issue with our cloud provider's infrastructure is affecting how virtual machines are provisioned for Azure Databricks in West Europe. Our engineering teams are working with the cloud provider to bring back provisioning capacity. We are also taking steps on our side to reduce load on the affected systems and help workloads recover. We are closely watching compute provisioning and service health while this work continues. Next Update We will provide another update within 1 hour, or sooner if service status changes significantly.

6. monitoring Oct 01, 2026, 02:18 PM UTC

   Impact Summary Between 09:49 UTC and 13:55 UTC on October 01, 2026, customers using Azure Databricks in West Europe may have experienced degraded availability with Serverless Compute, AI/BI, Databricks Apps, Databricks SQL, Declarative Pipelines, Jobs, and Notebooks. Affected customers may have encountered workload start failures, cluster allocation timeouts, or errors when running queries, jobs, pipelines, notebooks, dashboards, and apps during this window. Symptoms • Serverless workloads failing to start or encountering cluster allocation timeouts • Jobs and pipeline runs failing, remaining pending, or not starting on schedule • SQL queries, notebook commands, AI/BI dashboards, and Databricks Apps failing 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.

7. resolved Oct 01, 2026, 03:46 PM UTC

   Impact Summary Between 09:49 UTC and 13:55 UTC on October 01, 2026, customers using Azure Databricks in West Europe may have experienced degraded availability with Serverless Compute, AI/BI, Databricks Apps, Databricks SQL, Declarative Pipelines, Jobs, and Notebooks. Affected customers may have encountered workload start failures, cluster allocation timeouts, or errors when running queries, jobs, pipelines, notebooks, dashboards, and apps during this window. Symptoms • Serverless workloads failing to start or encountering cluster allocation timeouts • Jobs and pipeline runs failing, remaining pending, or not starting on schedule • SQL queries, notebook commands, AI/BI dashboards, and Databricks Apps failing or returning errors Current Status The issue has been resolved, and all affected services have been restored. 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

Read the full incident report →

Started Oct 01, 2026, 08:19 AM UTC· resolved Oct 01, 2026, 10:31 AM UTC

1. investigating Oct 01, 2026, 08:19 AM UTC

   We are actively investigating an issue affecting Databricks compute. We will provide another update within 1 hour, or sooner if there is a material change in service status.

2. monitoring Oct 01, 2026, 09:56 AM UTC

   Impact Summary Between 06:13 UTC and 08:37 UTC October 01, 2026, customers using Azure Databricks may have experienced degraded performance with Classic Compute. Affected customers may have been unable to provision, attach to, or run customer-managed compute-backed workloads during this window. Symptoms • Cluster launch failures due to library installation errors • Library installation failures or timeouts on clusters • Job and notebook run failures for workloads dependent on cluster libraries Current Status The issue has been mitigated and service is operational. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

3. resolved Oct 01, 2026, 10:31 AM UTC

   Impact Summary Between 06:13 UTC and 08:37 UTC on October 01, 2026, customers using Azure Databricks may have experienced degraded availability with Classic Compute. Affected customers may have encountered cluster launch failures, library installation failures, or failures of dependent jobs and notebooks during this window. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Cluster library installation failures • Job and notebook run failures during cluster startup Current Status The issue has been resolved, and all affected services have been restored. 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

Read the full incident report →

Started Sep 29, 2026, 04:46 PM UTC· resolved Sep 29, 2026, 06:54 PM UTC

1. investigating Sep 29, 2026, 04:46 PM UTC

   Impact Summary Starting at 15:15 UTC September 29, 2026, customers using Azure Databricks in West US 3 may experience failures or degraded availability with Declarative Pipelines. Affected customers may encounter pipeline runs that fail, do not start, or do not progress. Symptoms • Pipeline runs failing with control plane errors • Pipeline runs not starting or not progressing • Missing or delayed pipeline status information Recommendations No customer action is required at this time. Current Status The issue is under active investigation. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

2. investigating Sep 29, 2026, 04:50 PM UTC

   Impact Summary Starting at 15:15 UTC September 29, 2026, customers using Azure Databricks in West US 3 may experience failures or degraded availability with Declarative Pipelines. Affected customers may encounter pipeline runs that fail, do not start, or do not progress. Symptoms • Pipeline runs failing with control plane errors • Pipeline runs not starting or not progressing • Missing or delayed pipeline status information Recommendations No customer action is required at this time. Current Status The issue is under active investigation. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

3. identified Sep 29, 2026, 05:43 PM UTC

   Impact Summary Starting at 15:15 UTC September 29, 2026, customers using Databricks may experience failures or degraded performance with Declarative Pipelines. Affected customers may find that pipeline runs fail intermittently or do not complete as expected. Symptoms • Pipeline runs failing with CONTROL_PLANE_FAILURE errors • Pipeline runs not progressing or terminating unexpectedly • Missing or delayed pipeline status information Recommendations No customer action is required at this time. Current Status The issue has been identified and mitigation efforts are in progress. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. monitoring Sep 29, 2026, 05:54 PM UTC

   Impact Summary Between 15:15 UTC and 17:40 UTC on September 29, 2026, a subset of customers using Databricks may have experienced degraded availability with Declarative Pipelines. Affected customers may have encountered pipeline run failures or pipelines that did not progress as expected during this window. Symptoms • Pipeline runs failing with control plane errors • Pipeline runs not starting or not progressing • Delayed or missing pipeline status information Current Status The issue has been mitigated and service is operational. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

5. resolved Sep 29, 2026, 06:54 PM UTC

   Impact Summary Between 15:15 UTC and 17:40 UTC on September 29, 2026, a subset of customers using Databricks may have experienced degraded performance with Declarative Pipelines. Affected customers may have encountered pipeline run failures or pipeline runs that did not progress during this window. Symptoms • Pipeline runs failing with control plane failure errors • Pipeline runs not progressing or not terminating as expected • Delayed or missing pipeline status information Current Status The issue has been resolved, and all affected services have been restored. 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

Read the full incident report →

Started Sep 26, 2026, 07:12 AM UTC· resolved Sep 26, 2026, 09:23 AM UTC

1. investigating Sep 26, 2026, 07:12 AM UTC

   We are actively investigating an issue affecting Databricks compute. We will provide another update within 1 hour, or sooner if there is a material change in service status.

2. monitoring Sep 26, 2026, 08:10 AM UTC

   Impact Summary Between 06:00 UTC and 06:30 UTC on September 26, 2026, customers using Azure Databricks in East US may have experienced degraded availability with Serverless Compute and Databricks SQL. Affected customers may have encountered failed or unexpectedly terminated serverless workloads and errors when running SQL queries during this window. Symptoms • Serverless workloads failing to start or terminating unexpectedly • SQL queries failing or returning internal errors; warehouses stuck in Starting or Resuming • Dashboard refreshes and BI tool connections failing or timing out 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.

3. resolved Sep 26, 2026, 09:23 AM UTC

   Impact Summary Between 06:00 UTC and 06:30 UTC on September 26, 2026, customers using Azure Databricks in East US may have experienced degraded availability and failures with Serverless Compute and Databricks SQL. Affected customers may have encountered workload errors, unexpected terminations, and failed or unreliable SQL query execution during this window. Symptoms • Serverless workloads failing to start or terminating unexpectedly • SQL queries and warehouse operations failing or returning internal errors • Job and pipeline runs failing during execution Current Status The issue has been resolved, and all affected services have been restored. 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

Read the full incident report →

Started Sep 22, 2026, 04:44 AM UTC· resolved Sep 22, 2026, 03:22 PM UTC

1. investigating Sep 22, 2026, 04:44 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 Sep 22, 2026, 04:45 AM UTC

   Impact Summary Starting at 02:54 UTC September 22, 2026, customers using Azure Databricks in East US 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 Declarative Pipelines. Symptoms • Serverless workloads failing to start or remaining in a pending state while waiting for resources • Cluster allocation and launch timeouts • Unexpected termination of serverless workloads, or errors returned when attempting to execute them Recommendations No customer action is required at this time. Current Status The issue is under active investigation, including 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.

3. identified Sep 22, 2026, 05:25 AM UTC

   Impact Summary Starting at 02:17 UTC on September 22, 2026, customers using Azure Databricks in East US may experience intermittent failures or 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 or timing out during cluster allocation • Unexpected termination of running serverless workloads • Errors returned when attempting to execute serverless notebooks, jobs, or pipelines • Pipelines remaining in a waiting-for-resources state Recommendations No customer action is required at this time. Current Status The issue has been identified and mitigation efforts are in progress. Impact is not yet confirmed to have stopped, and the incident remains under active monitoring. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. identified Sep 22, 2026, 06:24 AM UTC

   Impact Summary Starting at 02:17 UTC on September 22, 2026, customers using Azure Databricks in East US may experience intermittent failures or 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 or timing out during cluster allocation • Unexpected termination of running serverless workloads • Errors returned when attempting to execute serverless notebooks, jobs, or pipelines • Pipelines remaining in a waiting-for-resources state Recommendations No customer action is required at this time. Current Status The issue has been identified and mitigation efforts are in progress. Impact is not yet confirmed to have stopped, and the incident remains under active monitoring. Next Update We will provide another update within 2 hour, or sooner if there is a material change in service status.

5. identified Sep 22, 2026, 08:20 AM UTC

   Impact Summary Starting at 02:17 UTC on September 22, 2026, customers using Azure Databricks in East US may experience intermittent failures or 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 or timing out during cluster allocation • Unexpected termination of running serverless workloads • Errors returned when attempting to execute serverless notebooks, jobs, or pipelines • Pipelines remaining in a waiting-for-resources state Recommendations No customer action is required at this time. Current Status The issue has been identified and mitigation efforts are in progress. Impact is not yet confirmed to have stopped, and the incident remains under active monitoring. Next Update We will provide another update within 2 hour, or sooner if there is a material change in service status.

6. identified Sep 22, 2026, 10:31 AM UTC

   Impact Summary Starting at 02:17 UTC on September 22, 2026, customers using Azure Databricks in East US may experience intermittent failures or 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 or timing out during cluster allocation • Unexpected termination of running serverless workloads • Errors returned when attempting to execute serverless notebooks, jobs, or pipelines • Pipelines remaining in a waiting-for-resources state Recommendations No customer action is required at this time. Current Status The issue has been identified in coordination with the cloud provider, and mitigation efforts are in progress. Impact is not yet confirmed to have stopped, Next Update We will provide another update within 2 hours, or sooner if there is a material change in service status.

7. identified Sep 22, 2026, 12:30 PM UTC

   Impact Summary Starting at 02:17 UTC September 22, 2026, customers using Azure Databricks in East US may experience transient failures or degraded availability with Serverless Compute and Jobs. Affected customers may encounter cluster launch timeouts, unexpected workload termination, or jobs and pipelines that remain pending or fail to progress. Symptoms • Serverless workloads failing to start, with cluster launch or allocation timeouts • Jobs and pipeline runs stuck waiting for resources, delayed, or failing to complete • Cancellation requests for running jobs or pipelines remaining in progress for extended periods 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 2 hours, or sooner if there is a material change in service status.

8. monitoring Sep 22, 2026, 02:29 PM UTC

   Impact Summary Between 02:17 UTC and 14:19 UTC on September 22, 2026, customers using Azure Databricks in East US may have experienced transient failures and degraded availability with Serverless Compute and Jobs. Affected customers may have encountered serverless cluster launch timeouts, workloads remaining in a pending state, or unexpected workload terminations during this window. Symptoms • Serverless workloads failing to start, with cluster launch or network setup timeouts • Jobs and pipeline runs remaining pending, failing to progress, or terminating unexpectedly • Delays or failures when attempting to cancel in-flight serverless runs 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.

9. resolved Sep 22, 2026, 03:22 PM UTC

   Impact Summary Between 02:17 UTC and 14:19 UTC on September 22, 2026, customers using Azure Databricks in East US may have experienced intermittent failures and degraded availability with Serverless Compute and Jobs. Affected customers may have encountered transient errors, cluster launch timeouts, or jobs and pipeline runs that failed to start or progress during this window. Symptoms • Serverless workloads failing to start with cluster launch or network setup timeouts • Jobs and pipeline runs remaining pending, failing to progress, or terminating unexpectedly • Delays when attempting to cancel in-flight serverless pipeline or job runs Current Status The issue has been resolved, and all affected services have been restored. Follow-up continues 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

Read the full incident report →

Started Sep 20, 2026, 04:05 AM UTC· resolved Sep 20, 2026, 06:33 AM UTC

1. investigating Sep 20, 2026, 04:05 AM UTC

   We are actively investigating an issue with the Databricks service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

2. monitoring Sep 20, 2026, 04:55 AM UTC

   Impact Summary Between 02:55 UTC and 04:02 UTC on September 20, 2026, customers using Azure Databricks in West Europe may have experienced degraded availability with Databricks SQL and Lakeflow. Affected customers may have encountered query and connection failures, delayed or failed job and pipeline runs. Symptoms • SQL warehouse connection timeouts, with queries failing or running significantly slower than usual • Jobs and pipeline runs remaining pending, failing to start on schedule, or terminating with errors Current Status The issue has been mitigated and service is operational. Monitoring is continuing to confirm sustained recovery. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

3. resolved Sep 20, 2026, 06:33 AM UTC

   Impact Summary Between 02:55 UTC and 04:02 UTC on September 20, 2026, customers using Azure Databricks in West Europe may have experienced degraded availability with Databricks SQL and Lakeflow. Affected customers may have encountered query and connection failures, jobs that did not start or failed shortly after launch, and pipeline runs that failed to progress during this window. Symptoms • SQL warehouse connections timing out, with queries failing or running slowly and dashboards or BI tools returning incomplete results • Jobs remaining pending, failing to start on schedule, or failing immediately after submission • Declarative Pipeline runs failing or not progressing, with delayed or missing status information Current Status The issue has been resolved, and all affected services have been restored. Next Update This is the final update 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

Read the full incident report →

Started Sep 18, 2026, 07:14 AM UTC· resolved Sep 18, 2026, 08:41 AM UTC

1. investigating Sep 18, 2026, 07:14 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. identified Sep 18, 2026, 07:48 AM UTC

   Impact Summary Starting at 06:54 UTC September 18, 2026, customers using Azure Databricks in Southeast Asia may experience degraded availability with Serverless Compute and Jobs. Affected customers may encounter errors, cluster allocation timeouts, or delays when starting or running serverless workloads and jobs. Symptoms • Serverless workloads failing to start or timing out during cluster allocation • Jobs remaining pending, not starting on schedule, or failing immediately • Errors returned when attempting to execute serverless notebooks, workflows, or pipeline runs Recommendations No customer action is required at this time. Current Status The issue has been identified and mitigation efforts are in progress. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

3. monitoring Sep 18, 2026, 08:03 AM UTC

   Impact Summary Between 06:54 UTC and 07:04 UTC on September 18, 2026, customers using Azure Databricks in Southeast Asia may have experienced degraded availability with Serverless Compute and Jobs. Affected customers may have encountered errors, failures starting serverless workloads, or unexpected termination of running workloads during this window. Symptoms • Serverless workloads failing to start or terminating unexpectedly • Errors returned when attempting to execute serverless workloads • Job runs failing or terminating due to dependency failures Current Status The issue has been mitigated and service is operational. Monitoring has confirmed no further failures following mitigation. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. resolved Sep 18, 2026, 08:41 AM UTC

   Impact Summary Between 06:54 UTC and 07:04 UTC on September 18, 2026, customers using Azure Databricks in Southeast Asia may have experienced degraded availability with Serverless Compute and Jobs. Affected customers may have encountered errors when starting serverless workloads, cluster allocation timeouts, unexpected workload termination, and job run failures during this window. Symptoms • Serverless workloads failing to start or terminating unexpectedly • Cluster allocation timeouts and internal errors when executing serverless workloads • Job runs failing or terminating due to dependency failures Current Status The issue has been resolved, and all affected services have been restored. 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

Read the full incident report →

Started Sep 18, 2026, 02:13 AM UTC· resolved Sep 18, 2026, 03:13 AM UTC

1. monitoring Sep 18, 2026, 02:13 AM UTC

   Impact Summary Between 00:19 UTC and 00:29 UTC on September 18, 2026, customers using Azure Databricks may have experienced degraded availability with Lakebase. Affected customers may have been unable to create, access, or operate Lakebase databases and related workloads during this window. Symptoms • Connection failures when attempting to reach Lakebase databases • Queries and administrative operations timing out or failing to complete • Errors returned by applications backed by Lakebase Current Status The issue has been mitigated and service is operational. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

2. resolved Sep 18, 2026, 03:13 AM UTC

   Impact Summary Between 00:19 UTC and 00:29 UTC on September 18, 2026, customers using Azure Databricks may have experienced degraded availability with Lakebase. Affected customers may have been unable to create, access, or operate Lakebase databases and related workloads during this window. Symptoms • Connection failures when attempting to reach Lakebase databases • Queries and administrative operations timing out or failing to complete • Errors returned by applications backed by Lakebase 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

Read the full incident report →

Started Sep 18, 2026, 02:11 AM UTC· resolved Sep 18, 2026, 03:12 AM UTC

1. monitoring Sep 18, 2026, 02:11 AM UTC

   Impact Summary Between 00:22 UTC and 00:45 UTC on September 18, 2026, customers using Azure Databricks may have experienced degraded availability with Lakebase. Affected customers may have been unable to create, access, or operate Lakebase databases and related workloads during this window. Symptoms • Connection failures when attempting to reach Lakebase databases • Queries and administrative operations timing out or failing to complete • Errors returned by applications backed by Lakebase Current Status The issue has been mitigated and service is operational. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

2. resolved Sep 18, 2026, 03:12 AM UTC

   Impact Summary Between 00:22 UTC and 00:45 UTC on September 18, 2026, customers using Azure Databricks may have experienced degraded availability with Lakebase. Affected customers may have been unable to create, access, or operate Lakebase databases and related workloads during this window. Symptoms • Connection failures when attempting to reach Lakebase databases • Queries and administrative operations timing out or failing to complete • Errors returned by applications backed by Lakebase 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

Read the full incident report →

Started Sep 17, 2026, 07:44 AM UTC· resolved Sep 17, 2026, 09:58 AM UTC

1. investigating Sep 17, 2026, 07:44 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. identified Sep 17, 2026, 08:45 AM UTC

   Impact Summary Starting at 07:30 UTC on September 17, 2026, customers using Azure Databricks in Southeast Asia may be experiencing failures or degraded availability with Serverless Compute and Jobs. Affected customers may encounter errors when starting serverless workloads, cluster allocation timeouts, or unexpected termination of running workloads. Symptoms • Serverless workloads failing to start, or terminating unexpectedly • Cluster allocation timeouts and errors returned when launching compute • Jobs and pipeline runs remaining pending, failing to start, or failing to progress Recommendations No customer action is required at this time. Current Status The issue has been identified and mitigation efforts are in progress. Monitoring of affected workloads continues while mitigation is applied. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

3. monitoring Sep 17, 2026, 09:04 AM UTC

   Impact Summary Between 07:30 UTC and 08:20 UTC on September 17, 2026, customers using Azure Databricks in Southeast Asia may have experienced degraded availability with Serverless Compute and Jobs. Affected customers may have encountered errors when launching workloads, cluster allocation timeouts, or unexpected termination of running workloads during this window. Symptoms • Serverless workloads failing to start, with quota or allocation errors returned on launch attempts • Jobs and pipeline runs remaining pending, failing immediately, or terminating unexpectedly • Delayed or missing status information for affected runs Current Status The issue has been mitigated and service is operational. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. resolved Sep 17, 2026, 09:58 AM UTC

   Impact Summary Between 07:30 UTC and 08:20 UTC on September 17, 2026, customers using Azure Databricks in Southeast Asia may have experienced degraded availability with Serverless Compute and Jobs. Affected customers may have encountered cluster launch failures, quota-related errors, and unexpected termination of workloads during this window. Symptoms • Serverless workloads failing to start or terminating unexpectedly • Cluster allocation failures and quota-related error messages when launching compute • Jobs and pipeline runs failing to start, remaining pending, or terminating before completion Current Status The issue has been resolved, and all affected services have been restored. 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

Read the full incident report →

Started Sep 16, 2026, 11:02 PM UTC· resolved Sep 17, 2026, 12:21 AM UTC

1. investigating Sep 16, 2026, 11:02 PM UTC

   Impact Summary Starting at 22:12 UTC September 16, 2026, customers using Azure Databricks in West US 3 may experience degraded availability with Jobs, Notebooks, and Login. Affected customers may encounter delayed or failed job and pipeline runs, errors when opening or running notebooks, and difficulty signing in. Symptoms • Jobs and pipeline runs failing to start, remaining pending, or completing with errors • Notebooks slow to load, stuck on spinners, or failing commands with unknown errors • Login attempts failing or taking longer than expected Recommendations No customer action is required at this time. Current Status The issue is under active investigation. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

2. identified Sep 16, 2026, 11:10 PM UTC

   Impact Summary Starting at 22:12 UTC on September 16, 2026, customers using Azure Databricks in West US 3 may be experiencing degraded availability with Jobs, Notebooks, and Login. Affected customers may encounter delayed or failed job and pipeline runs, errors when opening or executing notebooks, and problems signing in to workspaces. Symptoms • Jobs and pipeline runs failing to start, remaining pending, or not progressing • Notebooks stuck loading, failing to execute commands, or returning unknown errors • Failures or delays when signing in to affected workspaces Recommendations No customer action is required at this time. Current Status The issue has been identified and mitigation efforts are in progress. Further updates will be provided as mitigation advances. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

3. monitoring Sep 16, 2026, 11:26 PM UTC

   Impact Summary Between 22:12 UTC and 23:09 UTC on September 16, 2026, customers using Azure Databricks in West US 3 may have experienced degraded availability with Jobs, Notebooks, and Login. Affected customers may have encountered failures starting or completing job runs, difficulty opening or executing notebooks, and errors when signing in during this window. Symptoms • Jobs failing to start on schedule, remaining pending, or failing immediately • Notebooks stuck on spinners or error pages, with commands failing or sessions disconnecting • Login attempts are failing or timing out when accessing workspaces Current Status The issue has been mitigated, and service is operational. Monitoring is ongoing to confirm sustained recovery across affected services. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

4. resolved Sep 17, 2026, 12:21 AM UTC

   Impact Summary Between 22:12 UTC and 23:09 UTC on September 16, 2026, customers using Azure Databricks in West US 3 may have experienced degraded availability with Jobs, Notebooks, and Login. Affected customers may have encountered failed or delayed job and pipeline runs, errors when opening or executing notebooks, and problems signing in to workspaces during this window. Symptoms • Jobs and pipeline runs failing to start on schedule, remaining pending, or failing immediately • Notebooks slow to load, stuck on spinners, or returning errors when executing commands • Failures or delays when signing in to workspaces Current Status The issue has been resolved, and all affected services have been restored. 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

Read the full incident report →

Started Sep 14, 2026, 05:49 PM UTC· resolved Sep 14, 2026, 11:50 PM UTC

1. investigating Sep 14, 2026, 05:49 PM UTC

   Impact Summary Starting at 17:06 UTC September 14, 2026, customers using Azure Databricks in East US may be experiencing degraded availability with Databricks SQL, AI/BI, Jobs, and Notebooks. Affected customers may encounter query failures, timeout errors, and dashboards or notebooks that fail to load or return results. Symptoms • SQL queries failing or timing out, with warehouses slow to respond • AI/BI dashboards failing to load or refresh, with filters spinning indefinitely • Notebook commands and scheduled job runs failing or not progressing Recommendations No customer action is required at this time. Current Status The issue is under active investigation. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

2. identified Sep 14, 2026, 06:18 PM UTC

   Impact Summary Starting at 17:06 UTC September 14, 2026, customers using Azure Databricks in East US may be experiencing degraded availability with Databricks SQL, AI/BI, Jobs, and Notebooks. Affected customers may encounter query execution failures, timeout errors, and dashboards that fail to load or refresh. Symptoms • SQL queries failing or timing out with deadline exceeded errors • Dashboards failing to load or refresh, or returning empty or partial results • Notebook commands and scheduled job runs failing 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. Recovery is being validated, and the incident remains under active monitoring 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.

3. identified Sep 14, 2026, 07:20 PM UTC

   Impact Summary Starting at 17:06 UTC September 14, 2026, customers using Azure Databricks in East US may be experiencing degraded availability with Databricks SQL, AI/BI, Jobs, and Notebooks. Affected customers may encounter query execution failures, timeout errors, and dashboards that fail to load or refresh. Symptoms • SQL queries failing or timing out with deadline exceeded errors • Dashboards failing to load or refresh, or returning empty or partial results • Notebook commands and scheduled job runs failing 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. Recovery is being validated, and the incident remains under active monitoring 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.

4. identified Sep 14, 2026, 08:21 PM UTC

   Impact Summary Starting at 17:06 UTC September 14, 2026, customers using Azure Databricks in East US may be experiencing degraded availability with Databricks SQL, AI/BI, Jobs, and Notebooks. Affected customers may encounter query execution failures, timeout errors, and dashboards that fail to load or refresh. Symptoms • SQL queries failing or timing out with deadline exceeded errors • Dashboards failing to load or refresh, or returning empty or partial results • Notebook commands and scheduled job runs failing 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. Recovery is being validated, and the incident remains under active monitoring 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.

5. monitoring Sep 14, 2026, 09:19 PM UTC

   Impact Summary Between 17:06 UTC and 20:59 UTC on September 14, 2026, customers using Azure Databricks in East US may have experienced degraded availability with Databricks SQL, AI/BI, Notebooks, and Jobs. Affected customers may have encountered SQL query failures or timeouts, unresponsive dashboards, notebook command errors, and reduced job run success during this window. Symptoms • SQL queries failing or timing out, with BI tool and dashboard connections returning errors or partial results • AI/BI dashboards failing to load or refresh, with filters and conversational analytics requests spinning or erroring • Notebook commands failing with unknown errors, including failed command cancellation • Job and pipeline runs failing or completing at reduced success rates Current Status The issue has been mitigated and service is operational. Mitigation was completed in coordination with the cloud provider, and recovery has been confirmed across affected services. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

6. resolved Sep 14, 2026, 11:50 PM UTC

   Impact Summary Between 17:06 UTC and 20:59 UTC on September 14, 2026, customers using Azure Databricks in East US may have experienced degraded availability and failures across Databricks SQL, AI/BI, Notebooks, and Jobs. Affected customers may have encountered query execution failures, timeouts, unresponsive dashboards, and stalled or failed job runs during this window. Symptoms • SQL queries failing, timing out, or slow to complete, with BI tool and dashboard requests returning errors or partial results • AI/BI dashboards failing to load or refresh, and conversational analytics requests erroring or timing out • Notebook commands failing with unknown errors or hanging, and job runs remaining pending, failing, or not completing Current Status The issue has been resolved, and all affected services have been restored. Resolution was completed 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

Read the full incident report →

Started Sep 12, 2026, 05:50 AM UTC· resolved Sep 12, 2026, 08:45 AM UTC

1. investigating Sep 12, 2026, 05:50 AM UTC

   We are actively investigating an issue with the Databricks service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

2. investigating Sep 12, 2026, 06:43 AM UTC

   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.

3. identified Sep 12, 2026, 08:05 AM UTC

   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.

4. monitoring Sep 12, 2026, 08:36 AM UTC

   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.

5. resolved Sep 12, 2026, 08:45 AM UTC

   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

Read the full incident report →

Started Sep 11, 2026, 11:50 AM UTC· resolved Sep 11, 2026, 02:51 PM UTC

1. investigating Sep 11, 2026, 11:50 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 Sep 11, 2026, 12:05 PM UTC

   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.

3. identified Sep 11, 2026, 12:53 PM UTC

   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.

4. monitoring Sep 11, 2026, 01:51 PM UTC

   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.

5. resolved Sep 11, 2026, 02:51 PM UTC

   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

Read the full incident report →

Started Sep 11, 2026, 07:07 AM UTC· resolved Sep 11, 2026, 10:57 AM UTC

1. investigating Sep 11, 2026, 07:07 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 Sep 11, 2026, 08:00 AM UTC

   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.

3. identified Sep 11, 2026, 09:06 AM UTC

   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.

4. monitoring Sep 11, 2026, 09:59 AM UTC

   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.

5. resolved Sep 11, 2026, 10:57 AM UTC

   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

Read the full incident report →

Started Sep 07, 2026, 02:20 PM UTC· resolved Sep 07, 2026, 05:58 PM UTC

1. investigating Sep 07, 2026, 02:20 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.

2. investigating Sep 07, 2026, 02:42 PM UTC

   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.

3. identified Sep 07, 2026, 03:04 PM UTC

   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.

4. monitoring Sep 07, 2026, 04:12 PM UTC

   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.

5. resolved Sep 07, 2026, 05:58 PM UTC

   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

Read the full incident report →

Started Sep 07, 2026, 06:40 AM UTC· resolved Sep 08, 2026, 06:04 AM UTC

1. investigating Sep 07, 2026, 06:40 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 Sep 07, 2026, 07:32 AM UTC

   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.

3. identified Sep 07, 2026, 07:36 AM UTC

   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.

4. identified Sep 07, 2026, 08:35 AM UTC

   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.

5. identified Sep 07, 2026, 09:33 AM UTC

   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.

6. identified Sep 07, 2026, 10:37 AM UTC

   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.

7. identified Sep 07, 2026, 11:33 AM UTC

   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.

8. identified Sep 07, 2026, 12:38 PM UTC

   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.

9. identified Sep 07, 2026, 01:41 PM UTC

   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.

10. identified Sep 07, 2026, 02:53 PM UTC

    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.

11. identified Sep 07, 2026, 04:17 PM UTC

    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.

12. identified Sep 07, 2026, 06:46 PM UTC

    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.

13. identified Sep 07, 2026, 08:46 PM UTC

    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.

14. identified Sep 07, 2026, 10:46 PM UTC

    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.

15. identified Sep 08, 2026, 12:46 AM UTC

    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.

16. identified Sep 08, 2026, 03:46 AM UTC

    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.

17. monitoring Sep 08, 2026, 04:58 AM UTC

    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.

18. resolved Sep 08, 2026, 06:04 AM UTC

    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

Read the full incident report →

Started Sep 05, 2026, 04:40 PM UTC· resolved Sep 05, 2026, 05:28 PM UTC

1. monitoring Sep 05, 2026, 04:40 PM UTC

   Impact Summary: Between 14:05 UTC and 14:55 UTC on September 05, 2026, customers using Azure Databricks in Central US 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 runs failing or terminating unexpectedly during this window. Symptoms: • Cluster launch failures or clusters stuck in Pending or Starting • Notebook attach failures on customer-managed compute • Job runs failing, remaining pending, or terminating during cluster startup Current Status: The issue has been mitigated and service is operational. Follow-up review 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.

2. resolved Sep 05, 2026, 05:28 PM UTC

   Impact Summary: Between 14:05 UTC and 14:55 UTC on September 05, 2026, customers using Azure Databricks in Central US may have experienced degraded availability with Classic Compute and Jobs. Affected customers may have encountered cluster launch failures, notebook attach errors, or job run failures during this window. Symptoms: • Cluster launch failures or clusters remaining in Pending or Starting states • Notebook attach failures to customer-managed compute • Job runs failing, terminating unexpectedly, or not progressing during cluster startup Current Status: The issue has been resolved, and all affected services have been restored. 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

Read the full incident report →