rewindex

CompaniesAsanaIncidents

Asana: Elevated application and API/Mobile errors

No impact listedStatus: postmortemStarted Resolved (10 min)4 updatesstspg.io (opens in new tab)

Affected components: AppJapan - AppMobileUS - MobileAppUS - AppAutomations and Background ActionsEU - Automations and Background ActionsAutomations and Background ActionsJapan - Automations and Background ActionsAutomations and Background ActionsUS - Automations and Background ActionsAPIAustralia - APIAppEU - AppAustralia - MobileMobileAPIJapan - APIAppAustralia - AppJapan - MobileMobileAPIEU - APIAustralia - Automations and Background ActionsAutomations and Background ActionsEU - MobileMobileAPIUS - API

Timeline of updates

  1. monitoring

    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.

  2. monitoring

    We are continuing to monitor for any further issues.

  3. resolved

    All system appear to have recovered, with recovery starting around 12:14 UTC. We will publish a postmortem within 72 hours.

  4. postmortem

    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.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

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).

Title
Elevated application and API/Mobile errors
Vendor
Asana
Date
URL
https://rewindex.com/company/asana/incidents/trn8dzjpj1rb

Asana profileRecent Asana incidentsAll outages on June 25, 2025Asana in June 2025MarkdownJSON