Companies / Upstash / incidents
Upstash: Region ap-northeast-1 outage on Upstash Global
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 archived incident (Sol). Check the timeline before relying on it.
Affected components: Redis Global - Tokyo, Japan (ap-northeast-1)Tokyo, Japan (ap-northeast-1)
Timeline of updates
- investigating
We are currently investigating this issue.
- monitoring
A fix has been implemented and we are monitoring the results.
- resolved
This incident has been resolved.
- postmortem
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.
Rewindex changes for this incident
- Critical incident: Region ap-northeast-1 outage on Upstash Global 2026-03-06 13:50 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Upstash profile · Recent Upstash incidents · Markdown · JSON