Is Databricks Azure down?

Last checked 5m ago
Current status
Databricks Azure is up

No incidents right now.

Official status page: https://status.azuredatabricks.net · Polled every 5 minutes · 331 components tracked

Real-time Databricks Azure status, recent outages, and incident history — pulled directly from Databricks Azure's official status page at https://status.azuredatabricks.net every 5 minutes. Pingoru tracks 331 Databricks Azure services and has captured 2 incidents in the last 90 days (99.98% uptime). Get email, Slack, Discord, or webhook alerts the moment Databricks Azure reports a new incident — free for 5 monitors, no credit card.

Users who monitor Databricks Azure also follow these Analytics services: New Relic Grafana Fivetran Segment Amplitude Mixpanel Hudl Qualtrics Hotjar Branch View all 6,000+ providers
Databricks Azure uptime 99.98% uptime · past 90 days
Mon Wed Fri
JanFebMarApr
Less More

Recent outages & incidents

Past 7 days
  1. Resolved 1h 56m
    Started Apr 28, 2026, 05:47 PM UTC · Resolved Apr 28, 2026, 07:43 PM UTC
    LakeflowUS Gov Virginia
    3 updates · show timeline
    • investigating · Apr 28, 2026, 05:47 PM UTC

      We 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.

    • investigating · Apr 28, 2026, 06:15 PM UTC

      Impact Summary Starting at 28 April 2026 17:21 UTC, Lakeflow Jobs and Lakeflow Spark Declarative Pipelines in Azure Government may fail to start or execute. Symptoms Customers may observe: - Job runs failing to start or remaining in a pending state - Pipeline updates failing to trigger or execute - Active workloads experiencing unexpected interruptions Recommendations No customer action is required at this time. Current Status Databricks engineering is investigating the issue. We will provide further updates as the investigation progresses. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

    • monitoring · Apr 28, 2026, 06:30 PM UTC

      Impact Summary Between 28 April 2026 17:21 UTC and 28 April 2026 18:22 UTC, Lakeflow Jobs and Lakeflow Spark Declarative Pipelines in Azure Government experienced disruptions. Service has been restored. Symptoms Customers may have observed: - Job runs failing to start or remaining in a pending state - Pipeline updates failing to trigger or execute - Active workloads experiencing unexpected interruptions Recommendations No customer action is required at this time. Current Status Service was restored as of 28 April 2026 18:22 UTC. Databricks engineering is monitoring to confirm full stabilization. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

    Latest: Impact Summary Between 28 April 2026 17:21 UTC and 28 April 2026 18:22 UTC, Lakeflow Jobs and Lakeflow Spark Declarative Pipelines in Azure Government experienced disruptions. Serv…

  2. Resolved 6h 39m
    Started Apr 27, 2026, 08:03 PM UTC · Resolved Apr 28, 2026, 02:43 AM UTC
    ComputeLakeflowEast US 2
    5 updates · show timeline
    • investigating · Apr 27, 2026, 08:03 PM UTC

      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.

    • identified · Apr 27, 2026, 08:22 PM UTC

      Impact Summary Starting at 27 April 2026 18:43 UTC, Serverless Compute resources in Azure East US 2 may experience degraded performance. Symptoms Customers may observe: - Serverless workloads taking longer than expected to start or complete - Intermittent failures or timeouts on Serverless Compute jobs and queries - Slower response times for notebooks and pipelines using Serverless Compute Recommendations No customer action is required at this time. Current Status We have identified the root cause of this issue and are actively working with our cloud provider on remediation. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

    • identified · Apr 27, 2026, 09:06 PM UTC

      Impact Summary Starting at 27 April 2026 18:43 UTC, Serverless Compute in Azure East US 2 may experience failures or become unavailable. Symptoms Customers may observe: - Serverless workloads failing to start or execute - Serverless compute requests returning errors or timing out Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident and are actively working to restore service. We will continue to provide updates as remediation progresses. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

    • identified · Apr 27, 2026, 10:15 PM UTC

      Impact Summary Starting at 27 April 2026 18:43 UTC, Serverless Compute in Azure East US 2 may experience failures or become unavailable. Symptoms Customers may observe: - Serverless workloads failing to start or execute - Serverless compute requests returning errors or timing out Recommendations No customer action is required at this time. Current Status We have identified the cause of this incident and are actively working to restore service. We will continue to provide updates as remediation progresses. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

    • monitoring · Apr 27, 2026, 11:15 PM UTC

      Impact Summary Between 27 April 2026 18:43 UTC and 27 April 2026 23:02 UTC, Serverless Compute resources in Azure East US 2 experienced degraded performance. Symptoms Customers may have observed: - Serverless workloads taking longer than expected to start or complete - Intermittent failures or timeouts on Serverless Compute jobs and queries - Slower response times for Lakeflow Jobs and pipelines using Serverless Compute Recommendations No customer action is required at this time. Current Status Full mitigation was confirmed at 27 April 2026 23:02 UTC. Service has been restored and we are actively monitoring to confirm full stabilization. Next Update We will provide another update within 1 hour, or sooner if there is a material change in service status.

    Latest: Impact Summary Between 27 April 2026 18:43 UTC and 27 April 2026 23:02 UTC, Serverless Compute resources in Azure East US 2 experienced degraded performance. Symptoms Customers may…

