Asana Outage History

25 incidents recorded over the last 365 days, 19 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Every Recorded Asana Incident

Asana incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Aug 4, 2026Webhooks and event streams partial data lossFrom 2026-08-04 15:25 UTC until 2026-08-06 03:51 UTC, Asana failed to send some events to registered webhooks and to return them in the event streams API. Apps which rely on this should refetch the underlying data from…0 minResolved
Aug 2, 2026Planned MaintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Jul 24, 2026Planned MaintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Jul 7, 2026Errors loading the Asana web app for some users in US**Incident**: A configuration change inadvertently removed a critical resource required by one of our services. While existing infrastructure continued to operate normally, newly scaled infrastructure could not become…34 minResolved
Apr 29, 2026Date Time Trigger Automation FailuesStarting 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…-11779 minResolved
Apr 29, 2026Notifications and Background Actions delayed in EUStarting 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…-13329 minResolved
Mar 26, 2026Errors loading AsanaThis incident has been resolved.3h 30mResolved
Mar 1, 2026AWS UAE issues might affect the ME regionThis incident has been resolved.321h 27mResolved
Feb 5, 2026API monitoringOur engineers have rolled back recent changes to our primary monitoring systems, and our API and mobile systems are fully operational.9 minResolved
Jan 26, 2026EU App and API issuesThis incident has been resolved.28 minResolved
Jan 22, 2026Asana webapp unavailableIncident: On 2026-01-22 the Asana App and all associated services had a service disruption due to dependency on a shared database used for storing metadata. This was triggered by a code path which caused overload for…1h 12mResolved
Jan 6, 2026Issues in with Asana in non-US regionsOn January 6th, 2026 at UTC 12:00, we experienced an approximately 50-minute service disruption affecting customers in non-US regions. During this time, some requests may have failed or timed out. What Happened: During…-857 minResolved
Jan 5, 2026Downtime for the Asana web appThank you for your patience. Service is fully restored, and the Asana web app is back to normal functionality.32 minResolved
Dec 13, 2025Planned MaintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Dec 13, 2025Planned MaintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Dec 6, 2025Planned MaintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Nov 24, 2025Permissions bug between 2025-11-18 and 2025-11-19Resolved - We have fully resolved an incident related to a product permissions bug that briefly impacted some of our customers between November 18 and November 19. This issue was contained entirely within customer…-8848 minResolved
Nov 22, 2025Planned MaintenanceThe scheduled maintenance has been completed.2h 0mScheduled
Nov 18, 2025Partial downtime for Asana's MCP serverIncident: [Cloudflare experienced an outage](https://blog.cloudflare.com/18-november-2025-outage/) that impacted the Workers KV service, a storage infrastructure service our MCP server relies on. This resulted in…-644 minResolved
Nov 7, 2025Asana downtime in all regionsWe had approximately 1 hour of full downtime, where the Asana application was unavailable for most of our users. There was no data loss or security vulnerability. ‌ A routine configuration change affected the Asana…45 minResolved
Oct 31, 2025Issues in with Asana in EU regionThis incident has been resolved. During the incident, users in EU experienced slow application performance, and automations, webhooks, and background actions were delayed.1h 0mResolved
Oct 20, 2025App Down**Incident:** AWS infrastructure had [an outage affecting core services](https://aws.amazon.com/message/101925/), which our application depends on, in the Virginia \(us-east-1\) region. The initial impact to our…5h 26mResolved
Oct 20, 2025App Down**Incident:** AWS infrastructure had [an outage affecting core services](https://aws.amazon.com/message/101925/), which our application depends on, in the Virginia \(us-east-1\) region. After partial recovery within…3h 13mResolved
Oct 13, 2025Stale data and crashesFrom 15:44 - 16:33 UTC, Asana users may have seen stale data in the web app. In some cases, users may have experienced crashes and failed API requests.0 minResolved
Oct 6, 2025Script-based actions on tasks were failingOne of our infrastructure services that we use to run the customer provided script was failing to start up for some workspaces. This was an unintended consequence of us rolling out improved security controls. We've…-6153 minResolved

How to Read This Asana Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Asana acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Asana outage in this window ran 13d 9h, against a mean recovery of 18h 26m. If you depend on Asana in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.