Databricks AWS experienced a minor incident on July 6, 2026 affecting Compute and Unity Catalog (US East 1), lasting 1h 33m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jul 06, 2026, 02:51 PM UTC
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.
- identified Jul 06, 2026, 02:51 PM UTC
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.
- monitoring Jul 06, 2026, 03:36 PM UTC
Between 09:55 UTC and 13:54 UTC on July 6, 2026, a subset of customers using Databricks may have experienced 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 have experienced degraded availability or errors with Classic Compute, Jobs, page loads. Symptoms • Clusters unexpectedly terminated shortly after launch • New cluster launches failed to start • Job runs failed or terminated unexpectedly • Degraded UI page loads Current Status The issue has been mitigated and services have been restored. 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.
- monitoring Jul 06, 2026, 03:36 PM UTC
Between 09:55 UTC and 13:54 UTC on July 6, 2026, a subset of customers using Databricks may have experienced 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 have experienced degraded availability or errors with Classic Compute, Jobs, page loads. Symptoms • Clusters unexpectedly terminated shortly after launch • New cluster launches failed to start • Job runs failed or terminated unexpectedly • Degraded UI page loads Current Status The issue has been mitigated and services have been restored. 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.
- resolved Jul 06, 2026, 04:25 PM UTC
Between 09:55 UTC and 13:54 UTC on July 6, 2026, a subset of customers using Databricks may have experienced 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 have experienced degraded availability or errors with Classic Compute, Jobs, page loads. Symptoms • Clusters unexpectedly terminated shortly after launch • New cluster launches failed to start • Job runs failed or terminated unexpectedly • Degraded UI page loads Current Status This incident has been resolved. We apologize for any inconvenience this may have caused. 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