App Down

Final update

**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. Postmortem · Oct 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.
2. Resolved · Oct 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.
3. Monitoring · Oct 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.
4. Monitoring · Oct 20, 09:32 UTC
   A fix has been implemented, and we are monitoring recovery.
5. Investigating · Oct 20, 09:18 UTC
   We are working to prepare our systems to recover once AWS resolves DynamoDB issues in us-east-1.
6. Investigating · Oct 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.
7. Investigating · Oct 20, 08:19 UTC
   We are continuing to work on this issue. AWS DynamoDB is disrupted, and this impacts our production services.
8. Investigating · Oct 20, 07:59 UTC
   We are continuing to investigate this issue.
9. Investigating · Oct 20, 07:43 UTC
   We are continuing to investigate this issue from our side, and waiting for an update from AWS.
10. Investigating · Oct 20, 07:30 UTC
    We are still seeing full downtime, and are continuing investigation.
11. Investigating · Oct 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.
12. Investigating · Oct 20, 07:10 UTC
    We are currently investigating an issue which affects all services.