We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment.
Incident: An internal system responsible for automatically scaling backend server capacity in one of our compute clusters stopped replacing capacity that had been cycled out during routine maintenance. This caused a gradual reduction in available capacity over several hours. A subsequent deployment was activated with insufficient capacity, causing all new requests for that compute cluster to fail. To mitigate the impact, we reverted to a previous release revision, which still had sufficient capacity. Impact: For approximately 30 minutes, customers whose traffic was handled by this compute cluster saw full downtime; other customers were unaffected. No customer data was lost. Moving forward: We have added additional monitoring to detect this type of capacity-scaling failure much earlier, and have added safeguards to prevent deployments from shifting traffic before sufficient healthy capacity is confirmed. _Our metric considers a weighted average of uptime experienced by users at each dat
The latest update from Asana.
State
Resolved
Started
60 d ago
2026-09-02 18:08 UTC
Lasted
42 min
until 2026-09-02 18:49 UTC
Worst impact
Partial outage
Timeline
6 updatesInvestigating
7 min 16%
Monitoring
35 min 84%
Updates
Times in UTCAs posted by Asana
Incident: An internal system responsible for automatically scaling backend server capacity in one of our compute clusters stopped replacing capacity that had been cycled out during routine maintenance. This caused a gradual reduction in available capacity over several hours. A subsequent deployment was activated with insufficient capacity, causing all new requests for that compute cluster to fail. To mitigate the impact, we reverted to a previous release revision, which still had sufficient capacity. Impact: For approximately 30 minutes, customers whose traffic was handled by this compute cluster saw full downtime; other customers were unaffected. No customer data was lost. Moving forward: We have added additional monitoring to detect this type of capacity-scaling failure much earlier, and have added safeguards to prevent deployments from shifting traffic before sufficient healthy capacity is confirmed. _Our metric considers a weighted average of uptime experienced by users at each dat
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The rollback seems to have completely resolved errors. We're monitoring closely, but users should be able to access Asana again.
We are continuing to investigate this issue.
We are currently investigating this issue.
Affected components
3Asana in the last 90 days
Full historyIncidents in 90 days
9
Days with an incident
10
Median duration
50 min
This incident
16% shorter than the median
Other Asana incidents
All incidentsAsana·Background jobs partial outage
This incident has been resolved.
Asana·Asana downtime
**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
Asana·Partial API outage
This incident has been resolved.
Asana·Partial API outage in EU
The incident has been resolved.
Asana·Automations not running for EU users
This incident has been resolved.
Follow Asana
Your coding agent knows when Asana is down, and tells you when a failure is theirs, not yours. You can also get Asana incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "asana" and tell me if Asana has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=asana/feed subscribe https://outages.cc/feed.xml?providers=asanaFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane