Databricks Azure incident

ES-2338758

Resolved after 1 hour 54 minutes, affecting Compute and Compute (Compute — Brazil South) and 1 more, on November 5, 2026.

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.

Started
Nov 05, 2026, 12:29 PM UTC
Resolved
Nov 05, 2026, 02:23 PM UTC
Duration
1h 54m
Detected by Pingoru
Nov 05, 2026, 12:29 PM UTC

Affected components

ComputeCompute (Compute — Brazil South)Databricks AppsDatabricks Apps (Databricks Apps — Brazil South)Databricks SQLDatabricks SQL (Databricks SQL — Brazil South)LakeflowLakeflow (Lakeflow — Brazil South)NotebooksNotebooks (Notebooks — Brazil South)

Update timeline

  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.

Your product runs on more than Databricks Azure

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →