On July 6, 2026, starting at approximately 09:55 UTC, AWS Databricks experienced a ~44-minute incident affecting Classic Compute and Jobs, causing cluster launch failures, unexpected cluster terminations, job run failures, and degraded UI page loads. The root cause was identified as an underlying AWS cloud provider issue impacting EC2 in us-east-1. Services showed signs of recovery with no customer action required.
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.
Starting at approximately 09:55 UTC on July 6, 2026, customers using Databricks may be experiencing failures or unexpected terminations when launching or running compute clusters, as well as failures with job runs on affected services. A subset of customers may be experiencing degraded availability or errors with Classic Compute, Jobs, page loads.
Symptoms
• Clusters unexpectedly terminating shortly after launch
• New cluster launches failing to start
• Job runs failing or terminating unexpectedly
• Degraded UI page loads
Recommendations
No customer action is required at this time.
Current Status
The root cause has been identified as a cloud provider issue impacting Classic Compute and Jobs, and the team is monitoring as affected services show signs of recovery.
For more details, refer to https://health.aws.amazon.com/health/status?eventID=arn:aws:health:us-east-1::event/EC2/AWS_EC2_OPERATIONAL_ISSUE/AWS_EC2_OPERATIONAL_ISSUE_5269E_F1B7AF74706
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