Outage history

Past 30 days · 2 incidents
  • ES-1885183 Resolved
    Started Apr 28, 2026, 05:47 PM UTC · Resolved Apr 28, 2026, 07:43 PM UTC · 1h 56m
  • ES-1852958 Resolved
    Started Apr 27, 2026, 08:03 PM UTC · Resolved Apr 28, 2026, 02:43 AM UTC · 6h 39m

See Databricks Azure in your Pingoru dashboard

Monitor Databricks Azure alongside every other service your stack depends on — same alerts, same timeline, same calendar — all in one place.

Every status page, one dashboard

Add Databricks Azure to your Pingoru monitors and it sits next to AWS, Stripe, GitHub, and every other vendor in your stack — a single dashboard for the live status of every cloud and SaaS provider you depend on. One subscription, one inbox, every incident.

Incident timeline, this provider or all of them

Every Databricks Azure incident — when it started, when it resolved, which services were affected, how bad it was, how long it lasted — laid out in one feed you can scan in 30 seconds. Filter to just Databricks Azure or see every provider at once.

Maintenance calendar

Scheduled Databricks Azure maintenance windows land in the same calendar as every other vendor you depend on — see what's running now, what's coming up, and a calendar view. Plan around your vendors instead of being caught out by them.

Every Databricks Azure status change, one inbox

Pingoru watches Databricks Azure's official status page every 5 minutes and delivers incident, resolution, and maintenance events to your email, Slack, Discord, Teams, or webhook.

Only alert on the services you use

Databricks Azure reports on 331 services. Subscribe to the ones you actually use — everything else stays silent.

Email + Slack + Discord + Teams

Signed webhooks on every plan. Route Databricks Azure alerts wherever your team already lives — no per-integration billing, no tier-gating the channels that matter.

Maintenance, not surprises

Upcoming Databricks Azure maintenance windows appear in your maintenance calendar days in advance. Plan deploys and rollouts around them instead of finding out during an incident.

Fine-grained alert control

Per-monitor switches for opened, updated, resolved, and maintenance events. Silence the noisy Databricks Azure services without silencing the monitor entirely.

Invite your team

Premium includes 10 team seats. Everyone watching Databricks Azure from the same account, with per-user notification preferences for any monitor.

Get notified on Databricks Azure status changes

Pingoru watches Databricks Azure's official status page and sends your team instant alerts when incidents open, change severity, or resolve. Route notifications to email, Slack, Discord, or a webhook — wherever your team already lives.

Start monitoring Databricks Azure free

Monitor Databricks Azure along with everything else

