Asana 장애 기록

1. 2026년 9월 2일 PM 6:08 UTCinvestigating

   우리는 현재이 문제를 조사하고 있습니다.

2. 2026년 9월 2일 PM 6:13 UTCinvestigating

   이 문제를 조사하고 있습니다.

3. 2026년 9월 2일 PM 6:14 UTCinvestigating

   롤백은 완전히 오류를 해결하는 것 같습니다. 우리는 밀접하게 감시하고, 그러나 사용자는 Asana에 다시 접근할 수 있어야 합니다.

4. 2026년 9월 2일 PM 6:14 UTCmonitoring

   수정이 구현되어 결과를 모니터링하고 있습니다.

5. 2026년 9월 2일 PM 6:49 UTCresolved

   이 사건은 해결되었습니다.

6. 2026년 9월 4일 PM 7:52 UTCpostmortem

   Incident: 자동적으로 우리의 compute 클러스터 중 하나에 있는 backend 서버 수용량을 사기를 책임지는 내부 체계는 일상적인 정비 도중 주기된 수용량을 대체했습니다. 이 몇 시간 동안 사용 가능한 용량에 유리한 감소를 발생. 이후의 배포는 충분한 용량으로 활성화되었으며, 모든 새로운 요청을 발생시키는 클러스터를 실패합니다. 충격을 완화하기 위해, 우리는 여전히 충분한 용량을 가지고 이전 릴리스 개정에 회신. 충격: 대략 30 분을 위해, 이 compute 송이 가득 차있는 가동불능시간에 의해 취급된 고객; 다른 고객은 unaffected. 고객 데이터가 손실되지 않았습니다. 앞으로 이동: 우리는 수용량 확장 실패의 이 유형을 검출하기 위하여 추가한 감시를 매우 일찍 추가하고, 충분한 건강한 수용량이 확인되기 전에 교통에서 배치를 방지하기 위하여 더 안전한 보호가 추가했습니다. Our 메트릭은 각 데이터 센터에서 사용자 경험한 가동 시간의 평균을 고려합니다. 가동 시간의 수는 이 무게를 다는 평균을 반영합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 31일 PM 3:14 UTCinvestigating

   우리는 느린 성능과 애플리케이션 오류에 대한 경고를 조사하고 있습니다.

2. 2026년 8월 31일 PM 3:55 UTCinvestigating

   우리는 문제를 조사하기 위해 계속된다; 우리는 최근의 변경을 회귀하고, 오류의 소스를 확인하기 위해 노력하고있다.

3. 2026년 8월 31일 PM 4:24 UTCinvestigating

   우리는 구성 변경을하고 부분 복구를 볼 수 있지만, 우리는 계속 몇 가지 높은 오류를 볼 수 있습니다.

4. 2026년 8월 31일 PM 4:47 UTCmonitoring

   우리는 수정을 적용하고 복구 표지판을 볼 수 있습니다.

5. 2026년 8월 31일 PM 5:18 UTCresolved

   사용자의 증상이 회복되었습니다. 우리는 모니터링을 계속하고 미래에 유사한 사건을 이해하고 방지하기 위해 복고풍을 우선합니다.

6. 2026년 9월 2일 PM 9:29 UTCpostmortem

   우리는 우리의 갱신 파이프라인에 캐싱 층을 추가하기 위하여 일하고, 주의깊게 조정하고 점차적으로 구르기. 수요일, 8 월 26 일 우리는 대부분의 사용 사례를 활성화하고 처음 잘 수행했습니다. 8 월 31 일 월요일, 관련 인프라 변경 및 피크 트래픽의 조합은 폐기 된 한계를 극복했습니다. 임계 값이 횡단 한 경우, 캐시가 불안정하고 많은 팟은 Asana 응용 프로그램에 대한 읽는 트래픽을 더 이상 제공 할 수 없습니다. 이전의 비스케이드 코드 경로를 사용하여 시스템을 반전하여 사건을 mitigated. 턴은 성공했지만 복구는 우리가이 종류의 문제를 기대하기보다 더 오래 걸렸다. 전체 분석은 언웨이입니다. 우리는 뿌리 원인, 행동 항목 및 개선과 함께 수행됩니다. 왜 회복이 되었는지. 우리는 2 시간 동안 약 25 %의 사용자를 위해 완전히 다운되었습니다. 15 분.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 6일 PM 5:24 UTCresolved

   From 2026-08-04 15:25 UTC until 2026-08-06 03:51 UTC, Asana failed to send some events to registered webhooks and to return them in the event streams API. Apps which rely on this should refetch the underlying data from the Asana API. Existing webhooks and event streams will continue to function, but events from the incident window will not be sent. Most events with type `task` and action `changed` were dropped during this period. Other events are not affected. The root cause of the incident was traced to a code change which unintentionally dropped change events for most fields on the task type, and the change was reverted.

