Upstash outage, 8 May 2026

QStash US Region Service Disruption

Started
Resolved
8 May 2026, 10:08 UTC (after 22 min)
Impact
Critical
Affected
US-EAST-1

Last update from Upstash

**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. Under normal behavior, scheduled tasks associated with a deleted account should wake up, detect that the account no longer exists, and exit after performing cleanup. Due to a bug introduced in the new scheduler implementation, this code path did not return early as intended. Execution continued and resulted in a nil pointer dereference. A second issue then amplified the impact. When a panic occurs in the scheduler, it is designed to be recovered, logged, and isolated so that the...

12 May 2026, 08:25 UTC

Read the full incident on the official Upstash status page

Is Upstash down now?

This page is the record of one past incident. For the live status, see Is Upstash down right now? - it reads the official status page every 2 minutes.

Other Upstash incidents

  1. Brief connection proxy degradation in us-east-1

  2. Intermittent DNS Resolution Errors for Upstash Vector in US East (us-east-1)

  3. Upstash Console login issue

  4. Message Persistence Issue - QStash us-east-1

  5. Fly.io infrastructure disruption affecting some Upstash Redis databases on Fly.io DFW Region

  6. QStash us-east-1 - URL Publish Errors

  7. Upstash Redis Partial Service Disruption

  8. QStash EU Region - Degraded Performance

All recorded Upstash incidents