Skip to content

Outage tracker / Databricks / In the US

Is Databricks down in the US?

Vendor reports no incidentWhat Databricks reports

Databricks reports no incident on its status page.

As of the last successful poll, 2026-11-05 16:38 UTC.

Databricks's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingin the US, measured from Ashburn and San Jose

All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Databricks at Nov 5, 2026, 4:48 PM UTC.

Over the last 24 hours we completed 254 checks from Ashburn and San Jose and 254 answered cleanly, 100.00% availability.

Of the 2 other regions we check Databricks from, all 2 read checks passing right now.

Email me when Databricks reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Databricks's own statement from its status page, with our regional reading beside it.

What our Ashburn and San Jose probes measured

AshburnChecks passing142 checks in 24h, 100.00%
San JoseChecks passing112 checks in 24h, 100.00%

Last checked Nov 5, 2026, 4:48 PM UTC.

Databricks from Ashburn and San Jose over the last 30 days

Over the last 30 days, Databricks answered our San Jose probe in 1,116 ms on average, and 1 check in 20 took longer than 1,802 ms.

Over the last 30 days, Databricks answered our Ashburn probe in 1,438 ms on average, and 1 check in 20 took longer than 1,811 ms.

Ranked by average response time across the 4 cities we check Databricks from, San Jose 1st, Ashburn 3rd; San Jose was fastest at 1,116 ms and Tokyo slowest at 1,940 ms.

From Ashburn and San Jose we ran 785 checks of Databricks in 4 days, and 784 answered cleanly: 99.87% availability.

1 of the 4 days had at least one failed check. The weakest was Nov 3 (UTC), at 99.59% across 248 checks.

In Ashburn local time (EST), Databricks was slowest around 12 AM, at 1,681 ms on average over the last 14 days, and quickest around 9 AM, at 1,168 ms.

Day (UTC)ChecksAvailabilityAverage response
Thu, Nov 5177100.00%1,375 ms
Wed, Nov 4254100.00%1,245 ms
Tue, Nov 324899.59%1,266 ms
Mon, Nov 2106100.00%1,369 ms

Databricks outages measured from the US

Our Ashburn and San Jose probes measured no confirmed Databricks outage in the last 90 days.

How the other regions read right now

Of the 2 other regions we check Databricks from, all 2 read checks passing right now.

Probe cityRight nowLast 24h
FrankfurtChecks passing100.00% of 101 checks
TokyoChecks passing100.00% of 60 checks

Other countries we check Databricks from

How we measured this

The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Databricks's public endpoints. They are not user reports, and they are not Databricks's own status page.

See Databricks's full check readings, the 90-day history by region, or the outage tracker methodology.

The US readings here are taken from that country and show the time of the last one, but Databricks has not yet accumulated enough continuous history for us to publish this page to search engines.

Check your own site from Ashburn

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter