Asana outage history

Asana experienced a brief degradation in API responses affecting multiple regions. The issue started in the US / API, Australia / API, Middle East / API, Japan / API, and EU / API at 9:52 PM UTC and persisted for about five minutes before services returned to normal, with the affected endpoints returning to their usual status by 9:57 PM UTC. Status updates indicated these regional API components entered a degraded state briefly before full restoration.

Users in Europe relying on the Asana mobile app experienced degraded performance for about 30 minutes as the EU / Mobile component briefly entered a degraded state. The issue began at 8:42 AM UTC and was resolved by 9:12 AM UTC. Asana's status page updates indicated the EU / Mobile area had returned to normal after the incident, with no broader impact on other regions or platforms.

Asana users may have experienced slower API responses and intermittent access issues as API endpoints in the US, EU, Australia, Middle East, and Japan briefly entered a degraded state. The disruption began at 9:17 PM UTC and was resolved by 9:22 PM UTC, lasting about five minutes before services returned to normal.

An issue in the EU / Mobile component caused a brief degradation of Asana for users in Europe. The degradation began at 9:37 AM UTC and was resolved by 10:12 AM UTC, lasting about 35 minutes. During this window, users on mobile in Europe may have encountered slower responses or intermittent access when using Asana, with the EU / Mobile component listed as degraded before returning to normal.

Asana experienced a brief degradation in the Middle East API component, with users in that region potentially seeing slower API responses while the issue was active. The degraded status began at 9:13 PM UTC and was resolved by 9:17 PM UTC as the component returned to normal. The incident was isolated to this regional API endpoint and did not indicate a broader service impact.

Users in the US region experienced a partial outage affecting Asana's API and mobile apps, with downstream Webhooks and Event Streams impacted early in the incident. The issue started with degraded Webhooks and Event Streams around 1:18 PM UTC and escalated to a broader outage by 1:32 PM UTC. By 2:37 PM UTC a Partial API outage was acknowledged while investigations continued. Webhooks and Event Streams briefly recovered by 2:52 PM UTC, and API and Mobile components returned to normal by 3:22 PM UTC. The outage lasted roughly two hours before full recovery.

A partial outage hit Asana's EU API, with users in Europe experiencing API access issues. The incident began at Sep 29, 2026 12:17 PM UTC when Asana flagged an EU API impairment and began investigating. Engineers worked to restore service, and the EU API component returned to normal by 3:27 PM UTC as the status moved back to up. The impact was localized to the EU region’s API surface, with operations returning to normal after the resolution.

Users in Europe relying on Asana on mobile experienced degraded performance starting at 8:22 AM UTC when the EU / Mobile component entered a degraded state, and the issue was resolved by 10:27 AM UTC. The event appeared limited to the EU / Mobile path and likely affected app responsiveness and syncing for about two hours before service returned to normal. Asana's status page documented a brief degradation and subsequent recovery as engineers worked to restore full functionality.

Users in the European region relying on Asana's mobile app experienced degraded performance for about 39 minutes, with the EU / Mobile component returning to normal after the incident. The issue began at 9:33 AM UTC and was resolved by 10:12 AM UTC according to Asana's status page updates. The impact appeared limited to the EU / Mobile path and did not indicate broader effects on other regions or on desktop access.

Asana experienced a brief degradation in its US Webhooks and Event Streams, with a degraded state starting at Sep 26, 2026 1:22 PM UTC. Webhook deliveries and real-time event streams for US integrations were affected for about 30 minutes before the component returned to normal by Sep 26, 2026 1:52 PM UTC. The incident was localized to the US Webhooks and Event Streams component, and normal service was restored after the brief disruption.