Automations not running for EU users
Last updateresolvedSep 21 · 16:10 UTC
This incident has been resolved.
Reported by Asana on their status page.
checked Sep 23, 2026 10:53 PM UTC · Asana's official status page
Asana is up and running.
Asana is currently operational with all systems functioning normally.
All components operational
Email only. No password. No card.
Be the first to know
Statusfield watches Asana alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
Email only. No password. Free.
Asana incident history
4 reports published by Asana in the last 30 days
When Asana breaks, it is typically resolved in 1h 3m — median across 26 resolved incidents over 90 days.
September 21, 2026
September 17, 2026
Slow performance for a subset of Asana users
Last updateresolvedSep 17 · 15:13 UTC
This incident has been resolved.
Reported by Asana on their status page.
September 2, 2026
We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment.
Last updatepostmortemSep 4 · 19:52 UTC
Incident: An internal system responsible for automatically scaling backend server capacity in one of our compute clusters stopped replacing capacity that had been cycled out during routine maintenance. This caused a gradual reduction in available capacity over several hours. A subsequent deployment was activated with insufficient capacity, causing all new requests for that compute cluster to fail. To mitigate the impact, we reverted to a previous release revision, which still had sufficient capacity. Impact: For approximately 30 minutes, customers whose traffic was handled by this compute cluster saw full downtime; other customers were unaffected. No customer data was lost. Moving forward: We have added additional monitoring to detect this type of capacity-scaling failure much earlier, and have added safeguards to prevent deployments from shifting traffic before sufficient healthy capacity is confirmed. _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._
Reported by Asana on their status page.
August 31, 2026
Asana full outage for some users (2 hours, 25% outage)
Last updatepostmortemSep 2 · 21:29 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.
Reported by Asana on their status page.