# App Down - Provider: [Asana](https://down.guide/asana) - Level: confirmed - Impact: Operational - lasted 3h 13m - started 2025-10-20 07:10 UTC - App, App, App +21 - us, us-east-1 - id: DWN-6a6c996d4e - Official page: https://stspg.io/3tsmgwgnfqw2 ## Updates from Asana ### 2025-10-20 07:10 UTC: investigating We are currently investigating an issue which affects all services. ### 2025-10-20 07:15 UTC: investigating 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. ### 2025-10-20 07:30 UTC: investigating We are still seeing full downtime, and are continuing investigation. ### 2025-10-20 07:43 UTC: investigating We are continuing to investigate this issue from our side, and waiting for an update from AWS. ### 2025-10-20 07:59 UTC: investigating We are continuing to investigate this issue. ### 2025-10-20 08:19 UTC: investigating We are continuing to work on this issue. AWS DynamoDB is disrupted, and this impacts our production services. ### 2025-10-20 08:32 UTC: investigating 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. ### 2025-10-20 09:18 UTC: investigating We are working to prepare our systems to recover once AWS resolves DynamoDB issues in us-east-1. ### 2025-10-20 09:32 UTC: monitoring A fix has been implemented, and we are monitoring recovery. ### 2025-10-20 10:08 UTC: monitoring 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. ### 2025-10-20 10:23 UTC: resolved 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. ### 2025-10-23 16:05 UTC: postmortem 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 . 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. From the builder: does your app depend on Asana? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=asana) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Asana. --- down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-6a6c996d4e), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.