Databricks AWS experienced a minor incident on August 24, 2026 affecting Lakebase and Unity Catalog (EU Central 1), lasting 1h 42m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 24, 2026, 09:12 PM UTC
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.
- investigating Aug 24, 2026, 09:12 PM UTC
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.
- identified Aug 24, 2026, 09:42 PM UTC
Starting at 20:22 UTC on August 24, 2026, customers using Databricks on AWS in EU Central 1 may experience degraded availability with Lakebase. Affected customers may be unable to create, access, or operate Lakebase databases and related workloads. Symptoms: • Database creation failures and failed connection attempts • Queries timing out or returning errors, and admin operations not completing • Applications backed by Lakebase returning errors Recommendations: No customer action is required at this time. Current Status: The issue has been identified and mitigation efforts are in progress. Further updates will be provided as mitigation advances. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.
- identified Aug 24, 2026, 09:42 PM UTC
Starting at 20:22 UTC on August 24, 2026, customers using Databricks on AWS in EU Central 1 may experience degraded availability with Lakebase. Affected customers may be unable to create, access, or operate Lakebase databases and related workloads. Symptoms: • Database creation failures and failed connection attempts • Queries timing out or returning errors, and admin operations not completing • Applications backed by Lakebase returning errors Recommendations: No customer action is required at this time. Current Status: The issue has been identified and mitigation efforts are in progress. Further updates will be provided as mitigation advances. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.
- monitoring Aug 24, 2026, 10:20 PM UTC
Impact Summary: Between 20:22 UTC and 22:08 UTC on August 24, 2026, customers using Databricks on AWS in EU Central 1 may have experienced degraded availability with Lakebase. Affected customers may have been unable to create, access, or operate Lakebase databases and related workloads during this window. Symptoms: • Failures when creating or accessing Lakebase databases • Connection failures, query timeouts, or errors on Lakebase-backed applications • Administrative operations not completing or remaining in progress Current Status: The issue has been mitigated and service is operational. Monitoring remains in place to confirm continued stability. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.
- monitoring Aug 24, 2026, 10:20 PM UTC
Impact Summary: Between 20:22 UTC and 22:08 UTC on August 24, 2026, customers using Databricks on AWS in EU Central 1 may have experienced degraded availability with Lakebase. Affected customers may have been unable to create, access, or operate Lakebase databases and related workloads during this window. Symptoms: • Failures when creating or accessing Lakebase databases • Connection failures, query timeouts, or errors on Lakebase-backed applications • Administrative operations not completing or remaining in progress Current Status: The issue has been mitigated and service is operational. Monitoring remains in place to confirm continued stability. Next Update: We will provide another update within 1 hour, or sooner if there is a material change in service status.
- resolved Aug 24, 2026, 10:55 PM UTC
Impact Summary: Between 20:22 UTC and 22:08 UTC on August 24, 2026, customers using Databricks on AWS in EU Central 1 may have experienced degraded availability with Lakebase. Affected customers may have been unable to create, access, or operate Lakebase databases and related workloads during this window. Symptoms: • Database creation and administrative operations failing to complete • Connection failures or queries timing out against Lakebase databases • Applications backed by Lakebase returning errors Current Status: The issue has been resolved, and all affected services have been restored. Next Update: This is the final update 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