Is DoorDash Down Right Now? Check if there is a current outage ongoing.

We have detected an issue with Order Creation and Fulfillment. We are actively investigating.

We are continuing to investigate this issue.

Starting 11:05PM PST, Doordash is experiencing degraded order health. Team is investigating the issue

We've detected an issue affecting some of our consumers. Our services are degraded and we're investigating.

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.

This incident has been resolved.

We are continuing to monitor for any further issues.

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.

We have identified the issue. Team is working on mitigating.

We have detected an issue with Order Creation and Fulfillment. We are actively investigating. Next update in 15 minutes.

We have identified the issue. Team is working on mitigating.

We have detected an issue with Order Creation and Fulfillment. We are actively investigating.Next update in 15 minutes.

This incident is resolve.

We are seeing the order are back to normal. Will be monitoring for couple of more minutes

Currently Team is investigating the issue

Currently Team is investigating the issue

The order health was affected by a hardware failure in one of our partner's infrastructure. The faulty resource was replaced, which helped restore order health afterward.

The incident has been resolved now.

The order health has recovered now. The team is continuing to investigate.

Doordash Order Health is impacted. Marketplace and Drive Orders are affected. We are currently investigating the issue.

On March 4th, between 10:23 AM and 10:31 AM PST, DoorDash app and Drive consumers encountered errors when attempting to place orders due to a faulty configuration update. The issue was resolved shortly after the faulty configuration was reverted.

The order health was impacted for marketplace orders. The issue has been mitigated already and the team is investigating further.

This incident has been resolved.

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

We are continuing to work on a fix for this issue.

We are continuing to work on a fix for this issue.

We have identified an issue with Order Creation and Fulfillment. We are actively working on a resolution. Next update in 15 minutes.

This incident has been resolved.

The incident is mitigated. We are continuing monitoring.

We are still seeing intermittent errors with most has been recovered. We are working for a full recovery.

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.

On February 14th, between 03:07 - 4:08 AM PST, we experienced increased error rates on the Drive API affecting key endpoints (e.g., /quote, /deliveries). This resulted in intermittent failures for delivery quotes and order placements. The issue was caused by a Cloudflare outage in the Portland (PDX) data center, which intermittently disrupted traffic. The incident has been resolved, and we continue to monitor for further issues.

This incident has been resolved. No further delays on webhooks are expected.

Team has implemented a mitigation. Webhook delays should now be recovering. We continue to monitor for stability.

Team is actively monitoring and investigating the issue. Webhooks may still experience delays. We will provide updates as we learn more.

We are currently investigating the issue; some webhooks might be delayed but orders are being created and fulfilled successfully.

This incident has been resolved.

We are continuing to work on a fix for this issue.

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

This incident has been resolved

We are continuing to monitor for any further issues.

Team is continuing to monitor. We are observing some higher latencies on the APIs but retries should be working.

We are continuing to monitor the APIs , availability is looking good

We are continuing to monitor for any further issues.

A fix has been implemented and we are seeing recovery.

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

We have detected issues with Drive API Drive Classic and Order fulfillment has not been impacted.

We detected issues in drive order creation between 9:05-9:15 AM PST . We have recovered and no further updates

This incident has been resolved.

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

We saw some latency in order confirmation

#### Impact Between 2:50 AM PST and 4:54 AM PST, DoorDash experienced degraded order processing functionality. Customers encountered intermittent issues placing orders and completing checkouts. Merchants faced challenges confirming orders, and Dashers encountered errors accessing order details. #### Root Cause The disruption stemmed from unexpected behavior during a planned database upgrade. The upgrade has since been completed. Our team is investigating the root cause and will implement a fix to prevent similar issues in future upgrades.

This is a past incident. From 2:57AM PST, we detected an issue affecting DoorDash Order health. It got recovered 4:57AM PST.

There was a spike in the availability of Drive V1 create and estimates endpoint. The issue started around 09:18pm PST has been mitigated as of 09:35pm PST.

This incident has been resolved.

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

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

We are seeing partial checkout failure

Root cause of the incident : Due to the high rate of incoming order requests, some compute resources became overloaded, prompting us to redirect traffic to other resources. However, the redirection process took some time, which caused orders to still be processed through the impacted resources, leading to failures.

This incident has been resolved.

The order health has been recovered and the incident has been mitigated.

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

We are continuing to investigate this issue.

Doordash is experiencing partial degradation in order health. We are currently investigating the issue.

