Asana Outage History

Started Oct 21, 2026, 03:33 PM UTC· resolved Oct 21, 2026, 04:10 PM UTC

1. identified Oct 21, 2026, 03:33 PM UTC

   Asana services are currently experiencing a major service disruption. We have identified a likely cause and are working on applying a fix. This affects all services and all regions.

2. identified Oct 21, 2026, 03:51 PM UTC

   We have identified the cause of this outage and have initiated changes to address this. We are seeing some signs of recovery, and will post an update once we've confirmed recovery.

3. identified Oct 21, 2026, 04:08 PM UTC

   We are continuing to work on a fix for this issue.

4. resolved Oct 21, 2026, 04:10 PM UTC

   The fix has been applied. We have observed recovery of error rates and traffic, and believe this incident is now resolved. We will post a postmortem/RCA within 72 hours.

Read the full incident report →

Started Sep 30, 2026, 02:31 PM UTC· resolved Sep 30, 2026, 03:21 PM UTC

1. investigating Sep 30, 2026, 02:31 PM UTC

   We are currently investigating this issue.

2. identified Sep 30, 2026, 03:09 PM UTC

   We are currently seeing system recovery and are actively monitoring the situation to ensure a full recovery.

3. resolved Sep 30, 2026, 03:21 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 29, 2026, 12:14 PM UTC· resolved Sep 29, 2026, 03:25 PM UTC

1. investigating Sep 29, 2026, 12:14 PM UTC

   We are currently investigating the issue.

2. resolved Sep 29, 2026, 03:25 PM UTC

   The incident has been resolved.

Read the full incident report →

Started Sep 21, 2026, 02:59 PM UTC· resolved Sep 21, 2026, 04:10 PM UTC

1. identified Sep 21, 2026, 02:59 PM UTC

   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.

2. identified Sep 21, 2026, 03:00 PM UTC

   We are continuing to work on a fix for this issue.

3. monitoring Sep 21, 2026, 03:39 PM UTC

   We're currently working our way through the backlog of automations that did not run.

4. resolved Sep 21, 2026, 04:10 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 17, 2026, 02:36 PM UTC· resolved Sep 17, 2026, 03:13 PM UTC

1. investigating Sep 17, 2026, 02:36 PM UTC

   We received an alert for unusual slow performance in several regions. We're investigating.

2. investigating Sep 17, 2026, 03:12 PM UTC

   We are continuing to investigate this issue.

3. resolved Sep 17, 2026, 03:13 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Sep 02, 2026, 06:08 PM UTC· resolved Sep 02, 2026, 06:49 PM UTC

1. investigating Sep 02, 2026, 06:08 PM UTC

   We are currently investigating this issue.

2. investigating Sep 02, 2026, 06:13 PM UTC

   We are continuing to investigate this issue.

3. investigating Sep 02, 2026, 06:14 PM UTC

   The rollback seems to have completely resolved errors. We're monitoring closely, but users should be able to access Asana again.

4. monitoring Sep 02, 2026, 06:14 PM UTC

   A fix has been implemented and we are monitoring the results.

5. resolved Sep 02, 2026, 06:49 PM UTC

   This incident has been resolved.

6. postmortem Sep 04, 2026, 07:52 PM 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._

Read the full incident report →

Started Aug 31, 2026, 03:14 PM UTC· resolved Aug 31, 2026, 05:18 PM UTC

1. investigating Aug 31, 2026, 03:14 PM UTC

   We are investigating alerts for slow performance and application errors.

2. investigating Aug 31, 2026, 03: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.

3. investigating Aug 31, 2026, 04:24 PM UTC

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

4. monitoring Aug 31, 2026, 04:47 PM UTC

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

5. resolved Aug 31, 2026, 05: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.

6. postmortem Sep 02, 2026, 09: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.

Read the full incident report →

Started Aug 04, 2026, 03:25 PM UTC· resolved Aug 05, 2026, 03:51 AM UTC

1. resolved Aug 06, 2026, 05:24 PM UTC

   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.

Read the full incident report →

