Is there an Asana outage?
Asana status: Systems Active
Last checked: 7 minutes ago
Get notified about any outages, downtime or incidents for Asana and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 7 minutes ago
Get notified about any outages, downtime or incidents for Asana and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Asana.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Australia | Active |
| API | Active |
| App | Active |
| Automations and Background Actions | Active |
| Mobile | Active |
| Webhooks and Event Streams | Active |
| EU | Active |
| API | Active |
| App | Active |
| Automations and Background Actions | Active |
| Mobile | Active |
| Webhooks and Event Streams | Active |
| Japan | Active |
| API | Active |
| App | Active |
| Automations and Background Actions | Active |
| Mobile | Active |
| Webhooks and Event Streams | Active |
| US | Active |
| API | Active |
| App | Active |
| Automations and Background Actions | Active |
| Mobile | Active |
| Webhooks and Event Streams | Active |
View the latest incidents for Asana and check for official updates:
Description: Incident: To ensure our systems can reliably recover when systems fail, Asana triggers an individual node failure at a time of low traffic when engineers are available to address any problems. A software bug in an internal application which replaces failed nodes prevented recovery when a node was terminated in this manner. Impact: Until engineers intervened to manually replace the failed node, about 12.5% of users experienced application crashes and about 1% of API requests failed. Moving forward: Planned work includes improved monitoring and resilience for node failures. 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.
Status: Postmortem
Impact: Major | Started At: Dec. 17, 2022, 1:13 a.m.
Description: Incident: Between 20:00 UTC and 23:30 UTC, Asana experienced a major production outage resulting in limited web application functionality and elevated error rates for API traffic. Two principal application services that serve Asana's web traffic were impacted: LunaDb, which performs data loading and handles communication with web clients, and [Worldstore](https://blog.asana.com/2020/09/worldstore-distributed-caching-reactivity-part-1/), which functions as a database caching layer and allows users to see the changes they’ve made. Typically these services deploy independently to reduce the load on either system. However, during this incident we saw updates to both services overlap which placed stress on a shared service, causing it to fail which then cascaded to other services. Engineers responded to automated alerts within minutes of the start of the incident, but stabilizing the Worldstore cluster took several hours and several different attempts. Impact: For the duration of the incident, web-app users saw a loss of reactivity, i.e. they perceived their own changes not being saved or did not receive collaborative edits made by other users. Users of Asana’s API and mobile may have been unable to make changes to Asana at all. At around 23:30 UTC, full application functionality across webapp and API was restored. Moving forward: We are changing the configurations of our LunaDb and Worldstore services to prevent overload under similar circumstances, and adjusting deployment times of these services to avoid updating both simultaneously. 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.
Status: Postmortem
Impact: Major | Started At: Aug. 18, 2022, 9 p.m.
Description: Incident: Between 20:00 UTC and 23:30 UTC, Asana experienced a major production outage resulting in limited web application functionality and elevated error rates for API traffic. Two principal application services that serve Asana's web traffic were impacted: LunaDb, which performs data loading and handles communication with web clients, and [Worldstore](https://blog.asana.com/2020/09/worldstore-distributed-caching-reactivity-part-1/), which functions as a database caching layer and allows users to see the changes they’ve made. Typically these services deploy independently to reduce the load on either system. However, during this incident we saw updates to both services overlap which placed stress on a shared service, causing it to fail which then cascaded to other services. Engineers responded to automated alerts within minutes of the start of the incident, but stabilizing the Worldstore cluster took several hours and several different attempts. Impact: For the duration of the incident, web-app users saw a loss of reactivity, i.e. they perceived their own changes not being saved or did not receive collaborative edits made by other users. Users of Asana’s API and mobile may have been unable to make changes to Asana at all. At around 23:30 UTC, full application functionality across webapp and API was restored. Moving forward: We are changing the configurations of our LunaDb and Worldstore services to prevent overload under similar circumstances, and adjusting deployment times of these services to avoid updating both simultaneously. 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.
Status: Postmortem
Impact: Major | Started At: Aug. 18, 2022, 9 p.m.
Description: Incident: A server version change resulted in some servers in the European and Australian data centers becoming incapable of serving new sessions, leading to users being unable to load Asana. Impact: From 3:19 UTC to 8:36 UTC, a significant portion of attempts to start new sessions failed for customers with data residency in Europe or Australia. ~20% of requests failed in Europe and ~80% failed in Australia. Existing sessions were unaffected, and there was no loss of customer data. Moving forward: We have added monitoring to alert us of this failure case, and have also added safeguards to the deployment process to prevent servers from reaching this state again. 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.
Status: Postmortem
Impact: Major | Started At: July 28, 2022, 7:36 a.m.
Description: We recovered around 7:37 UTC. The impact was delayed webhooks for about 45 minutes.
Status: Resolved
Impact: Minor | Started At: June 21, 2022, 7:18 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