This incident has been resolved.

We are currently investigating this issue.

Between 3:23 PM PST to 3:37 PM PST on November 25, 2024, DoorDash experienced an incident which prevented certain users from placing orders on Marketplace. The incident was caused by a bad deployment of new set of rules in one of the critical internal services. The incident was quickly mitigated by reverting the change. To prevent this in future we have introduced more checks and process when making changes in critical flows.

This incident has been resolved.

We have mitigated and are continuing to monitor.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved

The issue has been mitigated and we are currently monitoring

We are currently investigating the incident

This incident has been resolved.

We identified and issue make a fix. We are recovering now.

We are continuing to investigate this issue.

We are investigating the issue now

This incident has been resolved.

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

We rolling back the canary deployment. Errors are going down now.

This incident has been resolved.

We are continuing to monitor for any further issues.

Mitigation measures have been taken. We have seen signal of recovery. It will be fully recovered in the next hour.

We are continuing to investigate this issue.

We have seeing increased lateness in delivery fulfillment and team is investigating right now. Next update in 1 hour.

On 11/13, the DoorDash Drive API was partially unavailable from 08:11 AM PT to 08:41 AM PT. An internal change disrupted database health and impacted our ability to accept orders. Fulfillment was largely unaffected. Reverting the change fixed the issue and made the DoorDash Drive API available. Since then, we have introduced additional levers to prevent these types of issues.

The issue with Drive API is now confirmed to be resolved. No further updates.

The issue is fixed and we are seeing recovery. We will continue to monitor the API health

Team has identified the issue. Right now we are seeing partial error rates on V1 across all APIs.

We have detected an issue with Order Creation. We are actively investigating. V1 order creation seems to be impacted. V2 seems healthy Next update in 15 minutes.

This incident has been resolved.

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

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

We have detected an issue with login to the Developer Portal. Team is actively investigating. Next update in 15 mins.

This incident has been resolved.

We are continuing to investigate this issue.

We are observing a dip in marketplace order volume and the team is investigating the issue.

This incident has been resolved.

We are continuing to investigate this issue.

Mx Portal and Business Manage App are unable to view the Order Details side-pane which includes all order information. Order creation is not impacted.

From 4:46 PM to 5:24 PM PDT on September 6, 2024, up to 40% of users \(Cx, Mx, Dx\) experienced intermittent access issues with DoorDash services, impacting the Marketplace and Drive. A critical failure occurred in one of the core backend services which resulted in errors and failed requests for login, order placements, and other functionalities. We have introduced more isolation of our critical workflows and tightened up our configuration to prevent these type of issues.

System looks good as of now. Traffic should be back to normal.

Team made the changes to resolve the Issue. Team is Monitoring.

Team made the changes to resolve the Issue. Team is Monitoring.

Identified the Issue team is trying to resolve the Issue

We have detected an issue with the orders functionality. We are investigating.

Due to a third party infra outage, we were observing partial outage on Drive delivery APIs between 7:30 PM CT to 10:15 PM CT. We are not recovered.

This incident has been resolved.

We have recovered. Drive Order Creation is operational.

Issue has been resolved and is recovering. Engineer team is actively monitoring to confirm full recovery.

We are working to mitigate the issue. Impact has been identified to be minor.

- Drive Order Fulfillment is not affected. - We are seeing issues with order creation. - Order Creation is degraded but NOT a hard down. - Issue has been identified and mitigation is happening.

On August 29th from 1:32 AM PT to 3:26 AM PT approximately 50% of orders were not able to be processed. Marketplace, Drive, and Storefront services were impacted during this window. The incident was triggered by an AWS network connectivity failure in a single region. This issue was resolved by AWS on August 29 at 3:26 AM PT and they do not expect a recurrence.

This incident has been resolved.

We are seeing recovery, and the team is active monitoring.

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

We are seeing an issue with the AWS infra and are actively working on it.

We are currently investigating this issue.

On 8/18 \(12:17 - 12:20 PDT and 20:35 - 20:39 PDT\) and 8/19 \(06:07 - 07:30 PDT\), DoorDash experienced issues with point of sale \(POS\) order transmission, resulting in merchants not receiving POS orders and failures to cancel orders. Additionally, financial and tax transaction workflows were delayed by 6\+ hours, but all transactions were successfully processed once the incident was resolved. The incident was caused due to unhealthy storage nodes from some of our clusters supporting these processes. The vendor hosting our storage instances identified an issue with the hardware used for our nodes. To fully resolve and help prevent the issue from reoccurring, our vendor is also upgrading to more performant and reliable hardware. We've identified and are implementing improvements to our observability and escalation processes with the vendor to prevent future incidents.

