Asana downtime

What to do

• Check whether you use Asana App, App, App, App and 12 more in us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 37m it lasted.

  Anything that failed between 2026-10-21 15:33 UTC and 2026-10-21 16:10 UTC may need a replay.

• Subscribe to Asana's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=asana works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Root cause

We have identified the cause of this outage and have initiated changes to address this.

Updates from Asana 5

1. identifiedOct 21, 2026, 3:33 PM UTC

   Asana services are currently experiencing a major service disruption. We have identified a likely cause and are working on applying a fix. This affects all services and all regions.

   provider

2. identifiedOct 21, 2026, 3:51 PM UTC

   We have identified the cause of this outage and have initiated changes to address this. We are seeing some signs of recovery, and will post an update once we've confirmed recovery.

   provider

3. identifiedOct 21, 2026, 4:08 PM UTC

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

   provider

4. resolvedOct 21, 2026, 4:10 PM UTC

   The fix has been applied. We have observed recovery of error rates and traffic, and believe this incident is now resolved. We will post a postmortem/RCA within 72 hours.

   provider

5. postmortemOct 24, 2026, 12:22 AM UTC

   **Incident:** An infrastructure update targeting security caused DynamoDB to become inaccessible across Asana's production environment. This change was related to a production isolation initiative, and was applied in a way that left all of our production services unable to use DynamoDB tables which we use for metadata and routing traffic. Once the change was reverted our services returned to normal operations.  **Impact:** Asana services were completely unavailable for approximately 30 minutes, 2026-10-21 15:21 UTC-15:51 UTC, and mostly unavailable for a further 20 minutes, including 15:05 UTC-15:55 UTC. This also caused delay for background actions during the impact period; recovery after the end of the incident completed by 16:00 UTC. **Moving forward:** We are updating the deployment process to catch this class of error. We will be moving to an isolation system which allows more gradual rollout of similar changes, allowing us to detect misconfiguration in pre-production testing. Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.