Upstash Outage History

26 incidents recorded over the last 365 days, 26 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Upstash status99.94% uptime history

Every Recorded Upstash Incident

Upstash incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Jul 22, 2026Fly.io infrastructure disruption affecting some Upstash Redis databases on Fly.io DFW RegionThis incident has been resolved.1h 15mResolved
Jul 16, 2026QStash us-east-1 - URL Publish ErrorsPartial outage due to http parsing errors. Problem was resolved couple minutes later. If problem continues, refreshing the DNS cache is recommended.-125 minResolved
Jun 25, 2026Upstash Redis Partial Service DisruptionThis incident has been resolved, we will publish RCA soon.1h 12mResolved
Jun 23, 2026QStash EU Region — Degraded Performance### **Summary** On June 23, 2026, QStash users in the EU-CENTRAL-1 region experienced elevated latency and degraded performance. The issue was caused by a regression introduced in a recent enhancement to Flow Control…52 minResolved
Jun 23, 2026Box Access and Management Operations UnavailableBetween 01:18 and 04:03 UTC, customers were unable to access running boxes or perform create, read, update, or delete operations. Running containers were not affected and continued operating throughout. The issue has…0 minResolved
Jun 19, 2026QStash Service Disruption in the EU Region## What happened A configuration change applied to QStash's EU networking layer introduced an outbound connectivity fault. Between **09:11 and 09:45 UTC**, a subset of QStash instances had degraded egress connectivity…-56 minResolved
Jun 4, 2026Fly.io - Upstash Vector service disruption on IAD regionThis incident has been resolved.3h 58mResolved
May 29, 2026Intermittent slowness in Vector US-EAST-1 regionThe issue affecting some Upstash Vector indexes in the US-EAST-1 region has been resolved. Our team investigated the incident and identified the conditions that were contributing to elevated memory pressure on the…11h 32mResolved
May 22, 2026New Database Creation Failing Due to Upstream Provider IssueThis incident has been resolved.32 minResolved
May 14, 2026Upstash Redis – intermittent connection issues in some regionsEarlier today, unexpected load on our proxies caused intermittent connection issues for Upstash Redis in the following regions: us-east-1, us-west-1, ap-southeast-2, and ap-south-1. During this period, some clients…1h 44mResolved
May 12, 2026Fly.io Upstash Redis Service DistruptionOn May 12th and 13th at various times, a subset of Upstash Redis instances on [Fly.io](http://Fly.io) experienced intermittent hangs and elevated error rates. The Redis process would stall inside a logging syscall —…3h 59mResolved
May 11, 2026Fly.io Upstash Redis service distruption (FRA region)On May 12th and 13th at various times, a subset of Upstash Redis instances on [Fly.io](http://Fly.io) experienced intermittent hangs and elevated error rates. The Redis process would stall inside a logging syscall —…3h 16mResolved
May 8, 2026QStash US Region Service Disruption**Root Cause Analysis** On **April 24**, we deployed a more optimized scheduler implementation in the **US East \(N. Virginia\)** region. On **May 8**, a user who had active schedules deleted their account…22 minResolved
May 5, 2026QStash US Region: Schedule Degradation# **Incident Postmortem: Scheduled Jobs Inconsistency in US Region** On May 1, 2026, we experienced an incident affecting a subset of schedules in the US region following a recent infrastructure update. The issue has…17h 40mResolved
Apr 27, 2026QStash us-east-1 SchedulesThis incident has been resolved.3h 4mResolved
Apr 2, 2026Fly.io Upstash Redis – iad Region Elevated Latency and Temporary Read-Only StateReplication complete, incident resolved.1h 8mResolved
Mar 27, 2026Upstash Redis: GCP Global Connectivity ProblemsDue 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.-95 minResolved
Mar 6, 2026Region ap-northeast-1 outage on Upstash GlobalOn 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…59 minResolved
Jan 23, 2026Upstash Redis: Intermittent latency on us-east-1We identified the cause of elevated latency impacting some databases in us-east-1 region between 15:30–15:35 UTC as a sudden surge of connection attempts that hit OS-level connection limits on our proxy layer. This…-95 minResolved
Dec 12, 2025QStash - Message delays for Flow Control configurationsWe identified and fixed a bug that could cause messages with Flow Control enabled to be delayed longer than their configured delay, resulting in unexpectedly long pending times. The fix is in place and the issue should…-16294 minResolved
Dec 10, 2025Connectivity issue impacting Regional Databases in US-East-1Issue has been identified and replicas were successfully reconnected.17 minResolved
Dec 5, 2025Upstash Console and Context7 Console is Currently Experiencing issuesThis incident has been resolved.14 minResolved
Oct 20, 2025Upstash Console issuesA fix has been deployed as a workaround so that our systems are not affected from the ongoing incident of the cloud provider3h 58mResolved
Oct 20, 2025Login Issues on Upstash ConsoleAs a side effect of an incident on the underlying cloud provider, Upstash Console has had availability issues between 07:00UTC and 09:23UTC. Only Upstash Console is impacted, Upstash products remained operational.0 minResolved
Oct 10, 2025Connectivity issue on us-east-1Between 15:46–15:55 UTC, some client connection attempts to databases in us-east-1 timed out due to unexpected high load on a server. The node was recovered at 15:50 UTC, and the updated DNS record propagated by 15:55…-61 minResolved
Sep 9, 2025Temporary Database Routing IssueImpact: A subset of clients connecting through the eu-central-1 region experienced increased error rates and timeouts when accessing certain databases. Clients in us-west-2 were also briefly affected. The issue was…-228 minResolved

How to Read This Upstash Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Upstash acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Upstash outage in this window ran 17h 40m, against a mean recovery of 2h 57m. If you depend on Upstash in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.