DoorDash incident
Drive Order Creation and Fulfillment - Issue Detected
DoorDash experienced a critical incident on May 14, 2025 affecting Drive API, lasting 2h 1m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 14, 2025, 09:08 PM UTC
We have detected an issue with Order Creation and Fulfillment. We are actively investigating. Next update in 15 minutes.
- identified May 14, 2025, 09:09 PM UTC
We have identified the issue. Team is working on mitigating.
- monitoring May 14, 2025, 09:16 PM UTC
The issue is mitigated. Drive V1 API saw 5xx errors between 1:30 PM PST and 2:10 PM PST. If you saw errors with creating deliveries, please retry now and it should work.
- monitoring May 14, 2025, 09:17 PM UTC
We are continuing to monitor for any further issues.
- resolved May 14, 2025, 11:09 PM UTC
This incident has been resolved.
- postmortem May 15, 2025, 06:14 PM UTC
On May 14, 2025, from approximately 1:29 PM to 2:12 PM PST, a configuration change introduced a corrupted setting that decreased the availability of the Drive Classic v1 APIs. Our monitoring systems promptly alerted us to the issue, and upon identification, we initiated and completed a rollback to restore normal service. The impact of this incident was limited to Drive Classic v1 APIs. Drive v2 APIs and order fulfillment systems remained fully operational throughout the incident. To avoid recurrence, we have implemented stricter validation checks and enhanced change management procedures for critical configuration files related to the Drive Classic v1 APIs. We apologize for any inconvenience caused and appreciate your understanding.