Changes / Asana / We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment.
Asana: Major incident: We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment.
Summary
Asana reported a major outage affecting a subset of customers across API, App, Mobile and US components from 2026-09-02 18:08 UTC to 2026-09-02 18:49 UTC (41 min). A deployment rollback restored access; the postmortem attributed failed requests to insufficient cluster capacity after an automatic scaling system stopped replacing capacity removed during maintenance.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment.
Before: not present
After: major
Before: not present
After: postmortem
Before: not present
After: 2026-09-02 18:08 UTC
Before: not present
After: 2026-09-02 18:49 UTC
Before: not present
After: API, App, Mobile, US - API, US - App, US - Mobile
Before: not present
After: We are currently investigating this issue.
Before: not present
After: We are continuing to investigate this issue.
Before: not present
After: The rollback seems to have completely resolved errors. We're monitoring closely, but users should be able to access Asana again.
Before: not present
After: A fix has been implemented and we are monitoring the results.
Before: not present
After: This incident has been resolved.
Before: not present
After: 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._
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment. (this change) Asana reported a major outage affecting a subset of customers across API, App, Mobile and US components from 2026-09-02 18:08 UTC to 2026-09-02 18:49 UTC (41 min). A deployment rollback restored access; the postmortem attributed failed requests to insufficient cluster capacity after an automatic scaling system stopped replacing capacity removed during maintenance. | Major incident |