Last checked: 8 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: Webhooks delivery was delayed from 7:10 PM PST to 8:15 PM PST. As of 8:23 PM PST, there is no longer a delay. The incident happened because of a scheduled database cleanup. No events were lost.
Status: Resolved
Impact: Minor | Started At: Jan. 28, 2022, 3 a.m.
Description: Incident: During a routine hardware change, a misconfiguration of our load balancer health checks caused EU load balancers to be marked as unhealthy, rejecting all requests from users. Impact: Asana was unavailable to load new sessions for EU users for 135 minutes, with only existing sessions able to be used. No customer data was lost. Moving forward: As a result of this incident, we are working to simplify load balancer architecture and improve operational processes around hardware changes. 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. 20, 2022, 8 p.m.
Description: Incident: During a routine hardware change, a misconfiguration of our load balancer health checks caused EU load balancers to be marked as unhealthy, rejecting all requests from users. Impact: Asana was unavailable to load new sessions for EU users for 135 minutes, with only existing sessions able to be used. No customer data was lost. Moving forward: As a result of this incident, we are working to simplify load balancer architecture and improve operational processes around hardware changes. 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. 20, 2022, 8 p.m.
Description: Incident: On 1/19/22 we made a configuration change that overloaded a class of servers required for serving web, mobile and API traffic. This overload subsequently cascaded to downstream systems responsible for displaying users’ changes. Impact: Users were unable to load new Asana sessions for 19 minutes. API and mobile users experienced downtime because many changes were not displayed. Some changes made through the application were not reflected for an additional ~2 hours. Moving Forward: We are working to make system components more resilient to failures in upstream dependencies. 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. 19, 2022, 1:01 a.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Critical | Started At: Jan. 19, 2022, 12:25 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.