Pingoru tracks 6,000+ cloud and SaaS status pages in one dashboard. Add Databricks Azure and every other provider you depend on — AWS, Stripe, GitHub, Cloudflare, OpenAI — and get a single view of the health of every service your app depends on.

Browse the full service directory

Track Databricks Azure uptime & incident history

See 90 days of Databricks Azure uptime at a glance, with every past incident linked to its component and update timeline. Export the history as CSV or JSON for SLA reports, postmortems, or vendor evaluations — data your team actually needs, not marketing numbers.

See Databricks Azure uptime history

Frequently asked questions

What is Databricks Azure's uptime?
Over the last 90 days, Databricks Azure reported 99.98% uptime on its official status page. That figure is calculated from the public incident timeline at https://status.azuredatabricks.net — each minute of degraded, partial-outage, or major-outage status counts against the total. Sign up to Pingoru free to see Databricks Azure's uptime history rolling forward in real time.
Has Databricks Azure had outages in 2026?
Yes — Databricks Azure has had 2 incidents reported on its official status page so far in 2026. The full timeline (start times, durations, components affected) is shown above on this page. Pingoru re-checks the status page every 5 minutes so the count stays current.
When was the last Databricks Azure outage?
The most recent Databricks Azure incident was "ES-1885183", which started on April 28, 2026 and was resolved on April 28, 2026. Pingoru captured this directly from https://status.azuredatabricks.net. See the full incident card above for affected components and the update timeline.
How often does Databricks Azure have outages?
Based on the last 90 days, Databricks Azure averages 0.7 reported incident per month on its official status page. Pingoru tracks each one with start time, duration, severity, and affected components — so you can see the pattern at a glance instead of digging through the vendor's archive.
Where is Databricks Azure's status page?
Databricks Azure's official status page is https://status.azuredatabricks.net. Pingoru polls it every 5 minutes and renders the same data here, alongside every other cloud or SaaS provider you depend on — so you can spot multi-vendor incidents (e.g. AWS + Stripe + Cloudflare degrading at the same minute) without flipping between tabs.
Is Databricks Azure down right now?
Databricks Azure is up. Pingoru checks the official status page every 5 minutes and flips this headline the moment Databricks Azure reports a change. Current status is based on 331 tracked services.
How does Pingoru know if Databricks Azure is down?
We read https://status.azuredatabricks.net directly, using Databricks Azure's own status page. If the vendor reports an incident, you see it within one check cycle — not after someone manually marks the page as down.
Where can I get notified when Databricks Azure has an outage?
Create a free Pingoru account and add Databricks Azure as a monitor. You can filter to specific services, pick severity thresholds, and route alerts via email, Slack, Discord, or a webhook.
Databricks Azure's status page says the service is up, but I'm having issues — what's wrong?
Three common reasons: • A real Databricks Azure incident that hasn't been acknowledged on their public status page yet — vendor status pages are updated manually and typically lag the first customer reports by 10–30 minutes. • A regional or account-scoped issue affecting a subset of customers — these rarely trigger a global status-page change. • A local problem: ISP / DNS / your own software. Try reproducing from a mobile data connection and from a different network to isolate. If you suspect a real Databricks Azure issue that isn't reflected yet, contact their support to escalate. Subscribing here means you get the alert the moment they do post an update.
Where does Pingoru get the official Databricks Azure status?
We use Databricks Azure's own status page at https://status.azuredatabricks.net and cross-reference their homepage (https://www.databricks.com/product/azure). Nothing is read in a way the vendor hasn't explicitly made public — we use the same data their own dashboard uses. So our data is as accurate as what you'd see loading the status page yourself, but rolled into one dashboard alongside every other service you depend on.
What does "Up" mean?
All tracked Databricks Azure components are reporting operational. No incidents are currently affecting service.

Stop finding out from your users.

We watch Databricks Azure's official status page every 5 minutes. The moment they report an incident, you get an email — often before the outage is widely noticed.

Monitor Databricks Azure free →

10 monitors free · email alerts · no credit card

Want the full picture first? See everything Pingoru does →