ES-1716456

We are actively investigating an issue affecting Databricks Serverless compute.

Further updates will be provided within the next hour, or as events warrant.

Impact Summary
Starting at 28 January 2026 15:05 UTC, Serverless and Classic Compute in AWS eu-west-1 experienced cluster creation failures and operational interruptions.

Symptoms
Affected customers may observe:
* Serverless and Classic cluster creation attempts may not complete
* Job runs may fail to start or show failed status
* Notebook operations may experience delays or timeouts

Recommendations
No customer action is required at this time.
Avoid retries or cluster recreation attempts; they may increase backlog while remediation continues.

Current Status
We have identified an infrastructure issue affecting the underlying cloud provider network in this region. Our engineering teams are coordinating with the cloud provider to restore normal service operations.

Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary
Starting at 28 January 2026 15:05 UTC, Serverless and Classic Compute in AWS eu-west-1 experienced cluster creation failures and operational interruptions.

Symptoms
Affected customers may observe:
* Serverless and Classic cluster creation attempts may not complete
* Job runs may fail to start or show failed status
* Notebook operations may experience delays or timeouts

Recommendations
No customer action is required at this time.
Avoid retries or cluster recreation attempts; they may increase backlog while remediation continues.

Current Status
We have identified an infrastructure issue affecting the underlying cloud provider network in this region. AWS is investigating the issue: https://health.aws.amazon.com/health/status

Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary
Starting at 28 January 2026 15:05 UTC, Serverless and Classic Compute in AWS eu-west-1 may fail to launch or complete job executions.

Symptoms
Affected customers may observe:
* Serverless and Classic cluster creation attempts may not complete
* Job runs may fail to start or show a failed status
* Notebook operations may experience delays or timeouts

Recommendations
No customer action is required at this time.
Avoid mass retries, cluster restarts, or cluster changes while remediation continues. Keep existing stable clusters running where possible. No workaround is available at this time.

Current Status
We have identified a networking infrastructure issue with the underlying cloud provider affecting this region. We are coordinating with the cloud provider and monitoring service recovery as their remediation progresses. For additional details, see the cloud provider's status page: https://health.aws.amazon.com/health/status.

Next Update
We will provide another update within 1 hour, or sooner if there is a material change in service status.