Is DoorDash down?

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.

We are aware of the issue and are currently investigating

We are continuing to investigate this issue.

The issue has been identified and a fix is being implemented.

We are continuing to work on a fix for the issue

We have identified a fix and are working to implement

We have implemented the fix and are starting to see some recovery

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

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.

We are currently investigating this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We have found root cause and mitigated the issue.

This incident has been resolved.

### **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.