Is Databricks AWS 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 From 2026-06-08 15:55 UTC to 2026-06-08 16:35 UTC, customers using Unity Catalog in the AWS US East (N. Virginia) region experienced failures and delays when accessing governed data, metadata, and System Tables. Service has been restored. Symptoms Customers experienced: - Errors or failures when accessing Unity Catalog-governed data and metadata - Failed or delayed requests to read or query System Tables (Audit Logs, Billable Usage, Lineage) - Intermittent failures performing catalog and governance operations Recommendations No customer action is required. Current Status Service has been restored as of 2026-06-08 16:35 UTC. We are actively monitoring to confirm full stabilization. Next Update We will provide another update within 1 hour.

Impact Summary From 2026-06-08 15:55 UTC to 2026-06-08 16:35 UTC, customers using Unity Catalog in the AWS US East (N. Virginia) region experienced failures and delays when accessing governed data, metadata, and System Tables. Service has been restored. Symptoms Customers experienced: - Errors or failures when accessing Unity Catalog-governed data and metadata - Failed or delayed requests to read or query System Tables (Audit Logs, Billable Usage, Lineage) - Intermittent failures performing catalog and governance operations Recommendations No customer action is required. Current Status Service has been restored as of 2026-06-08 16:35 UTC. We are actively monitoring to confirm full stabilization. Next Update We will provide another update within 1 hour.

