- Level
- confirmed
- Worst impact
- Degraded
- Components
- App, API, Mobile, Automations and Background Actions, Webhooks and Event Streams, Notifications
- Regions
- me, me-central-1
What to do
Check whether you use Asana App, API, Mobile, Automations and Background Actions and 2 more in me, me-central-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 13d 9h it lasted.
Anything that failed between 2026-03-01 20:31 UTC and 2026-03-15 05:58 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 9
- investigating
Asana remains accessible to customers in the ME region, but we are seeing backends impacted by an AWS ME outage. If that isn't resolved soon, we expect to see some performance degradation and possible outages of the Asana application. This is only for the ME region; other regions are unaffected.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We no longer see impact on our servers. We're monitoring, as the AWS incident has not resolved.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are seeing major impact in the ME region making Asana services unavailable to users whose data is stored in that region. We have taken steps to avoid additional loss of EC2 resources, but are continuing to see high error rates. This cause is AWS incidents affecting the infrastructure (az1 and az3) in the Middle East region: https://health.aws.amazon.com/health/status
provider
- investigating
We are still seeing major impact in the ME region making Asana services unavailable to users whose data is stored in that region. We are continuing to monitor the situation. The cause is AWS incidents affecting the infrastructure in the Middle East region: https://health.aws.amazon.com/health/status
provider
- investigating
We are still seeing major impact in the ME region making Asana services unavailable to users whose data is stored in that region. We are continuing to monitor the situation. The cause is widespread AWS incidents affecting the infrastructure in the Middle East region: https://health.aws.amazon.com/health/status
provider
- monitoring
A small number of users were affected by the AWS outage in UAE (me-central-1); following AWS's recommendations, we have moved processing to other regions, and believe there is no user impact.
provider
- resolved
This incident has been resolved.
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-c22f4ffd25
Is Asana still down?
No, this incident was resolved 2026-03-15 05:58 UTC. For Asana's live state, see https://down.guide/asana.
How long did it last?
13d 9h, from 2026-03-01 20:31 UTC to 2026-03-15 05:58 UTC, by the times Asana posted.
What was affected?
Asana named App, API, Mobile, Automations and Background Actions and 2 more in me, me-central-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.