1. 2026년 7월 7일 PM 6:49 UTCidentified

   우리는 Asana webapp에 대한 미국 사용자의 일부 (약 10 %)에 대한 오류를보고 있습니다. 우리는 뿌리 원인을 확인하고 해결을 식별하는 작업입니다.

2. 2026년 7월 7일 PM 7:12 UTCmonitoring

   우리는 완화를 구현하고 복구를 보장하기 위해 모니터링합니다.

3. 2026년 7월 7일 PM 7:21 UTCmonitoring

   우리는 더 많은 문제를 모니터링하고 있습니다.

4. 2026년 7월 7일 PM 7:24 UTCresolved

   이 사건은 해결되었습니다.

5. 2026년 7월 8일 PM 9:28 UTCpostmortem

   ** 인사**: 구성 변경은 우리의 서비스 중 하나에 의해 요구되는 중요한 리소스를 inadvertently 제거. 기존 인프라가 정상적으로 작동하면서 새로 확장된 인프라가 준비되어 있지 않을 수 있습니다. 아침 교통이 증가함에 따라 들어오는 요청과 시스템의 용량 사이의 이동이 증가하여 서비스 향상을 유도했습니다. 우리는 수동으로 누락 된 리소스를 복원하고 제거를 일으키는 구성 변경을 수정하여 문제를 해결했습니다. ** 중요 **: 약 1.5 시간 동안 고객은 웹 응용 프로그램 및 데스크톱 응용 프로그램의 전체 아웃 시간을 경험했습니다. 이 시간 동안, 영향을받는 사용자는 Asana에 액세스 할 수 없었다. 고객 데이터가 손실되지 않았습니다. ** 앞으로 이동 **: 우리는 우리의 구성 관리 프로세스에 대한 추가 보호 기능을 구현하여 잘못된 리소스를 inadvertently remove에서 방지합니다. 우리는 또한 고객 접근에 영향을 미치는 전, 개량하기 위하여 우리의 감시 체계를 강화하고 있습니다. 우리의 미터는 각 자료 센터에 사용자에 의해 경험된 가동 시간의 무게를 다는 평균을 고려합니다. 가동 중단 시간의 수는 이 무게를 다는 평균을 반영합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 4월 29일 PM 11:19 UTCresolved

   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. 2026년 4월 30일 AM 12:43 UTCpostmortem

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

1. 2026년 4월 29일 PM 11:09 UTCresolved

   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. 2026년 4월 30일 AM 12:34 UTCpostmortem

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

1. 2026년 3월 26일 PM 3:03 UTCinvestigating

   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. 2026년 3월 26일 PM 3:50 UTCmonitoring

   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. 2026년 3월 26일 PM 6:34 UTCresolved

   This incident has been resolved.

1. 2026년 3월 1일 PM 8:31 UTCinvestigating

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

2. 2026년 3월 1일 PM 9:03 UTCinvestigating

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

3. 2026년 3월 2일 AM 9:02 UTCinvestigating

   We are continuing to investigate this issue.

4. 2026년 3월 2일 AM 9:05 UTCinvestigating

   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

5. 2026년 3월 2일 AM 10:27 UTCinvestigating

   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

6. 2026년 3월 2일 PM 12:03 UTCinvestigating

   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

7. 2026년 3월 13일 PM 6:44 UTCmonitoring

   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.

8. 2026년 3월 15일 AM 5:58 UTCresolved

   This incident has been resolved.

1. 2026년 2월 5일 PM 11:49 UTCmonitoring

   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. 2026년 2월 5일 PM 11:58 UTCresolved

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

1. 2026년 1월 26일 AM 3:01 UTCinvestigating

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

2. 2026년 1월 26일 AM 3:19 UTCmonitoring

   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. 2026년 1월 26일 AM 3:20 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 2026년 1월 26일 AM 3:29 UTCresolved

   This incident has been resolved.

1. 2026년 1월 22일 PM 5:48 UTCinvestigating

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

2. 2026년 1월 22일 PM 5:51 UTCinvestigating

   We are continuing to investigate this issue.

3. 2026년 1월 22일 PM 5:59 UTCinvestigating

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

