Global Outage Map
← Live dashboard
Asana logoAsana

We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment.

ResolvedmajorOfficial source confirmedSpecific component onlyFirst recorded update 02-09-2026 20:08 · Resolved 02-09-2026 20:49

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

Asana live status →

Free for 3 services · Pro adds recovery alertsAdd to Chrome

What visitors reported during this incident

No visitor reports were filed for this incident.

View all comments
    Having problems with Asana now? Check the current status

    Affected services

    AppMobileAPI

    Updates (6)

    1. 04-09-2026 21:52
      We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment.

      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 clu

      Asana ↗
    2. 02-09-2026 20:49
      We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment.

      This incident has been resolved.

      Asana ↗
    3. 02-09-2026 20:14
      We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment.

      A fix has been implemented and we are monitoring the results.

      Asana ↗
    4. 02-09-2026 20:14
      We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment.

      The rollback seems to have completely resolved errors. We're monitoring closely, but users should be able to access Asana again.

      Asana ↗
    5. 02-09-2026 20:13
      We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment.

      We are continuing to investigate this issue.

      Asana ↗
    6. 02-09-2026 20:08
      We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment.

      We are currently investigating this issue.

      Asana ↗

    What to do next

    • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
    • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
    • Watch the provider going forward. Follow Asana's status feed →

    GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.