ES-1903956

We are actively investigating an issue with the Databricks service.

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 07 May 2026 23:59 UTC, customers using Databricks in AWS us-east-1 may experience service unavailability.

Symptoms
Customers may observe:
- General unavailability of Databricks services, including
- Unity Catalog operations failing or not completing
- Workloads in Classic Compute (all-purpose clusters), Lakeflow Jobs, Databricks SQL, and Lakeflow Spark Declarative Pipelines experiencing failures

Recommendations
No customer action is required at this time.

Current Status
Our engineering team is actively investigating a service disruption affecting Unity Catalog and dependent Databricks features in AWS us-east-1.  We are aware of a cloud provider incident and are monitoring for impact. Refer to https://health.aws.amazon.com/health/status for more information.

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 07 May 2026 23:59 UTC, customers using Databricks in AWS us-east-1 may experience service unavailability.

Symptoms
Customers may observe:
- General unavailability of Databricks services, including
- Unity Catalog operations failing or not completing
- Workloads in Classic Compute (all-purpose clusters), Lakeflow Jobs, Databricks SQL, and Lakeflow Spark Declarative Pipelines experiencing failures

Recommendations
No customer action is required at this time.

Current Status
Our engineering team is actively investigating a service disruption affecting Unity Catalog and dependent Databricks features in AWS us-east-1. We are aware of a cloud provider incident and are monitoring for impact. Refer to https://health.aws.amazon.com/health/status for more information.

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 07 May 2026 23:59 UTC, customers using Databricks in AWS us-east-1 may experience service unavailability.

Symptoms
Customers may observe:
- General unavailability of Databricks services, including
- Unity Catalog operations failing or not completing
- Workloads in Classic Compute (all-purpose clusters), Lakeflow Jobs, Databricks SQL, and Lakeflow Spark Declarative Pipelines experiencing failures

Recommendations
No customer action is required at this time.

Current Status
Our engineering team is actively investigating a service disruption affecting Unity Catalog and dependent Databricks features in AWS us-east-1. We are aware of a cloud provider incident and are monitoring for impact. Refer to https://health.aws.amazon.com/health/status for more information.

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 07 May 2026 23:59 UTC, customers using Databricks services in AWS us-east-1 may experience degraded service or failures.

Symptoms
Customers may observe:
- General unavailability of Databricks services, including
- Unity Catalog operations failing or not completing
- Workloads in Classic Compute (all-purpose clusters), Lakeflow Jobs, Databricks SQL, and Lakeflow Spark Declarative Pipelines experiencing failures

Recommendations
Customers are advised to avoid retrying operations at high frequency while remediation is underway. The Flexible Node Types and Auto-AZ features are designed to help customers during periods of reduced capacity and zonal impacts.
- https://docs.databricks.com/aws/en/compute/flexible-node-types
- https://docs.databricks.com/aws/en/compute/pools#auto-az-with-pools

Current Status
Our engineering team has moved most services out of the impacted AZ. While many services are returning to service, customers may still see increased latency or intermittent job failures while the region continues to stabilize.

We are continuing to work with the cloud provider and monitoring for full recovery. Refer to health.aws.amazon.com/health/status for more information.

Impact Summary

Starting at 07 May 2026 23:59 UTC, customers using Databricks services in AWS us-east-1 may experience degraded service or failures.

Symptoms

Customers may observe:

* General unavailability of Databricks services
* Unity Catalog operations failing or not completing
* Workloads in Classic Compute (all-purpose clusters), Lakeflow Jobs, Databricks SQL, and Lakeflow Spark Declarative Pipelines experiencing failures

Recommendations

Customers are advised to avoid retrying operations at high frequency while remediation is underway. The Flexible Node Types and Auto-AZ features are designed to help customers during periods of reduced capacity and zonal impacts.

* Flexible Node Types: https://docs.databricks.com/aws/en/compute/flexible-node-types
* Auto-AZ with Pools: https://docs.databricks.com/aws/en/compute/pools#auto-az-with-pools

Current Status

We have identified the cause of this incident. Our engineering team has moved most services out of the impacted availability zone. While many services are returning to normal operation, customers may still experience increased latency or intermittent failures while the region continues to stabilize.

We are continuing to work with the cloud provider and monitoring for full recovery. Refer to health.aws.amazon.com/health/status for more information.

Next Update

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

Impact Summary
Starting at 07 May 2026 23:59 UTC, customers using Databricks services in AWS us-east-1 may experience degraded service or failures.

Symptoms
Customers may observe:

General unavailability of Databricks services
Unity Catalog operations failing or not completing
Workloads in Classic Compute (all-purpose clusters), Lakeflow Jobs, Databricks SQL, and Lakeflow Spark Declarative Pipelines experiencing failures


Recommendations
Customers are advised to avoid retrying operations at high frequency while remediation is underway. The Flexible Node Types and Auto-AZ features are designed to help customers during periods of reduced capacity and zonal impacts.

Flexible Node Types: https://docs.databricks.com/aws/en/compute/flexible-node-types
Auto-AZ with Pools: https://docs.databricks.com/aws/en/compute/pools#auto-az-with-pools


Current Status
Our engineering team has moved most services out of the impacted availability zone. While many services are returning to normal operation, customers may still experience increased latency or intermittent failures while the region continues to stabilize.
We are continuing to work with the cloud provider and monitoring for full recovery. Refer to health.aws.amazon.com/health/status for more information.

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

