Asana full outage for some users (2 hours, 25% outage)

What to do

• Check whether you use Asana App, API, Mobile. 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 2h 4m it lasted.

  Anything that failed between 2026-08-31 15:14 UTC and 2026-08-31 17:18 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 6

1. investigatingAug 31, 2026, 3:14 PM UTC

   We are investigating alerts for slow performance and application errors.

   provider

2. investigatingAug 31, 2026, 3:55 PM UTC

   We are continuing to investigate the issue; we have reverted recent changes, and are working to identify the source of the errors.

   provider

3. investigatingAug 31, 2026, 4:24 PM UTC

   We have made configuration changes and see partial recovery, but we continue to see some elevated errors.

   provider

4. monitoringAug 31, 2026, 4:47 PM UTC

   We've applied a fix are seeing signs of recovery.

   provider

5. resolvedAug 31, 2026, 5:18 PM UTC

   User-facing symptoms have recovered. We'll continue to monitor, and will prioritize a retrospective to understand and prevent similar incidents in the future.

   provider

6. postmortemSep 2, 2026, 9:29 PM UTC

   We’ve been working to add a caching layer to our update pipeline, tuning it carefully and rolling it out gradually. On Wednesday, August 26 we enabled it for most use cases, and it initially performed well. On Monday, August 31, a combination of unrelated infrastructure changes and peak traffic pushed the cache past its scaling limits. Once that threshold was crossed, the cache became unusable, and many pods serving read traffic for the Asana application could no longer serve it. We mitigated the incident by reverting the system to use the previous, non-cached code path. The revert was successful, but recovery took longer than we would expect for this class of issue. A fuller analysis is underway. We will follow up with root causes, action items, and improvements, including why recovery took as long as it did. We were fully down for about 25% of our users, for 2 hours, 15 minutes.

   provider

Corrections

None so far.

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