Live  /  Providers  /  Databricks

Databricks

databricks.comNo open incidents

Independent assessment — SquidGrid is not affiliated with Databricks. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

SaaS & business software · SquidGrid tracks Databricks’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what Databricks is reporting

Current & recent incidents

Resolved

ES-2359687

2026-11-13 20:13 UTC

Resolved

ES-2342108

2026-11-06 23:21 UTC

Resolved

ES-2292938

2026-10-16 15:27 UTC

Resolved

ES-2281237

2026-10-12 12:57 UTC

Resolved

ES-2263963

2026-10-05 23:59 UTC

Resolved

ES-2248197

2026-09-29 17:10 UTC

Resolved

ES-2231583

2026-09-21 23:22 UTC

Incident titles and states as published by the provider. Times in UTC.

Track record

SquidGrid has archived 7 incidents from Databricks’s own status page since 2026-09-21.

Computed by SquidGrid from the incidents Databricks published. Their own page shows only recent history; this archive keeps every one.

Independent path health

A status page tells you what Databricks has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

Databricks runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of Databricks is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with Databricks.