- Level
- confirmed
- Worst impact
- Degraded
- Components
- App, App, App, App, API, API, API, API
- Down Index
- 22of 100
What to do
Check whether you use Asana App, App, App, App and 4 more. 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 52m it lasted.
Anything that failed between 2025-03-25 14:36 UTC and 2025-03-25 15:28 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 5
- investigating
We saw a high rate of errors due to overload of internal infrastructure. We see partial recovery, and are continuing to investigate.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- monitoring
We have scaled up affected infrastructure are continuing to monitor application health and metrics.
provider
- resolved
This incident has been resolved. We are doing root cause analysis and will post an update within 72 hours.
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-5535e0024b
Is Asana still down?
No, this incident was resolved 2025-03-25 15:28 UTC. For Asana's live state, see https://down.guide/asana.
How long did it last?
52m, from 2025-03-25 14:36 UTC to 2025-03-25 15:28 UTC, by the times Asana posted.
What was affected?
Asana named App, App, App, App and 4 more.
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.