Asana webapp unavailable
Final update
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.
Timeline
- Postmortem · Jan 27, 07:53 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.
- Resolved · Jan 22, 19:00 UTC
This incident has been resolved.
- Investigating · Jan 22, 18:38 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.
- Investigating · Jan 22, 18:04 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.
- Investigating · Jan 22, 17:59 UTC
We've identified the cause and have rolled back. Based on our monitoring, we should be recovered for some users.
- Investigating · Jan 22, 17:51 UTC
We are continuing to investigate this issue.
- Investigating · Jan 22, 17:48 UTC
We're investigating an outage, it looks like no one is able to reach the Asana webapp.
More from Asana
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 2114:59 UTC | Automations not running for EU users | minor | 1h 10m |
| Sep 1714:36 UTC | Slow performance for a subset of Asana users | minor | 36m |
| Sep 218:08 UTC | We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment. | major | 42m |
| Aug 3115:14 UTC | Asana full outage for some users (2 hours, 25% outage) | major | 2h 4m |
| Aug 415:30 UTC | Webhooks and event streams partial data loss | minor | 0m |
| Jul 718:49 UTC | Errors loading the Asana web app for some users in US | major | 35m |
Also caused by capacity and load
All| Started | Vendor | Incident | Impact | Duration |
|---|---|---|---|---|
| Sep 2213:19 UTC | We are investigating an issue with CH servers in Azure germanywestcentral region | minor | 5h 6m | |
| Sep 1607:20 UTC | Degradation with Gemini 3.8 Flash | major | 10h 28m | |
| Sep 1509:47 UTC | Disruption with some GitHub services | minor | 1h 30m | |
| Sep 422:02 UTC | Degradation in repos contents API | minor | 21m | |
| Sep 221:44 UTC | Elevated Linux worker queue times | minor | 21m | |
| Sep 115:00 UTC | Delays in commit processing | minor | 1h 1m |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.