Skip to main content
Asana

Permissions bug between 2025-11-18 and 2025-11-19

Degraded Lasted 0m · started · Asana's page

Level
confirmed
Worst impact
Degraded
Down Index
8of 100

What to do

  • Check whether your product depends on Asana. 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 0m it lasted.

    Anything that failed between 2025-11-24 20:28 UTC and 2025-11-18 17:00 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 1

  1. resolved

    Resolved - We have fully resolved an incident related to a product permissions bug that briefly impacted some of our customers between November 18 and November 19. This issue was contained entirely within customer domains and did not expose any data externally.

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

Is Asana still down?

No, this incident was resolved 2025-11-18 17:00 UTC. For Asana's live state, see https://down.guide/asana.

How long did it last?

0m, from 2025-11-24 20:28 UTC to 2025-11-18 17:00 UTC, by the times Asana posted.

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.