Changes / Upstash / Region ap-northeast-1 outage on Upstash Global

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 from the diff below (Sol; type: incident outage). Check the diff before relying on it.

Major incidentLabel: outage (model (Jev), 80%)Changed Detected Source: stspg.io (opens in new tab)

What changed

AddedTitle#1
Before: not present
After: Region ap-northeast-1 outage on Upstash Global
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: postmortem
AddedStart time#4
Before: not present
After: 2026-03-06 13:50 UTC
AddedResolved time#5
Before: not present
After: 2026-03-06 14:49 UTC
AddedAffected components#6
Before: not present
After: Redis Global - Tokyo, Japan (ap-northeast-1), Tokyo, Japan (ap-northeast-1)
AddedUpdateinvestigating#7
Before: not present
After: We are currently investigating this issue.
AddedUpdatemonitoring#8
Before: not present
After: A fix has been implemented and we are monitoring the results.
AddedUpdateresolved#9
Before: not present
After: This incident has been resolved.
AddedUpdatepostmortem#10
Before: not present
After: 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.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Critical incident: Region ap-northeast-1 outage on Upstash Global (this change)
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.
Major incident

All Upstash changes → · Upstash profile · Markdown · JSON