Started Jul 07, 2026, 06:49 PM UTC· resolved Jul 07, 2026, 07:24 PM UTC

1. identified Jul 07, 2026, 06:49 PM UTC

   We are seeing errors for part (about 10%) of users in US for the Asana webapp. We've identified the root cause and are working on identifying a resolution.

2. monitoring Jul 07, 2026, 07:12 PM UTC

   We have implemented a mitigation and are monitoring to ensure recovery.

3. monitoring Jul 07, 2026, 07:21 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Jul 07, 2026, 07:24 PM UTC

   This incident has been resolved.

5. postmortem Jul 08, 2026, 09:28 PM UTC

   **Incident**: A configuration change inadvertently removed a critical resource required by one of our services. While existing infrastructure continued to operate normally, newly scaled infrastructure could not become ready. As morning traffic increased, there was a growing gap between incoming requests and our system's capacity to handle them, resulting in service degradation. We resolved the issue by manually restoring the missing resource and correcting the configuration change that caused its removal. ‌ **Impact**: For approximately 1.5 hours, a subset of customers experienced a full outage of our web application and desktop applications. During this time, affected users were unable to access Asana. No customer data was lost. ‌ **Moving forward**: We are implementing additional safeguards in our configuration management process to prevent critical resources from being inadvertently removed. We are also enhancing our monitoring systems to detect degradation earlier, before it impacts customer access. ‌ 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.

Read the full incident report →

Started Apr 21, 2026, 05:00 PM UTC· resolved Apr 22, 2026, 11:00 AM UTC

1. resolved Apr 29, 2026, 11:19 PM UTC

   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.

2. postmortem Apr 30, 2026, 12:43 AM UTC

   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**.

Read the full incident report →

Started Apr 20, 2026, 05:00 PM UTC· resolved Apr 21, 2026, 11:00 AM UTC

1. resolved Apr 29, 2026, 11:09 PM UTC

   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.

2. postmortem Apr 30, 2026, 12:34 AM UTC

   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**.

Read the full incident report →

Started Mar 26, 2026, 03:03 PM UTC· resolved Mar 26, 2026, 06:34 PM UTC

1. investigating Mar 26, 2026, 03:03 PM UTC

   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.

2. monitoring Mar 26, 2026, 03:50 PM UTC

   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.

3. resolved Mar 26, 2026, 06:34 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 01, 2026, 08:31 PM UTC· resolved Mar 15, 2026, 05:58 AM UTC

1. investigating Mar 01, 2026, 08:31 PM UTC

   Asana remains accessible to customers in the ME region, but we are seeing backends impacted by an AWS ME outage. If that isn't resolved soon, we expect to see some performance degradation and possible outages of the Asana application. This is only for the ME region; other regions are unaffected.

2. investigating Mar 01, 2026, 09:02 PM UTC

   We are continuing to investigate this issue.

3. investigating Mar 01, 2026, 09:03 PM UTC

   We no longer see impact on our servers. We're monitoring, as the AWS incident has not resolved.

4. investigating Mar 02, 2026, 09:02 AM UTC

   We are continuing to investigate this issue.

5. investigating Mar 02, 2026, 09:05 AM UTC

   We are seeing major impact in the ME region making Asana services unavailable to users whose data is stored in that region. We have taken steps to avoid additional loss of EC2 resources, but are continuing to see high error rates. This cause is AWS incidents affecting the infrastructure (az1 and az3) in the Middle East region: https://health.aws.amazon.com/health/status

6. investigating Mar 02, 2026, 10:27 AM UTC

   We are still seeing major impact in the ME region making Asana services unavailable to users whose data is stored in that region. We are continuing to monitor the situation. The cause is AWS incidents affecting the infrastructure in the Middle East region: https://health.aws.amazon.com/health/status

7. investigating Mar 02, 2026, 12:03 PM UTC

   We are still seeing major impact in the ME region making Asana services unavailable to users whose data is stored in that region. We are continuing to monitor the situation. The cause is widespread AWS incidents affecting the infrastructure in the Middle East region: https://health.aws.amazon.com/health/status

