- Level
- confirmed
- Worst impact
- Degraded
- Components
- App, App, App, App, API, API, API, API, Mobile, Mobile, Mobile, Mobile, Automations and Background Actions, Automations and Background Actions, Automations and Background Actions, Automations and Background Actions
- Down Index
- 23of 100
What to do
Check whether you use Asana App, App, App, App and 12 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 10m it lasted.
Anything that failed between 2025-06-25 12:25 UTC and 2025-06-25 12: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 4
- monitoring
We have identified an issue causing errors starting around 11:50 UTC, and have reverted the change which caused this. We are monitoring to confirm recovery.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- resolved
All system appear to have recovered, with recovery starting around 12:14 UTC. We will publish a postmortem within 72 hours.
provider
- postmortem
**Incident**: A configuration change unintentionally blocked internal network access between application components. This change was identified as the cause of downtime and reverted. **Impact**: The Asana App and API were unavailable for 24 minutes. App and API traffic recovered over the next 5 minutes, and Automations & Background Actions recovered over 10 minutes. **Moving forward**: We have completed a redesign of our core application architecture to better protect our services from disruption by segmentation into independent sections, or "cells." We are considering ways we can leverage this architecture to roll out configuration changes like the one which triggered this incident more gradually and carefully across our systems to ensure safety & stability. 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-3d840bd57a
Is Asana still down?
No, this incident was resolved 2025-06-25 12:35 UTC. For Asana's live state, see https://down.guide/asana.
How long did it last?
10m, from 2025-06-25 12:25 UTC to 2025-06-25 12:35 UTC, by the times Asana posted.
What was affected?
Asana named App, App, App, App and 12 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.