Asana

Affected: App, App, App, App, API, API, API, API, Mobile, Mobile, Mobile, Mobile, Automations and Background Actions, Automations and Background Actions, Automations and Background Actions, Automations and Background Actions

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-10-21 15:33 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 2026-10-21 15:51 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 2026-10-21 16:08 UTC

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

4. resolved 2026-10-21 16:10 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.

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, App, App, App, App, API, API, API, API, API, Mobile, Mobile, Mobile, Mobile, Mobile, Automations and Background Actions, Automations and Background Actions, Automations and Background Actions, Automations and Background Actions, Automations and Background Actions, Webhooks and Event Streams, Webhooks and Event Streams, Webhooks and Event Streams, Webhooks and Event Streams, Webhooks and Event Streams, Notifications, Notifications, Notifications, Notifications, Notifications

1. investigating 2026-10-21 15:33 UTC

   We are currently investigating this issue.

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: API, Mobile

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-30 14:31 UTC

   We are currently investigating this issue.

2. identified 2026-09-30 15:09 UTC

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

3. resolved 2026-09-30 15:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: API

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-29 12:14 UTC

   We are currently investigating the issue.

2. resolved 2026-09-29 15:25 UTC

   The incident has been resolved.

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: Automations and Background Actions

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-09-21 14:59 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...

2. identified 2026-09-21 15:00 UTC

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

3. monitoring 2026-09-21 15:39 UTC

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

4. resolved 2026-09-21 16:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, App, API, API, Mobile, Mobile, Automations and Background Actions, Automations and Background Actions, Webhooks and Event Streams, Webhooks and Event Streams, Notifications, Notifications

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-17 14:36 UTC

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

2. investigating 2026-09-17 15:12 UTC

   We are continuing to investigate this issue.

3. resolved 2026-09-17 15:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, API, Mobile

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-09-02 18:08 UTC

   We are currently investigating this issue.

2. investigating 2026-09-02 18:13 UTC

   We are continuing to investigate this issue.

3. investigating 2026-09-02 18:14 UTC

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

4. monitoring 2026-09-02 18:14 UTC

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

5. resolved 2026-09-02 18:49 UTC

   This incident has been resolved.

6. postmortem 2026-09-04 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...

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, API, Mobile

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-31 15:14 UTC

   We are investigating alerts for slow performance and application errors.

2. investigating 2026-08-31 15:55 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 2026-08-31 16:24 UTC

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

4. monitoring 2026-08-31 16:47 UTC

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

5. resolved 2026-08-31 17:18 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 2026-09-02 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...

Excerpts are shortened. Read the full incident on Asana's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-08-04 15:30 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...

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-07-07 18:49 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 2026-07-07 19:12 UTC

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

3. monitoring 2026-07-07 19:21 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-07-07 19:24 UTC

   This incident has been resolved.

5. postmortem 2026-07-08 21:28 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...

Excerpts are shortened. Read the full incident on Asana's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-04-21 19:00 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 2026-04-30 00:43 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...

Excerpts are shortened. Read the full incident on Asana's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-04-20 17:00 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 2026-04-30 00:34 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...

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App

Failure mode: CDN or edge layer failed or served bad content. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-26 15:03 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 2026-03-26 15:50 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 2026-03-26 18:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, API, Mobile, Automations and Background Actions, Webhooks and Event Streams, Notifications

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

Started during AWS: Multiple services (UAE): Region Availability.

1. investigating 2026-03-01 20:31 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...

2. investigating 2026-03-01 21:02 UTC

   We are continuing to investigate this issue.

3. investigating 2026-03-01 21:03 UTC

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

4. investigating 2026-03-02 09:02 UTC

   We are continuing to investigate this issue.

5. investigating 2026-03-02 09:05 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...

6. investigating 2026-03-02 10:27 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:...

7. investigating 2026-03-02 12:03 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:...

8. monitoring 2026-03-13 18:44 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 2026-03-15 05:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: API, API, API, API, API, Mobile, Mobile, Mobile, Mobile, Mobile

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-02-05 23:49 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 2026-02-05 23:58 UTC

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

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, API, Mobile

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-26 03:01 UTC

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

