Companies / Asana / incidents

Asana: App Down

Affected components: AppJapan - AppMobileUS - MobileEU - NotificationsNotificationsAppUS - AppJapan - Webhooks and Event StreamsWebhooks and Event StreamsAutomations and Background ActionsEU - Automations and Background ActionsAutomations and Background ActionsJapan - Automations and Background ActionsAutomations and Background ActionsUS - Automations and Background ActionsUS - Webhooks and Event StreamsWebhooks and Event StreamsJapan - NotificationsNotificationsAustralia - Webhooks and Event StreamsWebhooks and Event StreamsAPIAustralia - APIAppEU - AppAustralia - MobileMobileAustralia - NotificationsNotificationsAPIJapan - APIAppAustralia - AppJapan - MobileMobileNotificationsUS - NotificationsAPIEU - APIAustralia - Automations and Background ActionsAutomations and Background ActionsEU - Webhooks and Event StreamsWebhooks and Event StreamsEU - MobileMobileAPIUS - API

Timeline of updates

1. investigating2025-10-20 07:10 UTC

   We are currently investigating an issue which affects all services.

2. investigating2025-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. investigating2025-10-20 07:30 UTC

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

4. investigating2025-10-20 07:43 UTC

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

5. investigating2025-10-20 07:59 UTC

   We are continuing to investigate this issue.

6. investigating2025-10-20 08:19 UTC

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

7. investigating2025-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. investigating2025-10-20 09:18 UTC

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

9. monitoring2025-10-20 09:32 UTC

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

10. monitoring2025-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. resolved2025-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. postmortem2025-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 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.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Asana profile · Recent Asana incidents · Markdown · JSON