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
Posted Mar 02, 2026 - 12:03 UTC
Update
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
Posted Mar 02, 2026 - 10:27 UTC
Update
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
Posted Mar 02, 2026 - 09:05 UTC
Update
We are continuing to investigate this issue.
Posted Mar 02, 2026 - 09:02 UTC
Update
We no longer see impact on our servers. We're monitoring, as the AWS incident has not resolved.
Posted Mar 01, 2026 - 21:03 UTC
Update
We are continuing to investigate this issue.
Posted Mar 01, 2026 - 21:02 UTC
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.
Posted Mar 01, 2026 - 20:31 UTC
This incident affects: Middle East (App, API, Mobile, Automations and Background Actions, Webhooks and Event Streams, Notifications).