Asana full outage for some users (2 hours, 25% outage)
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.
The latest update from Asana.
State
Resolved
Started
62 d ago
2026-08-31 15:14 UTC
Lasted
2 h 4 min
until 2026-08-31 17:18 UTC
Worst impact
Partial outage
Timeline
6 updatesInvestigating
1 h 33 min 75%
Monitoring
31 min 25%
Updates
Times in UTCAs posted by Asana
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.
User-facing symptoms have recovered. We'll continue to monitor, and will prioritize a retrospective to understand and prevent similar incidents in the future.
We've applied a fix are seeing signs of recovery.
We have made configuration changes and see partial recovery, but we continue to see some elevated errors.
We are continuing to investigate the issue; we have reverted recent changes, and are working to identify the source of the errors.
We are investigating alerts for slow performance and application errors.
Affected components
3Asana in the last 90 days
Full historyIncidents in 90 days
9
Days with an incident
10
Median duration
50 min
This incident
2.5× the median
Other Asana incidents
All incidentsAsana·Background jobs partial outage
This incident has been resolved.
Asana·Asana downtime
**Incident:** An infrastructure update targeting security caused DynamoDB to become inaccessible across Asana's production environment. This change was related to a production isolation initiative, and was applied in a way that left all of our production services unable to use DynamoDB tables which we use for metadata and routing traffic. Once the change was reverted our services returned to normal operations. **Impact:** Asana services were completely unavailable for approximately 30 minutes, 2026-10-21 15:21 UTC-15:51 UTC, and mostly unavailable for a further 20 minutes, including 15:05 UTC-15:55 UTC. This also caused delay for background actions during the impact period; recovery after the end of the incident completed by 16:00 UTC. **Moving forward:** We are updating the deployment process to catch this class of error. We will be moving to an isolation system which allows more gradual rollout of similar changes, allowing us to detect misconfiguration in pre-production testing. Our
Asana·Partial API outage
This incident has been resolved.
Asana·Partial API outage in EU
The incident has been resolved.
Asana·Automations not running for EU users
This incident has been resolved.
Follow Asana
Your coding agent knows when Asana is down, and tells you when a failure is theirs, not yours. You can also get Asana incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "asana" and tell me if Asana has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=asana/feed subscribe https://outages.cc/feed.xml?providers=asanaFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane