Upstash reported this critical-impact incident on its official status page on May 8, 2026, 09:46 UTC. It was resolved after 22 min.
Right now Upstash is operational. Live Upstash status →
**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 process remains healthy. Because of another bug in the panic recovery path, the panic was not properly caught, which caused the worker process handling the scheduled job to terminate. After that process exited, another worker picked up responsibility for delivering the same scheduled task. Since
This incident has been resolved, we will publish RCA soon.
A fix has been implemented and we are monitoring the results.
We are continuing to investigate this issue.
We are currently investigating the 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