Background jobs partial outage
Last updateresolvedOct 24 · 02:35 UTC
This incident has been resolved.
Reported by Asana on their status page.
checked Nov 8, 2026 4:04 PM UTC · Asana's official status page
Asana is up and running.
Asana is currently operational with all systems functioning normally.
All components operational
Get updates without checking back
Get email updates for the reported Asana status changes you choose. Follow your other dependencies in the same workspace.
30-day free trial, no card needed. First-time customers; continued monitoring requires a paid subscription.
Asana incident history
2 reports published by Asana in the last 30 days
When Asana breaks, it is typically resolved in 1h 33m — median across 2 resolved incidents over 30 days.
October 23, 2026
October 21, 2026
Asana downtime
Last updatepostmortemOct 24 · 00:22 UTC
Incident: An infrastructure update targeting security caused DynamoDB to become inaccessible across Asana's production environment. This change was related to a production isolation initiative, and was applied in a way that left all of our production services unable to use DynamoDB tables which we use for metadata and routing traffic. Once the change was reverted our services returned to normal operations.
Impact: Asana services were completely unavailable for approximately 30 minutes, 2026-10-21 15:21 UTC-15:51 UTC, and mostly unavailable for a further 20 minutes, including 15:05 UTC-15:55 UTC. This also caused delay for background actions during the impact period; recovery after the end of the incident completed by 16:00 UTC.
Moving forward: We are updating the deployment process to catch this class of error. We will be moving to an isolation system which allows more gradual rollout of similar changes, allowing us to detect misconfiguration in pre-production testing.
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.
Reported by Asana on their status page.