Skip to main content

Is DoorDash Down?

No — DoorDash is up

Reachable from all 8 checked regions

Average response time: 308ms

Last checked · checks run every 6 hours

Official status page: https://doordash.statuspage.io

DoorDash uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
313ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 13 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

13-day clean streak
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: no data
Aug 27: no data
Aug 28: no data
Aug 29: no data
Aug 30: no data
Aug 31: no data
Sep 1: no data
Sep 2: no data
Sep 3: no data
Sep 4: no data
Sep 5: no data
Sep 6: no data
Sep 7: no data
Sep 8: 100.00% uptime, 22 checks
Sep 9: 100.00% uptime, 24 checks
Sep 10: 100.00% uptime, 32 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 31 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 31 checks
Sep 16: 100.00% uptime, 30 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 31 checks
Sep 20: 100.00% uptime, 24 checks
Aug 22 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
281ms
DNS 122ms TCP 17ms TLS 42ms TTFB 201ms
arn
480ms
DNS 251ms TCP 25ms TLS 47ms TTFB 351ms
bom
315ms
DNS 248ms TCP 3ms TLS 28ms TTFB 290ms
cdg
299ms
DNS 177ms TCP 14ms TLS 38ms TTFB 244ms
dfw
368ms
DNS 86ms TCP 32ms TLS 52ms TTFB 205ms
ewr
221ms
DNS 128ms TCP 8ms TLS 34ms TTFB 182ms
fra
241ms
DNS 172ms TCP 5ms TLS 29ms TTFB 215ms
yyz
259ms
DNS 59ms TCP 19ms TLS 58ms TTFB 159ms

What DoorDash does

DoorDash is an on-demand delivery marketplace connecting customers with restaurants, grocery and convenience stores in the US, Canada and Australia. Beyond its own app it sells DoorDash Drive, a white-label delivery service that other companies use to fulfil orders placed on their own websites, so a business can depend on DoorDash without any customer ever opening the DoorDash app.

What an outage looks like

Orders fail at checkout or sit without a Dasher assigned, live tracking stops updating mid-delivery, and restaurant menus load empty or refuse to add items. Merchants see orders stop arriving on the tablet while the storefront still accepts them. Businesses using Drive see deliveries placed from their own website fail even though their site is working normally.

What to do about it

Read doordash.statuspage.io and match the row to your side of the service. Its components are grouped around merchant and Drive surfaces (Orders, Menu Updates, Catalog, Inventory, Merchant Portal, Merchant Tablet, and Drive API, Drive Order Fulfillment and Drive Delivery Tracking Page), so a Drive incident and a marketplace incident are separate. If an order was charged but never confirmed, wait for it to resolve rather than reordering, and use the in-app order help for refunds.

Is it down for everyone, or just you?

If this page says DoorDash is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Stripe
Stripe
Twilio
Twilio
AWS
AWS
Shopify
Shopify

DoorDash outage FAQ

DoorDash's status page says everything is operational, but my order will not go through. Why?
The published components are mostly merchant, Drive and developer surfaces rather than a single consumer verdict, so an all-clear there does not always describe the customer app. The measurements on this page probe the DoorDash app origin directly from several regions, which is a different signal. A payment authorisation failure or a restaurant that has gone offline also produce a checkout error with nothing wrong at DoorDash.
Ordering from a restaurant's own website failed. Is that a DoorDash outage?
It can be. DoorDash Drive is a white-label delivery service other companies use to fulfil orders taken on their own sites, and DoorDash reports it as its own component group with Drive API, Drive Order Fulfillment and Drive Delivery Tracking Page rows. A Drive incident breaks delivery on those sites while the DoorDash marketplace app keeps working, so the two failures do not appear together.
Is DoorDash down for everyone or just me?
Check the per-region measurements above before assuming a platform outage. DoorDash serves several countries and its own components are reported separately, so a fault can hit one surface and leave others untouched. If our regions all report the app reachable, look at your network, an outdated app version, or a payment method that needs re-authorising. A single restaurant showing as closed is a merchant state, not an outage.
Will I be charged for an order placed during a DoorDash outage?
An order that never confirmed usually leaves a pending authorisation rather than a completed charge, and pending authorisations drop off on their own. DoorDash does not publish a guarantee covering every failure mode, so check your order history once the incident clears and raise anything that completed without arriving through in-app order help. Avoid reordering while the first attempt is still pending, because both can eventually go through.
My Dasher tracking has frozen. Is the delivery still happening?
Often yes. DoorDash publishes Drive Delivery Tracking Page and Dasher Status Updates as components separate from order fulfilment, so the map and status text can stop updating while the courier is still driving. Treat a frozen tracker as lost visibility rather than a lost order, and wait for the delivery window before contacting support.

How we measure this

  • We request DoorDash's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where DoorDash publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when DoorDash goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required