Looking for an update now? Check the current status, or follow Asana for future changes.
55.1%of 49 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
46.7%
30
16
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 14Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
We're currently working our way through the backlog of automations that did not run.
identified
We are continuing to work on a fix for this issue.
identified
We've heard reports of rules and automations not running in the EU region. We've identified the source of the issue and fixed it for new automations triggers going forward. Our engineers are currently working on the backlog of automations that triggered and did not run during the incident.
AppAppAPIAPIMobileMobileAutomations and Background ActionsAutomations and Background ActionsWebhooks and Event StreamsWebhooks and Event StreamsNotificationsNotifications
investigating
We received an alert for unusual slow performance in several regions. We're investigating.
We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment.
We have made configuration changes and see partial recovery, but we continue to see some elevated errors.
investigating
We are continuing to investigate the issue; we have reverted recent changes, and are working to identify the source of the errors.
investigating
We are investigating alerts for slow performance and application errors.
Legacy Incident Archive
3 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
July 2026
Errors loading the Asana web app for some users in US
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have implemented a mitigation and are monitoring to ensure recovery.
identified
We are seeing errors for part (about 10%) of users in US for the Asana webapp. We've identified the root cause and are working on identifying a resolution.
March 2026
Errors loading Asana
Source not attested
Last archived state: resolved
View archived record details
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.
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.
AWS UAE issues might affect the ME region
Source not attested
Last archived state: resolved
View archived record details
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.
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
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
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
investigating
We are continuing to investigate this issue.
investigating
We no longer see impact on our servers. We're monitoring, as the AWS incident has not resolved.
investigating
We are continuing to investigate this issue.
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.
