- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Automations and Background Actions, Webhooks and Event Streams, Notifications
- Down Index
- 32of 100
What to do
Check whether you use Asana Automations and Background Actions, Webhooks and Event Streams, Notifications. 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 2h 38m it lasted.
Anything that failed between 2026-10-23 23:57 UTC and 2026-10-24 02:35 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 3
- investigating
We have a significant degradation in our system for processing asynchronous work. We previously had some crashes from web application users, but that appears to have resolved. We're monitoring the asynchronous work.
provider
- monitoring
We've paused some problematic workloads, and we think we're seeing recovery.
provider
- resolved
This incident has been resolved.
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-4978551b23
Is Asana still down?
No, this incident was resolved 2026-10-24 02:35 UTC. For Asana's live state, see https://down.guide/asana.
How long did it last?
2h 38m, from 2026-10-23 23:57 UTC to 2026-10-24 02:35 UTC, by the times Asana posted.
What was affected?
Asana named Automations and Background Actions, Webhooks and Event Streams, Notifications.
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.