Asana Outage History

Users in the United States faced a partial outage where the Asana web app failed to load for a subset of users. The issue began around 6:26 PM UTC with reports of pages not loading, and Asana acknowledged the problem at 6:52 PM UTC, noting that about 10% of US users were affected and that the root cause had been identified with a fix in progress. StatusGator detected the issue at 6:26 PM UTC, roughly 26 minutes before the official acknowledgment. A mitigation was put in place by 7:17 PM UTC as the team monitored for recovery.

Users relying on Asana in the EU region experienced a disruption to webhooks and real-time event streams as the EU / Webhooks and Event Streams component degraded at 11:02 AM UTC, escalating to a full outage by 11:07 AM UTC. The service remained unavailable for the affected features for about two hours, with recovery completed by 1:07 PM UTC. During the incident, webhook deliveries and event-driven updates stalled, impacting automations, integrations, and real-time collaboration workflows that depend on Asana events.

Asana's status updates showed the EU component moving from up to warn, then down, and back to up as engineers worked to restore functionality. The outage was localized to the EU region's Webhooks and Event Streams and did not indicate a broader global disruption.

Starting at 9:22 AM UTC, Asana's EU / Mobile component showed degraded performance, affecting users in Europe and on mobile clients with slower page loads and intermittent access. The status page reflected the impact by listing the EU / Mobile component as degraded and moving the incident to a warning state.

About an hour later, at 10:22 AM UTC, the EU / Mobile component returned to normal and the status transitioned back to up. The incident was contained to the EU region and services were restored with no broader impact indicated.

Users in Europe on Asana's mobile path experienced a brief degraded performance when the EU / Mobile component entered a degraded state. According to Asana's status updates, the issue began at 10:12 AM UTC and was resolved about forty minutes later, with the component returning to normal at 10:52 AM UTC after moving from up to warn and back to up.

The incident appeared regional to the EU / Mobile path and did not indicate broader service disruption. The status changes reflect a short-lived degradation that was addressed promptly, returning to full functionality for users once the component recovered.

Users in Asana's EU region experienced degraded performance that impacted the mobile app and webhook/event streaming integrations. The degradation began for EU / Mobile at 8:57 AM UTC, followed by EU / Webhooks and Event Streams entering a degraded state at 9:27 AM UTC. The Webhooks and Event Streams component briefly recovered before another brief degradation, and both components returned to normal by 10:02 AM UTC as EU / Mobile moved back to up. The incident was regional in scope and appeared to affect user interactions relying on mobile access and automated integrations.

Asana users on mobile in Europe experienced a brief degradation in the EU / Mobile component, which could have caused intermittent access or slower performance. The issue began at 11:22 AM UTC and was resolved by 12:07 PM UTC, lasting about 45 minutes.

European users of the Asana mobile app experienced degraded performance for a short period, limited to the EU / Mobile component. The impact likely included slower responses or intermittent access for mobile users in Europe. The incident began at 10:42 AM UTC and was resolved by 11:07 AM UTC.

Status page updates show the EU / Mobile component moving from up to warn at 10:42 AM UTC and then returning to up at 11:07 AM UTC, indicating a brief partial outage affecting European mobile users.

An incident affected Asana's EU / Mobile component, briefly impacting users relying on mobile access in the European region. The issue began at 9:27 AM UTC and was resolved by 10:07 AM UTC, with the component moving from up to a degraded state and back to normal within about 40 minutes. Asana's status page documented the EU / Mobile component transitioning during that window and then returning to full operation. The event appears to have been localized to the EU region and did not indicate a broader service impact.

Users in Asana's EU region using the Mobile component experienced a brief degradation beginning at 10:22 AM UTC, as the EU / Mobile service entered a degraded state on the status page. The issue was resolved by 10:42 AM UTC, with the component returning to normal. The impact appeared isolated to that component and did not indicate a broader disruption across other regions or features. The recovery occurred within about twenty minutes, with no lasting impact after the resolution.

Asana's mobile app in the EU region experienced a brief degradation, with intermittent access and slower performance for about fifty minutes as the EU / Mobile component entered a degraded state. The impact began at Jun 24, 2026 9:07 AM UTC and was resolved by Jun 24, 2026 9:57 AM UTC. The EU / Mobile component then returned to normal, according to updates on Asana's status page. The disruption was localized to EU/mobile and did not indicate a wider impact.