We started checking Databricks on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Databricks reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Databricks's own status page declared. Below it, any public chatter we saw about Databricks and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Databricks's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Databricks in the last 24 hours, which is not evidence that nothing is wrong.
Databricks's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Databricks's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Databricks next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
447
US-West
99.71%
348
Europe
100.00%
318
Asia-Pacific
100.00%
193
Their declared record
Databricks's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
ES-2292938Minor incident
Oct 16, 2026, 3:27 PM UTC to Oct 16, 2026, 4:36 PM UTC (1h 9m)resolved
their latest update (Oct 16, 2026, 4:36 PM UTC): Impact Summary Between 15:07 UTC and 15:49 UTC on October 16, 2026, customers using Databricks may have experienced degraded availability with Serverless Compute, Databricks Apps, Databricks SQL, Jobs, Notebooks, and Genie One. Affected customers may have encountered errors, unav…
ES-2281237Minor incident
Oct 12, 2026, 12:57 PM UTC to Oct 12, 2026, 5:42 PM UTC (4h 45m)resolved
their latest update (Oct 12, 2026, 5:42 PM UTC): Impact Summary Between 12:30 UTC and 16:30 UTC on October 12, 2026, customers using Databricks on AWS in US West 2 may have experienced degraded availability with Serverless Compute, AI/BI, Databricks SQL, Declarative Pipelines, Jobs, and Genie. Affected customers may have encoun…
ES-2263963Minor incident
Oct 5, 2026, 11:59 PM UTC to Oct 6, 2026, 2:32 AM UTC (2h 33m)resolved
their latest update (Oct 6, 2026, 2:32 AM UTC): Impact Summary Between 23:10 UTC and 23:31 UTC October 05, 2026, customers using Databricks on AWS in US East 1 may have experienced degraded performance with Databricks SQL and AI/BI. Affected customers may have encountered SQL query failures or timeouts, and AI/BI dashboards th…
ES-2248197Minor incident
Sep 29, 2026, 5:10 PM UTC to Sep 29, 2026, 6:54 PM UTC (1h 44m)resolved
their latest update (Sep 29, 2026, 6:54 PM UTC): Impact Summary Between 15:15 UTC and 17:40 UTC on September 29, 2026, a subset of customers using Databricks may have experienced degraded performance with Declarative Pipelines. Affected customers may have encountered pipeline run failures or pipeline runs that did not progress …
ES-2231583Minor incident
Sep 21, 2026, 11:22 PM UTC to Sep 22, 2026, 12:51 AM UTC (1h 29m)resolved
their latest update (Sep 22, 2026, 12:51 AM UTC): Impact Summary Between 22:57 UTC and 23:45 UTC on September 21, 2026, customers using Databricks on AWS in US East 1 may have experienced complete unavailability of Classic Compute, Serverless Compute, Declarative Pipelines, and Jobs. Affected customers may have been unable to la…
Regular Planned MaintenanceMaintenance
Sep 2, 2026, 1:59 PM UTC to Sep 19, 2026, 2:00 AM UTC (16d 12h)completed
their latest update (Sep 19, 2026, 2:00 AM UTC): Scheduled maintenance is complete.
Regular Planned MaintenanceMaintenance
Sep 2, 2026, 6:46 AM UTC to Sep 2, 2026, 1:54 PM UTC (7h 8m)completed
their latest update (Sep 2, 2026, 1:54 PM UTC): The maintenance scheduled on Saturday, September 19, 2026, from 01:00 UTC to 02:00 UTC has been canceled. We do apologize for the inconvenience, you will be notified if a new maintenance window is required.
ES-2154303Minor incident
Aug 24, 2026, 9:12 PM UTC to Aug 24, 2026, 10:55 PM UTC (1h 43m)resolved
their latest update (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 wor…
Regular Planned MaintenanceMaintenance
Aug 21, 2026, 7:33 PM UTC to Aug 31, 2026, 1:00 PM UTC (9d 17h)completed
their latest update (Aug 31, 2026, 1:00 PM UTC): Scheduled maintenance is complete.
An emergency maintenance event.Maintenance
Aug 21, 2026, 12:09 AM UTC to Aug 23, 2026, 6:00 AM UTC (2d 5h)completed
their latest update (Aug 23, 2026, 6:00 AM UTC): Scheduled maintenance is complete.
These entries are Databricks's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Databricks's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.