Asana Outage History

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 →

Started Aug 18, 2025, 01:01 AM UTC· resolved Aug 18, 2025, 02:43 AM UTC

1. identified Aug 18, 2025, 01:01 AM UTC

   Asana is currently observing delay for all automations and background actions. Engineers are currently taking steps to mitigate the impact of this delay, and are investigating further to address the root cause.

2. monitoring Aug 18, 2025, 01:41 AM UTC

   The root cause of automation delay has been addressed, and controls are in place for automations and background actions to catch up on overdue work. Our engineers are monitoring metrics for recovery, and we expect Asana to return to full functionality shortly.

3. resolved Aug 18, 2025, 02:43 AM UTC

   Automations and background actions are back to normal operations for all Asana users and customers.

4. postmortem Aug 20, 2025, 12:02 AM UTC

   **Incident**: Around 2025-08-17 23:35, a conflict occurred between two database management systems. For most Asana customers, database locks prevented execution of background actions, automations, and webhooks were delayed. **Impact**: Users experienced delays in asynchronous operations, including automations and webhooks. Core application functions remained available and operational throughout the incident. No customer data was lost. The incident lasted approximately 2 hours, after which delayed operations ran normally. **Moving forward**: Asana engineers completed an investigation into the root cause, and have implemented changes to prevent the conflict between these systems. We are also reviewing our upgrade and management processes to be resilient against 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.

Read the full incident report →

Started Jul 25, 2025, 01:15 AM UTC· resolved Jul 25, 2025, 01:32 AM UTC

1. resolved Jul 25, 2025, 01:52 AM UTC

   On 7/25/2025, between approximately 01:24 and 01:32 UTC, our inbound email system was completely down, which means that no emails from customers emailing Asana (e.g. at @mail.asana.com) were processed. No tasks or messages were created via email during that time.

Read the full incident report →

Started Jun 25, 2025, 12:25 PM UTC· resolved Jun 25, 2025, 12:35 PM UTC

1. monitoring Jun 25, 2025, 12:25 PM UTC

   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.

2. monitoring Jun 25, 2025, 12:30 PM UTC

   We are continuing to monitor for any further issues.

3. resolved Jun 25, 2025, 12:35 PM UTC

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

4. postmortem Jun 27, 2025, 10:20 PM UTC

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

Read the full incident report →

Started Apr 25, 2025, 10:42 PM UTC· resolved Apr 25, 2025, 11:44 PM UTC

1. monitoring Apr 25, 2025, 10:42 PM UTC

   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.

2. resolved Apr 25, 2025, 11:44 PM UTC

   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.

Read the full incident report →

Started Apr 08, 2025, 10:47 PM UTC· resolved Apr 08, 2025, 10:47 PM UTC

1. resolved Apr 16, 2025, 10:47 PM UTC

   From April 4th to April 8th, approximately 0.5% of users using SAML for authentication experienced errors during login.

2. postmortem Apr 16, 2025, 10:47 PM UTC

   **Incident:** From April 4 to April 8, 2025, a subset of users were blocked from logging in with SAML, despite no changes to their identity provider setup. We believe the root cause to be a combination of recent code changes upgrading our infrastructure. These changes inadvertently affected how SAML responses were processed. **Impact:** Approximately 0.5% of users who authenticate through SAML were unable to log in to their Asana accounts during this period. No customer data was lost or compromised, and users who do not use SAML were unaffected. Our Customer Support team worked with affected domains to restore access while we resolved the issue. **Moving forward:** Our existing monitors did not trigger for this incident, which led to an extended period of downtime. We are improving existing monitoring and increasing monitor coverage to allow us to detect and respond to authentication issues more quickly 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.

Read the full incident report →

Started Mar 25, 2025, 10:47 PM UTC· resolved Mar 25, 2025, 11:09 PM UTC

1. monitoring Mar 25, 2025, 10:47 PM UTC

   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.

2. monitoring Mar 25, 2025, 11:05 PM UTC

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

3. resolved Mar 25, 2025, 11:09 PM UTC

   This incident has been resolved.

4. postmortem Mar 27, 2025, 07:37 PM UTC

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

Read the full incident report →

Started Mar 25, 2025, 02:36 PM UTC· resolved Mar 25, 2025, 03:28 PM UTC

