Is there an Asana outage?
Asana status: Systems Active
Last checked: 53 seconds ago
Get notified about any outages, downtime or incidents for Asana and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 53 seconds 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. 2, 2024, 8:09 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Jan. 17, 2024, 7 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Jan. 17, 2024, 7 p.m.
Description: **Incident** On 2023-12-20, an engineer made a configuration change that caused a large amount of unexpected logging. The following day during peak hours, at 2023-12-21 at 14:13 UTC, the excess logging caused resource saturation that led to slow requests and timeouts. The configuration change was reverted, and related infrastructure was scaled up to aid recovery. After initial recovery, some users experienced a second period of degraded performance due to a retry mechanism that confirms event logs are recorded. **Impact** On 2023-12-21, between 14:13 UTC and 14:18 UTC, about 20% of Asana users in the US region experienced forced reloads, and existing sessions experienced delayed writes and API performance issues. Between 15:35 UTC and 15:45 UTC, about 5% of Asana users experienced delayed writes and API performance issues. Application uptime and performance was fully restored by 2023-12-21 15:46 UTC. No data was lost. **Moving Forward** The incident uncovered a gap in how we monitor logging volume and its effects on server performance during high traffic times. Moving forward, we have action items to improve the resiliency of our infrastructure to unexpected increases in logging volume, as well as to ensure our monitoring will enable us to proactively detect and prevent similar issues in the future. 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: Dec. 20, 2023, 10:13 p.m.
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.
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.