This incident has been resolved.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

The issue should be mitigated and we are monitoring the results.

We are continuing to investigate this issue.

We are currently investigating this issue.

Between 4:41 PM PST to 5:10 PM PST on 7/02, DoorDash experienced an incident that affected one of the critical databases. The incident was caused by a bad database query that couldn’t be run efficiently and led to other queries on this database slowing down and eventually timing out. The issue affected all of DoorDash including Marketplace and Storefront orders and Drive deliveries. The incident was mitigated after the bad query was reverted and existing query executions terminated. Majority of the action items following this incident are focused on limiting the potential impact of bad queries on the overall health of our platform.

This incident has been resolved.

We are continuing to monitor for any further issues.

Marketplace order volume is back to normal, the team is continuing monitoring the recovery.

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

We are continuing to investigate this issue.

We are currently investigating this issue.

On 7/2/2024, a breaking change was deployed causing the DoorDash Restaurant store page fully unavailable for IOS users between 12:39 PT and 13:13 PT.  There were partial outages for the IOS app  from 11:45 PT to 12:39 PT,  and 13:13 PT to 13:32 PT, during the deployment of the breaking change, as well as during the rollback period. This caused the drop in marketplace order volume.  The team is working on a number of action items focused on preventing incidents like this from happening by introducing new guardrails against breaking contract changes, better observability and alerting for issues potentially caused by an ongoing deployment and making rollbacks quicker.

This incident has been resolved.

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

We have confirmed that this issue only affects restaurants and should not impact our retail and grocery partners. We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently investigating this issue.

On July 2nd from 4:40pm to 5:30pm PT DoorDash services were largely unavailable and fulfillment was degraded. This was caused by a configuration change to an internal system. The issue was partially mitigated at 5:05pm PT and error rates dropped for some endpoints. The issue was fully resolved and systems returned to normal at 5:30pm PT. We are taking steps to reduce the risk and impact of such config changes.

The issue with Order Fulfillment is now confirmed to be resolved. No further updates.

The issue with Order Creation and Fulfillment is resolved but we will continue to monitor. Next update in 15 minutes.

We are showing recovery across all endpoints, and order fulfillment is recovering. Next update in 15 minutes

We are continuing to work on a fix for this issue.

We have identified an issue with Order Creation and Fulfillment. We are actively working on a resolution. Next update in 15 minutes.

From June 28th 4:15pm to June 29th 3:29am PT, DoorDash Drive failed to geocode and validate up to 10% of addresses. As a result, Drive's order rejection rate increased across all order validation and creation endpoints. The incident was resolved once Google's geocoding incident was resolved. We are working to make our systems more resilient to geocoding failures.

The issue with Order Validation and Creation is now confirmed to be resolved. No further updates.

Google geocoding APIs had an issue which caused a lot of addresses to fail without state and country fields. This caused a lot of invalid_address errors on the Drive APIs. Google has updated that the issue is fixed on their end but would take a few hours for the changes to propagate to all regions. Teams are continuing to monitor the errors. This mostly impacts addresses which do not have a street number and instead pass the street corner as the address. This seems to be true for a lot of Australia addresses. We will follow up with an update in the morning. For more updates from Google: https://status.cloud.google.com/maps-platform/incidents/M8g1TTuS53SJDRzXDswS

We have detected an issue with Order Validation for a subset of requests. We are actively investigating.

