Upstash reported this critical-impact incident on its official status page on Mar 6, 2026, 13:50 UTC. It was resolved after 1h.
Right now Upstash is operational. Live Upstash status →
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.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
Our 5-minute checks didn't record a change in Upstash's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Upstash reported 3 incidents in the last 90 days, 1 of them major or critical. See Upstash's uptime and incident history