There were 4 Upstash outages since March 6, 2026 totaling 5h 11m of downtime. Each is summarised below — incident details, duration, and resolution information.
Some users on QStash US might be experiencing schedule issues.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Servers in the iad region experienced unexpected disk load, resulting in elevated latencies and a temporary read-only state. We are migrating replicas to new instances to mitigate the issue and expect to have it fully resolved shortly.
Replication complete, incident resolved.
Due to a race condition in a process that attaches static IPs to nodes, some of the IPs in the dns were detached from the nodes, causing timeouts.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
Pingoru polls Upstash's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
5 free monitors · No credit card required