Impact Summary
From 07 May 2026 23:59 UTC to 08 May 2026 06:00 UTC, customers using Databricks services in AWS us-east-1 experienced degraded service or failures. Service has been restored.

Symptoms Customers experienced:

* General unavailability of Databricks services
* Unity Catalog operations failing or not completing
* Workloads in Classic Compute (all-purpose clusters), Lakeflow Jobs, Databricks SQL, and Lakeflow Spark Declarative Pipelines experiencing failures
* Mosaic AI Vector Search queries failing or experiencing degraded availability
* Intermittent issues with authentication and login

Recommendations
No customer action is required at this time.

Current Status
Service has been restored as of 08 May 2026 06:00 UTC. Our engineering team is actively monitoring to confirm full stabilization across all affected services.

For information about the underlying cloud provider event, refer to health.aws.amazon.com/health/status.

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

Impact Summary
Starting 07 May 2026 23:59 UTC  customers using Databricks services in AWS us-east-1 experienced degraded service or failures. As of 08 May 2026 06:00 UTC, nearly all Databricks services have been moved out of the faulty AZ, however some intermittent symptoms may be experienced while AWS works to restore the remaining AZ capacity.

Symptoms Customers experienced:

* General unavailability of Databricks services
* Unity Catalog operations failing or not completing
* Workloads in Classic Compute (all-purpose clusters), Lakeflow Jobs, Databricks SQL, and Lakeflow Spark Declarative Pipelines experiencing failures
* Mosaic AI Vector Search queries failing or experiencing degraded availability
* Intermittent issues with authentication and login

Recommendations
No customer action is required at this time.

Current Status
Databricks services have been restored as of 08 May 2026 06:00 UTC.
Some additional degradation was observed from 17:03 UTC to 17:24 UTC.
Our engineering team is actively monitoring and working with AWS to confirm full stabilization across all affected services.
For information about the underlying cloud provider event, refer to health.aws.amazon.com/health/status.

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

Impact Summary
Starting 07 May 2026 23:59 UTC customers using Databricks services in AWS us-east-1 experienced degraded service or failures. As of 08 May 2026 06:00 UTC, nearly all Databricks services have been moved out of the faulty AZ, however some intermittent symptoms may be experienced while AWS works to restore the remaining AZ capacity.

Symptoms Customers experienced:

* General unavailability of Databricks services
* Unity Catalog operations failing or not completing
* Workloads in Classic Compute (all-purpose clusters), Lakeflow Jobs, Databricks SQL, and Lakeflow Spark Declarative Pipelines experiencing failures
* Mosaic AI Vector Search queries failing or experiencing degraded availability
* Intermittent issues with authentication and login

Recommendations
No customer action is required at this time.

Current Status
Databricks services have been restored as of 08 May 2026 06:00 UTC.
Some additional degradation was observed from 17:03 UTC to 17:24 UTC.
Our engineering team is actively monitoring and working with AWS to confirm full stabilization across all affected services.
For information about the underlying cloud provider event, refer to health.aws.amazon.com/health/status.

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

Impact Summary
Starting 07 May 2026 23:59 UTC customers using Databricks services in AWS us-east-1 experienced degraded service or failures. As of 08 May 2026 06:00 UTC, nearly all Databricks services have been moved out of the faulty AZ, however some intermittent symptoms may be experienced while AWS works to restore the remaining AZ capacity.

Symptoms Customers experienced:

* General unavailability of Databricks services
* Unity Catalog operations failing or not completing
* Workloads in Classic Compute (all-purpose clusters), Lakeflow Jobs, Databricks SQL, and Lakeflow Spark Declarative Pipelines experiencing failures
* Mosaic AI Vector Search queries failing or experiencing degraded availability
* Intermittent issues with authentication and login

Recommendations
No customer action is required at this time.

Current Status
Databricks services have been restored as of 08 May 2026 06:00 UTC.
Some additional degradation was observed from 17:03 UTC to 17:24 UTC.
Our engineering team is actively monitoring and working with AWS to confirm full stabilization across all affected services.
For information about the underlying cloud provider event, refer to health.aws.amazon.com/health/status.

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

Impact Summary
From 07 May 2026 23:59 UTC to 08 May 2026 17:24 UTC, and again from 23:36 UTC to 23:55 UTC, customers using Databricks workspaces in the AWS us-east-1 region experienced intermittent errors and failures across catalog, compute, and job execution features.

Symptoms
Customers experienced:
* General unavailability of Databricks services
* Unity Catalog operations failing or not completing
* Workloads in Classic Compute (all-purpose clusters), Lakeflow Jobs, Databricks SQL, and Lakeflow Spark Declarative Pipelines experiencing failures
* Mosaic AI Vector Search queries failing or experiencing degraded availability
* Intermittent issues with authentication and login

Current Status
Databricks services have been restored as of 08 May 2026 06:00 UTC.
Some additional degradation was observed from 17:03 UTC to 17:24 UTC and from 23:36 UTC to 23:55 UTC.
Our engineering team is actively monitoring and working with AWS to confirm full stabilization across all affected services.
For information about the underlying cloud provider event, refer to health.aws.amazon.com/health/status.

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