4. 2026년 1월 22일 PM 6:04 UTCinvestigating

   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. 2026년 1월 22일 PM 6:38 UTCinvestigating

   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. 2026년 1월 22일 PM 7:00 UTCresolved

   This incident has been resolved.

7. 2026년 1월 27일 AM 7:53 UTCpostmortem

   Incident: On 2026-01-22 the Asana App and all associated services had a service disruption due to dependency on a shared database used for storing metadata. This was triggered by a code path which caused overload for that database, followed by request queuing, timeouts, and errors. Impact: From 17:33 - 17:57 UTC the Asana App and all associated services were unavailable. There was a further 14 minutes of partial downtime from 18:45 - 18:59 UTC affecting 10-20% of users, also triggered by dependency on this shared database. Moving forward: We immediately rolled back our application code and added resources for this database. Going forward we will continue to reduce dependency on this shared database for common paths to reduce risk, and monitor for unexpected resource usage. Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.

1. 2026년 1월 6일 PM 2:17 UTCresolved

   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.

1. 2026년 1월 5일 PM 9:17 UTCinvestigating

   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. 2026년 1월 5일 PM 9:29 UTCmonitoring

   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. 2026년 1월 5일 PM 9:50 UTCresolved

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

1. 2025년 11월 24일 PM 8:28 UTCresolved

   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.

1. 2025년 11월 18일 PM 10:14 UTCresolved

   Asana's MCP server experienced partial unavailability for three hours due to an upstream provider outage. No data loss or security issues occurred during this outage. This resulted in an increased rate of errors from 3:20 - 5:00 AM PT and some failed requests from 5:04 - 6:26 AM PT. The service fully recovered after the upstream provider resolved the issue.

2. 2025년 11월 21일 AM 12:29 UTCpostmortem

   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.

1. 2025년 11월 7일 PM 9:22 UTCidentified

   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. 2025년 11월 7일 PM 9:24 UTCidentified

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

3. 2025년 11월 7일 PM 9:39 UTCidentified

   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. 2025년 11월 7일 PM 9:56 UTCmonitoring

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

5. 2025년 11월 7일 PM 10:03 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 2025년 11월 7일 PM 10:08 UTCresolved

   The incident is now resolved.

7. 2025년 11월 12일 PM 5:15 UTCpostmortem

   We had approximately 1 hour of full downtime, where the Asana application was unavailable for most of our users. There was no data loss or security vulnerability. ‌ A routine configuration change affected the Asana application globally. While refactoring the configuration consumption, we missed an unintended side effect, causing the app to fail loading in all regions. We reverted the change and restarted servers for full recovery.

1. 2025년 10월 31일 PM 4:17 UTCinvestigating

   We are currently investigating the issue.

2. 2025년 10월 31일 PM 4:28 UTCidentified

   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. 2025년 10월 31일 PM 5:05 UTCmonitoring

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

4. 2025년 10월 31일 PM 5:18 UTCresolved

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

1. 2025년 10월 20일 PM 2:28 UTCidentified

   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. 2025년 10월 20일 PM 3:07 UTCidentified

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

3. 2025년 10월 20일 PM 4:55 UTCidentified

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

4. 2025년 10월 20일 PM 6:43 UTCidentified

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

5. 2025년 10월 20일 PM 7:54 UTCmonitoring

   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. 2025년 10월 20일 PM 8:34 UTCresolved

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

7. 2025년 10월 23일 PM 4:07 UTCpostmortem

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

1. 2025년 10월 20일 AM 7:10 UTCinvestigating

   We are currently investigating an issue which affects all services.

2. 2025년 10월 20일 AM 7:15 UTCinvestigating

   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. 2025년 10월 20일 AM 7:30 UTCinvestigating

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

4. 2025년 10월 20일 AM 7:43 UTCinvestigating

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

5. 2025년 10월 20일 AM 7:59 UTCinvestigating

   We are continuing to investigate this issue.

6. 2025년 10월 20일 AM 8:19 UTCinvestigating

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

7. 2025년 10월 20일 AM 8:32 UTCinvestigating

   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. 2025년 10월 20일 AM 9:18 UTCinvestigating

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

9. 2025년 10월 20일 AM 9:32 UTCmonitoring

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

10. 2025년 10월 20일 AM 10:08 UTCmonitoring

    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. 2025년 10월 20일 AM 10:23 UTCresolved

    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. 2025년 10월 23일 PM 4:05 UTCpostmortem

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

1. 2025년 10월 13일 PM 8:56 UTCresolved

   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.