AWS Databricks experienced a 36-minute incident starting November 17, 2026 at 18:43 UTC, where Serverless Compute failed to start or remained stuck in a starting state across multiple regions on AWS, Azure, and GCP. Databricks SQL, Jobs Service, and Compute Service were all affected, causing delays and failures in notebooks, jobs, and pipelines. The root cause was identified and resolved via a rollback to restore normal service.
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 with the Databricks service.
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Impact Summary
Starting at 2026-11-17 18:43 UTC, customers using Serverless Compute in multiple regions across AWS, Azure, and GCP may experience delays or failures when starting compute.
Symptoms
Customers may observe:
- Serverless compute remaining in a starting state, or failing to start
- Notebooks, jobs, or pipelines that use serverless compute being delayed or failing to start
Recommendations
No customer action is required at this time.
Current Status
We have identified the issue preventing serverless compute from starting. A rollback is in progress to restore normal service.
Next Update
We will provide another update within 1 hour.
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