# Asana: Major incident: Elevated error rates

**Summary:** A major Asana outage left a majority of users unable to access Asana, affecting API and App components in Australia, EU, Japan and US. It ran from 2024-06-17 16:44 UTC to 2024-06-17 19:49 UTC (3 h 4 min). Asana attributed failures to load balancer resource saturation under high traffic; a fix was implemented at 06-17 16:52 UTC. _(machine-written, sol)_
- Kind: Major incident · Label: outage (model (Jev))
- Changed: 2024-06-17 16:44 UTC · Detected: 2026-10-17 18:22 UTC
- [Source: https://stspg.io/4k4m7x3yq5w5](https://stspg.io/4k4m7x3yq5w5)
- [Company: Asana](https://rewindex.com/company/asana.md)
- Versions: before (none: first archived) → after incident\_version:90/vqkfn889w7zf@0d8fe9e27ab9
- Change 1 of 1 for this incident

## What changed

**1. Added: Title**

```diff
+ Elevated error rates
```

**2. Added: Impact**

```diff
+ major
```

**3. Added: Status**

```diff
+ postmortem
```

**4. Added: Start time**

```diff
+ 2024-06-17 16:44 UTC
```

**5. Added: Resolved time**

```diff
+ 2024-06-17 19:49 UTC
```

**6. Added: Affected components**

```diff
+ API, App, Australia - API, Australia - App, EU - API, EU - App, Japan - API, Japan - App, US - API, US - App
```

**7. Added: Update** (investigating) · 2024-06-17 16:44 UTC

```diff
+ We're currently experiencing some difficulties; as a result, a majority of our users are unable to access Asana. Our Development Team is currently working to resolve this issue as soon as possible. Sincere apologies for the inconvenience caused, please keep an eye on this page for the latest updates.
```

**8. Added: Update** (monitoring) · 2024-06-17 16:52 UTC

```diff
+ A fix has been implemented and we are monitoring the results.
```

**9. Added: Update** (resolved) · 2024-06-17 19:49 UTC

```diff
+ This incident has been resolved.
```

**10. Added: Update** (postmortem) · 2024-06-19 15:45 UTC

```diff
+ Incident: Asana uses several load balancers to route incoming requests to the correct backend service. As our volume of traffic increased over time, these load balancers consumed more resources to handle the additional requests. High traffic pushed computing resource utilization past a critical threshold leading to queueing of slow requests and eventual failures. This incident was made worse by certain error reporting mechanisms sending additional requests through the same load balancing infrastructure. ‌ Impact: Between 15:08 and 16:50 UTC on June 17, 2024, requests to load the Asana application, use of the Asana mobile applications, and calls to our API were delayed or failed at an elevated rate. Users in our European, Australian, and Japanese data centers may have experienced additional crashes while using Asana. ‌ Moving forward: In the short term, we have increased the capacity for our load balancing infrastructure to handle our current traffic as well as anticipated growth, and improved the monitoring to alert us before failure. In the longer term, we have efforts underway to replace this component entirely with routing and load balancing infrastructure that automatically scales in response to increases in traffic. 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.
```

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 2024-06-17 16:44 UTC | Major incident: Elevated error rates (this change) | outage |

All Asana changes: [timeline](https://rewindex.com/company/asana/changes.md)
_Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._


---
Canonical: https://rewindex.com/change/ia3e9e554ff8de1 · Markdown: https://rewindex.com/change/ia3e9e554ff8de1.md · JSON: https://rewindex.com/api/v1/changes/ia3e9e554ff8de1 · Generated 2026-10-18T02:55:10.104Z