2. monitoring 2026-01-26 03:19 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 2026-01-26 03:20 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-01-26 03:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, App, App, App, App

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-22 17:48 UTC

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

2. investigating 2026-01-22 17:51 UTC

   We are continuing to investigate this issue.

3. investigating 2026-01-22 17:59 UTC

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

4. investigating 2026-01-22 18:04 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 2026-01-22 18:38 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 2026-01-22 19:00 UTC

   This incident has been resolved.

7. postmortem 2026-01-27 07:53 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...

Excerpts are shortened. Read the full incident on Asana's status page.

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-01-06 00:00 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...

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, App, App, App

Failure mode: A code release introduced the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-05 21:17 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 2026-01-05 21:29 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 2026-01-05 21:50 UTC

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

Excerpts are shortened. Read the full incident on Asana's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-11-18 17:00 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.

Excerpts are shortened. Read the full incident on Asana's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. resolved 2025-11-18 11:30 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...

2. postmortem 2025-11-21 00:29 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...

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, API

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-11-07 21:22 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 2025-11-07 21:24 UTC

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

3. identified 2025-11-07 21:39 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 2025-11-07 21:56 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 2025-11-07 21:59 UTC

   We are continuing to monitor for any further issues.

6. monitoring 2025-11-07 22:03 UTC

   We are continuing to monitor for any further issues.

7. resolved 2025-11-07 22:08 UTC

   The incident is now resolved.

8. postmortem 2025-11-12 17:15 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...

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, API, Mobile, Automations and Background Actions, Webhooks and Event Streams, Notifications

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-31 16:17 UTC

   We are currently investigating the issue.

2. identified 2025-10-31 16:28 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 2025-10-31 17:05 UTC

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

4. resolved 2025-10-31 17:18 UTC

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

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, API, Mobile, Automations and Background Actions, Webhooks and Event Streams, Notifications

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2025-10-20 14:28 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 2025-10-20 15:07 UTC

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

3. identified 2025-10-20 16:55 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...

4. identified 2025-10-20 18:43 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...

5. monitoring 2025-10-20 19:54 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 2025-10-20 20:34 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...

7. postmortem 2025-10-23 16:07 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...

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, App, App, App, API, API, API, API, Mobile, Mobile, Mobile, Mobile, Automations and Background Actions, Automations and Background Actions, Automations and Background Actions, Automations and Background Actions, Webhooks and Event Streams, Webhooks and Event Streams, Webhooks and Event Streams, Webhooks and Event Streams, Notifications, Notifications, Notifications, Notifications

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-20 07:10 UTC

   We are currently investigating an issue which affects all services.

2. investigating 2025-10-20 07:15 UTC

   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.

3. investigating 2025-10-20 07:30 UTC

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

4. investigating 2025-10-20 07:43 UTC

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

5. investigating 2025-10-20 07:59 UTC

   We are continuing to investigate this issue.

6. investigating 2025-10-20 08:19 UTC

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

7. investigating 2025-10-20 08:32 UTC

   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.

8. investigating 2025-10-20 09:18 UTC

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

9. monitoring 2025-10-20 09:32 UTC

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

10. monitoring 2025-10-20 10:08 UTC

    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.

11. resolved 2025-10-20 10:23 UTC

    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.

12. postmortem 2025-10-23 16:05 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. After partial recovery within AWS, we made configuration changes and saw recovery for our...

Excerpts are shortened. Read the full incident on Asana's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-10-13 16:33 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.

Excerpts are shortened. Read the full incident on Asana's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-10-02 12:00 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...

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: Automations and Background Actions, Automations and Background Actions, Automations and Background Actions, Automations and Background Actions

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2025-08-18 01:01 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 2025-08-18 01:41 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 2025-08-18 02:43 UTC

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

4. postmortem 2025-08-20 00:02 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...

Excerpts are shortened. Read the full incident on Asana's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-07-25 01:15 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.

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, App, App, App, API, API, API, API, Mobile, Mobile, Mobile, Mobile, Automations and Background Actions, Automations and Background Actions, Automations and Background Actions, Automations and Background Actions

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2025-06-25 12:25 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 2025-06-25 12:30 UTC

   We are continuing to monitor for any further issues.

