Skip to content

Outage tracker / DoorDash

Is DoorDash down?

Short linkrlup.io/down/doordash

I'm having a problem

Operationalchecked 1 minute ago

We reached DoorDash from all 2 regions we check.

As of Oct 5, 2026, 8:18 PM UTC, DoorDash answered RealUptime's probes in all 2 regions that returned a reading.

Functional endpoints verified

No outage recorded in the 58 days we have measured DoorDash (since Aug 8, 2026).

Email me the next time we see DoorDash go down

Measured by our own probes from ten regions, not DoorDash's status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

our independent probeslive · checked Oct 5, 2026, 8:18 PM UTC
US-East370 msOperational
US-West274 msOperational

DoorDash operates in North America and a small number of other markets, so we check it from our US regions only.

their status pagetheir claim, not our reading

DoorDash publishes no status feed we can read, so the only independent reading here is ours on the left.

DoorDash response time, by region

US-East
607msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 615ms2026-09-07 UTC: p95 608ms2026-09-08 UTC: p95 645ms2026-09-09 UTC: p95 729ms2026-09-10 UTC: p95 721ms2026-09-11 UTC: p95 752ms2026-09-12 UTC: p95 724ms2026-09-13 UTC: p95 618ms2026-09-14 UTC: p95 621ms2026-09-15 UTC: p95 650ms2026-09-16 UTC: p95 792ms2026-09-17 UTC: p95 736ms2026-09-18 UTC: p95 697ms2026-09-19 UTC: p95 711ms2026-09-20 UTC: p95 674ms2026-09-21 UTC: p95 752ms2026-09-22 UTC: p95 727ms2026-09-23 UTC: p95 818ms2026-09-24 UTC: p95 931ms2026-09-25 UTC: p95 670ms2026-09-26 UTC: p95 689ms2026-09-27 UTC: p95 700ms2026-09-28 UTC: p95 685ms2026-09-29 UTC: p95 781ms2026-09-30 UTC: p95 893ms2026-10-01 UTC: p95 580ms2026-10-02 UTC: p95 545ms2026-10-03 UTC: p95 617ms2026-10-04 UTC: p95 623ms2026-10-05 UTC: p95 607ms
Sep 6Sep 20Oct 5
US-West
567msp95 · latest
1s500ms0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-06 UTC: p95 556ms2026-09-07 UTC: p95 466ms2026-09-08 UTC: p95 440ms2026-09-09 UTC: p95 447ms2026-09-10 UTC: p95 404ms2026-09-11 UTC: p95 393ms2026-09-12 UTC: p95 316ms2026-09-13 UTC: p95 446ms2026-09-14 UTC: p95 474ms2026-09-15 UTC: p95 487ms2026-09-16 UTC: p95 544ms2026-09-17 UTC: p95 582ms2026-09-18 UTC: p95 524ms2026-09-19 UTC: p95 486ms2026-09-20 UTC: p95 532ms2026-09-21 UTC: p95 500ms2026-09-22 UTC: p95 686ms2026-09-23 UTC: p95 601ms2026-09-24 UTC: p95 486ms2026-09-25 UTC: p95 822ms2026-09-26 UTC: p95 817ms2026-09-27 UTC: p95 789ms2026-09-28 UTC: p95 646ms2026-09-29 UTC: p95 644ms2026-09-30 UTC: p95 584ms2026-10-01 UTC: p95 630ms2026-10-02 UTC: p95 593ms2026-10-03 UTC: p95 543ms2026-10-04 UTC: p95 573ms2026-10-05 UTC: p95 567ms
Sep 6Sep 20Oct 5
Why some readings show as awaiting data. 2 of 4 readings for DoorDash came back as a filtered response to our automated checks (a response code that refuses automated clients, such as 403, 405, 406, 429 or 451, a redirect loop, or a timeout we could rule out as a real outage using a second endpoint) rather than a normal success or failure. That tells us about our own probe's reception, not about DoorDash's actual health, so we publish no verdict for those readings rather than guessing in either direction. 2 of those readings received an actual response: we confirmed the connection, the TLS handshake, and the edge all answered, with a real measured latency. That is a positive result, we verified reachability, just not through the specific path automated checks are filtered on. Read how we tell the difference.

Is it DoorDash, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not DoorDash -- it cannot diagnose DoorDash's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What we measured, and what people reported

  • North America
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 370msstatus code: 401checked: Oct 5, 2026, 8:09 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach DoorDash normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 274msstatus code: 401checked: Oct 5, 2026, 8:18 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach DoorDash normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionDoorDash is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionDoorDash is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionDoorDash is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Not monitored from this regionDoorDash is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • UK
      Not monitored from this regionDoorDash is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Not monitored from this regionDoorDash is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Southeast Asia
      Not monitored from this regionDoorDash is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionDoorDash is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using DoorDash, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for DoorDash yet, which is not evidence that nothing is wrong.

Recent outages

No outages on record yet for DoorDash.

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring DoorDash since August 8, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for DoorDash covering any window you pick, with our measurements and DoorDash's own claim at the time, side by side.

Full availability history for DoorDash: 90-day availability by region, month-by-month uptime, and every incident on record.

Put this badge in your README

DoorDash uptime measured by RealUptimeLive, from this page's own readings.
[![DoorDash uptime measured by RealUptime](https://realuptime.io/outages/doordash/badge.svg?days=30)](https://realuptime.io/outages/doordash)
<a href="https://realuptime.io/outages/doordash"><img src="https://realuptime.io/outages/doordash/badge.svg?days=30" alt="DoorDash uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What DoorDash's SLA implies, from our measurement

At or above your target

We measured none of downtime for DoorDash over the last 30 days, which is 100% uptime by our reading. A 99.9% target allows 43 minutes over that period.

By our measurement there is no shortfall to claim for this period.

This is computed from our own probe measurements, not from DoorDash's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://api.doordash.com/drive/v2/deliveries
RealUptime is not affiliated with DoorDash; the name identifies what we measured, and nothing here speaks for DoorDash's own team. We send a single web request to DoorDash from 2 regions on our own schedule and time the response. We do not see inside DoorDash's systems, do not use an account or real transaction, and are not the same signal DoorDash's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for DoorDash is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. DoorDash operates in North America and a small number of other markets, so we check it from our US regions only. Read the full methodology.

Related services

AirbnbAmazonApple iCloudBest BuyBooking.com