Is DoorDash down?

Last checked 7m ago
Current status
DoorDash is up

No incidents right now.

Official status page: https://www.doordashstatus.com · Polled every 5 minutes · 16 components tracked

DoorDash is operational right now. Last checked 7m ago; the most recent incident resolved 51d ago.

Real-time DoorDash status, recent outages, and incident history — pulled directly from DoorDash's official status page at https://www.doordashstatus.com every 5 minutes. Pingoru tracks 16 DoorDash services and has captured 3 incidents in the last 90 days (97.92% uptime). Get email, Slack, Discord, or webhook alerts the moment DoorDash reports a new incident — free for 5 monitors, no credit card.

Users who monitor DoorDash also follow these No-Code services: Zapier Airtable Webflow Typeform IFTTT Vasion Bubble Skylight Coda AnyDesk View all 6,000+ providers
DoorDash uptime 97.92% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Jul 24, 2026, 05:15 PM UTC · Resolved Jul 24, 2026, 11:00 AM UTC
    Timeline · 1 update
    • resolved · Jul 24, 2026, 05:15 PM UTC

      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.

    Latest: 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…

  2. Resolved 2h 41m
    Started Jun 28, 2026, 10:33 PM UTC · Resolved Jun 29, 2026, 01:15 AM UTC
    OrdersMenu UpdatesDasher Status Updates
    Timeline · 7 updates
    • investigating · Jun 28, 2026, 10:33 PM UTC

      We are currently investigating this issue.

    • investigating · Jun 28, 2026, 10:44 PM UTC

      We are continuing to investigate this issue.

    • investigating · Jun 28, 2026, 10:45 PM UTC

      We are continuing to investigate this issue.

    • monitoring · Jun 29, 2026, 12:26 AM UTC

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

    • monitoring · Jun 29, 2026, 12:27 AM UTC

      We are continuing to monitor for any further issues.

    • resolved · Jun 29, 2026, 01:15 AM UTC

      This incident has been resolved.

    • postmortem · Jul 02, 2026, 12:20 AM UTC

      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.

    Latest: 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 …

  3. Resolved 2h 8m
    Started Jun 16, 2026, 02:14 PM UTC · Resolved Jun 16, 2026, 04:22 PM UTC
    Drive APIMx WebsitesDrive Order FulfillmentNative AppsDrive Delivery Tracking PageOnline Ordering (Storefront)Developer PortalMerchant PortalOrdersMerchant Tablet
    Timeline · 9 updates
    • 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.

    Latest: 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 re…

Outage history

Past 90 days · 3 incidents View full outage history →