Asana Outage History

An outage briefly affected the Asana EU / Mobile component, with some users in Europe experiencing intermittent access to the mobile app or features. The incident lasted about five minutes, starting at Apr 30, 2025 11:52 PM UTC and ending at Apr 30, 2025 11:57 PM UTC.

Asana's status page reported a Minor Service Outage. The EU / Mobile component moved from up to warn and then back to up, with the provider issuing two status updates during the incident to communicate the disruption and recovery.

The impact appeared limited to the EU region's mobile experience, with services restored quickly and no global disruption reported.

Asana's EU / Mobile component briefly experienced an outage beginning at Apr 25, 2025 10:27 PM UTC and resolving at Apr 25, 2025 10:37 PM UTC. Users on EU mobile platforms saw intermittent access or degraded performance during the incident. The status page listed a Minor Service Outage for the EU / Mobile component, and the issue was resolved about 10 minutes later when the component returned to normal. The outage was localized to the EU / Mobile path with no broader impact reported.

An outage briefly affected the Asana US / Mobile component, causing short degraded performance for users. The incident began at 10:12 PM UTC when the component entered a degraded state and was fully resolved by 10:17 PM UTC as services returned to normal. Asana documented the event on its status page as a Minor Service Outage, with the US / Mobile component returning to normal after two official updates, within about 5 minutes.

Asana experienced a brief partial outage in the EU region affecting the EU/API and EU/Mobile components. The incident began at Apr 25, 2025 8:57 PM UTC and was resolved by Apr 25, 2025 9:07 PM UTC, lasting about 10 minutes. Users attempting to access API or mobile features in the EU may have seen intermittent failures or degraded responses during this window.

Status updates on Asana's status page indicated a Partial System Outage for the affected components, followed by a restoration update once services were back online. The incident appeared to be isolated to EU/API and EU/Mobile, with no broader impact reported.

Asana experienced a brief outage affecting the EU / Mobile component, with users in that region potentially unable to access or experiencing degraded mobile functionality. The incident began on 10:37 PM UTC and was resolved by 10:47 PM UTC. Status updates on Asana's status page documented the event, with two updates describing a minor service outage and later restoration, and indicating the component returned to normal. The disruption appeared localized to the EU / Mobile path.

An outage affected Asana users relying on the EU / Mobile component, causing a brief degradation and service disruption lasting approximately 16 minutes. The incident began on 3:27 PM UTC when the Asana status page listed a Minor Service Outage for EU / Mobile, and was resolved by 3:43 PM UTC as the component returned to normal. The issue appeared isolated to the EU / Mobile path and did not indicate a broader impact across other regions or Asana services.

The outage began at Mar 28, 2025 5:12 PM UTC with the EU / App reporting downtime, then expanded to the US region affecting the US / API, US / App, and US / Mobile components. Users in both regions experienced downtime prompts and inability to access workflows, with a Grapevine, Texas user reporting a reload prompt around Mar 28, 2025 5:13 PM UTC. The incident involved four status updates as Asana worked to restore services. The outage lasted about 15 minutes across EU and US components.

Recovery progressed with US components returning by Mar 28, 2025 5:22 PM UTC and EU App and US App restored by Mar 28, 2025 5:27 PM UTC.

Asana experienced a partial outage starting at 10:37 PM UTC, with issues escalating from a minor service disruption to a broader partial outage. The incident affected multiple regions and core components, including the API, Asana App, Mobile apps, Webhooks and Event Streams, and Automations and Background Actions, resulting in degraded or unavailable functionality for users trying to manage tasks. The outage lasted about 35 minutes, with a fix implemented by 10:53 PM UTC and monitoring continuing until recovery was observed by 11:12 PM UTC.

An Asana partial outage affected multiple regions, impacting US Automations and Background Actions, EU Automations and Background Actions, and Japan API and Mobile. Desktop users reported trouble loading pages and repeated reload prompts, with some pages appearing blank. The incident began around 2:23 PM UTC. StatusGator detected the issue at Mar 25, 2025 2:23 PM UTC, about 4 minutes before Asana's first official update.

Asana's status page issued three updates during the incident, all labeled Partial System Outage. The first update at 2:27 PM UTC noted the initial regional impact. A second update at 2:32 PM UTC reported recovery for EU App, API, and Mobile components, while US components were still affected. The final update at 2:47 PM UTC confirmed recovery for remaining US components. The outage lasted roughly 24 minutes, with most services recovered by 2:47 PM UTC. The Early Warning Signal ended at 10:52 PM UTC.

The incident appeared to have limited user reports but disrupted access for some desktop and mobile users during the window, reflecting a cross-region partial outage across multiple Asana services.

Asana experienced a partial outage starting at 2:17 PM UTC, impacting 10 components across the US, EU, and Japan. Users reported blank pages and reload prompts across affected US, EU, and Japan apps, APIs, and mobile clients.

Over the next ~30 minutes, the incident progressed with five official updates. Recovery occurred in stages: EU App moved from down to up by 2:32 PM UTC and other EU components followed, while US and Japan components gradually restored and returned to normal by 2:47 PM UTC. The service was considered restored by that time.

User reports were modest but consistent with the symptoms, with 3 reports logged by 2:15 PM UTC describing blank pages or reload prompts across offices and remote work environments.