Asana API Outage History

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

This incident has been resolved.

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.

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.

This incident has been resolved.

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.

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

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

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

We are continuing to investigate this issue.

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

We are continuing to investigate this issue.

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.

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

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.

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.

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.

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.

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

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.

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.

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.

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.

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

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

**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. After partial recovery within AWS, we made configuration changes and saw recovery for our traffic. We continued to observe while AWS worked through the incident on their side. The remaining impact on Asana's side is covered in [https://status.asana.com/incidents/lvtt14d4d80g](https://status.asana.com/incidents/lvtt14d4d80g) . **Impact:** We saw global downtime from 2025-10-20 06:52 UTC through 09:27 UTC, 2 hours and 35 minutes. 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.

This incident has been resolved; error rates and latency have gone down and we've caught up on existing traffic. We will publish a postmortem here within 72 hours.

The root cause has been fixed, and we are monitoring recovery; we still see somehow degraded performance in the US region, and are adjusting configuration to address this.

A fix has been implemented, and we are monitoring recovery.

We are working to prepare our systems to recover once AWS resolves DynamoDB issues in us-east-1.

We are continuing to work on this issue, and will update once we have an ETA for resolution. Also see https://health.aws.amazon.com/health/status for status on resolution for infrastructure issues.

We are continuing to work on this issue. AWS DynamoDB is disrupted, and this impacts our production services.

We are continuing to investigate this issue.

We are continuing to investigate this issue from our side, and waiting for an update from AWS.

We are still seeing full downtime, and are continuing investigation.

AWS is investigating errors in Virginia, per https://health.aws.amazon.com/health/status . We are continuing to investigate and will provide an update in 15 minutes.

We are currently investigating an issue which affects all services.

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.

**Incident**: A configuration change unintentionally blocked internal network access between application components. This change was identified as the cause of downtime and reverted.  **Impact**: The Asana App and API were unavailable for 24 minutes. App and API traffic recovered over the next 5 minutes, and Automations & Background Actions recovered over 10 minutes.  **Moving forward**: We have completed a redesign of our core application architecture to better protect our services from disruption by segmentation into independent sections, or "cells." We are considering ways we can leverage this architecture to roll out configuration changes like the one which triggered this incident more gradually and carefully across our systems to ensure safety & stability. 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.

All system appear to have recovered, with recovery starting around 12:14 UTC. We will publish a postmortem within 72 hours.

We are continuing to monitor for any further issues.

We have identified an issue causing errors starting around 11:50 UTC, and have reverted the change which caused this. We are monitoring to confirm recovery.

**Incident:** From June 5th, 2025 through June 17th we disabled MCP \(an opt-in API feature\) for maintenance to address a vulnerability. **Impact:** If your organization was using the MCP server and was impacted by this issue, we have already reached out to you directly with important details and next steps. **Moving forward:** We've fixed the the bug which was identified. As part of our remediation efforts, we reset all connections to the MCP server. This means you'll need to manually reconnect your Asana instance to the MCP server.

Asana's MCP server is now operational.

We anticipate the MCP server will be back online by June 17, 17:00 UTC. We'll provide another update at that time or when the server is redeployed. Thank you for your patience as we work through this issue.

We identified a bug affecting our Model Context Protocol (MCP) server. Our engineering team has resolved the underlying issue and is now working to reinstate the server. We will post another update shortly with a time estimate.

Asana's MCP server is undergoing maintenance. During this maintenance, MCP is unavailable to the customers who've opted-in.

We've paused upgrades for the remaining customer databases, and will complete the remaining upgrades after looking into why we saw more errors than expected.

We started upgrade processes for databases; these are proceeding, but some restarts are taking longer than expected. As a result some customers are encountering transient errors during this process. We expect each customer database upgrade to complete within a few minutes; and no data will be lost.

