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: This incident has been resolved.
Status: Resolved
Impact: Major | Started At: April 25, 2022, 4:16 p.m.
Description: Incident: At 2022-04-05 00:00 UTC, maintenance on underlying hardware caused a leader node in a critical system to become unavailable. This had an unexpected impact on dependent systems, causing them to crash. Automated resolution can take up to 15 minutes; we took manual action to recover sooner. Unfortunately, it took longer for the dependent systems to stabilize. Impact: The web app was unavailable from 00:00 -00:25 UTC, and the API and mobile apps from 00:00-00:33 UTC. Moving Forward: We are in the process of deprecating the dependency of our core systems on the system which failed. We are also looking at how our systems could have continued running in a degraded state instead of crashing. 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: April 5, 2022, midnight
Description: Incident: At 2022-04-05 00:00 UTC, maintenance on underlying hardware caused a leader node in a critical system to become unavailable. This had an unexpected impact on dependent systems, causing them to crash. Automated resolution can take up to 15 minutes; we took manual action to recover sooner. Unfortunately, it took longer for the dependent systems to stabilize. Impact: The web app was unavailable from 00:00 -00:25 UTC, and the API and mobile apps from 00:00-00:33 UTC. Moving Forward: We are in the process of deprecating the dependency of our core systems on the system which failed. We are also looking at how our systems could have continued running in a degraded state instead of crashing. 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: April 5, 2022, midnight
Description: Incident: Beginning around 7am UTC, we began observing API traffic failures, which continued to deteriorate. When action was taken to resolve the issues at a high peak traffic time, key components of the system overloaded. Impact: Asana experienced approximately 50% unavailability from 14:10-14:36 UTC and approximately 30% unavailability from 16:21-16:30 UTC. An operator error during the final part of the response caused full unavailability from 18:58-19:40 UTC. The API remained unavailable until 19:54 UTC. Background systems resumed normal operation by 20:15 UTC. Moving Forward: We have since updated our tools to make operator error unlikely to recur, and are investigating the cause of the initial problems. 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: April 4, 2022, 2:33 p.m.
Description: Incident: Beginning around 7am UTC, we began observing API traffic failures, which continued to deteriorate. When action was taken to resolve the issues at a high peak traffic time, key components of the system overloaded. Impact: Asana experienced approximately 50% unavailability from 14:10-14:36 UTC and approximately 30% unavailability from 16:21-16:30 UTC. An operator error during the final part of the response caused full unavailability from 18:58-19:40 UTC. The API remained unavailable until 19:54 UTC. Background systems resumed normal operation by 20:15 UTC. Moving Forward: We have since updated our tools to make operator error unlikely to recur, and are investigating the cause of the initial problems. 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: April 4, 2022, 2:33 p.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.
