DoorDash had 13 outages in the last 2 years totaling 16h 50m of downtime — averaging 0.5 incidents per month.
There were 13 DoorDash outages since October 8, 2025 totaling 16h 50m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
Seeing recovery from AWS side, monitoring order health
We are continuing to monitor for any further issues.
This incident has been resolved.
Between approximately 04:00 and 04:15 am PT on July 24, 2026, an upstream infrastructure provider (Cloudflare) outage caused a service disruption affecting Drive order creation and webhook delivery. During this ~15-minute window, some orders and status webhooks may have failed or been delayed. Service fully recovered automatically once the upstream provider was restored, and no manual mitigation was required on the DoorDash Drive side. We apologize for the disruption.
We are currently investigating this issue.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
On June 28, 2026, DoorDash experienced an internal infrastructure issue that disrupted order transmission to POS-integrated merchants. As a result, Marketplace orders could not be delivered to affected merchant systems for approximately 90 minutes \(3:10 PM–4:40 PM PT\). The issue was identified, mitigated, and service was restored. During recovery, orders resumed processing successfully with operational safeguards in place, and normal service levels were fully restored by approximately 7:00 PM PT. We are implementing automated lifecycle management, completing a review of remaining legacy-managed infrastructure, and strengthening monitoring governance to improve early detection and reduce the likelihood of similar incidents recurring.
Doordash order health seems to be impacted partially, seeing higher than expected latency. The team is actively investigating the issue.
The team has investigated and resolved the issue. Seeing api metrics back in trend.
This incident has been resolved.
We have detected an issue with Event Logs in Developer Portal. We are actively investigating.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
The incident has been resolved.
We are aware of users to be unable to access developer portal. The team is actively investigating the issue.
A fix has been deployed and we are monitoring auth errors.
We are no longer seeing the errors, Dev Portal should be available now.
We are currently experiencing service degradation due to an outage with Cloudflare. This issue is causing platform-wide issues with DoorDash and may cause errors for some users. Our engineering teams are monitoring the situation and working to mitigate customer impact.
We are continuing to investigate this issue.
We are seeing recovery across our systems and are monitoring to confirm full restoration.
This incident has been resolved.
We have detected an issue with Drive Order Creation V1 API. We are actively investigating. API calls to the Create Delivery V1 endpoint that fail may be successful on retry. Next update in 15 minutes.
The issue with Order Creation is resolved but we will continue to monitor. Next update in 15 minutes.
The issue with Order Creation is now confirmed to be resolved. No further updates.
Partial order volume impact
This incident has been resolved.
From 9am to 12:49pm PT a new validation rule on DoorDash Drive was unexpectedly applied, requiring non-empty first and last names. This rule caused order creation requests with an empty customer first or last name to be rejected across API integrations and through the "Request a Delivery" form on the Merchant portal. After the rule change was rolled back by 12:49pm PT, the previous name validation rules were being applied and orders with empty first or last name were being accepted.
From 7:55 PM PDT on October 7, 2025 to 11:15PM PDT October 7, 2025, Drive experienced degraded ETA accuracy due to an internal database corruption issue. During this time, ETA estimates appeared significantly longer than expected for all Drive merchants. The underlying issue was partially resolved by 11:15 PM PDT and fully resolved by 2:25 AM PDT on October 8, 2025, and ETA accuracy has since returned to normal.