Skip to main content
Databricks

ES-2154303

Partial outage Lasted 0m · started · Databricks's page

Level
confirmed
Worst impact
Partial outage
Regions
eu
Down Index
22of 100

What to do

  • Check whether you use Databricks in eu. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

    Anything that failed between 2026-08-24 22:55 UTC and 2026-08-24 22:55 UTC may need a replay.
  • Subscribe to Databricks's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=databricks works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Databricks 1

  1. resolved

    August 24, 2026 21:12 UTC Investigating - 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. August 24, 2026 21:42 UTC Identified - 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. August 24, 2026 22:20 UTC Monitoring - 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. August 24, 2026 22:55 UTC Resolved - 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.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-c97ff41248

Is Databricks still down?

No, this incident was resolved 2026-08-24 22:55 UTC. For Databricks's live state, see https://down.guide/databricks.

How long did it last?

0m, from 2026-08-24 22:55 UTC to 2026-08-24 22:55 UTC, by the times Databricks posted.

What was affected?

Databricks named in eu.

What caused it?

Databricks hasn't published a root cause. If it does, it shows here.

Where does this come from?

Databricks's official status page, https://status.databricks.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.