Impact Summary Between 2026-06-08 15:55 UTC and 2026-06-08 16:35 UTC, customers using Unity Catalog in the AWS US East (N. Virginia) region experienced failures and delays when accessing governed data, metadata, and System Tables. Symptoms Customers experienced: - Errors or failures when accessing Unity Catalog-governed data and metadata - Failed or delayed requests to read or query System Tables (Audit Logs, Billable Usage, Lineage) - Intermittent failures performing catalog and governance operations Current Status This incident has been fully resolved as of 2026-06-08 16:35 UTC, and Unity Catalog is operating normally. We apologize for the disruption. If you require further details about this incident, please submit a support ticket or contact [email protected]. Next Update No further updates are planned 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

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:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances. Symptoms • Pipeline runs are failing or terminating unexpectedly with errors • Lakebase queries and connections are failing with connectivity errors • Synced table pipelines are unable to complete successfully Recommendations No customer action is required at this time. Current Status We are actively investigating an issue causing failures and errors with Declarative Pipelines and Lakebase, and our engineering teams are working to resolve the disruption. 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:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances. Symptoms • Pipeline runs are failing or terminating unexpectedly with errors • Lakebase queries and connections are failing with connectivity errors • Synced table pipelines are unable to complete successfully Recommendations No customer action is required at this time. Current Status We are actively investigating an issue causing failures and errors with Declarative Pipelines and Lakebase, and our engineering teams are working to resolve the disruption. 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:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances. Symptoms • Pipeline runs are failing or terminating unexpectedly with errors • Lakebase queries and connections are failing with connectivity errors • Synced table pipelines are unable to complete successfully Recommendations If you are experiencing connectivity failures with a Lakebase instance, restarting the instance may restore connectivity. Please contact Databricks support if issues persist after restarting. Current Status We have identified the cause of the issue affecting Declarative Pipelines and Lakebase, and our engineering teams are actively working to resolve the disruption. 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:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances. Symptoms • Pipeline runs are failing or terminating unexpectedly with errors • Lakebase queries and connections are failing with connectivity errors • Synced table pipelines are unable to complete successfully Recommendations If you are experiencing connectivity failures with a Lakebase instance, restarting the instance may restore connectivity. Please contact Databricks support if issues persist after restarting. Current Status We have identified the cause of the issue affecting Declarative Pipelines and Lakebase, and our engineering teams are actively working to resolve the disruption. 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:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances. Symptoms • Pipeline runs are failing or terminating unexpectedly with errors • Lakebase queries and connections are failing with connectivity errors • Synced table pipelines are unable to complete successfully Recommendations If you are experiencing connectivity failures with a Lakebase instance, restarting the instance may restore connectivity. Please contact Databricks support if issues persist after restarting. Current Status We have identified the cause of the issue affecting Declarative Pipelines and Lakebase, and our engineering teams are actively working to resolve the disruption. 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:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances. Symptoms • Pipeline runs are failing or terminating unexpectedly with errors • Lakebase queries and connections are failing with connectivity errors • Synced table pipelines are unable to complete successfully Recommendations If you are experiencing connectivity failures with a Lakebase instance, restarting the instance may restore connectivity. Please contact Databricks support if issues persist after restarting. Current Status We have identified the cause of the issue affecting Declarative Pipelines and Lakebase, and our engineering teams are actively working to resolve the disruption. 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:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances. Symptoms • Pipeline runs are failing or terminating unexpectedly with errors • Lakebase queries and connections are failing with connectivity errors • Synced table pipelines are unable to complete successfully Recommendations If you are experiencing connectivity failures with a Lakebase instance, restarting the instance may restore connectivity. Please contact Databricks support if issues persist after restarting. Current Status We have identified the cause of the issue affecting Declarative Pipelines and Lakebase, and our engineering teams are actively working to resolve the disruption. 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:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances. Symptoms • Pipeline runs are failing or terminating unexpectedly with errors • Lakebase queries and connections are failing with connectivity errors • Synced table pipelines are unable to complete successfully Recommendations If you are experiencing connectivity failures with a Lakebase instance, restarting the instance may restore connectivity. Please contact Databricks support if issues persist after restarting. Current Status We have identified the cause of the issue affecting Declarative Pipelines and Lakebase, and our engineering teams are actively working to resolve the disruption. 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:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances. Symptoms • Pipeline runs are failing or terminating unexpectedly with errors • Lakebase queries and connections are failing with connectivity errors • Synced table pipelines are unable to complete successfully Recommendations If you are experiencing connectivity failures with a Lakebase instance, restarting the instance may restore connectivity. Please contact Databricks support if issues persist after restarting. Current Status We have identified the cause of the issue affecting Declarative Pipelines and Lakebase, and our engineering teams are actively working to resolve the disruption. 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:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances. Symptoms • Pipeline runs are failing or terminating unexpectedly with errors • Lakebase queries and connections are failing with connectivity errors • Synced table pipelines are unable to complete successfully Recommendations If you are experiencing connectivity failures with a Lakebase instance, restarting the instance may restore connectivity. Please contact Databricks support if issues persist after restarting. Current Status We have identified the cause of the issue affecting Declarative Pipelines and Lakebase, and our engineering teams are actively working to resolve the disruption. 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:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances. Symptoms • Pipeline runs are failing or terminating unexpectedly with errors • Lakebase queries and connections are failing with connectivity errors • Synced table pipelines are unable to complete successfully Recommendations If you are experiencing connectivity failures with a Lakebase instance, restarting the instance may restore connectivity. Please contact Databricks support if issues persist after restarting. Current Status We have identified the cause of the issue affecting Declarative Pipelines and Lakebase, and our engineering teams are actively working to resolve the disruption. 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:00 UTC on May 31, 2026, customers using Databricks may be experiencing errors and failures with Declarative Pipelines and Lakebase. Affected customers may be unable to run or complete pipeline workloads, and may be experiencing failures when attempting to connect to or query Lakebase instances. Symptoms • Pipeline runs are failing or terminating unexpectedly with errors • Lakebase queries and connections are failing with connectivity errors • Synced table pipelines are unable to complete successfully Recommendations If you are experiencing connectivity failures with a Lakebase instance, restarting the instance may restore connectivity. Please contact Databricks support if issues persist after restarting. Current Status We have identified the cause of the issue affecting Declarative Pipelines and Lakebase, and our engineering teams are actively working to resolve the disruption. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 00:00 UTC and 07:27 UTC on May 31, 2026, customers using Databricks may have experienced errors and failures with Declarative Pipelines and Lakebase. A subset of customers may have been unable to run or complete pipeline workloads, and may have experienced failures when attempting to connect to or query Lakebase instances. Symptoms • Pipeline runs failed or terminated unexpectedly with errors, including synced table pipeline failures • Lakebase queries and connections failed with 'Couldn't connect to compute node' errors • Synced table pipelines were unable to complete successfully Current Status The issue has been mitigated and services have been restored. We are actively monitoring to confirm stability. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 00:00 UTC and 07:27 UTC on May 31, 2026, customers using Databricks may have experienced errors and failures with Declarative Pipelines and Lakebase. A subset of customers may have been unable to run or complete pipeline workloads, and may have experienced failures when attempting to connect to or query Lakebase instances. Symptoms • Pipeline runs failed or terminated unexpectedly with errors, including synced table pipeline failures • Lakebase queries and connections failed with 'Couldn't connect to compute node' errors • Synced table pipelines were unable to complete successfully Current Status The issue has been mitigated and services have been restored. We are actively monitoring to confirm stability. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 00:00 UTC and 07:27 UTC on May 31, 2026, customers using Databricks may have experienced errors and failures with Declarative Pipelines and Lakebase. A subset of customers may have been unable to run or complete pipeline workloads, and may have experienced failures when attempting to connect to or query Lakebase instances. Symptoms • Pipeline runs failed or terminated unexpectedly with errors, including synced table pipeline failures • Lakebase queries and connections failed with connectivity errors • Synced table pipelines were unable to complete successfully 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 a support ticket or contact [email protected]. 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.