8. monitoring Mar 13, 2026, 06:44 PM UTC

   A small number of users were affected by the AWS outage in UAE (me-central-1); following AWS's recommendations, we have moved processing to other regions, and believe there is no user impact.

9. resolved Mar 15, 2026, 05:58 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 05, 2026, 11:49 PM UTC· resolved Feb 05, 2026, 11:58 PM UTC

1. monitoring Feb 05, 2026, 11:49 PM UTC

   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.

2. resolved Feb 05, 2026, 11:58 PM UTC

   Our engineers have rolled back recent changes to our primary monitoring systems, and our API and mobile systems are fully operational.

Read the full incident report →

Started Jan 26, 2026, 03:01 AM UTC· resolved Jan 26, 2026, 03:29 AM UTC

1. investigating Jan 26, 2026, 03:01 AM UTC

   We are investigating an elevated rate of API errors as well as delays reflecting changes for the App in EU.

2. monitoring Jan 26, 2026, 03:19 AM UTC

   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.

3. monitoring Jan 26, 2026, 03:20 AM UTC

   We are continuing to monitor for any further issues.

4. resolved Jan 26, 2026, 03:29 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 22, 2026, 05:48 PM UTC· resolved Jan 22, 2026, 07:00 PM UTC

1. investigating Jan 22, 2026, 05:48 PM UTC

   We're investigating an outage, it looks like no one is able to reach the Asana webapp.

2. investigating Jan 22, 2026, 05:51 PM UTC

   We are continuing to investigate this issue.

3. investigating Jan 22, 2026, 05:59 PM UTC

   We've identified the cause and have rolled back. Based on our monitoring, we should be recovered for some users.

4. investigating Jan 22, 2026, 06:04 PM UTC

   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.

5. investigating Jan 22, 2026, 06:38 PM UTC

   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.

6. resolved Jan 22, 2026, 07:00 PM UTC

   This incident has been resolved.

7. postmortem Jan 27, 2026, 07:53 AM UTC

   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.

Read the full incident report →

Started Jan 06, 2026, 12:00 AM UTC· resolved Jan 06, 2026, 12:00 AM UTC

1. resolved Jan 06, 2026, 02:17 PM UTC

   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.

Read the full incident report →

Started Jan 05, 2026, 09:17 PM UTC· resolved Jan 05, 2026, 09:50 PM UTC

1. investigating Jan 05, 2026, 09:17 PM UTC

   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.

2. monitoring Jan 05, 2026, 09:29 PM UTC

   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.

3. resolved Jan 05, 2026, 09:50 PM UTC

   Thank you for your patience. Service is fully restored, and the Asana web app is back to normal functionality.

Read the full incident report →

Started Nov 18, 2025, 05:00 PM UTC· resolved Nov 18, 2025, 05:00 PM UTC

1. resolved Nov 24, 2025, 08:28 PM UTC

   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.

Read the full incident report →

Started Nov 18, 2025, 11:20 AM UTC· resolved Nov 18, 2025, 02:20 PM UTC

1. resolved Nov 18, 2025, 10:14 PM UTC

   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.

2. postmortem Nov 21, 2025, 12:29 AM UTC

   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.

Read the full incident report →

Started Nov 07, 2025, 09:22 PM UTC· resolved Nov 07, 2025, 10:08 PM UTC

1. identified Nov 07, 2025, 09:22 PM UTC

   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!

2. identified Nov 07, 2025, 09:24 PM UTC

   We are continuing to work on a fix for this issue.

3. identified Nov 07, 2025, 09:39 PM UTC

   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.

4. monitoring Nov 07, 2025, 09:56 PM UTC

   Functionality to the Asana webapp is now restored. We are still experiencing errors in the API, and are working to resolve them.

5. monitoring Nov 07, 2025, 09:59 PM UTC

   We are continuing to monitor for any further issues.

6. monitoring Nov 07, 2025, 10:03 PM UTC

   We are continuing to monitor for any further issues.

7. resolved Nov 07, 2025, 10:08 PM UTC

   The incident is now resolved.

8. postmortem Nov 12, 2025, 05:15 PM UTC

   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.

