# Asana: Incident updated: Asana downtime

> Incident updated: Asana downtime. Detected 2026-10-24 by Rewindex: what changed on Asana’s status page, with the before/after diff.

Canonical: https://rewindex.com/change/r14dbcbde865dee
Last updated: 2026-10-24T00:23:50Z

**Summary:** _summary pending_
- Kind: Incident update · Label: Normal progress (rule)
- Changed: 2026-10-24 00:23 UTC · Detected: 2026-10-24 00:23 UTC
- [Source: https://stspg.io/flc98gjg9wdn](https://stspg.io/flc98gjg9wdn)
- [Company: Asana](https://rewindex.com/company/asana.md)
- Versions: before incident\_version:90/hmnfnm98zvy4@08b215112430 → after incident\_version:90/hmnfnm98zvy4@b09655a6245d
- Change 3 of 3 for this incident

Incident page (full timeline): [Asana downtime](https://rewindex.com/company/asana/incidents/hmnfnm98zvy4.md)
## What changed

**1. Changed: Status**

```diff
- resolved
+ postmortem
```

**2. Added: Update** (postmortem) · 2026-10-24 00:23 UTC

```diff
+ Incident: An infrastructure update targeting security caused DynamoDB to become inaccessible across Asana's production environment. This change was related to a production isolation initiative, and was applied in a way that left all of our production services unable to use DynamoDB tables which we use for metadata and routing traffic. Once the change was reverted our services returned to normal operations.  Impact: Asana services were completely unavailable for approximately 30 minutes, 2026-10-21 15:21 UTC-15:51 UTC, and mostly unavailable for a further 20 minutes, including 15:05 UTC-15:55 UTC. This also caused delay for background actions during the impact period; recovery after the end of the incident completed by 16:00 UTC. Moving forward: We are updating the deployment process to catch this class of error. We will be moving to an isolation system which allows more gradual rollout of similar changes, allowing us to detect misconfiguration in pre-production testing. 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 |
| --- | --- | --- |
| 2026-10-21 15:33 UTC | [Major incident: Asana downtime](https://rewindex.com/change/ibd85429ebf4b86.md) | outage |
| 2026-10-22 14:03 UTC | [Incident silently edited: Asana downtime](https://rewindex.com/change/r1b7bed45a13e0d.md) | minor edit |
| 2026-10-24 00:23 UTC | Incident updated: Asana downtime (this change) | Normal progress |

Previous: [change](https://rewindex.com/change/r1b7bed45a13e0d.md) · 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._

## Cite this

Incident updated: Asana downtime on Asana’s status page, changed 2026-10-24 00:23 UTC (change 3 of 3).

- Canonical URL: https://rewindex.com/change/r14dbcbde865dee
- Citation: Asana, “Incident updated: Asana downtime” (2026-10-24 00:23 UTC). Archived by Rewindex: https://rewindex.com/change/r14dbcbde865dee (CC BY 4.0).
- Markdown link: `[Asana: Incident updated: Asana downtime (2026-10-24)](https://rewindex.com/change/r14dbcbde865dee)`


---
Canonical: https://rewindex.com/change/r14dbcbde865dee · Markdown: https://rewindex.com/change/r14dbcbde865dee.md · JSON: https://rewindex.com/api/v1/changes/r14dbcbde865dee · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-11T04:58:52.021Z