Elevated application and API/Mobile errors

Final update

**Incident**: A configuration change unintentionally blocked internal network access between application components. This change was identified as the cause of downtime and reverted.  **Impact**: The Asana App and API were unavailable for 24 minutes. App and API traffic recovered over the next 5 minutes, and Automations & Background Actions recovered over 10 minutes.  **Moving forward**: We have completed a redesign of our core application architecture to better protect our services from disruption by segmentation into independent sections, or "cells." We are considering ways we can leverage this architecture to roll out configuration changes like the one which triggered this incident more gradually and carefully across our systems to ensure safety & stability. 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.

1. Postmortem · Jun 27, 22:20 UTC
   **Incident**: A configuration change unintentionally blocked internal network access between application components. This change was identified as the cause of downtime and reverted.  **Impact**: The Asana App and API were unavailable for 24 minutes. App and API traffic recovered over the next 5 minutes, and Automations & Background Actions recovered over 10 minutes.  **Moving forward**: We have completed a redesign of our core application architecture to better protect our services from disruption by segmentation into independent sections, or "cells." We are considering ways we can leverage this architecture to roll out configuration changes like the one which triggered this incident more gradually and carefully across our systems to ensure safety & stability. 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.
2. Resolved · Jun 25, 12:35 UTC
   All system appear to have recovered, with recovery starting around 12:14 UTC. We will publish a postmortem within 72 hours.
3. Monitoring · Jun 25, 12:30 UTC
   We are continuing to monitor for any further issues.
4. Monitoring · Jun 25, 12:25 UTC
   We have identified an issue causing errors starting around 11:50 UTC, and have reverted the change which caused this. We are monitoring to confirm recovery.