- Level
- confirmed
- Worst impact
- Degraded
- Components
- Automations and Background Actions
- Regions
- eu
What to do
Check whether you use Asana Automations and Background Actions in eu. 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 1h 10m it lasted.
Anything that failed between 2026-09-21 14:59 UTC and 2026-09-21 16:10 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 4
- identified
We've heard reports of rules and automations not running in the EU region. We've identified the source of the issue and fixed it for new automations triggers going forward. Our engineers are currently working on the backlog of automations that triggered and did not run during the incident.
provider
- identified
We are continuing to work on a fix for this issue.
provider
- monitoring
We're currently working our way through the backlog of automations that did not run.
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-5c6cebf10c
Is Asana still down?
No, this incident was resolved 2026-09-21 16:10 UTC. For Asana's live state, see https://down.guide/asana.
How long did it last?
1h 10m, from 2026-09-21 14:59 UTC to 2026-09-21 16:10 UTC, by the times Asana posted.
What was affected?
Asana named Automations and Background Actions in eu.
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.