Asana Status

Resolved: This incident has been resolved. We are doing root cause analysis and will post an update within 72 hours.

Monitoring: We have scaled up affected infrastructure are continuing to monitor application health and metrics.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We saw a high rate of errors due to overload of internal infrastructure. We see partial recovery, and are continuing to investigate.

Postmortem: Incident: A configuration change triggered a bug affecting how internal systems process configuration data, leading to application downtime. The issue impacted internal server uptime, resulting in approximately 28 minutes of degraded service on March 25, 2025, from 22:32 UTC to 23:00 UTC (3:32 PM to 4:00 PM PDT).

‌

Impact: During the incident, customers experienced difficulties accessing Asana on web and mobile apps, including login failures and errors while using the application. Internal services gradually recovered after the problematic change was reverted.

‌

Moving forward: We are enhancing our configuration validation processes to prevent similar issues. Additional monitoring and safeguards are being introduced to ensure rapid identification and recovery from similar incidents.

‌

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.

Resolved: This incident has been resolved.

Monitoring: Our systems have recovered, and we are continuing to monitor.

Monitoring: Asana App and API had about 9 minutes of downtime due to a configuration error; a fix has been implemented, and we are observing for recovery.

Resolved: This incident has been resolved. We are doing root cause analysis and will post an update within 72 hours.

Monitoring: We have scaled up affected infrastructure are continuing to monitor application health and metrics.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We saw a high rate of errors due to overload of internal infrastructure. We see partial recovery, and are continuing to investigate.

Postmortem: Incident: A configuration change triggered a bug affecting how internal systems process configuration data, leading to application downtime. The issue impacted internal server uptime, resulting in approximately 28 minutes of degraded service on March 25, 2025, from 22:32 UTC to 23:00 UTC (3:32 PM to 4:00 PM PDT).

‌

Impact: During the incident, customers experienced difficulties accessing Asana on web and mobile apps, including login failures and errors while using the application. Internal services gradually recovered after the problematic change was reverted.

‌

Moving forward: We are enhancing our configuration validation processes to prevent similar issues. Additional monitoring and safeguards are being introduced to ensure rapid identification and recovery from similar incidents.

‌

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.

Resolved: This incident has been resolved.

Monitoring: Our systems have recovered, and we are continuing to monitor.

Monitoring: Asana App and API had about 9 minutes of downtime due to a configuration error; a fix has been implemented, and we are observing for recovery.

Resolved: This incident has been resolved. We are doing root cause analysis and will post an update within 72 hours.

Monitoring: We have scaled up affected infrastructure are continuing to monitor application health and metrics.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We saw a high rate of errors due to overload of internal infrastructure. We see partial recovery, and are continuing to investigate.

Postmortem: Incident: A configuration change triggered a bug affecting how internal systems process configuration data, leading to application downtime. The issue impacted internal server uptime, resulting in approximately 28 minutes of degraded service on March 25, 2025, from 22:32 UTC to 23:00 UTC (3:32 PM to 4:00 PM PDT).

‌

Impact: During the incident, customers experienced difficulties accessing Asana on web and mobile apps, including login failures and errors while using the application. Internal services gradually recovered after the problematic change was reverted.

‌

Moving forward: We are enhancing our configuration validation processes to prevent similar issues. Additional monitoring and safeguards are being introduced to ensure rapid identification and recovery from similar incidents.

‌

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.

Resolved: This incident has been resolved.

Monitoring: Our systems have recovered, and we are continuing to monitor.

Monitoring: Asana App and API had about 9 minutes of downtime due to a configuration error; a fix has been implemented, and we are observing for recovery.

Resolved: This incident has been resolved. We are doing root cause analysis and will post an update within 72 hours.

Monitoring: We have scaled up affected infrastructure are continuing to monitor application health and metrics.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We saw a high rate of errors due to overload of internal infrastructure. We see partial recovery, and are continuing to investigate.

Postmortem: Incident: A configuration change triggered a bug affecting how internal systems process configuration data, leading to application downtime. The issue impacted internal server uptime, resulting in approximately 28 minutes of degraded service on March 25, 2025, from 22:32 UTC to 23:00 UTC (3:32 PM to 4:00 PM PDT).

‌

Impact: During the incident, customers experienced difficulties accessing Asana on web and mobile apps, including login failures and errors while using the application. Internal services gradually recovered after the problematic change was reverted.

‌

Moving forward: We are enhancing our configuration validation processes to prevent similar issues. Additional monitoring and safeguards are being introduced to ensure rapid identification and recovery from similar incidents.

‌

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.

Resolved: This incident has been resolved.

Monitoring: Our systems have recovered, and we are continuing to monitor.

Monitoring: Asana App and API had about 9 minutes of downtime due to a configuration error; a fix has been implemented, and we are observing for recovery.