1. investigating Mar 25, 2025, 02:36 PM UTC

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

2. monitoring Mar 25, 2025, 02:43 PM UTC

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

3. monitoring Mar 25, 2025, 02:44 PM UTC

   We are continuing to monitor for any further issues.

4. monitoring Mar 25, 2025, 03:12 PM UTC

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

5. resolved Mar 25, 2025, 03:28 PM UTC

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

Read the full incident report →

Started Feb 06, 2025, 03:38 PM UTC· resolved Feb 06, 2025, 04:18 PM UTC

1. investigating Feb 06, 2025, 03:52 PM UTC

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

2. identified Feb 06, 2025, 03:57 PM UTC

   We have identified a cause and are implemented a fix.

3. monitoring Feb 06, 2025, 04:21 PM UTC

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

4. resolved Feb 06, 2025, 04:29 PM UTC

   This incident has been resolved.

5. postmortem Feb 07, 2025, 10:47 PM UTC

   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.

Read the full incident report →

Started Feb 05, 2025, 09:19 PM UTC· resolved Feb 05, 2025, 09:54 PM UTC

1. investigating Feb 05, 2025, 09:19 PM UTC

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

2. investigating Feb 05, 2025, 09:22 PM UTC

   We are continuing to investigate this issue.

3. investigating Feb 05, 2025, 09:34 PM UTC

   We have made configuration changes and are monitoring for recovery.

4. monitoring Feb 05, 2025, 09:35 PM UTC

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

5. resolved Feb 05, 2025, 09:54 PM UTC

   This incident has been resolved.

6. postmortem Feb 07, 2025, 10:46 PM UTC

   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.

Read the full incident report →

Started Jan 17, 2025, 09:50 PM UTC· resolved Jan 17, 2025, 11:39 PM UTC

1. investigating Jan 17, 2025, 09:50 PM UTC

   We are currently experiencing some difficulties; as a result, Asana might not be available for some of our customers. Our Development Team is currently investigating this issue and we're hoping to get it fixed as soon as possible. Sincere apologies for the inconvenience; if you're impacted by this issue, please keep an eye on this page for the latest updates.

2. identified Jan 17, 2025, 09:51 PM UTC

   The issue has been identified and a fix is being implemented.

3. monitoring Jan 17, 2025, 10:05 PM UTC

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

4. resolved Jan 17, 2025, 11:39 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Dec 03, 2024, 12:09 AM UTC· resolved Dec 03, 2024, 12:55 AM UTC

1. investigating Dec 03, 2024, 12:09 AM UTC

   We are currently investigating this issue.

2. monitoring Dec 03, 2024, 12:22 AM UTC

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

3. resolved Dec 03, 2024, 12:55 AM UTC

   This incident has been resolved.

4. postmortem Dec 05, 2024, 10:30 PM UTC

   Incident: During an automated deployment of new code, an error in an internal networking service caused several system components to retain stale network connections. This caused requests to fail across a portion of our European data center. Impact: Users in our European datacenter were unable to load the Asana web app between 2024-12-02 2340UTC and 2024-12-03 0050UTC. The mobile app, our developer API, and app integrations saw degraded performance and an inability to modify or add data to Asana. Existing sessions on the Asana web app were mostly unaffected by this incident. Moving forward: We are adjusting our configuration of the library responsible for incorrectly retaining connections to avoid similar issues in the future. Additionally, Asana is in the process of upgrading and simplifying our internal routing infrastructure. ‌ 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 18, 2024, 11:02 AM UTC· resolved Nov 19, 2024, 01:27 AM UTC

1. resolved Nov 22, 2024, 10:45 PM UTC

   We are currently investigating this issue.

2. postmortem Nov 22, 2024, 10:45 PM UTC

   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.

Read the full incident report →

Started Nov 08, 2024, 08:46 PM UTC· resolved Nov 08, 2024, 09:08 PM UTC

1. identified Nov 08, 2024, 08:46 PM UTC

   We are experiencing issues in regions other than the US due to a network issue. We've identified the problem and are working on a fix.

2. identified Nov 08, 2024, 08:48 PM UTC

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

3. monitoring Nov 08, 2024, 08:55 PM UTC

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

4. resolved Nov 08, 2024, 09:08 PM UTC

   This incident has been resolved.

Read the full incident report →