Skip to content
Asana · Apps and SaaSJan 22, 2026, 17:48 UTC

Asana webapp unavailable

CriticalCapacityUpdated 20h ago
Jan 22, 17:48 UTCJan 22, 19:00 UTC
Duration
1h 12m
Impact
Critical
Root cause
Capacity
Asana, 90 days
6 incidents
Affected
AppUS - AppEU - AppJapan - AppAustralia - AppMiddle East - App
Status page

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

  1. 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.
  2. Resolved · Jan 22, 19:00 UTC
    This incident has been resolved.
  3. 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.
  4. 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.
  5. 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.
  6. Investigating · Jan 22, 17:51 UTC
    We are continuing to investigate this issue.
  7. 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

Also caused by capacity and load

All
StartedIncidentDuration
Sep 2213:19 UTCWe are investigating an issue with CH servers in Azure germanywestcentral regionClickHouse5h 6m
Sep 1607:20 UTCDegradation with Gemini 3.8 FlashGitHub10h 28m
Sep 1509:47 UTCDisruption with some GitHub servicesGitHub1h 30m
Sep 422:02 UTCDegradation in repos contents APIGitHub21m
Sep 221:44 UTCElevated Linux worker queue timesExpo21m
Sep 115:00 UTCDelays in commit processingGitHub1h 1m

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.