# Upstash: Critical incident: Region ap-northeast-1 outage on Upstash Global

**Summary:** Upstash reported a critical outage affecting Redis Global in Tokyo, Japan (ap-northeast-1), causing elevated latency and connection errors for some databases. The incident ran from 2026-03-06 13:50 UTC to 2026-03-06 14:49 UTC (59 min). A traffic spike increased network utilization and connection load; Upstash mitigated it by scaling regional capacity and redistributing load across additional nodes. _(machine-written, sol)_
- Kind: Major incident · Label: outage (model (Jev))
- Changed: 2026-03-06 13:50 UTC · Detected: 2026-10-17 18:22 UTC
- [Source: https://stspg.io/fstdc8k6z87l](https://stspg.io/fstdc8k6z87l)
- [Company: Upstash](https://rewindex.com/company/upstash.md)
- Versions: before (none: first archived) → after incident\_version:171/774krfq667vd@28f84bcca9dd
- Change 1 of 1 for this incident

## What changed

**1. Added: Title**

```diff
+ Region ap-northeast-1 outage on Upstash Global
```

**2. Added: Impact**

```diff
+ critical
```

**3. Added: Status**

```diff
+ postmortem
```

**4. Added: Start time**

```diff
+ 2026-03-06 13:50 UTC
```

**5. Added: Resolved time**

```diff
+ 2026-03-06 14:49 UTC
```

**6. Added: Affected components**

```diff
+ Redis Global - Tokyo, Japan (ap-northeast-1), Tokyo, Japan (ap-northeast-1)
```

**7. Added: Update** (investigating) · 2026-03-06 13:50 UTC

```diff
+ We are currently investigating this issue.
```

**8. Added: Update** (monitoring) · 2026-03-06 14:08 UTC

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

**9. Added: Update** (resolved) · 2026-03-06 14:49 UTC

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

**10. Added: Update** (postmortem) · 2026-03-09 10:07 UTC

```diff
+ On March 6, between approximately 13:44–14:07 UTC, some databases experienced elevated latency and connection errors in the Tokyo \(ap-northeast-1\) region. The issue was caused by a sudden spike in traffic that significantly increased network utilization and connection load on a subset of nodes. Our team mitigated the incident by scaling up capacity in the region and redistributing load across additional nodes. Service recovered once the additional capacity was brought online. Resolution We have increased the number of machines in the Tokyo region to provide additional headroom and reduce the likelihood of similar incidents during traffic spikes. Next Steps We are continuing to review capacity safeguards and connection-handling limits to improve resilience against sudden traffic surges.
```

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 2026-03-06 13:50 UTC | Critical incident: Region ap-northeast-1 outage on Upstash Global (this change) | outage |

All Upstash changes: [timeline](https://rewindex.com/company/upstash/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/ibf3ace85fad735 · Markdown: https://rewindex.com/change/ibf3ace85fad735.md · JSON: https://rewindex.com/api/v1/changes/ibf3ace85fad735 · Generated 2026-10-18T02:54:56.772Z