outages.live
Live

Asana

Asana is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

9

Days with an incident

10

Median duration

50 min

Longest incident

3 h 12 min

Components

30

US

App Operational
90 days ago4 days with an incidentToday
API Operational
90 days ago5 days with an incidentToday
Mobile Operational
90 days ago5 days with an incidentToday
Automations and Background Actions Operational
90 days ago4 days with an incidentToday
Webhooks and Event Streams Operational
90 days ago3 days with an incidentToday
Notifications Operational
90 days ago3 days with an incidentToday

EU

App Operational
90 days ago2 days with an incidentToday
API Operational
90 days ago3 days with an incidentToday
Mobile Operational
90 days ago2 days with an incidentToday
Automations and Background Actions Operational
90 days ago3 days with an incidentToday
Webhooks and Event Streams Operational
90 days ago1 day with an incidentToday
Notifications Operational
90 days ago1 day with an incidentToday

Japan

App Operational
90 days ago1 day with an incidentToday
API Operational
90 days ago1 day with an incidentToday
Mobile Operational
90 days ago1 day with an incidentToday
Automations and Background Actions Operational
90 days ago1 day with an incidentToday
Webhooks and Event Streams Operational
90 days agoNo incidentsToday
Notifications Operational
90 days agoNo incidentsToday

Australia

App Operational
90 days ago1 day with an incidentToday
API Operational
90 days ago1 day with an incidentToday
Mobile Operational
90 days ago1 day with an incidentToday
Automations and Background Actions Operational
90 days ago1 day with an incidentToday
Webhooks and Event Streams Operational
90 days agoNo incidentsToday
Notifications Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 23, 2026

Duration2 h 38 min23:57 to 02:35Background jobs partial outagePartial outage

This incident has been resolved.

Oct 21, 2026

Duration37 min15:33 to 16:10Asana downtimePartial outage

**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

Sep 30, 2026

Duration50 min14:31 to 15:21Partial API outagePartial outage

This incident has been resolved.

Sep 29, 2026

Duration3 h 12 min12:14 to 15:25Partial API outage in EUDegraded

The incident has been resolved.

Sep 21, 2026

Duration1 h 10 min14:59 to 16:10Automations not running for EU usersDegraded

This incident has been resolved.

Sep 17, 2026

Duration36 min14:36 to 15:13Slow performance for a subset of Asana usersDegraded

This incident has been resolved.

Sep 2, 2026

Duration42 min18:08 to 18:49We are fully down for a subset of customers. We're investigating the issue, and are rolling back a deployment.Partial outage

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

Aug 31, 2026

Duration2 h 4 min15:14 to 17:18Asana full outage for some users (2 hours, 25% outage)Partial outage

We’ve been working to add a caching layer to our update pipeline, tuning it carefully and rolling it out gradually. On Wednesday, August 26 we enabled it for most use cases, and it initially performed well. On Monday, August 31, a combination of unrelated infrastructure changes and peak traffic pushed the cache past its scaling limits. Once that threshold was crossed, the cache became unusable, and many pods serving read traffic for the Asana application could no longer serve it. We mitigated the incident by reverting the system to use the previous, non-cached code path. The revert was successful, but recovery took longer than we would expect for this class of issue. A fuller analysis is underway. We will follow up with root causes, action items, and improvements, including why recovery took as long as it did. We were fully down for about 25% of our users, for 2 hours, 15 minutes.

Aug 4, 2026

Duration1 min15:30 to 15:30Webhooks and event streams partial data lossDegraded

From 2026-08-04 15:25 UTC until 2026-08-06 03:51 UTC, Asana failed to send some events to registered webhooks and to return them in the event streams API. Apps which rely on this should refetch the underlying data from the Asana API. Existing webhooks and event streams will continue to function, but events from the incident window will not be sent. Most events with type `task` and action `changed` were dropped during this period. Other events are not affected. The root cause of the incident was traced to a code change which unintentionally dropped change events for most fields on the task type, and the change was reverted.

Maintenance

Planned Maintenance

On Saturday, Nov 7th, 2026, between 4:00 AM and 7:00 AM UTC, users may experience interruptions or limited availability while we upgrade our databases. During this maintenance window, Asana web and mobile applications and API may be affected. Thank you for your understanding and patience. Please contact support for any questions.

Maintenancestarts in 5 d

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.

Prompt
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.

RSS
https://outages.cc/feed.xml?providers=asana
Slack
/feed subscribe https://outages.cc/feed.xml?providers=asana

Go from tracking outages to fixing production issues with Polylane.

Try Polylane