What happened when DoorDash froze at lunchtime?

The lunch rush hit, phones opened, and for thousands of DoorDash users the app simply would not play along. Orders stalled, logins failed, and some drivers were left holding food they could not properly complete through the platform. By late Tuesday morning in the US, DoorDash said the issue had been resolved, after outage reports surged past 36,000 on Downdetector.

How Events Unfolded

The disruption began showing clearly around 9:30 a.m. ET on Tuesday, June 16, when users began reporting problems with the DoorDash app and website. Downdetector, which tracks user-submitted outage reports, recorded a rapid spike that climbed above 30,000, then above 35,000, before USA Today reported more than 36,000 reports at 10:20 a.m. ET.

The biggest reported trouble spot was the mobile app. The New York Post reported that 73% of issues were tied to the app, while about 23% of users said they could not order because of login failures. Tom's Guide also reported that browser login attempts were failing, with one error screen pointing to a possible DNS-related issue, though DoorDash did not disclose the technical cause.

The reports were concentrated in major US cities including New York, Chicago, Detroit, Dallas and Los Angeles. That matters because a delivery app outage is not just a screen problem: when orders are already in motion, a broken app can leave customers without meals, restaurants with prepared food, and Dashers unable to complete jobs.

DoorDash later said the short outage had been resolved. In a post cited by USA Today, the company said it was working to correct impacted Dashers and orders, and encouraged users with questions or concerns to contact DoorDash Customer Service.

Critical Details

The core issue appears to have hit access and ordering rather than a single late-delivery incident. Multiple reports described users being locked out, unable to place orders, or unable to move through delivery workflows. Tom's Guide said some drivers could not log in to complete orders, which turns a consumer outage into a labour and payment issue as well.

By 11:01 a.m. ET, Downdetector reports had dropped to about 17,000, down from more than 35,000 at the height. Tom's Guide later reported around 590 reports at 12:13 p.m. ET, then about 500 by 12:39 p.m. ET, describing the service as working normally again for many users.

For Australian readers, the useful takeaway is less about those US city maps and more about how quickly delivery platforms can become brittle when login, ordering and driver systems fail together. DoorDash is built around tight timing: restaurants prepare food, drivers collect it, and customers expect live status updates. If the app layer breaks during that chain, the mess spreads across all three sides of the marketplace.

Downdetector

A service that tracks real-time outage reports submitted by users across apps and websites.

DNS error

A technical error that can stop a browser or app from reaching the correct online service, though DoorDash did not confirm DNS as the cause.

Dasher

DoorDash's term for a delivery driver using the platform.

Reactions & Responses

DoorDash acknowledged the issue on its Help account on X shortly after 10 a.m. ET, saying it was aware of a platform problem and was working urgently to resolve it. Just before noon ET, USA Today reported that DoorDash said the outage was resolved and that the company was working to correct affected Dashers and orders.

Users responded with the kind of frustration that comes when money, food and time are all tied up at once. The New York Post reported complaints from customers who said orders were marked delivered when they had not arrived, while another user said they had waited two hours and missed the McDonald's breakfast window.

Drivers also faced an awkward bind. Tom's Guide reported one X user saying they were at a pickup location while still on the clock but unable to log in. Another user raised the compensation problem: if food was already prepared or collected, the outage created a chain of refunds, restaurant costs and driver payments that DoorDash would need to sort through after the app recovered.

Putting It in Perspective

This was not the only consumer app disruption reported that morning. Spotify also experienced a short outage, with Forbes reporting that Spotify complaints peaked at about 5,000 on Downdetector before falling sharply and the platform later saying the issue was all clear. PhillyBurbs reported that DoorDash and Spotify issues both began around 9:30 a.m. ET, but said it was unclear whether there was any connection.

The DoorDash outage was bigger in scale than the Spotify spike, based on the supplied Downdetector numbers. A music outage interrupts listening; a food delivery outage can interrupt paid orders already in progress. That difference explains why the DoorDash recovery phase matters: fixing the app is only step one, while correcting payments, refunds and driver issues can take longer.

The New York Post reported that DoorDash directed users to seek help through the app by selecting the order, tapping Help, and choosing the delivery issue. On the website, users were told to open the menu, go to Orders, select the specific order, then choose Help. The same report also listed DoorDash's 24/7 support line as 855-431-0459.

Looking Ahead

What is confirmed is that DoorDash said the outage was resolved before noon ET and that it was working on affected Dashers and orders. The cause of the disruption has not been disclosed by DoorDash in the supplied reports.

The next practical step for affected users is support, not speculation. Anyone whose order failed, was wrongly marked delivered, or created a billing issue should use the order-specific Help flow described by DoorDash coverage, because that gives the platform the exact transaction it needs to review.