Changes / Databricks / ES-2154303
Databricks: Major incident: ES-2154303
Summary
Summary pending. The diff below shows exactly what changed.
Major incidentLabel: outage (model (Jev), 64%)Changed Detected Source: status.databricks.com (opens in new tab)
Incident page: full timeline of updates →
What changed
Before: not present
After: ES-2154303
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-08-24 21:12 UTC
Before: not present
After: 2026-08-24 22:55 UTC
Before: not present
After: Lakebase
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: ES-2154303 (this change) | Major incident |
All Databricks changes → · Databricks profile · Markdown · JSON