Impact Summary Starting at 26 May 2026 17:14 UTC, customers using Lakeflow Spark Declarative Pipelines may experience pipeline start and restart failures. Symptoms Customers may observe: - Pipelines failing to start or restart - Pipeline updates terminating shortly after launch Recommendations Manually stopping and restarting Pipelines is expected to succeed. Current Status Our engineering team is actively investigating the issue and working to identify the cause. We will share more information as it becomes available. 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 26 May 2026 17:14 UTC, customers using Lakeflow Spark Declarative Pipelines may experience pipeline start and restart failures. Symptoms Customers may observe: - Pipelines failing to start or restart - Pipeline updates terminating shortly after launch Recommendations Manually stopping and restarting Pipelines is expected to succeed. Current Status Our engineering team is actively investigating the issue and working to identify the cause. We will share more information as it becomes available. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Between 26 May 2026 17:14 UTC and 26 May 2026 20:53 UTC, customers using Lakeflow Spark Declarative Pipelines may have experienced pipeline start and restart failures. Symptoms Customers may have observed: - Pipelines failing to start or restart - Pipeline updates terminating shortly after launch Recommendations No customer action is required at this time. Current Status A fix has been applied and service has been restored. We are actively monitoring to confirm stability. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Between 26 May 2026 17:14 UTC and 26 May 2026 20:53 UTC, customers using Lakeflow Spark Declarative Pipelines may have experienced pipeline start and restart failures. Symptoms Customers may have observed: - Pipelines failing to start or restart - Pipeline updates terminating shortly after launch Recommendations No customer action is required at this time. Current Status A fix has been applied and service has been restored. We are actively monitoring to confirm stability. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Between 26 May 2026 17:14 UTC and 26 May 2026 20:53 UTC, customers using Lakeflow Spark Declarative Pipelines experienced pipeline start and restart failures. Symptoms Customers may have observed: - Pipelines failing to start or restart - Pipeline updates terminating shortly after launch Current Status This incident has been fully resolved and normal operation has been restored. We apologize for the disruption. If you require further details about this incident, please submit a support ticket or contact [email protected]. Next Update No further updates are planned 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

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 00:34 UTC on May 19, 2026, a subset of customers using Databricks may be experiencing failures or degraded availability with Serverless Compute workloads. Affected customers may observe errors or inability to start or run Serverless Compute jobs. Symptoms • Serverless Compute workloads failing to start or terminating unexpectedly • Cluster allocation timeouts preventing jobs and pipelines from running • Errors when attempting to execute Serverless Compute workloads Recommendations No customer action is required at this time. Our engineering teams are actively investigating the issue. Current Status We are actively investigating a disruption affecting Serverless Compute and will provide updates as more information becomes available. 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:34 UTC on May 19, 2026, a subset of customers using Databricks may be experiencing failures or degraded availability with Serverless Compute workloads. Affected customers may observe errors or inability to start or run Serverless Compute jobs. Symptoms • Serverless Compute workloads failing to start or terminating unexpectedly • Cluster allocation timeouts preventing jobs and pipelines from running • Errors when attempting to execute Serverless Compute workloads Recommendations No customer action is required at this time. Our engineering teams are actively investigating the issue. Current Status We are actively investigating a disruption affecting Serverless Compute and will provide updates as more information becomes available. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 00:34 UTC and 01:40 UTC on May 19, 2026, a subset of customers using Databricks may have experienced failures or degraded availability with Serverless Compute, Declarative Pipelines, and Jobs. Affected customers may have encountered errors, cluster allocation timeouts, or unexpected termination of workloads during this window. Symptoms • Serverless Compute workloads failed to start or terminated unexpectedly • Cluster allocation timeouts prevented Declarative Pipelines and Jobs from running • Errors were returned when attempting to execute Serverless Compute workloads 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:34 UTC and 01:40 UTC on May 19, 2026, a subset of customers using Databricks may have experienced failures or degraded availability with Serverless Compute, Declarative Pipelines, and Jobs. Affected customers may have encountered errors, cluster allocation timeouts, or unexpected termination of workloads during this window. Symptoms • Serverless Compute workloads failed to start or terminated unexpectedly • Cluster allocation timeouts prevented Declarative Pipelines and Jobs from running • Errors were returned when attempting to execute Serverless Compute workloads 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.

