Upstash outage, 6 March 2026

Region ap-northeast-1 outage on Upstash Global

Started
Resolved
6 Mar 2026, 14:49 UTC (after 60 min)
Impact
Critical
Affected
Tokyo, Japan (ap-northeast-1)

Last update from Upstash

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...

9 Mar 2026, 10:07 UTC

Read the full incident on the official Upstash status page

Is Upstash down now?

This page is the record of one past incident. For the live status, see Is Upstash down right now? - it reads the official status page every 2 minutes.

Other Upstash incidents

  1. Brief connection proxy degradation in us-east-1

  2. Intermittent DNS Resolution Errors for Upstash Vector in US East (us-east-1)

  3. Upstash Console login issue

  4. Message Persistence Issue - QStash us-east-1

  5. Fly.io infrastructure disruption affecting some Upstash Redis databases on Fly.io DFW Region

  6. QStash us-east-1 - URL Publish Errors

  7. Upstash Redis Partial Service Disruption

  8. QStash EU Region - Degraded Performance

All recorded Upstash incidents