Asana Outage History

Asana is up right now

There were 5 Asana outages since February 5, 2026 totaling 325h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.asana.com

Notice April 29, 2026

Date Time Trigger Automation Failues

Detected by Pingoru
Apr 29, 2026, 11:19 PM UTC
Resolved
Apr 21, 2026, 07:00 PM UTC
Duration
—
Timeline · 2 updates
  1. resolved Apr 29, 2026, 11:19 PM UTC

    Between April 21st and April 23rd, many rules triggered by date time triggers did not run. New rule triggers ran normally starting April 23rd, and the delayed triggers were processed by April 27th.

  2. postmortem Apr 30, 2026, 12:43 AM UTC

    Starting on **April 20th, 2026 at 10:00 AM PDT**, a combination of scaled-up background action jobs in the EU and a recent change to how date time trigger volume is managed overloaded the system that processes resource intensive background action jobs. This caused multi-hour delays in email and inbox notifications in the EU and prevented date time triggers from executing in all regions. Engineers were first alerted on **April 21st** by our monitoring systems, but did not recognize the full scope of the incident until **April 23rd**. On April 23rd, the change to manage date time trigger volume was reverted and the problematic background action jobs were isolated. All delayed notifications were sent by **April 24th, 11:30 AM PDT**, and all delayed date time triggers were executed by **April 27th, 4:00 AM PDT**.

Read the full incident report →

Notice April 29, 2026

Notifications and Background Actions delayed in EU

Detected by Pingoru
Apr 29, 2026, 11:09 PM UTC
Resolved
Apr 20, 2026, 05:00 PM UTC
Duration
—
Timeline · 2 updates
  1. resolved Apr 29, 2026, 11:09 PM UTC

    Between April 20th and April 24th, 60% of email and inbox notifications were delayed by at least one hour in EU. Notifications were delayed up to 3 days. Other resource intensive background actions were also impacted at a lesser rate.

  2. postmortem Apr 30, 2026, 12:34 AM UTC

    Starting on **April 20th, 2026 at 10:00 AM PDT**, a combination of scaled-up background action jobs in the EU and a recent change to how date time trigger volume is managed overloaded the system that processes resource intensive background action jobs. This caused multi-hour delays in email and inbox notifications in the EU and prevented date time triggers from executing in all regions. Engineers were first alerted on **April 21st** by our monitoring systems, but did not recognize the full scope of the incident until **April 23rd**. On April 23rd, the change to manage date time trigger volume was reverted and the problematic background action jobs were isolated. All delayed notifications were sent by **April 24th, 11:30 AM PDT**, and all delayed date time triggers were executed by **April 27th, 4:00 AM PDT**.

Read the full incident report →

Notice March 26, 2026

Errors loading Asana

Detected by Pingoru
Mar 26, 2026, 03:03 PM UTC
Resolved
Mar 26, 2026, 06:34 PM UTC
Duration
3h 30m
Affected: App
Timeline · 3 updates
  1. investigating Mar 26, 2026, 03:03 PM UTC

    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.

  2. monitoring Mar 26, 2026, 03:50 PM UTC

    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.

  3. resolved Mar 26, 2026, 06:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 1, 2026

AWS UAE issues might affect the ME region

Detected by Pingoru
Mar 01, 2026, 08:31 PM UTC
Resolved
Mar 15, 2026, 05:58 AM UTC
Duration
13d 9h
Affected: AppAPIMobileAutomations and Background ActionsWebhooks and Event StreamsNotifications
Timeline · 9 updates
  1. investigating Mar 01, 2026, 08:31 PM UTC

    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.

  2. investigating Mar 01, 2026, 09:02 PM UTC

    We are continuing to investigate this issue.

  3. investigating Mar 01, 2026, 09:03 PM UTC

    We no longer see impact on our servers. We're monitoring, as the AWS incident has not resolved.

  4. investigating Mar 02, 2026, 09:02 AM UTC

    We are continuing to investigate this issue.

  5. investigating Mar 02, 2026, 09:05 AM UTC

    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

  6. investigating Mar 02, 2026, 10:27 AM UTC

    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

  7. investigating Mar 02, 2026, 12:03 PM UTC

    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

  8. monitoring Mar 13, 2026, 06:44 PM UTC

    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.

  9. resolved Mar 15, 2026, 05:58 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 5, 2026

API monitoring

Detected by Pingoru
Feb 05, 2026, 11:49 PM UTC
Resolved
Feb 05, 2026, 11:58 PM UTC
Duration
9m
Affected: APIAPIAPIAPIAPIMobileMobileMobileMobileMobile
Timeline · 2 updates
  1. monitoring Feb 05, 2026, 11:49 PM UTC

    Our primary monitoring is observing an outage for our API and mobile services, but secondary monitoring indicates that API and mobile traffic is operating as usual. Our engineers are reviewing our primary monitoring and will provide updates on the situation.

  2. resolved Feb 05, 2026, 11:58 PM UTC

    Our engineers have rolled back recent changes to our primary monitoring systems, and our API and mobile systems are fully operational.

Read the full incident report →

Looking to track Asana downtime and outages?

Pingoru polls Asana's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Asana reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Asana alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Asana for free

5 free monitors · No credit card required