Asana had 23 outages in the last 2 years totaling 343h 42m of downtime — averaging 0.9 incidents per month.
There were 23 Asana outages since October 13, 2025 totaling 343h 42m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
We are currently seeing system recovery and are actively monitoring the situation to ensure a full recovery.
This incident has been resolved.
We are currently investigating the issue.
The incident has been resolved.
We've heard reports of rules and automations not running in the EU region. We've identified the source of the issue and fixed it for new automations triggers going forward. Our engineers are currently working on the backlog of automations that triggered and did not run during the incident.
We are continuing to work on a fix for this issue.
We're currently working our way through the backlog of automations that did not run.
This incident has been resolved.
We received an alert for unusual slow performance in several regions. We're investigating.
We are continuing to investigate this issue.
This incident has been resolved.
We are investigating alerts for slow performance and application errors.
We are continuing to investigate the issue; we have reverted recent changes, and are working to identify the source of the errors.
We have made configuration changes and see partial recovery, but we continue to see some elevated errors.
We've applied a fix are seeing signs of recovery.
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 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.
From 2026-08-04 15:25 UTC until 2026-08-06 03:51 UTC, Asana failed to send some events to registered webhooks and to return them in the event streams API. Apps which rely on this should refetch the underlying data from the Asana API. Existing webhooks and event streams will continue to function, but events from the incident window will not be sent. Most events with type `task` and action `changed` were dropped during this period. Other events are not affected. The root cause of the incident was traced to a code change which unintentionally dropped change events for most fields on the task type, and the change was reverted.
Between April 21st and April 23rd, many rules triggered by date time triggers did not run. New rule triggers ran normally starting April 23rd, and the delayed triggers were processed by April 27th.
Starting on **April 20th, 2026 at 10:00 AM PDT**, a combination of scaled-up background action jobs in the EU and a recent change to how date time trigger volume is managed overloaded the system that processes resource intensive background action jobs. This caused multi-hour delays in email and inbox notifications in the EU and prevented date time triggers from executing in all regions. Engineers were first alerted on **April 21st** by our monitoring systems, but did not recognize the full scope of the incident until **April 23rd**. On April 23rd, the change to manage date time trigger volume was reverted and the problematic background action jobs were isolated. All delayed notifications were sent by **April 24th, 11:30 AM PDT**, and all delayed date time triggers were executed by **April 27th, 4:00 AM PDT**.
Between April 20th and April 24th, 60% of email and inbox notifications were delayed by at least one hour in EU. Notifications were delayed up to 3 days. Other resource intensive background actions were also impacted at a lesser rate.
Starting on **April 20th, 2026 at 10:00 AM PDT**, a combination of scaled-up background action jobs in the EU and a recent change to how date time trigger volume is managed overloaded the system that processes resource intensive background action jobs. This caused multi-hour delays in email and inbox notifications in the EU and prevented date time triggers from executing in all regions. Engineers were first alerted on **April 21st** by our monitoring systems, but did not recognize the full scope of the incident until **April 23rd**. On April 23rd, the change to manage date time trigger volume was reverted and the problematic background action jobs were isolated. All delayed notifications were sent by **April 24th, 11:30 AM PDT**, and all delayed date time triggers were executed by **April 27th, 4:00 AM PDT**.
We have received reports that some users are unable to load Asana, especially in and around New York/the East Coast of the US, and have observed intermittent errors. We are investigating this, and will provide an update within an hour.
We believe that this was related to http3, and have disabled http3 for the affected CloudFront distribution. We believe Asana should now load after a hard refresh.
This incident has been resolved.
Our primary monitoring is observing an outage for our API and mobile services, but secondary monitoring indicates that API and mobile traffic is operating as usual. Our engineers are reviewing our primary monitoring and will provide updates on the situation.
Our engineers have rolled back recent changes to our primary monitoring systems, and our API and mobile systems are fully operational.
We are investigating an elevated rate of API errors as well as delays reflecting changes for the App in EU.
We have identified certain expensive workloads and reduced background processing to mitigate this. We see recovery in user facing services and are investigating the expensive workloads; user traffic is now working normally.
We are continuing to monitor for any further issues.
This incident has been resolved.
We're investigating an outage, it looks like no one is able to reach the Asana webapp.
We are continuing to investigate this issue.
We've identified the cause and have rolled back. Based on our monitoring, we should be recovered for some users.
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.
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.
This incident has been resolved.
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.
On January 6th, 2026 at UTC 12:00, we experienced an approximately 50-minute service disruption affecting customers in non-US regions. During this time, some requests may have failed or timed out. What Happened: During routine maintenance, we upgraded a core infrastructure component. While the upgrade itself completed as expected, some services did not successfully reconnect to the updated infrastructure. This led to temporary communication issues and degraded service in the affected regions. We apologize for the inconvenience and want to assure you that we are taking steps to help prevent similar issues in the future.
Users are currently unable to begin new sessions in the Asana web app. Our engineers are working to investigate and mitigate this issue as soon as possible. Existing web sessions are unaffected, along with mobile and API traffic.
Our engineers have identified and reverted the change preventing users from starting new Asana web app sessions. We're monitoring the situation to ensure recovery. The Asana web app is operational, and other services (mobile, API) are unaffected.
Thank you for your patience. Service is fully restored, and the Asana web app is back to normal functionality.
Resolved - We have fully resolved an incident related to a product permissions bug that briefly impacted some of our customers between November 18 and November 19. This issue was contained entirely within customer domains and did not expose any data externally.
Asana's MCP server experienced partial unavailability for three hours due to an upstream provider outage. No data loss or security issues occurred during this outage. This resulted in an increased rate of errors from 3:20 - 5:00 AM PT and some failed requests from 5:04 - 6:26 AM PT. The service fully recovered after the upstream provider resolved the issue.
Incident: [Cloudflare experienced an outage](https://blog.cloudflare.com/18-november-2025-outage/) that impacted the Workers KV service, a storage infrastructure service our MCP server relies on. This resulted in increased error rates and failed requests for a portion of our MCP traffic over the span of 3 hours. Impact: Approximately 100 users making requests to the MCP server received error responses or were unable to reach the server from 2025-11-18 11:20 UTC through 14:20 UTC. Moving forward: We are investing in our MCP Server to improve its resilience to KV store outages, and are investigating ways to reduce the overall impact of Cloudflare outages. 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.
We're currently experiencing a high volume of crashes for the Asana app. We've identified the cause and are actively working to resolve the issue. Thank you for your patience!
We are continuing to work on a fix for this issue.
The root cause has been addressed, and some sessions are starting to see recovery. We are taking action to speed up recovery across all regions.
Functionality to the Asana webapp is now restored. We are still experiencing errors in the API, and are working to resolve them.
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
The incident is now resolved.
We had approximately 1 hour of full downtime, where the Asana application was unavailable for most of our users. There was no data loss or security vulnerability. A routine configuration change affected the Asana application globally. While refactoring the configuration consumption, we missed an unintended side effect, causing the app to fail loading in all regions. We reverted the change and restarted servers for full recovery.
We are currently investigating the issue.
We’re currently experiencing increased system load. Our team has identified the source and is actively working to mitigate the impact. Thank you for your patience.
We have identified the source of load and addressed it, and are monitoring recovery.
This incident has been resolved. During the incident, users in EU experienced slow application performance, and automations, webhooks, and background actions were delayed.
From 15:44 - 16:33 UTC, Asana users may have seen stale data in the web app. In some cases, users may have experienced crashes and failed API requests.