- 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-31 13: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 19:33 UTC Scheduled - A maintenance event is scheduled to occur between 7:00 AM UTC and 1:00 PM UTC on Monday, August 31st, 2026. During this time window, running Lakebase endpoints will be restarted; clients may observe a downtime of a few seconds to reconnect; workloads may experience temporary performance degradation for approximately 10 minutes. Impacted services include: - Database connectivity may get interrupted. - Database transactions may be interrupted. We apologize for any inconvenience this may have caused. August 31, 2026 07:00 UTC Active - A maintenance event is scheduled to occur between 7:00 AM UTC and 1:00 PM UTC on Monday, August 31st, 2026. During this time window, running Lakebase endpoints will be restarted; clients may observe a downtime of a few seconds to reconnect; workloads may experience temporary performance degradation for approximately 10 minutes. Impacted services include: - Database connectivity may get interrupted. - Database transactions may be interrupted. We apologize for any inconvenience this may have caused. August 31, 2026 13: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-80cfa4f7f1
Is this Databricks maintenance still going on?
No, it ended 2026-08-31 13:00 UTC.
How long did it last?
0m, from 2026-08-31 13:00 UTC to 2026-08-31 13: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.