Region ap-northeast-1 outage on Upstash Global

What to do

• Check whether you use Upstash Tokyo, Japan (ap-northeast-1) in ap-northeast-1, apac, jp. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h it lasted.

  Anything that failed between 2026-03-06 13:50 UTC and 2026-03-06 14:49 UTC may need a replay.

• Subscribe to Upstash's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=upstash works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Upstash 4

1. investigatingMar 6, 2026, 1:50 PM UTC

   We are currently investigating this issue.

   provider

2. monitoringMar 6, 2026, 2:08 PM UTC

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

   provider

3. resolvedMar 6, 2026, 2:49 PM UTC

   This incident has been resolved.

   provider

4. postmortemMar 9, 2026, 10:07 AM UTC

   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.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.