Starting at approximately 00:34 UTC on May 19, 2026, a subset of customers using Databricks may be experiencing failures or degraded availability with Serverless Compute, Declarative Pipelines, and Jobs. There was a brief recovery period between approximately 01:31 UTC and 01:51 UTC on May 19, 2026, during which services appeared to stabilize before a further period of disruption was observed. Affected customers may be encountering errors, cluster allocation timeouts, or unexpected termination of workloads. Symptoms • Serverless Compute workloads failing to start or terminating unexpectedly • Cluster allocation timeouts preventing Declarative Pipelines and Jobs from running • Errors returned when attempting to execute Serverless Compute workloads Recommendations No customer action is required at this time. Current Status The issue has been identified and engineering teams are applying mitigations. 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:34 UTC on May 19, 2026, a subset of customers using Databricks may be experiencing failures or degraded availability with Serverless Compute, Declarative Pipelines, and Jobs. There was a brief recovery period between approximately 01:31 UTC and 01:51 UTC on May 19, 2026, during which services appeared to stabilize before a further period of disruption was observed. Affected customers may be encountering errors, cluster allocation timeouts, or unexpected termination of workloads. Symptoms • Serverless Compute workloads failing to start or terminating unexpectedly • Cluster allocation timeouts preventing Declarative Pipelines and Jobs from running • Errors returned when attempting to execute Serverless Compute workloads Recommendations No customer action is required at this time. Current Status The issue has been identified and engineering teams are applying mitigations. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 00:34 UTC and 03:00 UTC on May 19, 2026, a subset of customers using Databricks may have experienced failures or degraded availability with Serverless Compute, Declarative Pipelines, and Jobs. There was a brief recovery period between approximately 01:31 UTC and 01:51 UTC during which services appeared to stabilize before further periods of disruption were observed. Affected customers may have encountered errors, cluster allocation timeouts, or unexpected termination of workloads during this window. Symptoms • Serverless Compute workloads failed to start or terminated unexpectedly • Cluster allocation timeouts prevented Declarative Pipelines and Jobs from running • Errors were returned when attempting to execute Serverless Compute workloads 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:34 UTC and 03:00 UTC on May 19, 2026, a subset of customers using Databricks may have experienced failures or degraded availability with Serverless Compute, Declarative Pipelines, and Jobs. There was a brief recovery period between approximately 01:31 UTC and 01:51 UTC during which services appeared to stabilize before further periods of disruption were observed. Affected customers may have encountered errors, cluster allocation timeouts, or unexpected termination of workloads during this window. Symptoms • Serverless Compute workloads failed to start or terminated unexpectedly • Cluster allocation timeouts prevented Declarative Pipelines and Jobs from running • Errors were returned when attempting to execute Serverless Compute workloads 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:34 UTC and 03:00 UTC on May 19, 2026, a subset of customers using Databricks may have experienced failures or degraded availability with Serverless Compute, Declarative Pipelines, and Jobs. There was a brief recovery period between approximately 01:31 UTC and 01:51 UTC during which services appeared to stabilize before further periods of disruption were observed. Affected customers may have encountered errors, cluster allocation timeouts, or unexpected termination of workloads during this window. Symptoms • Serverless Compute workloads failed to start or terminated unexpectedly • Cluster allocation timeouts prevented Declarative Pipelines and Jobs from running • Errors were returned when attempting to execute Serverless Compute workloads 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 a support ticket or contact [email protected]. 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.

