Outage in AWS Databricks
ES-1882222
Resolved Major
April 27, 2026 - Started 3 days ago
- Lasted about 1 hour
Incident Report
Summary AI Generated
AWS Databricks experienced a major incident affecting Classic Compute and Serverless Compute clusters across multiple regions starting at 17:20 UTC on April 27, 2026. Customers encountered cluster start failures, unresponsive existing clusters, and inability to connect notebooks, jobs, and SQL workloads to their clusters. The root cause was identified and remediation efforts were underway as of the last update.
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.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Components affected
AWS Databricks Compute ServiceTrusted by 1,000+ teams
Never miss outages in third-party dependencies
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
Latest Updates ( sorted recent to last )
3 days ago - at 04/27/2026 05:37PM
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.
3 days ago - at 04/27/2026 06:12PM
Impact Summary
Starting at 27 April 2026 17:20 UTC, Classic Compute clusters and Serverless Compute in multiple regions may fail to start or become unresponsive.
Symptoms
Customers may observe:
- Cluster driver becoming unreachable or unresponsive
- Cluster start operations failing or timing out
- Running clusters or serverless workloads becoming unavailable
Recommendations
No customer action is required at this time.
Current Status
We are actively investigating reports of Classic Compute and Serverless Compute unavailability across multiple regions.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
3 days ago - at 04/27/2026 06:32PM
Impact Summary
Starting at 27 April 2026 17:20 UTC, Classic Compute and Serverless Compute clusters across multiple regions may fail to start or become unresponsive.
Symptoms
Customers may observe:
- Cluster start operations failing or remaining in a pending state
- Existing clusters becoming unresponsive or unreachable
- Notebooks, jobs, and SQL workloads unable to connect to their cluster
Recommendations
No customer action is required at this time.
Current Status
We have identified the root cause of this issue and are actively working on remediation.
Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.
Latest AWS Databricks outages
ES-1873238 - 8 days ago
ES-1868544 - 9 days ago
ES-1864534 - 11 days ago
ES-1862841 - 12 days ago
ES-1856982 - 14 days ago
Never miss outages in third-party dependencies
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
