Skip to main content
Asana

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

Partial outage Lasted 42m · started · Asana's page

Level
confirmed
Worst impact
Partial outage
Components
App, API, Mobile

What to do

  • Check whether you use Asana App, API, Mobile. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 42m it lasted.

    Anything that failed between 2026-09-02 18:08 UTC and 2026-09-02 18:49 UTC may need a replay.
  • Subscribe to Asana's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=asana works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Asana 6

  1. investigating

    We are currently investigating this issue.

    provider

  2. investigating

    We are continuing to investigate this issue.

    provider

  3. investigating

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

    provider

  4. monitoring

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

    provider

  5. resolved

    This incident has been resolved.

    provider

  6. postmortem

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

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-87485cc8f9

Is Asana still down?

No, this incident was resolved 2026-09-02 18:49 UTC. For Asana's live state, see https://down.guide/asana.

How long did it last?

42m, from 2026-09-02 18:08 UTC to 2026-09-02 18:49 UTC, by the times Asana posted.

What was affected?

Asana named App, API, Mobile.

What caused it?

Asana hasn't published a root cause. If it does, it shows here.

Where does this come from?

Asana's official status page, https://status.asana.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.