On **July 02, 2024 at 19:09 \(UTC-7:00\)**, the IT CI team observed general site unavailability for [careers.doordash.com](http://careers.doordash.com). **July 02, 2024 at 19:28 \(UTC-7:00\)** service `externalcareers_externalcareers` reached steady state, returning the service experience to operational.

The site is available.

We are continuing to monitor for any further issues.

A fix has been implemented, and the IT team is evaluating performance of the site.

The IT team is investigating general unavailability of careers.doordash.com.

On 6/21/2024, between 6:40 AM PST and 7:21 AM PST, we experienced an issue with the Drive APIs resulting in degradation in Order Creation, and Updates. This issue was caused by an erroneous update at our traffic layer, which has since been resolved. The system remains healthy since 7:21 AM and we are taking appropriate actions to increase the resilience of our system to these types of events.

This incident has been resolved.

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

We have identified an issue with Order Creation and Fulfillment. We are actively working on a resolution. Next update in 15 minutes.

We have detected an issue with Order Creation and Fulfillment. We are actively investigating. Next update in 15 minutes.

This was a false alarm caused by a drop in a metric unrelated to our marketplace's health. Please disregard.

We have detected an issue with the orders functionality. We are investigating.

This incident has been resolved.

We are seeing partial failure for drive create delivery but retry should work. We identified the issue and mitigated it. Still monitoring the APIs.

This incident has been resolved.

Starting at 10:15 AM PST until 11:50am PST we observed issues accepting credit card payments for orders submitted with the request delivery form. During this time some orders may not have been created. Issue has been identified and we are seeing recovery now where we can accept credit card payments for these orders submitted via the request delivery form.

This incident has been resolved.

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

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

On 4/24/2024 between 7:10 and 7:50PM PST we experienced an issue with the Drive APIs and web surface areas resulting in degradation in Order Creation, Fulfillment, and Tracking. This issue was caused by an issue at our traffic layer, which has since been resolved. The system remains healthy since 7:50 PM and we are taking appropriate actions to increase the resilience of our system to these types of events.

This incident has been resolved. No further updates

We are seeing the system working as intended, however are continuing to monitor as we continue to tweak to maintain stability. As of now, deliveries should be able to be created, fulfilled, and tracked as intended.

We have identified the issue and are seeing early signs of recovery. Actively monitoring.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently seeing a degradation in Drive Order Creation, Fulfillment, and Webhooks across APIs and Drive Form. The team is actively investigating and mitigating impact. Updates to follow

On April 4th, Doordash experienced service degradation from 1:16 PM PST to 2:06 PM PST due to an issue with the traffic infrastructure. This issue affected our traffic routing fleet, resulting in connection failures for a certain percentage of incoming requests from Customers, Merchants, and Dashers on all platforms. We observed an increased error rate for Doordash Marketplace Orders, Storefront, and Drive Fulfillment as a result. To resolve the issue, we reverted the changes and allowed our traffic infrastructure to stabilize. We are also adding guardrails to ensure that similar changes are rolled out gradually and do not cause similar issues in the future.

This incident has been resolved.

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

We have identified the issue and working on mitigating. We are seeing partial recovery already.

We are continuing to investigate this issue.

We are continuing to investigate the issue. About 50% of traffic coming into Doordash seems to be impacted. Customer tracking pages and Merchant portal are also impacted in some regions.

We have detected an issue with Order Fulfillment and are actively investigating. Next update in 15 minutes.

There has been no issues observed after the fix has been implemented. This status is resolved.

A fix has been implemented and we are monitoring the results. Next update: 30 minutes.

The issue has been identified and we are applying a fix. Next update in 30 minutes, or when the issue has been mitigated.

We have detected an issue with some reports generated in Merchant Portal. We are actively investigating. Next update in 30 minutes.

This incident has been resolved.

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

We are currently investigating this issue.

As of now, the issue has been resolved and order health is back to normal.

We are currently experiencing order failures within Drive , Marketplace and Merchant Tablet for 10% of the requests. The engineering team has identified the issue and actively working to resolve it.

We were able to identify the traffic blocking rule and the issue is resolved now. Financial reports are downloadable now.

We have partial outage on Mx Portal financial reports. These reports are able to be generated but not downloadable. We are currently investigating the issue

This incident has been resolved.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

We have mitigated. We continue to monitor

The issue has been identified and team is working to mitigate.

We are currently investigating this issue.

The incident is now resolved. Customer tracking pages are back online.

Issue has been identified and mitigated Drive customer tracking pages are working now. We will continue to monitor.

Drive Customer tracking pages are down. We have identified the issue and fixing the issue right now. No impact to fulfillment and only the tracking page is impacted. Next update in 15 mins.

On March 4th DoorDash services were degraded from 5:53 PM PT to 6:15 PM PT. This was caused by a degradation of our edge provider which impacted external traffic coming to DoorDash. This caused elevated errors in DoorDash Marketplace and Drive Orders.

We experienced a degradation in API latency across Drive APIs between 5:58 pm PT and 6:15 pm PT due to issues with our DNS network provider. This issue has been resolved and no further updates will be provided.