Header Image
Active Incident

Updated a few seconds ago

Welcome to Azure Databricks status page. Here you will find high-level availability information for all of the Azure Databricks services.

AI/BI

Operational

Compute

Operational

Databricks Apps

Operational

Databricks SQL

Operational

Lakebase

Operational

Lakeflow

Operational

Mosaic AI

Operational

Notebooks

Operational

Unity Catalog

Operational

ES-1882222Operational

Incident Status

Operational

Components

Compute

Locations

Canada Central, Canada East, Central India, South India, West India, Germany West Central, Norway East, Sweden Central, Switzerland North, Switzerland West, West US, West US 2, West US 3, South Central US, West Central US, West Europe, North Europe, UK West, UK South, South Africa North, UAE North, Australia East, Australia Central, Australia Central 2, Australia Southeast, Japan East, Japan West, Korea Central, Southeast Asia, East Asia, Brazil South, East US 2, East US, North Central US, Central US, France Central, China East 2, China North 2, China North 3, US Gov Virginia, US Gov Arizona, China East 3, Qatar Central, Mexico Central


April 27, 2026 17:39 UTC
INVESTIGATING

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.

April 27, 2026 18:12 UTC
INVESTIGATING

Impact Summary Starting at 27 April 2026 17:20 UTC, Classic Compute clusters and Serverless Compute in multiple regions may fail to start or become unresponsive. Symptoms Customers may observe: - Cluster driver becoming unreachable or unresponsive - Cluster start operations failing or timing out - Running clusters or serverless workloads becoming unavailable Recommendations No customer action is required at this time. Current Status We are actively investigating reports of Classic Compute and Serverless Compute unavailability across multiple regions. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

April 27, 2026 18:31 UTC
IDENTIFIED

Impact Summary Starting at 27 April 2026 17:20 UTC, Classic Compute and Serverless Compute clusters across multiple regions may fail to start or become unresponsive. Symptoms Customers may observe: - Cluster start operations failing or remaining in a pending state - Existing clusters becoming unresponsive or unreachable - Notebooks, jobs, and SQL workloads unable to connect to their cluster Recommendations No customer action is required at this time. Current Status We have identified the root cause of this issue and are actively working on remediation. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

April 27, 2026 18:39 UTC
MONITORING

Impact Summary From 17:20 UTC to 18:30 UTC 27 April 2026, Classic Compute clusters and Serverless Compute in multiple regions experienced failures to start or became unresponsive. Service has been restored. Symptoms Customers may have observed: - Cluster driver becoming unreachable or unresponsive - Cluster start operations failing or timing out - Running clusters or serverless workloads becoming unavailable Recommendations No customer action is required at this time. Current Status Service has been restored as of 27 April 2026 18:30 UTC. We are actively monitoring to confirm full stabilization. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

April 27, 2026 19:54 UTC
MONITORING

Impact Summary From 17:20 UTC to 18:30 UTC 27 April 2026, Classic Compute clusters and Serverless Compute in multiple regions experienced failures to start or became unresponsive. Service has been restored. Symptoms Customers may have observed: - Cluster driver becoming unreachable or unresponsive - Cluster start operations failing or timing out - Running clusters or serverless workloads becoming unavailable Current Status This incident has been fully resolved as of 27 April 2026, 18:30 UTC. We apologize for any inconvenience this may have caused. If you require further details about this incident, please submit an Azure support ticket.