# Asana: App Down

- Impact (vendor’s label): none
- Status: postmortem
- Started: 2025-10-20 15:07 UTC · Resolved: 2025-10-20 20:34 UTC · Duration: 5.5 h
- Updates: 7 · Affected components: Mobile, US - Mobile, App, US - App, Automations and Background Actions, US - Automations and Background Actions, US - Webhooks and Event Streams, Webhooks and Event Streams, Notifications, US - Notifications, API, US - API
- [Vendor status page: https://stspg.io/plk75j57xyjx](https://stspg.io/plk75j57xyjx)
- [Company: Asana](https://rewindex.com/company/asana.md)

## Timeline of updates

- **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
- **identified** 2025-10-20 15:07 UTC: We are still working on fixing the issue, this is affecting most of our users
- **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 recovery efforts and will restore full functionality as soon as possible.
- **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 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.
- **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.
- **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 performance closely, but Asana is back to normal.
- **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 \[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.


---
Canonical: https://rewindex.com/company/asana/incidents/lvtt14d4d80g · Markdown: https://rewindex.com/company/asana/incidents/lvtt14d4d80g.md · JSON: https://rewindex.com/api/v1/companies/asana/incidents/lvtt14d4d80g · Generated 2026-10-18T11:49:09.997Z