Is Databricks AWS down?

Between 00:34 UTC and 01:21 UTC on July 30, 2026, a subset of customers using Databricks may have experienced failures or delayed startup of Serverless Compute workloads, along with degraded availability affecting Jobs and Declarative Pipelines. The disruption has since been mitigated and normal availability was restored. Symptoms • Serverless clusters failed to launch, returning cluster-matching errors • Jobs and Declarative Pipelines experienced failures or delays tied to compute availability • Databricks SQL availability was degraded during the incident window. Current Status The issue has been mitigated and services have been restored. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 00:34 UTC and 01:21 UTC on July 30, 2026, a subset of customers using Databricks may have experienced failures or delayed startup of Serverless Compute workloads, along with degraded availability affecting Jobs and Declarative Pipelines. The disruption has since been mitigated and normal availability was restored. Symptoms • Serverless clusters failed to launch, returning cluster-matching errors • Jobs and Declarative Pipelines experienced failures or delays tied to compute availability Current Status The issue has been mitigated and services have been restored. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 00:34 UTC and 01:21 UTC on July 30, 2026, a subset of customers using Databricks may have experienced failures or delayed startup of Serverless Compute workloads, along with degraded availability affecting Databricks SQL, Jobs, and Declarative Pipelines. Normal availability was restored by the end of the impact window. Symptoms • Serverless compute clusters failed to launch, returning cluster-matching errors. • Jobs and Declarative Pipelines experienced failures or delays tied to compute availability. • Databricks SQL availability was degraded during the incident window. 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

Between 22:29 UTC and 23:00 UTC on July 10, 2026, a subset of customers using Databricks may have experienced failures or delays when starting new compute clusters or running jobs. Affected services included Classic Compute and Jobs, with customers encountering errors related to cluster startup or configuration, and some workspace console pages failing to load. The issue has since been mitigated and normal service has been restored. Symptoms • Clusters failed to start or experienced significant startup delays • Jobs failed to launch or were delayed • Errors related to cluster configuration or startup, and some workspace console pages failed to load Current Status The issue has been mitigated and services have been restored. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 22:29 UTC and 23:00 UTC on July 10, 2026, a subset of customers using Databricks may have experienced failures or delays when starting new compute clusters or running jobs. Affected services included Classic Compute and Jobs, with customers encountering errors related to cluster startup or configuration, and some workspace console pages failing to load. The issue has since been mitigated and normal service has been restored. Symptoms • Clusters failed to start or experienced significant startup delays • Jobs failed to launch or were delayed • Errors related to cluster configuration or startup, and some workspace console pages failed to load Current Status The issue has been mitigated and services have been restored. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Between 22:29 UTC and 23:00 UTC on July 10, 2026, a subset of customers using Databricks may have experienced failures or delays when starting new compute clusters or running jobs. Affected services included Classic Compute and Jobs, with customers encountering errors related to cluster startup or configuration, and some workspace console pages failing to load. The issue was resolved and normal service was restored by the end of the impact window. Symptoms • Clusters failed to start or experienced significant startup delays • Jobs failed to launch or were delayed • Some workspace console pages failed to load, showing errors related to cluster configuration or startup 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

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.

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.

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.

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.

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

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.

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 From 29 June 2026 21:22 UTC to 29 June 2026 22:19 UTC, customers using Databricks Apps in AWS US East (N. Virginia) may have been unable to create, deploy, stop, or delete apps. Service has been restored. Symptoms Customers may have experienced: - App creation, deployment, stop, and deletion operations failing or returning errors - App management operations not completing through the Workspace UI or Databricks APIs Recommendations No customer action is required. Current Status Service has been restored as of 29 June 2026 22:19 UTC. We are actively monitoring to confirm full stabilization. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary From 29 June 2026 21:22 UTC to 29 June 2026 22:19 UTC, customers using Databricks Apps in AWS US East (N. Virginia) may have been unable to create, deploy, stop, or delete apps. Service has been restored. Symptoms Customers may have experienced: - App creation, deployment, stop, and deletion operations failing or returning errors - App management operations not completing through the Workspace UI or Databricks APIs Recommendations No customer action is required. Current Status Service has been restored as of 29 June 2026 22:19 UTC. We are actively monitoring to confirm full stabilization. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Impact Summary Between 29 June 2026 21:22 UTC and 29 June 2026 22:19 UTC, customers using Databricks Apps in AWS US East (N. Virginia) may have been unable to create, deploy, stop, or delete apps. Symptoms Customers may have experienced: - App creation, deployment, stop, and deletion operations failing or returning errors - App management operations not completing through the Workspace UI or Databricks APIs Current Status This incident has been fully resolved as of 29 June 2026 22:19 UTC. We apologize for the disruption. 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

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.

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 From 2026-06-08 15:55 UTC to 2026-06-08 16:35 UTC, customers using Unity Catalog in the AWS US East (N. Virginia) region experienced failures and delays when accessing governed data, metadata, and System Tables. Service has been restored. Symptoms Customers experienced: - Errors or failures when accessing Unity Catalog-governed data and metadata - Failed or delayed requests to read or query System Tables (Audit Logs, Billable Usage, Lineage) - Intermittent failures performing catalog and governance operations Recommendations No customer action is required. Current Status Service has been restored as of 2026-06-08 16:35 UTC. We are actively monitoring to confirm full stabilization. Next Update We will provide another update within 1 hour.

Impact Summary From 2026-06-08 15:55 UTC to 2026-06-08 16:35 UTC, customers using Unity Catalog in the AWS US East (N. Virginia) region experienced failures and delays when accessing governed data, metadata, and System Tables. Service has been restored. Symptoms Customers experienced: - Errors or failures when accessing Unity Catalog-governed data and metadata - Failed or delayed requests to read or query System Tables (Audit Logs, Billable Usage, Lineage) - Intermittent failures performing catalog and governance operations Recommendations No customer action is required. Current Status Service has been restored as of 2026-06-08 16:35 UTC. We are actively monitoring to confirm full stabilization. Next Update We will provide another update within 1 hour.

Impact Summary Between 2026-06-08 15:55 UTC and 2026-06-08 16:35 UTC, customers using Unity Catalog in the AWS US East (N. Virginia) region experienced failures and delays when accessing governed data, metadata, and System Tables. Symptoms Customers experienced: - Errors or failures when accessing Unity Catalog-governed data and metadata - Failed or delayed requests to read or query System Tables (Audit Logs, Billable Usage, Lineage) - Intermittent failures performing catalog and governance operations Current Status This incident has been fully resolved as of 2026-06-08 16:35 UTC, and Unity Catalog is operating normally. We apologize for the disruption. If you require further details about this incident, please submit a support ticket or contact [email protected]. Next Update No further updates are planned for this incident. 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