Is Asana down?

Last checked 5m ago
Current status
Asana is up

No incidents right now.

Official status page: https://status.asana.com · Polled every 5 minutes · 30 components tracked

Asana is operational right now. Last checked 5m ago; the most recent incident resolved 53d ago.

Real-time Asana status, recent outages, and incident history — pulled directly from Asana's official status page at https://status.asana.com every 5 minutes. Pingoru tracks 30 Asana services and has captured 3 incidents in the last 90 days (100.00% uptime). Get email, Slack, Discord, or webhook alerts the moment Asana reports a new incident — free for 5 monitors, no credit card.

Users who monitor Asana also follow these Project Management services: Atlassian Jira Software Trello Incident IQ Notion Shortcut Jira Service Management LaunchDarkly Basecamp Jira Core View all 6,000+ providers
Asana uptime 100.00% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Apr 29, 2026, 11:19 PM UTC · Resolved Apr 21, 2026, 07:00 PM UTC
    Timeline · 2 updates
    • 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.

    • 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**.

    Latest: 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 overloa…

  2. Resolved
    Started Apr 29, 2026, 11:09 PM UTC · Resolved Apr 20, 2026, 05:00 PM UTC
    Timeline · 2 updates
    • 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.

    • 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**.

    Latest: 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 overloa…

  3. Resolved 3h 30m
    Started Mar 26, 2026, 03:03 PM UTC · Resolved Mar 26, 2026, 06:34 PM UTC
    App
    Timeline · 3 updates
    • 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.

    • 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.

    • resolved · Mar 26, 2026, 06:34 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

Outage history

Past 90 days · 3 incidents View full outage history →