Thousands of DoorDash users reported a platform outage Tuesday morning, June 16, with Downdetector logging more than 36,000 problem reports by 10:20 a.m. ET.
The surge in reports began near 9:30 a.m. ET and by 10 a.m. ET Downdetector showed 73% of the issues were tied to the mobile app, the tracker’s real-time data indicated. The majority of reports came from New York, Chicago, Detroit, Dallas and Los Angeles.
The disruption — widely described online with phrases such as doordash app down — left customers and drivers unable to use the service normally during a busy morning window. The volume of reports was large enough to register as a widespread outage rather than isolated complaints.
Downdetector provides real-time outage updates and was the primary source of the report totals and timing. The tracker’s timeline shows the number of problem reports spiking starting at 9:30 a.m. ET and climbing steadily through the midmorning, reaching the 36,000-plus mark by 10:20 a.m. ET.
The immediate consequence was practical: users who rely on the DoorDash mobile app to place or accept orders faced service interruptions at scale while restaurants and couriers adjusted on the fly. In cities where reports were heaviest, the outage likely affected hundreds or thousands of active orders and deliveries during the peak of the disruption.
Despite the size of the outage, DoorDash had not provided additional information on the cause or a restoration timeline as reports grew. reached out to DoorDash for comment on June 16; at the time Downdetector’s counters were still climbing and the company had not issued a public explanation tied to the morning’s spike.
The gap between the scale of the disruption and the company’s public response is the central tension of the morning: tens of thousands of users were reporting failures while an official account of what went wrong and when normal service would resume was absent. That unresolved gap leaves businesses, couriers and customers without a clear line of sight to recovery or remedies for interrupted orders.
For now, the most important facts are the numbers and the pattern: the peak of outage reports began at 9:30 a.m. ET, 73% of issues were associated with the mobile app as of 10 a.m. ET, and more than 36,000 users had logged problems by 10:20 a.m. ET. Those figures quantify the scale and narrow the inquiry to app-side failures rather than, say, isolated account or payment issues.
The next development readers should watch is any official update from DoorDash explaining the cause and a timeline for full restoration. Because the outage was active as of the latest timestamps, the service’s status could change quickly; an official statement from DoorDash would confirm whether the disruption was resolved, limited in scope, or still unfolding.
The unanswered questions remain blunt: what triggered the outage, why it hit the mobile app most severely, and when normal operations will resume. Until DoorDash provides those answers, the morning’s numbers and city breakdowns are the best available evidence of how widespread the interruption was.