3. resolved 2025-06-25 12:35 UTC

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

4. postmortem 2025-06-27 22:20 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...

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: API, API, API, API

Failure mode: Security incident or emergency response to a vulnerability. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-06-05 17:51 UTC

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

2. monitoring 2025-06-16 20:45 UTC

   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.

3. monitoring 2025-06-16 23:54 UTC

   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.

4. resolved 2025-06-17 16:51 UTC

   Asana's MCP server is now operational.

5. postmortem 2025-06-17 16:52 UTC

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

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, App, App, App, API, API, API, API, Mobile, Mobile, Mobile, Mobile, Automations and Background Actions, Automations and Background Actions, Automations and Background Actions, Automations and Background Actions, Webhooks and Event Streams, Webhooks and Event Streams, Webhooks and Event Streams, Webhooks and Event Streams, Notifications, Notifications, Notifications, Notifications

Failure mode: A schema or data migration caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-04-25 22:42 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...

2. resolved 2025-04-25 23:44 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.

Excerpts are shortened. Read the full incident on Asana's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-04-08 22:47 UTC

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

2. postmortem 2025-04-16 22:47 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...

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, App, App, App, API, API, API, API

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. monitoring 2025-03-25 22:47 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 2025-03-25 23:05 UTC

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

3. resolved 2025-03-25 23:09 UTC

   This incident has been resolved.

4. postmortem 2025-03-27 19:37 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...

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, App, App, App, API, API, API, API

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-03-25 14:36 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 2025-03-25 14:43 UTC

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

3. monitoring 2025-03-25 14:44 UTC

   We are continuing to monitor for any further issues.

4. monitoring 2025-03-25 15:12 UTC

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

5. resolved 2025-03-25 15:28 UTC

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

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, App, App, App, API, API, API, API

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-02-06 15:38 UTC

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

2. identified 2025-02-06 15:52 UTC

   We have identified a cause and are implemented a fix.

3. monitoring 2025-02-06 16:02 UTC

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

4. resolved 2025-02-06 16:18 UTC

   This incident has been resolved.

5. postmortem 2025-02-07 22:47 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...

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, API

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-02-05 21:19 UTC

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

2. investigating 2025-02-05 21:22 UTC

   We are continuing to investigate this issue.

3. investigating 2025-02-05 21:34 UTC

   We have made configuration changes and are monitoring for recovery.

4. monitoring 2025-02-05 21:35 UTC

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

5. resolved 2025-02-05 21:54 UTC

   This incident has been resolved.

6. postmortem 2025-02-07 22:46 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...

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, API, Mobile, Automations and Background Actions, Webhooks and Event Streams

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-01-17 21:50 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...

2. identified 2025-01-17 21:51 UTC

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

3. monitoring 2025-01-17 22:05 UTC

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

4. resolved 2025-01-17 23:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, API, Mobile, Automations and Background Actions, Webhooks and Event Streams

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-12-03 00:09 UTC

   We are currently investigating this issue.

2. monitoring 2024-12-03 00:22 UTC

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

3. resolved 2024-12-03 00:55 UTC

   This incident has been resolved.

4. postmortem 2024-12-05 22:30 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...

Excerpts are shortened. Read the full incident on Asana's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-11-18 19:00 UTC

   We are currently investigating this issue.

2. postmortem 2024-11-22 22:45 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...

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, App, App, API, API, API, Mobile, Mobile, Mobile, Automations and Background Actions, Automations and Background Actions, Automations and Background Actions, Webhooks and Event Streams, Webhooks and Event Streams, Webhooks and Event Streams

Failure mode: Network, DNS, routing or connectivity failure. Root cause: Network or DNS. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2024-11-08 20:46 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 2024-11-08 20:48 UTC

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

3. monitoring 2024-11-08 20:55 UTC

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

4. resolved 2024-11-08 21:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, App, App, App

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-10-24 14:53 UTC

   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.

Excerpts are shortened. Read the full incident on Asana's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. resolved 2024-10-15 13:30 UTC

   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.

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, App, App, App

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-10-10 02:13 UTC

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

2. monitoring 2024-10-10 02:36 UTC

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

