DoorDash Outage History
DoorDash is up right nowPingoru has recorded 51 incidents for DoorDash: 14 in the last 12 months and 2 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 0 of 720 (0%) |
| May 2026 | 1 | 2 of 744 (0%) |
| June 2026 | 2 | 5 of 720 (1%) |
| July 2026 | 1 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 1 | 3 of 720 (0%) |
| October 2026 | 1 | 3 of 521 (1%) |
Incidents, newest first
Minor October 20, 2026 Partial Order Health impacted 3h 22m Orders, Menu Updates
Started Oct 20, 2026, 08:48 AM UTC· resolved Oct 20, 2026, 12:11 PM UTC
- investigating Oct 20, 2026, 08:48 AM UTC
We are currently experiencing partial disruption in order health, the team is investigating
- investigating Oct 20, 2026, 08:55 AM UTC
We are continuing to investigate this issue.
- investigating Oct 20, 2026, 10:32 AM UTC
The incident has been mitigated and the order health is back to normal
- resolved Oct 20, 2026, 12:11 PM UTC
This incident has been resolved.
Notice September 27, 2026 AWS Outage -- Doordash Health Impacted 3h 16m Drive API, Developer Portal, Merchant Portal, Orders and 1 more
Started Sep 27, 2026, 12:32 AM UTC· resolved Sep 27, 2026, 03:49 AM UTC
- investigating Sep 27, 2026, 01:09 AM UTC
We are currently investigating this issue.
- monitoring Sep 27, 2026, 01:11 AM UTC
Seeing recovery from AWS side, monitoring order health
- monitoring Sep 27, 2026, 03:48 AM UTC
We are continuing to monitor for any further issues.
- resolved Sep 27, 2026, 03:49 AM UTC
This incident has been resolved.
Critical July 24, 2026 Cloudflare-Related Drive Order & Webhook Disruption –
Started Jul 24, 2026, 11:00 AM UTC· resolved Jul 24, 2026, 11:00 AM UTC
- resolved Jul 24, 2026, 05:15 PM UTC
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.
Critical June 28, 2026 Order Health Impacted 2h 41m Orders, Menu Updates, Dasher Status Updates
Started Jun 28, 2026, 10:33 PM UTC· resolved Jun 29, 2026, 01:15 AM UTC
- investigating Jun 28, 2026, 10:33 PM UTC
We are currently investigating this issue.
- investigating Jun 28, 2026, 10:44 PM UTC
We are continuing to investigate this issue.
- investigating Jun 28, 2026, 10:45 PM UTC
We are continuing to investigate this issue.
- monitoring Jun 29, 2026, 12:26 AM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Jun 29, 2026, 12:27 AM UTC
We are continuing to monitor for any further issues.
- resolved Jun 29, 2026, 01:15 AM UTC
This incident has been resolved.
- postmortem Jul 02, 2026, 12:20 AM UTC
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.
Critical June 16, 2026 DoorDash outage 2h 8m Drive API, Mx Websites, Drive Order Fulfillment, Native Apps and 11 more
Started Jun 16, 2026, 02:14 PM UTC· resolved Jun 16, 2026, 04:22 PM UTC
- investigating Jun 16, 2026, 02:14 PM UTC
We are aware of the issue and are currently investigating
- investigating Jun 16, 2026, 02:15 PM UTC
We are continuing to investigate this issue.
- identified Jun 16, 2026, 02:18 PM UTC
The issue has been identified and a fix is being implemented.
- identified Jun 16, 2026, 02:33 PM UTC
We are continuing to work on a fix for the issue
- identified Jun 16, 2026, 03:03 PM UTC
We have identified a fix and are working to implement
- identified Jun 16, 2026, 03:35 PM UTC
We have implemented the fix and are starting to see some recovery
- monitoring Jun 16, 2026, 03:49 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 16, 2026, 04:22 PM UTC
This incident has been resolved.
- postmortem Jun 24, 2026, 11:00 PM UTC
On June 16, 2026, an unintended configuration change introduced invalid data into a critical authentication service. As a result the service was unable to process authentication requests correctly, resulting in widespread authentication failures. This led to significant disruptions in order processing, reduced delivery volume, elevated cancellation rates, delayed deliveries, and increased customer remediation costs. The incident was resolved by restoring a known-good configuration, increasing service capacity to accelerate recovery, and temporarily managing incoming traffic while systems stabilized. To reduce the likelihood and impact of similar incidents in the future, we are implementing stronger configuration validation and schema enforcement, improving resilience and fallback behavior in critical services, and adding additional safeguards and rollout controls for changes to tier-0 infrastructure components.
Critical May 5, 2026 Open API Order Health Impacted 2h 26m Orders
Started May 05, 2026, 03:47 PM UTC· resolved May 05, 2026, 06:14 PM UTC
- investigating May 05, 2026, 03:47 PM UTC
We are currently investigating this issue.
- investigating May 05, 2026, 04:27 PM UTC
We are continuing to investigate this issue.
- investigating May 05, 2026, 04:50 PM UTC
We are continuing to investigate this issue.
- investigating May 05, 2026, 06:12 PM UTC
We have found root cause and mitigated the issue.
- resolved May 05, 2026, 06:14 PM UTC
This incident has been resolved.
- postmortem May 07, 2026, 12:38 AM UTC
### **What happened** On May 5, 2026, a subset of partners integrated with DoorDash through openapi endpoints saw degraded connectivity. During the impacted window, some partner’s requests experienced elevated latency, errors, or timeouts. The affected merchants were unable to confirm orders within normal response windows. Our automated platform safeguard temporarily paused the stores on the impacted providers to help prevent additional failed order experiences. The issue was identified, mitigated, and fully resolved. Affected stores were brought back online once normal platform behavior was restored. ### **\[High Level\] Root cause** The disruption was triggered when a partner inadvertently routed requests to an unintended endpoint with unexpected request payload. This resulted in degradation of a shared platform component responsible for handling API traffic. The degradation of this shared component led to elevated latency and timeouts for legitimate api requests. Interpreting these timeouts as store-level failures, our health-monitoring systems temporarily paused the affected stores to protect the overall ordering experience. ### **What we are improving** * Strengthening isolation between api traffic sources so that an issue from one path is less likely to affect another partner. * Conduct a comprehensive audit of platform paths and onboarding procedures to bolster overall system resilience. ### **Closing statement** We offer our sincere apologies to all merchants, partners, dashers, and consumers impacted by this disruption. DoorDash remains dedicated to providing a reliable platform for our integrated partners. We are focused on utilizing the insights gained from this event to strengthen our recovery processes and platform stability.
Minor March 19, 2026 Event logs outage 6h 23m Developer Portal
Started Mar 19, 2026, 04:22 PM UTC· resolved Mar 19, 2026, 10:46 PM UTC
- investigating Mar 19, 2026, 04:22 PM UTC
We have detected an issue with Event Logs in Developer Portal. We are actively investigating.
- identified Mar 19, 2026, 04:49 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Mar 19, 2026, 05:57 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 19, 2026, 10:46 PM UTC
The incident has been resolved.
Major December 12, 2025 Developer portal authentication issue 58m Developer Portal
Started Dec 12, 2025, 03:15 PM UTC· resolved Dec 12, 2025, 04:14 PM UTC
- identified Dec 12, 2025, 03:15 PM UTC
We are aware of users to be unable to access developer portal. The team is actively investigating the issue.
- monitoring Dec 12, 2025, 03:42 PM UTC
A fix has been deployed and we are monitoring auth errors.
- resolved Dec 12, 2025, 04:14 PM UTC
We are no longer seeing the errors, Dev Portal should be available now.
Major December 5, 2025 Service Degradation Due to Cloudflare Outage 34m Drive API, DoorDash Careers Site, Mx Websites, Drive Order Fulfillment and 12 more
Started Dec 05, 2025, 09:01 AM UTC· resolved Dec 05, 2025, 09:35 AM UTC
- investigating Dec 05, 2025, 09:01 AM UTC
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.
- investigating Dec 05, 2025, 09:03 AM UTC
We are continuing to investigate this issue.
- monitoring Dec 05, 2025, 09:26 AM UTC
We are seeing recovery across our systems and are monitoring to confirm full restoration.
- resolved Dec 05, 2025, 09:35 AM UTC
This incident has been resolved.
Minor December 3, 2025 Drive Order Creation - Issue Detected 28m Drive API
Started Dec 03, 2025, 10:16 PM UTC· resolved Dec 03, 2025, 10:45 PM UTC
- investigating Dec 03, 2025, 10:16 PM UTC
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.
- monitoring Dec 03, 2025, 10:27 PM UTC
The issue with Order Creation is resolved but we will continue to monitor. Next update in 15 minutes.
- resolved Dec 03, 2025, 10:45 PM UTC
The issue with Order Creation is now confirmed to be resolved. No further updates.
Major December 3, 2025 Order volume impacted 2m Orders
Started Dec 03, 2025, 01:36 AM UTC· resolved Dec 03, 2025, 01:38 AM UTC
- investigating Dec 03, 2025, 01:36 AM UTC
Partial order volume impact
- resolved Dec 03, 2025, 01:38 AM UTC
This incident has been resolved.
Notice October 16, 2025 Drive Order Creation - Issue Resolved –
Started Oct 16, 2025, 04:00 PM UTC· resolved Oct 16, 2025, 04:00 PM UTC
- resolved Oct 17, 2025, 07:36 PM UTC
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.
Notice October 8, 2025 Drive Order Fulfillment - Drive ETA Degradation 6h 30m
Started Oct 08, 2025, 02:55 AM UTC· resolved Oct 08, 2025, 09:25 AM UTC
- resolved Oct 14, 2025, 06:00 PM UTC
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.
Major September 11, 2025 Drive Order Creation - Issue detected 16m Drive Order Fulfillment, Online Ordering (Storefront), Orders
Started Sep 11, 2025, 03:45 PM UTC· resolved Sep 11, 2025, 04:02 PM UTC
- investigating Sep 11, 2025, 03:45 PM UTC
We have detected an issue with Order Creation. We are actively investigating.
- investigating Sep 11, 2025, 03:50 PM UTC
We are continuing to investigate this issue.
- monitoring Sep 11, 2025, 03:51 PM UTC
A fix has been implemented and we are monitoring the results.
- identified Sep 11, 2025, 03:51 PM UTC
The issue has been identified and working to be mitigated. We are seeing recovery
- monitoring Sep 11, 2025, 03:54 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Sep 11, 2025, 04:02 PM UTC
This incident has been resolved.
Notice August 6, 2025 Degradation on SSIO (store onboarding) endpoint 14m
Started Aug 06, 2025, 08:49 PM UTC· resolved Aug 06, 2025, 09:04 PM UTC
- investigating Aug 06, 2025, 08:49 PM UTC
Impact since 8/6 7am PST
- resolved Aug 06, 2025, 09:04 PM UTC
Team identified cause and issue is now mitigated as of 2pm.
Minor August 5, 2025 Drive API error spike 18m Drive API
Started Aug 05, 2025, 07:10 PM UTC· resolved Aug 05, 2025, 07:28 PM UTC
- investigating Aug 05, 2025, 07:10 PM UTC
We are currently investigating this issue.
- investigating Aug 05, 2025, 07:18 PM UTC
We have recovered and root causing the error spikes.
- monitoring Aug 05, 2025, 07:22 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Aug 05, 2025, 07:27 PM UTC
We are continuing to monitor for any further issues.
- resolved Aug 05, 2025, 07:28 PM UTC
This incident has been resolved. From 11:42 to 11:48, 12:02 to 12:10 we had two API 500 error spikes caused by internal DB outage. During the incident 7% of Drive Classic requests got impacted; and 25% of Drive API requests got impacted. Retries during the time would have worked if the clients have retry logic.
Notice August 5, 2025 Marketplace Orders impacted –
Started Aug 05, 2025, 07:00 PM UTC· resolved Aug 05, 2025, 07:00 PM UTC
- resolved Aug 05, 2025, 08:03 PM UTC
This incident has been resolved. From 11:42 AM to 11:48 AM and 12:02 PM to 12:10 PM PT, due to internal outage there was drop in order volume. We have since recovered.
Critical July 31, 2025 Doordash orders - Issue detected 28m Orders, Merchant Tablet
Started Jul 31, 2025, 09:35 AM UTC· resolved Jul 31, 2025, 10:04 AM UTC
- investigating Jul 31, 2025, 09:35 AM UTC
We have detected an issue with the orders functionality. We are investigating.
- identified Jul 31, 2025, 09:43 AM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jul 31, 2025, 09:49 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 31, 2025, 10:04 AM UTC
This incident has been resolved.
Critical July 9, 2025 Marketplace Order impacted 3h 21m Orders
Started Jul 09, 2025, 10:20 AM UTC· resolved Jul 09, 2025, 01:42 PM UTC
- investigating Jul 09, 2025, 10:20 AM UTC
Team is investigating on the issue
- identified Jul 09, 2025, 12:36 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jul 09, 2025, 01:04 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 09, 2025, 01:42 PM UTC
This incident has been resolved.
Major July 9, 2025 Drive Order Fulfillment - Issue Detected 4h 3m Drive Order Fulfillment, Drive Delivery Tracking Page
Started Jul 09, 2025, 09:43 AM UTC· resolved Jul 09, 2025, 01:46 PM UTC
- investigating Jul 09, 2025, 09:43 AM UTC
We have detected an issue with Order Fulfillment and are actively investigating.
- investigating Jul 09, 2025, 10:07 AM UTC
We are continuing to investigate this issue.
- investigating Jul 09, 2025, 11:00 AM UTC
We are continuing to investigate this issue.
- identified Jul 09, 2025, 12:12 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jul 09, 2025, 12:41 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jul 09, 2025, 01:46 PM UTC
This incident has been resolved.
Minor June 10, 2025 Drive Order Creation and Fulfillment - Issue Detected 2h 12m Drive API, Drive Order Fulfillment
Started Jun 10, 2025, 07:29 AM UTC· resolved Jun 10, 2025, 09:42 AM UTC
- investigating Jun 10, 2025, 07:29 AM UTC
We have detected an issue with Order Creation and Fulfillment. We are actively investigating.
- investigating Jun 10, 2025, 08:10 AM UTC
We have detected an issue with Order Creation and Fulfillment. We are actively investigating.
- investigating Jun 10, 2025, 08:35 AM UTC
We are continuing to investigate this issue.
- identified Jun 10, 2025, 08:57 AM UTC
We have identified an issue with Order Creation and Fulfillment. We are actively working on a resolution. Next update in 15 minutes.
- monitoring Jun 10, 2025, 09:37 AM UTC
The issue with Order Creation and Fulfillment is resolved but we will continue to monitor.
- investigating Jun 10, 2025, 09:42 AM UTC
The issue with Order Creation and Fulfillment is now confirmed to be resolved. No further updates.
- resolved Jun 10, 2025, 09:42 AM UTC
The issue with Order Creation and Fulfillment is now confirmed to be resolved. No further updates.
Major June 10, 2025 Order Health Degraded 2h 23m Developer Portal, Orders
Started Jun 10, 2025, 07:08 AM UTC· resolved Jun 10, 2025, 09:32 AM UTC
- investigating Jun 10, 2025, 07:08 AM UTC
Starting 11:05PM PST, Doordash is experiencing degraded order health. Team is investigating the issue
- investigating Jun 10, 2025, 07:12 AM UTC
We are continuing to investigate this issue.
- investigating Jun 10, 2025, 08:18 AM UTC
We are continuing to investigate this issue.
- investigating Jun 10, 2025, 08:44 AM UTC
We are seeing some recovery, but haven't fully mitigated yet. We are continuing to investigate and mitigate.
- investigating Jun 10, 2025, 09:12 AM UTC
We are seeing major recovery. We will continue to investigate and fully mitigate.
- monitoring Jun 10, 2025, 09:25 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 10, 2025, 09:32 AM UTC
The issues affecting Order health have been fixed, and we are fully recovered.
Major June 6, 2025 Drive API Degraded 1h 4m Drive API
Started Jun 06, 2025, 06:41 PM UTC· resolved Jun 06, 2025, 07:45 PM UTC
- investigating Jun 06, 2025, 06:41 PM UTC
We've detected an issue affecting Drive API. Our services are degraded and we're investigating.
- investigating Jun 06, 2025, 06:44 PM UTC
We are continuing to investigate this issue.
- identified Jun 06, 2025, 07:10 PM UTC
The issue has been identified, and the team is working on a multi-step fix. Service has partially recovered, and public API error rates have significantly decreased and are currently stable. The team is continuing to closely monitor the situation.
- identified Jun 06, 2025, 07:44 PM UTC
The issue has been mitigated and system behavior has stabilized.
- resolved Jun 06, 2025, 07:45 PM UTC
The team is continuing with cleanup efforts and will monitor closely to ensure full recovery. Thank you for your patience during this incident
Critical March 4, 2025 Drive Order Creation and Fulfillment - Issue Identified 12m Drive API
Started Mar 04, 2025, 06:38 PM UTC· resolved Mar 04, 2025, 06:50 PM UTC
- identified Mar 04, 2025, 06:38 PM UTC
We have identified an issue with Order Creation and Fulfillment. We are actively working on a resolution. Next update in 15 minutes.
- identified Mar 04, 2025, 06:40 PM UTC
We are continuing to work on a fix for this issue.
- identified Mar 04, 2025, 06:41 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Mar 04, 2025, 06:47 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 04, 2025, 06:50 PM UTC
This incident has been resolved.
Minor February 19, 2025 Developer portal is degraded 3h 49m Developer Portal
Started Feb 19, 2025, 03:58 PM UTC· resolved Feb 19, 2025, 07:47 PM UTC
- monitoring Feb 19, 2025, 03:58 PM UTC
Starting 5AM PST today, users are unable to log into developer portal. Team has identified the cause and applied a temporary fix. We are monitoring.
- monitoring Feb 19, 2025, 06:14 PM UTC
We are still seeing intermittent errors with most has been recovered. We are working for a full recovery.
- monitoring Feb 19, 2025, 07:16 PM UTC
The incident is mitigated. We are continuing monitoring.
- resolved Feb 19, 2025, 07:47 PM UTC
This incident has been resolved.