Databricks AWS experienced a major incident on May 14, 2026 affecting AI/BI and Compute and 1 more component, lasting 2h 52m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 14, 2026, 06:04 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.
- investigating May 14, 2026, 06:04 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.
- investigating May 14, 2026, 06:38 AM UTC
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.
- investigating May 14, 2026, 06:38 AM UTC
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.
- identified May 14, 2026, 07:20 AM UTC
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.
- identified May 14, 2026, 07:20 AM UTC
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.
- monitoring May 14, 2026, 08:02 AM UTC
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.
- monitoring May 14, 2026, 08:02 AM UTC
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.
- resolved May 14, 2026, 08:57 AM UTC
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