Struck in red is what Databricks removed; blue is what they added. Muted text is unchanged context.
BeforeAfter
ChangedStatus#1
Before: monitoring
After: resolved
AddedResolved time#2
Before: not present
After: 2026-11-07 02:10 UTC
AddedUpdateresolved#3
Before: not present
After: Impact Summary From 22:42 UTC on November 06, 2026 to 00:43 UTC on November 07, 2026, Classic Compute, Serverless Compute, Databricks SQL, and Lakeflow Jobs were unavailable for customers using Databricks on AWS in the us-west-2 region. Affected customers may have encountered cluster launch failures, delays starting serverless workloads and SQL warehouses, or failed job runs. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Serverless workloads and SQL warehouses failing to start or stuck in Starting • Job runs and SQL queries failing or terminating unexpectedly Current Status This incident has been resolved, and normal operation of all affected services has been restored. We apologize for any inconvenience this may have caused. If you require further details about this incident, please submit a support ticket or contact help@databricks.com. This incident was related to a cloud provider issue. Additional information is available on the cloud provider's status page: https://health.aws.com/health/status
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.