Is Databricks Azure down?

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.

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

Impact Summary Starting at 11 June 2026 17:28 UTC, customers using Unity Catalog in Azure West US may experience service failures or timeouts. Lakeflow Spark Declarative Pipelines, Lakeflow Jobs, and login and authentication operations that depend on Unity Catalog are also affected. Symptoms Customers may observe: - Unity Catalog operations failing or timing out - Lakeflow Spark Declarative Pipelines failing to start or terminating unexpectedly - Lakeflow Jobs failures involving Unity Catalog operations - Login and authentication failures, including inability to create access tokens Recommendations No customer action is required at this time. Current Status The cause of this incident has been identified. Our engineering team is actively working to restore service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Starting at 11 June 2026 17:28 UTC, customers using Unity Catalog in Azure West US may experience service failures or timeouts. Lakeflow Spark Declarative Pipelines, Lakeflow Jobs, and login and authentication operations that depend on Unity Catalog are also affected. Symptoms Customers may observe: - Unity Catalog operations failing or timing out - Lakeflow Spark Declarative Pipelines failing to start or terminating unexpectedly - Lakeflow Jobs failures involving Unity Catalog operations - Login and authentication failures, including inability to create access tokens Recommendations No customer action is required at this time. Current Status The cause of this incident has been identified. Our engineering team is actively working to restore service. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary From 11 June 2026 17:28 UTC to 11 June 2026 18:09 UTC, customers using Unity Catalog in Azure West US experienced service failures or timeouts. Service has been restored. Symptoms Customers experienced: - Unity Catalog operations failing or timing out - Lakeflow Spark Declarative Pipelines failing to start or terminating unexpectedly - Lakeflow Jobs failures involving Unity Catalog operations - Login and authentication failures, including inability to create access tokens Recommendations No customer action is required at this time. Current Status Service has been restored as of 11 June 2026 18:09 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

Impact Summary From 11 June 2026 17:28 UTC to 11 June 2026 18:09 UTC, customers using Unity Catalog in Azure West US experienced service failures or timeouts. Service has been restored. Symptoms Customers experienced:   - Unity Catalog operations failing or timing out   - Lakeflow Spark Declarative Pipelines failing to start or terminating unexpectedly   - Lakeflow Jobs failures involving Unity Catalog operations   - Login and authentication failures, including inability to create access tokens Recommendations No customer action is required at this time. Current Status Service has been restored as of 11 June 2026 18:09 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

Impact Summary Between 11 June 2026 17:28 UTC and 11 June 2026 18:09 UTC, customers using Unity Catalog in Azure West US experienced service failures or timeouts. Symptoms Customers experienced: - Unity Catalog operations failing or timing out - Lakeflow Spark Declarative Pipelines failing to start or terminating unexpectedly - Lakeflow Jobs failures involving Unity Catalog operations - Login and authentication failures, including inability to create access tokens Current Status This incident has been fully resolved as of 11 June 2026 18:09 UTC. Normal service operation has been restored. We apologize for any inconvenience this may have caused. If you require further details about this incident, please submit an Azure support ticket. Next Update No further updates are planned unless conditions change. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription

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

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

Starting at approximately 3:54 UTC on June 10, 2026, a subset of customers using Azure Databricks may be experiencing failures and errors when attempting to launch or restart Classic Compute clusters. Affected customers may find that their clusters are unable to start successfully, with startup attempts resulting in errors or prolonged failures. This disruption is affecting Classic Compute workloads, and the issue remains ongoing as our engineering teams continue to work toward a resolution. Symptoms • Cluster launch or restart attempts are failing, with errors indicating that the compute instance is unreachable after bootstrap completes • Classic Compute clusters cannot be started or restarted, leaving dependent workloads unavailable • Degraded availability of Classic Compute resources, with cluster startup errors being reported during normal operations Recommendations No customer action is required at this time. Current Status We have identified the root cause and are working on a fix. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 3:54 UTC on June 10, 2026, a subset of customers using Azure Databricks may be experiencing failures and errors when attempting to launch or restart Classic Compute clusters. Affected customers may find that their clusters are unable to start successfully, with startup attempts resulting in errors or prolonged failures. This disruption is affecting Classic Compute workloads, and the issue remains ongoing as our engineering teams continue to work toward a resolution. Symptoms • Cluster launch or restart attempts are failing, with errors indicating that the compute instance is unreachable after bootstrap completes • Classic Compute clusters cannot be started or restarted, leaving dependent workloads unavailable • Degraded availability of Classic Compute resources, with cluster startup errors being reported during normal operations Recommendations No customer action is required at this time. Current Status We have identified the root cause and are working on a fix. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 3:54 UTC and 7:53 UTC on June 10, 2026, a subset of customers using Azure Databricks may have experienced failures or errors when attempting to launch or restart Classic Compute clusters. Affected customers may have found that cluster startup attempts resulted in errors or prolonged failures, with degraded availability of Classic Compute workloads during this period. Symptoms • Classic Compute cluster launch or restart attempts failed with errors indicating the compute instance was unreachable after bootstrap completed. • Customers were unable to start or restart Classic Compute clusters, leaving dependent workloads unavailable. • Cluster startup errors were reported during normal operations, with some clusters failing intermittently after initial recovery. Current Status The issue has been mitigated and services have been restored. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 3:54 UTC and 7:53 UTC on June 10, 2026, a subset of customers using Azure Databricks may have experienced failures or errors when attempting to launch or restart Classic Compute clusters. Affected customers may have found that cluster startup attempts resulted in errors or prolonged failures, with degraded availability of Classic Compute workloads during this period. Symptoms • Classic Compute cluster launch or restart attempts failed with errors indicating the compute instance was unreachable after bootstrap completed. • Customers were unable to start or restart Classic Compute clusters, leaving dependent workloads unavailable. • Cluster startup errors were reported during normal operations, with some clusters failing intermittently after initial recovery. Current Status The issue has been mitigated and services have been restored. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 3:54 UTC and 7:53 UTC on June 10, 2026, a subset of customers using Azure Databricks may have experienced failures or errors when attempting to launch or restart Classic Compute clusters. Affected customers may have found that cluster startup attempts resulted in errors or prolonged failures, with degraded availability of Classic Compute workloads during this period. Symptoms • Classic Compute cluster launch or restart attempts failed with errors indicating the compute instance was unreachable after bootstrap completed. • Customers were unable to start or restart Classic Compute clusters, leaving dependent workloads unavailable. • Cluster startup errors were reported during normal operations, with some clusters failing intermittently after initial recovery. Current Status This incident has been resolved. We apologize for any inconvenience this may have caused. If you require further details about this incident, please submit an Azure support ticket. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription

