- Level
- confirmed
- Worst impact
- Degraded
- Components
- App, App, App, App, API, API, API, API, Mobile, Mobile, Mobile, Mobile, Automations and Background Actions, Automations and Background Actions, Automations and Background Actions, Automations and Background Actions, Webhooks and Event Streams, Webhooks and Event Streams, Webhooks and Event Streams, Webhooks and Event Streams, Notifications, Notifications, Notifications, Notifications
- Regions
- us, us-east-1
- Down Index
- 34of 100
What to do
Check whether you use Asana App, App, App, App and 20 more in us, us-east-1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 3h 13m it lasted.
Anything that failed between 2025-10-20 07:10 UTC and 2025-10-20 10:23 UTC may need a replay.Subscribe to Asana's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=asana works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Asana 12
- investigating
We are currently investigating an issue which affects all services.
provider
- 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.
provider
- investigating
We are still seeing full downtime, and are continuing investigation.
provider
- investigating
We are continuing to investigate this issue from our side, and waiting for an update from AWS.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are continuing to work on this issue. AWS DynamoDB is disrupted, and this impacts our production services.
provider
- 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.
provider
- investigating
We are working to prepare our systems to recover once AWS resolves DynamoDB issues in us-east-1.
provider
- monitoring
A fix has been implemented, and we are monitoring recovery.
provider
- 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.
provider
- 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.
provider
- 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](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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-6a6c996d4e
Is Asana still down?
No, this incident was resolved 2025-10-20 10:23 UTC. For Asana's live state, see https://down.guide/asana.
How long did it last?
3h 13m, from 2025-10-20 07:10 UTC to 2025-10-20 10:23 UTC, by the times Asana posted.
What was affected?
Asana named App, App, App, App and 20 more in us, us-east-1.
What caused it?
Asana hasn't published a root cause. If it does, it shows here.
Where does this come from?
Asana's official status page, https://status.asana.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.