Read the full incident report →

Started Oct 31, 2025, 04:17 PM UTC· resolved Oct 31, 2025, 05:18 PM UTC

1. investigating Oct 31, 2025, 04:17 PM UTC

   We are currently investigating the issue.

2. identified Oct 31, 2025, 04:28 PM UTC

   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.

3. monitoring Oct 31, 2025, 05:05 PM UTC

   We have identified the source of load and addressed it, and are monitoring recovery.

4. resolved Oct 31, 2025, 05:18 PM UTC

   This incident has been resolved. During the incident, users in EU experienced slow application performance, and automations, webhooks, and background actions were delayed.

Read the full incident report →

Started Oct 20, 2025, 02:28 PM UTC· resolved Oct 20, 2025, 08:34 PM UTC

1. identified Oct 20, 2025, 02:28 PM UTC

   We are currently investigating an issue which affects about 10% of our users, this is a continuation of the AWS outage that happened earlier today

2. identified Oct 20, 2025, 03:07 PM UTC

   We are still working on fixing the issue, this is affecting most of our users

3. identified Oct 20, 2025, 04:55 PM UTC

   We are continuing to work on resolving the issue impacting access to Asana. This outage is related to the ongoing AWS service disruption, which is affecting many applications and customers globally (https://health.aws.amazon.com/health/status). Our team is closely monitoring AWS recovery efforts and will restore full functionality as soon as possible.

4. identified Oct 20, 2025, 06:43 PM UTC

   We are continuing to work on restoring access to Asana. This outage is related to the ongoing AWS service disruption, which is affecting many applications and customers globally (https://health.aws.amazon.com/health/status). Our engineers are actively deploying mitigation strategies to restore Asana functionality and reduce our reliance on affected services. We're observing some recovery in foundational infrastructure, and are working towards restoring core app functionality.

5. monitoring Oct 20, 2025, 07:54 PM UTC

   Asana is functional again. We’ve begun re-enabling API traffic and are gradually allowing traffic from all clients. Most functionality is coming back online, though some users may still experience intermittent errors or slower performance while systems stabilise.

6. resolved Oct 20, 2025, 08:34 PM UTC

   Asana is now fully operational, and all services are performing normally. API traffic and client access have been fully restored, and we’re no longer seeing elevated error rates or latency. This incident was related to an earlier AWS service disruption. We’ll continue to monitor performance closely, but Asana is back to normal.

7. postmortem Oct 23, 2025, 04:07 PM UTC

   **Incident:** AWS infrastructure had [an outage affecting core services](https://aws.amazon.com/message/101925/), which our application depends on, in the Virginia \(us-east-1\) region. The initial impact to our services is covered by [https://status.asana.com/incidents/zfdtyvckl5k2](https://status.asana.com/incidents/zfdtyvckl5k2); this covers the second major impact to our services. **Impact:** Starting at 2025-10-20 14:58 UTC, our application was down for approximately 10% of our users. By 15:08 UTC the application was completely down for all users We saw some improvement in internal error rates around 17:06 UTC resulting in intermittent availability. We did not see full infrastructure recovery until approximately 19:50 UTC and our traffic fully recovered by 20:29 UTC. This affected all regions because we store some global state and shared application configuration in the Virginia region. **Moving forward:** We are working on ways to reduce the impact of single region outages, including for this region, to limit the impact and improve options for recovery. 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.

Read the full incident report →

Started Oct 13, 2025, 03:44 PM UTC· resolved Oct 13, 2025, 04:33 PM UTC

1. resolved Oct 13, 2025, 08:56 PM UTC

   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.

Read the full incident report →

Started Oct 02, 2025, 12:00 PM UTC· resolved Oct 02, 2025, 12:00 PM UTC

1. resolved Oct 06, 2025, 06:33 PM UTC

   One of our infrastructure services that we use to run the customer provided script was failing to start up for some workspaces. This was an unintended consequence of us rolling out improved security controls. We've mitigated this by deploying a previously working version for the service and will continue to investigate why this happened.

Read the full incident report →