Is there an Asana outage?
Asana status: Systems Active
Last checked: 3 minutes ago
Get notified about any outages, downtime or incidents for Asana and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 3 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: A bug in our cleanup scripts caused some active container repositories to become unavailable. At approximately 13:33 UTC, a memory problem caused servers which handle pageload \(initial load of our web application\) to crash, and because of the bug in the cleanup script they were unable to restart without operator intervention. Customers were unable to start new sessions for about 28 minutes, but existing sessions were unaffected. Impact: Asana was largely unavailable to new sessions for 28 minutes on Asana Desktop. Existing sessions, mobile and API were unaffected. Moving Forward: We will be conducting a 5 Whys analysis to identify process changes that can prevent similar incidents in the future. We will also work on detecting this type of issue before they impact customer traffic. 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: Jan. 1, 2023, 1:30 p.m.
Description: Incident: A bug in our cleanup scripts caused some active container repositories to become unavailable. At approximately 13:33 UTC, a memory problem caused servers which handle pageload \(initial load of our web application\) to crash, and because of the bug in the cleanup script they were unable to restart without operator intervention. Customers were unable to start new sessions for about 28 minutes, but existing sessions were unaffected. Impact: Asana was largely unavailable to new sessions for 28 minutes on Asana Desktop. Existing sessions, mobile and API were unaffected. Moving Forward: We will be conducting a 5 Whys analysis to identify process changes that can prevent similar incidents in the future. We will also work on detecting this type of issue before they impact customer traffic. 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: Jan. 1, 2023, 1:30 p.m.
Description: **Incident**: A scheduled, manual deployment led to abnormally high load on our reactive data loading layer, overloading it. Application level caches were slow to update, and a subset of data returned to customers was stale. **Impact**: Although application writes continued to be successful, a subset of customers experienced delays in viewing their changes to the Asana webapp from 2022-12-21 00:27 - 01:52 UTC. By 02:20 UTC, tabs that were loaded or refreshed no longer contained stale data. By 03:10 UTC, all users were no longer seeing stale data. About 2% of customer API requests also experienced timeouts until 01:52 UTC. Affected API customers would have seen persistently failing API read requests. **Moving forward**: We have identified operational changes to reduce the likelihood of incidents and decrease the time to resolution. 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. 21, 2022, 2:11 a.m.
Description: **Incident**: A scheduled, manual deployment led to abnormally high load on our reactive data loading layer, overloading it. Application level caches were slow to update, and a subset of data returned to customers was stale. **Impact**: Although application writes continued to be successful, a subset of customers experienced delays in viewing their changes to the Asana webapp from 2022-12-21 00:27 - 01:52 UTC. By 02:20 UTC, tabs that were loaded or refreshed no longer contained stale data. By 03:10 UTC, all users were no longer seeing stale data. About 2% of customer API requests also experienced timeouts until 01:52 UTC. Affected API customers would have seen persistently failing API read requests. **Moving forward**: We have identified operational changes to reduce the likelihood of incidents and decrease the time to resolution. 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. 21, 2022, 2:11 a.m.
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.
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.
