DoorDash experienced a critical incident on June 16, 2026 affecting Drive API and Mx Websites and 1 more component, lasting 2h 8m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.