**Incident**: A configuration change triggered a bug affecting how internal systems process configuration data, leading to application downtime. The issue impacted internal server uptime, resulting in approximately 28 minutes of degraded service on March 25, 2025, from 22:32 UTC to 23:00 UTC \(3:32 PM to 4:00 PM PDT\). ‌ **Impact**: During the incident, customers experienced difficulties accessing Asana on web and mobile apps, including login failures and errors while using the application. Internal services gradually recovered after the problematic change was reverted. ‌ **Moving forward**: We are enhancing our configuration validation processes to prevent similar issues. Additional monitoring and safeguards are being introduced to ensure rapid identification and recovery from similar incidents. ‌ 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.

This incident has been resolved.

Our systems have recovered, and we are continuing to monitor.

Asana App and API had about 9 minutes of downtime due to a configuration error; a fix has been implemented, and we are observing for recovery.

This incident has been resolved. We are doing root cause analysis and will post an update within 72 hours.

We have scaled up affected infrastructure are continuing to monitor application health and metrics.

We are continuing to monitor for any further issues.

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

We saw a high rate of errors due to overload of internal infrastructure. We see partial recovery, and are continuing to investigate.

Incident: At 2025-02-06 15:37 UTC, a configuration change caused some of our servers to crash, leading to complete downtime for 20 minutes. We rolled back the configuration, but this event triggered a cascade failure in network routing components; our systems recovered over the next 30 minutes, with full recovery by 2025-02-06 16:30. Impact: Users were unable to use Asana during this event in all regions, with downtime including App, API, and Mobile. No customer data was lost. Moving forward: We have added validation to prevent a repeat of this issue, and are updating our networking components to avoid this form of cascade failure. We will be moving to staged configuration rollouts to identify this class of issue without causing downtime for customer traffic. 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.

This incident has been resolved.

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

We have identified a cause and are implemented a fix.

We are seeing elevated errors for App and API, and are investigating.

Incident: Starting at 2025-02-05 21:05 UTC, a configuration change caused a large increase in server logs, overloading logging infrastructure and causing server restarts. This caused cascade failure as other servers were overloaded. The configuration change was reverted, and our application recovered after the servers restarted, with recovery by around 2025-02-05 21:30. Impact: Users saw errors loading our application and loading data within the application. No customer data was lost. Moving forward: We have removed the source of logs which resulted in overload, and are improving monitoring and resilience of the system which triggered failure. We will also be moving to staged configuration rollouts to help reduce or avoid customer impact for similar issues. 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.

This incident has been resolved.

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

We have made configuration changes and are monitoring for recovery.

We are continuing to investigate this issue.

We are seeing a high rate of errors for the Asana application in the US region.

Incident: A gradual rollout changing Asana’s network routing resulted in certain internal requests for our non-North American clusters being misrouted. This caused sporadic errors loading information for users whose Asana domains are hosted in non-US clusters.  ‌ Impact: Users with SAML SSO configured saw intermittent errors when attempting to login to Asana between November 18, 11:02 UTC and November 19, 01:27 UTC. ‌ Moving forward: We are improving our internal monitoring to promptly identify issues with future networking changes and working to make our login flow more resilient to data loading errors.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 are currently investigating this issue.

From 7 AM - 3 PM UTC time, there was a problem with signing up to Asana. This issue has now been resolved, and users should be able to sign up again.

Our engineers have fixed the issue and Asana which cause global downtime for ~10 minutes and connectivity issues for a small subset of users for around an hour after that. Asana is now running normally for all our customers.

**Incident:** On 2024-10-10, between 01:23 and 02:31 UTC a software change caused overload to a shared resource, leading to application errors. The change was rolled back, with recovery for most users around 02:31 and full recovery by 02:39 UTC. **Impact:** Users were unable to start new sessions on the web and desktop apps, though mobile and existing sessions were unaffected. No data was lost. **Next Steps:** We will conduct a retrospective using the 5 Whys method to improve monitoring, tooling, and playbooks. We will also update our software to manage load more efficiently and reduce reliance on globally shared resources to prevent similar issues in the future. 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 have seen full resolution. We add a postmortem within 72 hours.

We are continuing to monitor for any further issues.

We have reverted the change, see recovery, and are monitoring.

