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: Our engineers have fixed the issue and Asana is now running normally. Again sincere apologies for any inconvenience this caused!
Status: Resolved
Impact: None | Started At: Feb. 22, 2024, 1:09 a.m.
Description: **Incident:** On 2024-02-08 from 19:19 UTC to 20:16 UTC one of our API authentication mechanisms experienced an outage, resulting in a 44% failure rate for API requests during the incident across all regions. The outage was caused by a backwards-incompatible dependency upgrade that was not caught before being deployed to production. [Asana's status page](https://status.asana.com/) was updated at 19:30 UTC to reflect a partial outage and we finished rolling back the deployment at 20:15 UTC. **Impact:** The outage impacted all customers accessing the API with an OAuth bearer token, directly or through the use of an app integration. API access using personal access tokens and via service accounts was not impacted by this outage. No data loss occurred during the incident. **Moving forward:** We will enhance our monitoring with test cases for the specific failure we observed. We are also investing in changes to our deployment process to better catch issues like this prior to deployment to production. 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: Feb. 8, 2024, 7:30 p.m.
Description: **Incident:** On 2024-02-08 from 19:19 UTC to 20:16 UTC one of our API authentication mechanisms experienced an outage, resulting in a 44% failure rate for API requests during the incident across all regions. The outage was caused by a backwards-incompatible dependency upgrade that was not caught before being deployed to production. [Asana's status page](https://status.asana.com/) was updated at 19:30 UTC to reflect a partial outage and we finished rolling back the deployment at 20:15 UTC. **Impact:** The outage impacted all customers accessing the API with an OAuth bearer token, directly or through the use of an app integration. API access using personal access tokens and via service accounts was not impacted by this outage. No data loss occurred during the incident. **Moving forward:** We will enhance our monitoring with test cases for the specific failure we observed. We are also investing in changes to our deployment process to better catch issues like this prior to deployment to production. 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: Feb. 8, 2024, 7:30 p.m.
Description: **Incident**: On 2024-02-07, a deployment of new code introduced a performance regression for automations and background actions. In our European data center during peak traffic from 03:56 to 04:54 UTC, our background job system hit autoscaling safety limits and did not keep up with incoming work due to the performance regression. We reverted this deployment and increased our scaling limits to speed time to recovery. **Impact**: During the incident, customers in our European data center experienced delayed background actions, such as rules, email notifications, imports and exports. No customer data was lost. **Moving forward**: We will improve our monitoring and playbooks to more quickly identify regressions like this and improve our ability to promptly respond. We have identified the root cause of this particular performance regression and are resolving the issue. 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: Minor | Started At: Feb. 7, 2024, 4 a.m.
Description: **Incident**: On 2024-02-07, a deployment of new code introduced a performance regression for automations and background actions. In our European data center during peak traffic from 03:56 to 04:54 UTC, our background job system hit autoscaling safety limits and did not keep up with incoming work due to the performance regression. We reverted this deployment and increased our scaling limits to speed time to recovery. **Impact**: During the incident, customers in our European data center experienced delayed background actions, such as rules, email notifications, imports and exports. No customer data was lost. **Moving forward**: We will improve our monitoring and playbooks to more quickly identify regressions like this and improve our ability to promptly respond. We have identified the root cause of this particular performance regression and are resolving the issue. 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: Minor | Started At: Feb. 7, 2024, 4 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.