Resolved: This incident has been resolved. We are doing root cause analysis and will post an update within 72 hours.

Monitoring: We have scaled up affected infrastructure are continuing to monitor application health and metrics.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We saw a high rate of errors due to overload of internal infrastructure. We see partial recovery, and are continuing to investigate.

Postmortem: Incident: A configuration change triggered a bug affecting how internal systems process configuration data, leading to application downtime. The issue impacted internal server uptime, resulting in approximately 28 minutes of degraded service on March 25, 2025, from 22:32 UTC to 23:00 UTC (3:32 PM to 4:00 PM PDT).

‌

Impact: During the incident, customers experienced difficulties accessing Asana on web and mobile apps, including login failures and errors while using the application. Internal services gradually recovered after the problematic change was reverted.

‌

Moving forward: We are enhancing our configuration validation processes to prevent similar issues. Additional monitoring and safeguards are being introduced to ensure rapid identification and recovery from similar incidents.

‌

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.

Resolved: This incident has been resolved.

Monitoring: Our systems have recovered, and we are continuing to monitor.

Monitoring: Asana App and API had about 9 minutes of downtime due to a configuration error; a fix has been implemented, and we are observing for recovery.

Resolved: This incident has been resolved. We are doing root cause analysis and will post an update within 72 hours.

Monitoring: We have scaled up affected infrastructure are continuing to monitor application health and metrics.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We saw a high rate of errors due to overload of internal infrastructure. We see partial recovery, and are continuing to investigate.

Postmortem: Incident: A configuration change triggered a bug affecting how internal systems process configuration data, leading to application downtime. The issue impacted internal server uptime, resulting in approximately 28 minutes of degraded service on March 25, 2025, from 22:32 UTC to 23:00 UTC (3:32 PM to 4:00 PM PDT).

‌

Impact: During the incident, customers experienced difficulties accessing Asana on web and mobile apps, including login failures and errors while using the application. Internal services gradually recovered after the problematic change was reverted.

‌

Moving forward: We are enhancing our configuration validation processes to prevent similar issues. Additional monitoring and safeguards are being introduced to ensure rapid identification and recovery from similar incidents.

‌

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.

Resolved: This incident has been resolved.

Monitoring: Our systems have recovered, and we are continuing to monitor.

Monitoring: Asana App and API had about 9 minutes of downtime due to a configuration error; a fix has been implemented, and we are observing for recovery.

Resolved: This incident has been resolved. We are doing root cause analysis and will post an update within 72 hours.

Monitoring: We have scaled up affected infrastructure are continuing to monitor application health and metrics.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We saw a high rate of errors due to overload of internal infrastructure. We see partial recovery, and are continuing to investigate.

Postmortem: Incident: A configuration change triggered a bug affecting how internal systems process configuration data, leading to application downtime. The issue impacted internal server uptime, resulting in approximately 28 minutes of degraded service on March 25, 2025, from 22:32 UTC to 23:00 UTC (3:32 PM to 4:00 PM PDT).

‌

Impact: During the incident, customers experienced difficulties accessing Asana on web and mobile apps, including login failures and errors while using the application. Internal services gradually recovered after the problematic change was reverted.

‌

Moving forward: We are enhancing our configuration validation processes to prevent similar issues. Additional monitoring and safeguards are being introduced to ensure rapid identification and recovery from similar incidents.

‌

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.

Resolved: This incident has been resolved.

Monitoring: Our systems have recovered, and we are continuing to monitor.

Monitoring: Asana App and API had about 9 minutes of downtime due to a configuration error; a fix has been implemented, and we are observing for recovery.

Resolved: This incident has been resolved. We are doing root cause analysis and will post an update within 72 hours.

Monitoring: We have scaled up affected infrastructure are continuing to monitor application health and metrics.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We saw a high rate of errors due to overload of internal infrastructure. We see partial recovery, and are continuing to investigate.

Postmortem: Incident: A configuration change triggered a bug affecting how internal systems process configuration data, leading to application downtime. The issue impacted internal server uptime, resulting in approximately 28 minutes of degraded service on March 25, 2025, from 22:32 UTC to 23:00 UTC (3:32 PM to 4:00 PM PDT).

‌

Impact: During the incident, customers experienced difficulties accessing Asana on web and mobile apps, including login failures and errors while using the application. Internal services gradually recovered after the problematic change was reverted.

‌

Moving forward: We are enhancing our configuration validation processes to prevent similar issues. Additional monitoring and safeguards are being introduced to ensure rapid identification and recovery from similar incidents.

‌

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.

Resolved: This incident has been resolved.

Monitoring: Our systems have recovered, and we are continuing to monitor.

Monitoring: Asana App and API had about 9 minutes of downtime due to a configuration error; a fix has been implemented, and we are observing for recovery.