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

- Impact (vendor’s label): major
- Status: postmortem
- Started: 2026-09-02 18:08 UTC · Resolved: 2026-09-02 18:49 UTC · Duration: 42 min
- Updates: 6 · Affected components: Mobile, US - Mobile, App, US - App, API, US - API
- [Vendor status page: https://stspg.io/9j079t3hxmmt](https://stspg.io/9j079t3hxmmt)
- [Company: Asana](https://rewindex.com/company/asana.md)

## 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, sol)_
## Timeline of updates

- **investigating** 2026-09-02 18:08 UTC: We are currently investigating this issue.
- **investigating** 2026-09-02 18:13 UTC: We are continuing to investigate this issue.
- **investigating** 2026-09-02 18:14 UTC: The rollback seems to have completely resolved errors. We're monitoring closely, but users should be able to access Asana again.
- **monitoring** 2026-09-02 18:14 UTC: A fix has been implemented and we are monitoring the results.
- **resolved** 2026-09-02 18:49 UTC: This incident has been resolved.
- **postmortem** 2026-09-04 19:52 UTC: 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.\_

## Rewindex changes for this incident

- 2026-09-02 18:08 UTC: [Major incident: We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment.](https://rewindex.com/change/i137fb04027a3ec.md)


---
Canonical: https://rewindex.com/company/asana/incidents/70ts4fqbblrc · Markdown: https://rewindex.com/company/asana/incidents/70ts4fqbblrc.md · JSON: https://rewindex.com/api/v1/companies/asana/incidents/70ts4fqbblrc · Generated 2026-10-18T10:39:44.277Z