We are actively investigating an issue 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.

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.

Starting at approximately 00:43 UTC on June 10, 2026, customers using Azure Databricks may be experiencing errors and failures when attempting to use the Notebooks service. A subset of customers using Azure Databricks may be unable to submit notebook workloads to clusters, execute notebook commands, or attach notebooks to clusters, resulting in disrupted notebook workflows. Symptoms • Errors when attempting to submit or run notebooks against a cluster • Notebook commands failing to execute, resulting in connection or communication errors • Inability to attach notebooks to clusters Recommendations No customer action is required at this time. Current Status We are actively investigating incident causing errors and failures for customers using the Notebooks service, and our engineering team is working to identify and apply a resolution. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 00:43 UTC on June 10, 2026, customers using Azure Databricks may be experiencing errors and failures when attempting to use the Notebooks service. A subset of customers using Azure Databricks may be unable to submit notebook workloads to clusters, execute notebook commands, or attach notebooks to clusters, resulting in disrupted notebook workflows. Symptoms • Errors when attempting to submit or run notebooks against a cluster • Notebook commands failing to execute, resulting in connection or communication errors • Inability to attach notebooks to clusters Recommendations No customer action is required at this time. Current Status We are actively investigating incident causing errors and failures for customers using the Notebooks service, and our engineering team is working to identify and apply a resolution. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 0:43 UTC on June 10, 2026, customers using Azure Databricks may be experiencing errors and failures when attempting to use the Notebooks service. A subset of customers using Azure Databricks may be unable to submit notebook workloads to clusters, execute notebook commands, or attach notebooks to clusters, resulting in disrupted notebook workflows. Symptoms • Errors when attempting to submit or run notebooks against a cluster • Notebook commands failing to execute, resulting in connection or communication errors • Inability to attach notebooks to clusters Recommendations No customer action is required at this time. Current Status Our engineering team has identified the root cause of the incident impacting the Notebooks service and has implemented a mitigation. We are continuing to investigate and closely monitor the situation. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 0:43 UTC on June 10, 2026, customers using Azure Databricks may be experiencing errors and failures when attempting to use the Notebooks service. A subset of customers using Azure Databricks may be unable to submit notebook workloads to clusters, execute notebook commands, or attach notebooks to clusters, resulting in disrupted notebook workflows. Symptoms • Errors when attempting to submit or run notebooks against a cluster • Notebook commands failing to execute, resulting in connection or communication errors • Inability to attach notebooks to clusters Recommendations No customer action is required at this time. Current Status Our engineering team has identified the root cause of the incident impacting the Notebooks service and has implemented a mitigation. We are continuing to investigate and closely monitor the situation. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 00:43 UTC and 04:01 UTC on June 10, 2026, a subset of customers using Azure Databricks may have experienced errors and failures when attempting to use the Notebooks service. Affected customers may have been unable to submit notebook workloads to clusters, execute notebook commands, or attach notebooks to clusters, resulting in disrupted notebook workflows. Symptoms • Errors when attempting to submit or run notebooks against a cluster • Notebook commands failing to execute, resulting in connection or communication errors • Inability to attach notebooks to clusters Current Status The issue has been mitigated and services have been restored. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 00:43 UTC and 04:01 UTC on June 10, 2026, a subset of customers using Azure Databricks may have experienced errors and failures when attempting to use the Notebooks service. Affected customers may have been unable to submit notebook workloads to clusters, execute notebook commands, or attach notebooks to clusters, resulting in disrupted notebook workflows. Symptoms • Errors when attempting to submit or run notebooks against a cluster • Notebook commands failing to execute, resulting in connection or communication errors • Inability to attach notebooks to clusters Current Status The issue has been mitigated and services have been restored. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 00:43 UTC and 04:01 UTC on June 10, 2026, a subset of customers using Azure Databricks may have experienced errors and failures when attempting to use the Notebooks service. Affected customers may have been unable to submit notebook workloads to clusters, execute notebook commands, or attach notebooks to clusters, resulting in disrupted notebook workflows. Symptoms • Errors when attempting to submit or run notebooks against a cluster • Notebook commands failing to execute, resulting in connection or communication errors • Inability to attach notebooks to clusters Current Status This incident has been resolved. 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

