Partial API outage
DegradedThis incident has been resolved.
Asana is up and running. Asana tracks team projects and tasks.
Worked out from the incidents Asana reported, so it is an estimate and not a measurement.
Last incident: “Partial API outage”, 19 days ago.
This incident has been resolved.
The incident has been resolved.
This incident has been resolved.
This incident has been resolved.
Incident: An internal system responsible for automatically scaling backend server capacity in one of our compute clusters stopped replacing capacity that had been cycled out during routine maintenance. This caused a gradual reduction in available capacity over several hours. A subsequent deployment was activated with insufficient capacity, causing all new requests for that compute cluster to fail. To mitigate the impact, we reverted to a previous release revision, which still had sufficient capacity. Impact: For approximately 30 minutes, customers whose traffic was handled by this compute cluster saw full downtime; other customers were unaffected. No customer data was lost. Moving forward: We have added additional monitoring to detect this type of capacity-scaling failure much earlier, and have added safeguards to prevent deployments from shifting traffic before sufficient healthy capacity is confirmed. _Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average._
Asana’s official status page says: All Systems Operational. This page checks it again when you load it, at most every 5 minutes.
The most recent incident Asana reported was “Partial API outage”, 19 days ago (2026-09-30 14:31 UTC). None of its incidents in the last 90 days were a full outage.
Asana reports 30 components on its status page, including App, App, App, App, App. Each is checked again whenever this page refreshes.
Keep working from local or offline copies where you can, and hold off on large imports or sync jobs until it is back.
Asana offers regional data residency, and the status page tracks App, API, Mobile, Automations and Webhooks per region. Only organizations hosted in the named region are touched.
'Automations and Background Actions' and 'Webhooks and Event Streams' are separate components per region — rules can pause while the app itself works.
If the status above is operational but Asana still fails for you, the cause is probably on your side: try another network, clear the cache, or check your own connection. If it shows a degradation or an outage, others are affected too.
OpenUptime checks your site every minute and sends an alert to Slack, Telegram, email or a webhook the moment it stops responding. It is open source and free to start.