Asana webapp unavailable

What to do

• Check whether you use Asana App, App, App, App and 1 more. 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 1h 12m it lasted.

  Anything that failed between 2026-01-22 17:48 UTC and 2026-01-22 19:00 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.

Updates from Asana 7

1. investigatingJan 22, 2026, 5:48 PM UTC

   We're investigating an outage, it looks like no one is able to reach the Asana webapp.

   provider

2. investigatingJan 22, 2026, 5:51 PM UTC

   We are continuing to investigate this issue.

   provider

3. investigatingJan 22, 2026, 5:59 PM UTC

   We've identified the cause and have rolled back. Based on our monitoring, we should be recovered for some users.

   provider

4. investigatingJan 22, 2026, 6:04 PM UTC

   Error rates have dropped significantly, to about 2%. It's possible some users continue to see errors, but we expect most users to be able to use Asana.

   provider

5. investigatingJan 22, 2026, 6:38 PM UTC

   Our error rates are back to normal baseline, and we don't expect an immediate recurrence. We'll create a post-mortem in the next few days with more details, including what happened and how we plan to prevent this going forward.

   provider

6. resolvedJan 22, 2026, 7:00 PM UTC

   This incident has been resolved.

   provider

7. postmortemJan 27, 2026, 7:53 AM UTC

   Incident: On 2026-01-22 the Asana App and all associated services had a service disruption due to dependency on a shared database used for storing metadata. This was triggered by a code path which caused overload for that database, followed by request queuing, timeouts, and errors. Impact: From 17:33 - 17:57 UTC the Asana App and all associated services were unavailable. There was a further 14 minutes of partial downtime from 18:45 - 18:59 UTC affecting 10-20% of users, also triggered by dependency on this shared database. Moving forward: We immediately rolled back our application code and added resources for this database. Going forward we will continue to reduce dependency on this shared database for common paths to reduce risk, and monitor for unexpected resource usage. 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.