Users who are attempting to open Asana are seeing errors. We believe this is due to a deployment, and we are reverting this change.

We expect that all user-visible impact has been resolved.

We are investigating issues which appear to include poor application performance followed by session crashes, affecting groups of users for approximately 15 minutes.

**Incident:** On 2024-08-01 at 14:09 UTC, an increased connection rate on a central database saturated the database’s ability to accept new connections. As a result, Asana became unavailable to users in all regions. In response, Asana engineers throttled traffic for automations, webhooks, and API, and were able to restore primary functionality of the Asana application at 15:01 UTC. The application continued to run with sporadic unavailability until 18:22 UTC, when the underlying cause of the increased connections was determined and disabled. At this point the application was fully operational, but asynchronous workloads such as automations and notifications were delayed due to the work enqueued while traffic was throttled. The incident was resolved when asynchronous work queues fully caught up at 19:39 UTC. **Impact:** From 14:09 UTC to 15:01 UTC, users were unable to access Asana through the web, mobile, or API. From 15:01 UTC to 18:22 UTC users could access Asana through the web and mobile, but experienced sporadic unavailability. Access to the API was restored gradually between 15:15 UTC and 15:58 UTC. From 15:01 UTC to 19:39 UTC users experienced delayed automations, background actions, webhooks, and event streams. No customer data was lost. **Moving forward:** We have reverted the change that caused the increased connections. We are adding monitoring to detect changes in database connection rates, so we can identify potential problems earlier. Beyond this, we will be replicating data from the central database to other databases to reduce the impact of any single database being overloaded.

This incident has been resolved.

We've identified the root cause and are monitoring our systems

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

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

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

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

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

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

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

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

We are investigating application issues related to overload, and will provide updates.

On 2024-07-26, a deployment of new code introduced a bug which caused delays for automations and background actions for a subset of our customers. Jobs were delayed between 00:55 and 12:30 UTC. We reverted this deployment, which allowed our system to catch up. Impact: During the incident, a subset of customers experienced delayed background actions, such as rules, email notifications, imports, and exports. For a small fraction of customers, during a 7-hour period, automations may not have executed as intended. Moving forward: We have identified the root cause of this particular bug and will improve our systems and processes to prevent it from happening in the future.

Incident: An off-peak routine update of our service handling new page loads caused us to deploy code that depended on an artifact that wasn't yet available. The net effect was that all traffic attempting to do a fresh page load was broken for 48 minutes from June 28 5:52 pm PT to June 28 6:39 pm PT. Impact: Asana was unavailable to new page loads, but existing sessions continued to work as normal. Moving forward: This incident involved interaction across teams and systems. Our postmortem of this event identified operational and tooling changes to reduce the likelihood of incidents -- and decrease the time to resolution. We have an ongoing [5 Whys](https://wavelength.asana.com/workstyle-ask-5-whys-to-get-to-the-root-of-any-problem/) analysis for this incident.

We've resolved the issue where some users were unable to load the Asana application. We're investigating the root cause. We apologize for the inconvenience.

Webhook subscriptions filtered to a specific story type (for example, comment_added) or a specific task type (approval, milestone, default_task) were dropped and not delivered between Friday June 7th, 2024, 1:16 AM (UTC) and Mon, Jun 10, 2024, 19:37 PM (UTC). A change in the data pipeline introduced this issue and has now been rolled back. We will share our plans to prevent similar issues after completing an analysis of the incident. Our engineers have fixed the issue and Asana is now running normally. Our sincere apologies for any inconvenience caused.

From approximately 2024-03-05 19:43 - 21:30 UTC (11:43 AM PST - 01:30 PM PST), some customers experienced connectivity issues from an external provider to AWS, resulting in errors loading the Asana application.

Analysis of errors and reports indicates this was limited to customers in California using a specific ISP; we are seeing recovery, and expect affected users should be able to connect now.

We are currently investigating reports that some users are unable to load the Asana application. This is affecting a subset of users. We will have an update by 2024-03-05 22:00 UTC. If you are reporting issues for this incident, please provide your location and ISP as part of the report.