Databricks logo

Is Databricks Down?

DatabaseLive status, outages, and incident history

No. Databricks is up right now.

Every monitored Databricks system is operational as of October 11, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · 60s while moving

Know the moment Databricks breaks

Databricks is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official Databricks status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

Databricks Component Status

The main Databricks systems on this page. All 177 are operational right now.

177operational
Agent Bricks [AP Northeast 1]
Operational
Agent Bricks [AP Northeast 2]
Operational
Agent Bricks [AP South 1]
Operational

174 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Agent Bricks [AP Southeast 1], Agent Bricks [AP Southeast 2], Agent Bricks [CA Central 1], Agent Bricks [EU Central 1], Agent Bricks [EU West 1], Agent Bricks [EU West 2], Agent Bricks [SA East 1], Agent Bricks [US East 1], Agent Bricks [US East 2], Agent Bricks [US West 2], AI/BI [AP Northeast 1], AI/BI [AP Northeast 2], and 162 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Databricks Outages & Incidents

Incident history from the official Databricks status page, including resolution updates.

ES-2263963Resolved Oct 5, 2026 · 2h 32mResolved

Impact Summary Between 23:10 UTC and 23:31 UTC on 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 statement execution failures, query timeouts, or dashboards that failed to load or refresh during this window. Symptoms • SQL queries failing or timing out • Dashboards failing to load, refresh, or showing empty or partial results • BI tool and SQL API connections timing out Current Status The issue has been mitigated, and service is operational. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

ES-2248197Resolved Sep 29, 2026 · 1h 43mResolved

Impact Summary Starting at 15:15 UTC September 29, 2026, customers using Azure Databricks in West US 3 may experience failures or degraded availability with Declarative Pipelines. Affected customers may encounter pipeline runs that fail, do not start, or do not progress. Symptoms • Pipeline runs failing with control plane errors • Pipeline runs not starting or not progressing • Missing or delayed pipeline status information Recommendations No customer action is required at this time. Current Status The issue is under active investigation. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status. --- [2026-09-29T17:43:52.327Z] (300) Impact Summary Starting at 15:15 UTC September 29, 2026, customers using Databricks may experience failures or degraded performance with Declarative Pipelines. Affected customers may find that pipeline runs fail intermittently or do not complete as expected. Symptoms • Pipeline runs failing with CONTROL_PLANE_FAILURE errors • Pipeline runs not progressing or terminating unexpectedly • Missing or delayed pipeline status information Recommendations No customer action is required at this time. Current Status The issue has been identified and mitigation efforts are in progress. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status. --- [2026-09-29T17:55:09.462Z] (100) Impact Summary Between 15:15 UTC and 17:40 UTC on September 29, 2026, a subset of customers using Databricks may have experienced degraded availability with Declarative Pipelines. Affected customers may have encountered pipeline run failures or pipelines that did not progress as expected during this window. Symptoms • Pipeline runs failing with control plane errors • Pipeline runs not starting or not progressing • Delayed or missing pipeline status information Current Status The issue has been mitigated and service is operational. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

ES-2231583Resolved Sep 21, 2026 · 1h 28mResolved

We 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. --- [2026-09-21T23:25:54.169Z] (400) Impact Summary Starting at 22:57 UTC September 21, 2026, customers using Databricks on AWS in US East 1 may experience degraded availability with Classic Compute, Declarative Pipelines, and Jobs. Affected customers may encounter cluster launch failures, operation timeouts, and jobs or pipeline runs that fail to start or complete. Symptoms • Cluster launch failures or clusters stuck in Pending or Starting • Notebook attach failures and job run terminations during cluster startup • Jobs and pipeline runs remaining pending, failing immediately, or not progressing Recommendations No customer action is required at this time. Current Status The issue is under active investigation, with triage ongoing in coordination with the cloud provider. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status. --- [2026-09-21T23:48:57.727Z] (500) Impact Summary Starting at 22:57 UTC September 21, 2026, customers using Databricks on AWS in US East 1 may be experiencing a complete unavailability of Classic Compute, Serverless Compute, Declarative Pipelines, and Jobs. Affected customers may encounter compute launch and termination failures, cluster allocation timeouts, and jobs or pipeline runs that fail to start or complete. Symptoms • Cluster launch failures; clusters stuck in Pending or Starting, and notebook attach failures • Serverless workloads failing to start, allocation timeouts, or unexpected workload termination • Jobs and pipeline runs remaining pending, failing immediately, or not progressing Recommendations No customer action is required at this time. Current Status The issue has been identified, and mitigation efforts are in progress in coordination with the cloud provider. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status. --- [2026-09-21T23:58:20.273Z] (100) 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 encountered cluster launch failures, allocation timeouts, and failed or terminated workloads during this window. Symptoms • Classic compute cluster launch failures, with clusters stuck in Pending or Starting and notebook attach failures • Serverless workloads failing to start, allocation timeouts, or unexpected workload termination • Jobs and pipeline runs remaining pending, failing immediately, or not progressing Current Status The issue has been mitigated, and service is operational. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

Databricks Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Databricks incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Jul 13100.00% average · 5 days with incidentsOct 11

Going further back: Databricks uptime by month and every recorded Databricks outage.

Live Databricks Outage Reports

Problems reported by engineers using Databricks. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Databricks problems reported yet.

Something wrong with Databricks on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Databricks

Databricks is the Data and AI company behind the Lakehouse architecture, providing unified analytics, data engineering, machine learning, and collaborative notebooks powered by Apache Spark. Databricks outages interrupt ETL pipelines, ML model training, and data science workflows. Track Databricks status and outages here.

Over the past 30 days, PulsAPI has measured Databricks uptime at 100.00%. Response times, incident history, and SLA tracking for Databricks are available on the PulsAPI dashboard.

Databricks Status FAQ

Is Databricks down right now?

The verdict at the top of this page comes from the latest poll of the official Databricks status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if Databricks is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Databricks recovers.

How do I check Databricks uptime history?

PulsAPI tracks Databricks uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Databricks changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Databricks outages?

PulsAPI reads the official Databricks status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual Databricks components?

Yes. PulsAPI monitors 177 individual Databricks components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Databricks goes down?

Yes. Create a free account and subscribe to Databricks: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Databricks to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Databricks problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Databricks?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Databricks plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Databricks with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services