Last checked: 6 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**: At 2023-12-14 23:40 UTC, an engineer made a configuration change that caused downtime. We reverted, but determined that some application servers got into an unrecoverable bad state. Affected servers were identified and restarted; to avoid overload, traffic was allowed to return incrementally as the servers became ready. Background actions were delayed starting at 2023-12-15 00:22 to aid recovery. **Impact**: This resulted in full application and API downtime across all regions. For the US region, application downtime was resolved for most users between 2023-12-15 00:13 and 00:30. For EU, Japan, and Australia, resolution started around 00:40. API traffic was restored between 00:36 and 00:43. Application and API availability was completely restored for all users by 2023-12-15 00:49. Background actions were delayed from 2023-12-15 00:22 through 01:08, with complete resolution by 01:30. **Moving forward**: This incident uncovered a bug preventing automatic restarts of our backend servers. We have action items to fix this bug, improve validation and config handling, and enhance observability and operational tools. In the medium term, we are working on creating more independent failure domains to limit the scope of unexpected downtime. We will follow our [5 Whys process](https://wavelength.asana.com/workstyle-ask-5-whys-to-get-to-the-root-of-any-problem/) to identify other potential action items. 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: Critical | Started At: Dec. 14, 2023, 11:55 p.m.
Description: **Incident:** Databases containing authentication information experienced increased load and reduced throughput due to a database migration. **Impact:** On 2023-11-28 from 18:00-18:25 PST, the Asana API was operating in a degraded state and/or unavailable. Asana Mobile and API users experienced increased response times and errors during this incident. **Moving forward:** To prevent similar incidents, Asana has increased database compute provisioning and has developed monitoring around the root cause. 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: None | Started At: Nov. 29, 2023, 2 a.m.
Description: **Incident:** Databases containing authentication information experienced increased load and reduced throughput due to a database migration. **Impact:** On 2023-11-28 from 18:00-18:25 PST, the Asana API was operating in a degraded state and/or unavailable. Asana Mobile and API users experienced increased response times and errors during this incident. **Moving forward:** To prevent similar incidents, Asana has increased database compute provisioning and has developed monitoring around the root cause. 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: None | Started At: Nov. 29, 2023, 2 a.m.
Description: **Incident:** On June 13, 2023, AWS had an outage for the AWS Lambda service for about 3.5 hours. This outage led certain Asana features, most notably webhooks, to not be available to Asana users. **Impact:** Asana users experienced an outage in webhooks functionality for about 3 hours, with a degradation for approximately another 40 mins. During the outage, users of webhooks were not able to receive webhook events. The outage led to a delay in delivery of these events and there was no loss of data. **Moving forward:** We are enhancing our operational tools in order to be more resilient to this type of outage and to minimize any potential impact of AWS unavailability.
Status: Postmortem
Impact: Major | Started At: June 13, 2023, 8:31 p.m.
Description: **Incident:** On June 13, 2023, AWS had an outage for the AWS Lambda service for about 3.5 hours. This outage led certain Asana features, most notably webhooks, to not be available to Asana users. **Impact:** Asana users experienced an outage in webhooks functionality for about 3 hours, with a degradation for approximately another 40 mins. During the outage, users of webhooks were not able to receive webhook events. The outage led to a delay in delivery of these events and there was no loss of data. **Moving forward:** We are enhancing our operational tools in order to be more resilient to this type of outage and to minimize any potential impact of AWS unavailability.
Status: Postmortem
Impact: Major | Started At: June 13, 2023, 8:31 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.