3. monitoring 2024-10-10 02:48 UTC

   We are continuing to monitor for any further issues.

4. resolved 2024-10-10 02:52 UTC

   We have seen full resolution. We add a postmortem within 72 hours.

5. postmortem 2024-10-11 23:13 UTC

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

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, App, App, App

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-09-16 18:56 UTC

   We've received reports of users unable to access the Asana web and desktop application and are currently investigating.

2. monitoring 2024-09-16 19:16 UTC

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

3. resolved 2024-09-16 19:38 UTC

   This incident has been resolved.

4. postmortem 2024-09-18 16:56 UTC

   Incident: An experimental flag was enabled that changed initial page loading behavior. With the flag enabled, users were inadvertently directed to load a code version that was not servable by all groups of servers. Subsequent requests would fail when requesting this incompatible...

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-08-20 15:32 UTC

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

2. resolved 2024-08-20 16:17 UTC

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

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, App, App, App, API, API, API, API, Mobile, Mobile, Mobile, Mobile, Automations and Background Actions, Automations and Background Actions, Automations and Background Actions, Automations and Background Actions, Webhooks and Event Streams, Webhooks and Event Streams, Webhooks and Event Streams, Webhooks and Event Streams

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2024-08-01 15:21 UTC

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

2. identified 2024-08-01 16:04 UTC

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

3. identified 2024-08-01 16:34 UTC

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

4. identified 2024-08-01 16:37 UTC

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

5. identified 2024-08-01 16:58 UTC

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

6. identified 2024-08-01 17:03 UTC

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

7. identified 2024-08-01 17:05 UTC

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

8. identified 2024-08-01 17:33 UTC

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

9. identified 2024-08-01 18:13 UTC

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

10. monitoring 2024-08-01 18:35 UTC

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

11. resolved 2024-08-01 19:49 UTC

    This incident has been resolved.

12. postmortem 2024-08-02 00:16 UTC

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

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: Automations and Background Actions, Automations and Background Actions

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2024-07-26 21:10 UTC

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

Excerpts are shortened. Read the full incident on Asana's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2024-07-01 22:30 UTC

   Some users were unable to connect to Asana; we investigated and have fixed the issue. We will post a postmortem with additional information.

2. postmortem 2024-07-15 22:48 UTC

   Incident: On 2024-07-01 22:30 UTC, changes related to ongoing work towards smaller, independent deployment environments resulted in an invalid configuration affecting approximately 18% of our customers in our US datacenter. Resolution was delayed due to an unrelated issue with...

Excerpts are shortened. Read the full incident on Asana's status page.

Failure mode: A code release introduced the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-06-28 17:50 UTC

   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.

2. postmortem 2024-07-09 20:47 UTC

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

Excerpts are shortened. Read the full incident on Asana's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2024-06-28 03:30 UTC

   Incident: On June 28, 2024 between 0334 and 0356 UTC, network maintenance was performed to remap internal endpoints, with unforecasted negative effects on communication between internal services. This caused a large amount of requests to Asana during the maintenance period to...

2. postmortem 2024-07-03 18:18 UTC

   **Incident**: On June 28, 2024 between 0334 and 0356 UTC, network maintenance was performed to remap internal endpoints, with unforecasted negative effects on communication between internal services. This caused a large amount of requests to Asana during the maintenance period...

Excerpts are shortened. Read the full incident on Asana's status page.

Affected: App, App, App, App, API, API, API, API

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-06-17 16:44 UTC

   We're currently experiencing some difficulties; as a result, a majority of our users are unable to access Asana. Our Development Team is currently working to resolve this issue as soon as possible. Sincere apologies for the inconvenience caused, please keep an eye on this page...

2. monitoring 2024-06-17 16:52 UTC

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

3. resolved 2024-06-17 19:49 UTC

   This incident has been resolved.

4. postmortem 2024-06-19 15:45 UTC

   Incident: Asana uses several load balancers to route incoming requests to the correct backend service. As our volume of traffic increased over time, these load balancers consumed more resources to handle the additional requests. High traffic pushed computing resource utilization...

Excerpts are shortened. Read the full incident on Asana's status page.