Upstash Status

Resolved: Earlier 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 may have seen connection timeouts or elevated error rates when reaching their databases. Our team identified the issue quickly and applied workarounds to relieve pressure on the affected proxies. Connection health has since been restored and we've been monitoring the regions to confirm everything is stable. All systems are now operating normally.

We appreciate your patience and apologize for any disruption this may have caused.

Monitoring: A fix has been implemented and we are monitoring.

Identified: The issue has been identified and a fix is being implemented.

Monitoring: We identified intermittent connection issues affecting some regions. Fix is being deployed. We'll update the list of affected regions shortly.

Resolved: Earlier 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 may have seen connection timeouts or elevated error rates when reaching their databases. Our team identified the issue quickly and applied workarounds to relieve pressure on the affected proxies. Connection health has since been restored and we've been monitoring the regions to confirm everything is stable. All systems are now operating normally.

We appreciate your patience and apologize for any disruption this may have caused.

Monitoring: A fix has been implemented and we are monitoring.

Identified: The issue has been identified and a fix is being implemented.

Monitoring: We identified intermittent connection issues affecting some regions. Fix is being deployed. We'll update the list of affected regions shortly.

Resolved: Earlier 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 may have seen connection timeouts or elevated error rates when reaching their databases. Our team identified the issue quickly and applied workarounds to relieve pressure on the affected proxies. Connection health has since been restored and we've been monitoring the regions to confirm everything is stable. All systems are now operating normally.

We appreciate your patience and apologize for any disruption this may have caused.

Monitoring: A fix has been implemented and we are monitoring.

Identified: The issue has been identified and a fix is being implemented.

Monitoring: We identified intermittent connection issues affecting some regions. Fix is being deployed. We'll update the list of affected regions shortly.

Resolved: Earlier 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 may have seen connection timeouts or elevated error rates when reaching their databases. Our team identified the issue quickly and applied workarounds to relieve pressure on the affected proxies. Connection health has since been restored and we've been monitoring the regions to confirm everything is stable. All systems are now operating normally.

We appreciate your patience and apologize for any disruption this may have caused.

Monitoring: A fix has been implemented and we are monitoring.

Identified: The issue has been identified and a fix is being implemented.

Monitoring: We identified intermittent connection issues affecting some regions. Fix is being deployed. We'll update the list of affected regions shortly.

Postmortem: 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 the same faulty execution path was still present, that worker also failed. This created a cascading failure pattern across workers attempting to process the affected schedules.
Resolution
We deployed two fixes:

• Added the missing early return in the deleted-account cleanup path, preventing the nil pointer dereference.
• Corrected the panic recovery logic so that future panics are safely recovered, logged, and reported without causing worker processes to terminate.

With these changes in place, the affected execution path is now safe. Even if a future bug triggers a panic in this area, it will be isolated and reported rather than causing process-level failure.

Resolved: This incident has been resolved, we will publish RCA soon.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating the issue.