Changes / Asana / Asana full outage for some users (2 hours, 25% outage)
Asana: Major incident: Asana full outage for some users (2 hours, 25% outage)
Summary
Asana reported a major full outage for some users (25% outage), affecting API, App and Mobile, including US components, from 2026-08-31 15:14 UTC to 2026-08-31 17:18 UTC (2 h 4 min). The postmortem attributed it to infrastructure changes and peak traffic exceeding cache scaling limits; user-facing symptoms recovered after configuration changes and a fix.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Asana full outage for some users (2 hours, 25% outage)
Before: not present
After: major
Before: not present
After: postmortem
Before: not present
After: 2026-08-31 15:14 UTC
Before: not present
After: 2026-08-31 17:18 UTC
Before: not present
After: API, App, Mobile, US - API, US - App, US - Mobile
Before: not present
After: We are investigating alerts for slow performance and application errors.
Before: not present
After: We are continuing to investigate the issue; we have reverted recent changes, and are working to identify the source of the errors.
Before: not present
After: We have made configuration changes and see partial recovery, but we continue to see some elevated errors.
Before: not present
After: We've applied a fix are seeing signs of recovery.
Before: not present
After: User-facing symptoms have recovered. We'll continue to monitor, and will prioritize a retrospective to understand and prevent similar incidents in the future.
Before: not present
After: 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.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Asana full outage for some users (2 hours, 25% outage) (this change) Asana reported a major full outage for some users (25% outage), affecting API, App and Mobile, including US components, from 2026-08-31 15:14 UTC to 2026-08-31 17:18 UTC (2 h 4 min). The postmortem attributed it to infrastructure changes and peak traffic exceeding cache scaling limits; user-facing symptoms recovered after configuration changes and a fix. | Major incident |