Impact Summary Starting at 14 May 2026 05:17 UTC, customers using the Workspace UI, Classic Compute, Databricks SQL, AI/BI Dashboards, and MLflow in AWS us-west-2 may be unable to complete operations across these services. Symptoms Customers may observe: - Errors when opening notebooks or browsing workspace folders - Failures when starting clusters or running jobs - Errors loading Databricks SQL queries and AI/BI Dashboards - Failures when calling Databricks APIs Recommendations No customer action is required at this time. Current Status We are actively investigating and working to restore normal 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 14 May 2026 05:17 UTC, customers using the Workspace UI, Classic Compute, Databricks SQL, AI/BI Dashboards, and MLflow in AWS us-west-2 may be unable to complete operations across these services. Symptoms Customers may observe: - Errors when opening notebooks or browsing workspace folders - Failures when starting clusters or running jobs - Errors loading Databricks SQL queries and AI/BI Dashboards - Failures when calling Databricks APIs Recommendations No customer action is required at this time. Current Status We are actively investigating and working to restore normal 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 14 May 2026 05:17 UTC, customers using the Workspace UI, Classic Compute, Databricks SQL, AI/BI Dashboards, and MLflow in AWS us-west-2 may be unable to complete operations across these services. Symptoms Customers may observe: * Errors when opening notebooks or browsing workspace folders * Failures when starting clusters or running jobs * Errors loading Databricks SQL queries and AI/BI Dashboards * Failures when calling Databricks APIs Recommendations No customer action is required at this time. Current Status We have identified the cause of the issue and are working to apply a mitigation. 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 14 May 2026 05:17 UTC, customers using the Workspace UI, Classic Compute, Databricks SQL, AI/BI Dashboards, and MLflow in AWS us-west-2 may be unable to complete operations across these services. Symptoms Customers may observe: * Errors when opening notebooks or browsing workspace folders * Failures when starting clusters or running jobs * Errors loading Databricks SQL queries and AI/BI Dashboards * Failures when calling Databricks APIs Recommendations No customer action is required at this time. Current Status We have identified the cause of the issue and are working to apply a mitigation. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Between 05:17 UTC and 07:43 UTC on 14 May 2026, customers using the Workspace UI, Classic Compute, Databricks SQL, AI/BI Dashboards, and MLflow in AWS us-west-2 may have been unable to complete operations across these services. Symptoms Customers may have observed: * Errors when opening notebooks or browsing workspace folders * Failures when starting clusters or running jobs * Errors loading Databricks SQL queries and AI/BI Dashboards * Failures when calling Databricks APIs Recommendations No customer action is required at this time. Current Status A mitigation has been applied and we are monitoring the services for full recovery. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Between 05:17 UTC and 07:43 UTC on 14 May 2026, customers using the Workspace UI, Classic Compute, Databricks SQL, AI/BI Dashboards, and MLflow in AWS us-west-2 may have been unable to complete operations across these services. Symptoms Customers may have observed: * Errors when opening notebooks or browsing workspace folders * Failures when starting clusters or running jobs * Errors loading Databricks SQL queries and AI/BI Dashboards * Failures when calling Databricks APIs Recommendations No customer action is required at this time. Current Status A mitigation has been applied and we are monitoring the services for full recovery. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Between 14 May 2026 05:17 UTC and 14 May 2026 07:43 UTC, customers using the Workspace UI, Classic Compute, Databricks SQL, AI/BI Dashboards, and MLflow in AWS us-west-2 experienced failures completing operations across these services. Symptoms Customers experienced: - Errors when opening notebooks or browsing workspace folders - Failures when starting clusters or running jobs - Errors loading Databricks SQL queries and AI/BI Dashboards - Failures when calling Databricks APIs Current Status This incident has been fully resolved as of 14 May 2026 07:43 UTC. Normal operation has been restored. We apologize for the disruption. If you require further details about this incident, please submit a support ticket or contact [email protected]. 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