- Level
- confirmed
- Worst impact
- Maintenance
What to do
Check whether your product depends on Databricks. 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.Check that everything you run on Databricks came back after the window closed 2026-08-23 06:00 UTC.
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
- resolved
August 21, 2026 00:09 UTC Scheduled - An emergency maintenance event is scheduled to occur between 05:00 UTC and 06:00 UTC on August 23, 2026. Actual service interruption for individual regions during this window is expected to take approximately 10 minutes. You may encounter the following impact during this maintenance: - Workspace login/authentication requests may fail or time out. - Workspace UI/API requests may fail; this may impact running jobs, cluster creation, notebooks, and queries. - Unity Catalog (UC) requests may fail or time out. August 23, 2026 05:00 UTC Active - An emergency maintenance event is scheduled to occur between 05:00 UTC and 06:00 UTC on August 23, 2026. Actual service interruption for individual regions during this window is expected to take approximately 10 minutes. You may encounter the following impact during this maintenance: - Workspace login/authentication requests may fail or time out. - Workspace UI/API requests may fail; this may impact running jobs, cluster creation, notebooks, and queries. - Unity Catalog (UC) requests may fail or time out. August 23, 2026 06:00 UTC Completed - Scheduled maintenance is complete.
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-978e2e9eef
Is this Databricks maintenance still going on?
No, it ended 2026-08-23 06:00 UTC.
How long did it last?
0m, from 2026-08-23 06:00 UTC to 2026-08-23 06:00 UTC, by the times Databricks posted.
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.