Lakebase project creation is temporarily unavailable in the East US Region. Existing Lakebase projects will continue to operate normally.

Lakebase project creation is temporarily unavailable in the East US Region. Existing Lakebase projects will continue to operate normally.

Lakebase Project creation had been temporarily unavailable in the East US Region. Pre-existing Lakebase Projects continued to operate normally. Project creation is now re-enabled. We will continue to monitor the platform for 1 hour to verify normal operation.

As of 23:00 UTC June 8 2026, Lakebase Project creation has been re-enabled in the East US Region. Back to current status Status History Subscribe to receive status updates by email Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates by webhook Each status update will POST a JSON payload to this URL Email address for managing webhook Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Microsoft Teams Enter your Microsoft Teams webhook. View Instructions Email address for managing subscription Close Subscribe Manage Subscription Manage Existing Subscription Create New Subscription Subscribe to receive status updates in Slack Slack channel ID Find the channel ID: Select the channel in your Slack workspace. The channel ID is displayed in the browser URL. Example: https://app.slack.com/client/T04SJBK1C/ C03SKGJ1P Email address Close Manage Subscription Manage Existing Subscription Create New Subscription

We are actively investigating an issue 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.

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.

Starting at approximately 18:51 UTC on June 5, 2026, customers using Azure Databricks may be experiencing failures or errors when attempting to create, update, or delete Databricks workspaces. Workspace management operations may be unavailable or returning errors during this period. Symptoms • Errors when attempting to create a new Databricks workspace • Failures when attempting to update or delete an existing Databricks workspace • Workspace management operations not completing or returning error responses Recommendations No customer action is required at this time. Our engineering team is actively investigating and working to restore full service. Please retry workspace operations once the incident is resolved. Current Status Our engineering team is actively investigating failures affecting Workspace CRUD operations and working to restore service as quickly as possible. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Starting at approximately 18:51 UTC on June 5, 2026, customers using Azure Databricks may be experiencing failures or errors when attempting to create, update, or delete Databricks workspaces. Workspace management operations may be unavailable or returning errors during this period. Symptoms • Errors when attempting to create a new Databricks workspace • Failures when attempting to update or delete an existing Databricks workspace • Workspace management operations not completing or returning error responses Recommendations No customer action is required at this time. Our engineering team is actively investigating and working to restore full service. Please retry workspace operations once the incident is resolved. Current Status Our engineering team is actively investigating failures affecting Workspace CRUD operations and working to restore service as quickly as possible. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 18:51 UTC and 19:55 UTC on June 5, 2026, customers using Azure Databricks may have experienced failures or errors when attempting to create, update, or delete Databricks workspaces. A subset of customers may have experienced Workspace management operations being unavailable or returning errors during this period. Symptoms • Errors when attempting to create a new Databricks workspace • Failures when attempting to update or delete an existing Databricks workspace • Workspace management operations not completing or returning error responses Current Status The issue has been mitigated and services have been restored. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 18:51 UTC and 19:55 UTC on June 5, 2026, customers using Azure Databricks may have experienced failures or errors when attempting to create, update, or delete Databricks workspaces. A subset of customers may have experienced Workspace management operations being unavailable or returning errors during this period. Symptoms • Errors when attempting to create a new Databricks workspace • Failures when attempting to update or delete an existing Databricks workspace • Workspace management operations not completing or returning error responses Current Status The issue has been mitigated and services have been restored. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 18:51 UTC and 19:55 UTC on June 5, 2026, customers using Azure Databricks may have experienced failures or errors when attempting to create, update, or delete Databricks workspaces. During this period, a subset of customers using Azure Databricks may have found workspace management operations unavailable or returning errors. Symptoms • Errors when attempting to create a new Databricks workspace • Failures when attempting to update or delete an existing Databricks workspace • Workspace management operations did not complete or returned error responses Current Status This incident has been resolved as of 19:55 UTC June 5 2026. 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