# Asana: Elevated application and API/Mobile errors

> Asana status incident “Elevated application and API/Mobile errors” on 2025-06-25: impact none (vendor’s label), 10 min, 4 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/asana/incidents/trn8dzjpj1rb
Last updated: 2025-06-27T22:20:46Z

- Impact (vendor’s label): none
- Status: postmortem
- Started: 2025-06-25 12:25 UTC · Resolved: 2025-06-25 12:35 UTC · Duration: 10 min
- Updates: 4 · Affected components: App, Japan - App, Mobile, US - Mobile, App, US - App, Automations and Background Actions, EU - Automations and Background Actions, Automations and Background Actions, Japan - Automations and Background Actions, Automations and Background Actions, US - Automations and Background Actions, API, Australia - API, App, EU - App, Australia - Mobile, Mobile, API, Japan - API, App, Australia - App, Japan - Mobile, Mobile, API, EU - API, Australia - Automations and Background Actions, Automations and Background Actions, EU - Mobile, Mobile, API, US - API
- [Vendor status page: https://stspg.io/dgh235rqg7ws](https://stspg.io/dgh235rqg7ws)
- [Company: Asana](https://rewindex.com/company/asana.md)

## Timeline of updates

- **monitoring** 2025-06-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.
- **monitoring** 2025-06-25 12:30 UTC: We are continuing to monitor for any further issues.
- **resolved** 2025-06-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.
- **postmortem** 2025-06-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.

## Cite this

Status incident (vendor impact label: none) posted by Asana, started 2025-06-25 12:25 UTC, resolved after 10 min, 4 update(s).

- Canonical URL: https://rewindex.com/company/asana/incidents/trn8dzjpj1rb
- Citation: Asana, “Elevated application and API/Mobile errors” (2025-06-25 12:25 UTC). Archived by Rewindex: https://rewindex.com/company/asana/incidents/trn8dzjpj1rb (CC BY 4.0).
- Markdown link: `[Asana: Elevated application and API/Mobile errors (2025-06-25)](https://rewindex.com/company/asana/incidents/trn8dzjpj1rb)`


---
Canonical: https://rewindex.com/company/asana/incidents/trn8dzjpj1rb · Markdown: https://rewindex.com/company/asana/incidents/trn8dzjpj1rb.md · JSON: https://rewindex.com/api/v1/companies/asana/incidents/trn8dzjpj1rb · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T15:06:12.148Z
