Critical incident
DoorDash: Open API Order Health Impacted
May 5, 2026, 18:12 UTC
started
18:14 UTC
resolved
1 min
duration
Affected: Orders
Current status of DoorDash: Operational — live DoorDash status
Timeline
- May 5, 2026, 15:47 UTCinvestigatingWe are currently investigating this issue.
- May 5, 2026, 16:27 UTCinvestigatingWe are continuing to investigate this issue.
- May 5, 2026, 16:50 UTCinvestigatingWe are continuing to investigate this issue.
- May 5, 2026, 18:12 UTCinvestigatingWe have found root cause and mitigated the issue.
- May 5, 2026, 18:14 UTCresolvedThis incident has been resolved.
- May 7, 2026, 00:38 UTCpostmortem### **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.
Updates as published by DoorDash (original).
Other services with incidents at the same time
- USG Services 18:50 UTC · Multi-Site DOE Outage - Comcast Last Mile
- balena.io 18:12 UTC · Elevated API Errors
- Berklee IT Services 17:21 UTC · Instructure (Canvas) Data Breach
More DoorDash incidents
- October 20, 2026 Partial Order Health impacted
- September 27, 2026 AWS Outage -- Doordash Health Impacted
- July 24, 2026 Cloudflare-Related Drive Order & Webhook Disruption
- June 28, 2026 Order Health Impacted
- June 16, 2026 DoorDash outage
- April 15, 2026 Partial Order Health impacted