Asana Outage History

Uptime record, past incidents, and downtime history for Asana.

Checking current status...
70% uptime over 70 days
99.9% ✗ 99.5% ✗ 99% ✗ 95% ✗

90-Day Trend

Jan 31Apr 10

Monthly Uptime

Month Uptime Days Tracked Days with Issues
April 2026 100% 10 0
March 2026 51.6% 31 15
February 2026 78.6% 28 6
January 2026 100% 1 0

Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.

Daily Status (Last 70 Days)

Jan 31 Today
Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

March 2026
Errors loading Asana

Started: Mar 26, 3:03 PM

monitoring
We believe that this was related to http3, and have disabled http3 for the affected CloudFront distribution. We believe Asana should now load after a hard refresh.
Mar 26, 3:50 PM
investigating
We have received reports that some users are unable to load Asana, especially in and around New York/the East Coast of the US, and have observed intermittent errors. We are investigating this, and will provide an update within an hour.
Mar 26, 3:03 PM
AWS UAE issues might affect the ME region

Started: Mar 1, 8:31 PM

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.
Mar 13, 6:44 PM
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
Mar 2, 12:03 PM
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
Mar 2, 10:27 AM
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
Mar 2, 9:05 AM
investigating
We are continuing to investigate this issue.
Mar 2, 9:02 AM
investigating
We no longer see impact on our servers. We're monitoring, as the AWS incident has not resolved.
Mar 1, 9:03 PM
investigating
We are continuing to investigate this issue.
Mar 1, 9:02 PM
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.
Mar 1, 8:31 PM