Upstash change history

Upstash reported a major QStash message-persistence disruption in us-east-1 and said a fix restored service. The listed start is 2026-08-28 22:56 UTC, but resolution is recorded as 2026-08-28 22:20 UTC and the update describes disruptions between 22:20 and 22:33 UTC; duration is unknown.

Upstash Redis and Redis Global experienced a major partial service disruption in eu-central-1, us-east-1 and us-west-1 from 2026-06-25 15:23 UTC to 2026-06-25 16:36 UTC, lasting 1 h 12 min. Upstash reported implementing a fix at 06-25 15:31 UTC; no cause was stated, and an RCA was promised.

Upstash reported a major QStash EU outage starting 2026-06-19 09:11 UTC; computed duration: 0 min. Its postmortem says a networking configuration change degraded outbound connectivity between 09:11 and 09:45 UTC, potentially failing initial message dispatches and causing some servers to use IPs outside the advertised outbound range. Upstash said the issue was resolved.

Upstash Redis had a major incident causing intermittent connection timeouts or elevated error rates in us-east-1, us-west-1, ap-southeast-2, and ap-south-1 from 2026-05-14 15:47 UTC to 2026-05-14 17:31 UTC, lasting 1 h 44 min. Upstash attributed it to unexpected proxy load and applied workarounds to relieve pressure; the incident was resolved.

A critical Fly.io Upstash Redis degradation caused intermittent hangs and elevated error rates for a subset of instances. It started at 2026-05-12 09:49 UTC and resolved at 2026-05-12 13:48 UTC, lasting 3 h 59 min. Upstash implemented a fix; its postmortem reported Redis processes stalling inside a logging syscall.

Upstash reported a major degradation affecting some Fly.io Redis databases in FRA, with increased latency or timeouts. It started at 2026-05-11 15:05 UTC and resolved at 2026-05-11 18:22 UTC, lasting 3 h 16 min. The postmortem described Redis processes stalling inside a logging syscall; the supplied root-cause explanation is truncated.

QStash's US-EAST-1 service suffered a critical disruption starting 2026-05-08 09:46 UTC, lasting 22 min and resolving at 2026-05-08 10:08 UTC. Upstash implemented a fix; its partial postmortem links the incident to a scheduler bug introduced in US East (N. Virginia), triggered when a user with active schedules deleted their account.

Upstash reported a critical outage affecting Redis Global in Tokyo, Japan (ap-northeast-1), causing elevated latency and connection errors for some databases. The incident ran from 2026-03-06 13:50 UTC to 2026-03-06 14:49 UTC (59 min). A traffic spike increased network utilization and connection load; Upstash mitigated it by scaling regional capacity and redistributing load across additional nodes.

Upstash reported a major connectivity incident affecting Regional Databases in US-East-1 from 2025-12-10 11:50 UTC to 2025-12-10 12:08 UTC, lasting 17 min. Database replicas had connectivity issues with each other and were successfully reconnected; other regions and Global databases were not impacted.

Upstash reported a critical outage affecting Upstash Console and Context7 Console, starting at 2025-12-05 09:03 UTC and resolved at 2025-12-05 09:18 UTC, with a computed duration of 14 min. An upstream provider confirmed an incident; no specific fix was stated.

Upstash reported a major incident affecting Console dashboard access and related operations, with Developer API (api.upstash.com) availability issues also reported. It started at 2025-10-20 14:52 UTC and was resolved at 2025-10-20 18:50 UTC, lasting 3 h 58 min. Upstash attributed the issues to an upstream cloud provider and deployed a workaround.

Upstash reported critical login and availability issues affecting only Upstash Console, starting 2025-10-20 07:00 UTC; products remained operational. The incident was resolved with a computed duration of 0 min, although the update reports issues between 07:00 UTC and 09:23 UTC as a side effect of an underlying cloud-provider incident.

Some users experienced login issues on Upstash Console due to a disruption in its authentication provider. Upstash rated the impact major; the incident started at 2025-06-26 06:53 UTC and lasted 41 min, resolving at 2025-06-26 07:34 UTC after a fix was implemented.

Upstash reported critical degraded performance affecting regional and Redis Global components from 2025-06-11 06:51 UTC to 2025-06-11 10:02 UTC (3 h 10 min). OS maintenance updates changed networking components and triggered restarts, causing EC2 nodes to fail health checks and disrupting high availability; a fix was implemented at 06-11 09:20 UTC.

Upstash reported a major outage affecting database reachability in AWS US-EAST-1 and Redis Regional - AWS US-EAST-1. Recorded start and resolution: 2025-01-29 18:03 UTC (computed duration: 0 min); the update reports disk failure at 16:52 UTC and recovery at 17:13 UTC after restarting affected components, with no data lost.

QStash had a major incident affecting EU-CENTRAL-1, with extremely high event-processing latency for all users and duplicate deliveries for some customers. It ran from 2024-11-13 14:14 UTC to 2024-11-13 17:27 UTC, lasting 3 h 12 min. Upstash attributed the degradation to sudden, extreme server load and reported implementing a fix before resolution.

Upstash’s QStash API was unreachable in an incident affecting QStash and EU-CENTRAL-1, rated critical by the vendor. It started at 2024-08-23 05:32 UTC and was resolved at 2024-08-23 06:01 UTC, lasting 28 min; Upstash reported identifying the issue and implementing a fix but provided no cause or fix details.