AWS Databricks experienced a service disruption starting at approximately 00:34 UTC on May 19, 2026, affecting Serverless Compute workloads for a subset of customers. Users encountered failures starting or running Serverless Compute jobs, cluster allocation timeouts, and unexpected workload terminations. The incident lasted 56 minutes and affected both the Compute Service and Jobs Service components.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
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.
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.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with