Databricks Outage History

15 incidents recorded over the last 365 days, 11 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Databricks status99.47% uptime history

Every Recorded Databricks Incident

Databricks incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 31, 2026Regular Planned MaintenanceScheduled Maintenance6h 0mScheduled
Aug 23, 2026An emergency maintenance event.Scheduled Maintenance1h 0mScheduled
Aug 7, 2026Emergency Maintenance Extended.Scheduled Maintenance1h 0mScheduled
Aug 7, 2026Emergency MaintenanceScheduled Maintenance4h 0mScheduled
Aug 6, 2026ES-2114298We are actively investigating an issue affecting Databricks compute. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.3h 0mResolved
Jul 30, 2026ES-2097037Between 00:34 UTC and 01:21 UTC on July 30, 2026, a subset of customers using Databricks may have experienced failures or delayed startup of Serverless Compute workloads, along with degraded availability affecting Jobs…24 minResolved
Jul 10, 2026ES-2052473Between 22:29 UTC and 23:00 UTC on July 10, 2026, a subset of customers using Databricks may have experienced failures or delays when starting new compute clusters or running jobs. Affected services included Classic…28 minResolved
Jul 6, 2026ES-2041234Starting at approximately 09:55 UTC on July 6, 2026, customers using Databricks may be experiencing failures or unexpected terminations when launching or running compute clusters, as well as failures with job runs on…1h 25mResolved
Jun 29, 2026ES-2026645We 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.1h 30mResolved
Jun 8, 2026ES-1968101We 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.2h 30mResolved
May 31, 2026ES-1948471We 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.6h 9mResolved
May 26, 2026ES-1940071We 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.3h 7mResolved
May 19, 2026ES-1924741We are actively investigating an issue affecting Databricks compute. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.3h 45mResolved
May 14, 2026ES-1917659We 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.2h 52mResolved
May 8, 2026ES-1903956We 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.25h 58mResolved

How to Read This Databricks Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Databricks acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Databricks outage in this window ran 1d 1h, against a mean recovery of 4h 13m. If you depend on Databricks in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.