# Performance degradation on QStash

- Provider: [Upstash](https://down.guide/upstash)
- Level: confirmed
- Impact: Partial outage
- lasted 3h 13m
- started 2024-11-13 14:14 UTC
- EU-CENTRAL-1
- eu, eu-central-1
- id: DWN-d94c7f1398
- Official page: https://stspg.io/6qn49g3pmlfw

## Updates from Upstash
### 2024-11-13 14:14 UTC: investigating
We are currently investigating this issue.

### 2024-11-13 15:38 UTC: identified
The issue has been identified and a fix is being implemented.

### 2024-11-13 17:27 UTC: resolved
We will be sharing a postmortem about the incident soon.

### 2024-11-13 20:38 UTC: postmortem
Product: QStash 
Impact: Degraded performance, delayed processing of events, and duplicate event deliveries for some customers
Incident Summary
QStash experienced an incident marked by a sudden and extreme load on our servers. This caused a degradation in performance, with extremely high latency for event processing for all users. We also noticed some of the events being delivered multiple times to some of the users. To mitigate the high load, we have increased the capacity as our initial response while investigation proceeds. Eventually, fixes for the issues are confirmed with an issue reproducer and deployed to production.
Root Cause Analysis
In a certain type of usage, failure handling of failureFunction (https://upstash.com/docs/workflow/basics/serve#failurefunction) can cause recursive calls which causes a leak in the queue of the tasks, causing a severe load on the QStash servers. This also triggered an edge case which caused some of the events to be delivered multiple times.
Resolution
Two hotfixes to the QStash processes are deployed
1. Prevent recursive calls within the failure function. 
2. Eliminate duplicate deliveries while keeping "at least once delivery" guarantee. 
 These are verified to successfully resolve the root cause, normalizing server load and restoring standard event processing operations.
Impact on Customers
High latency of event processing is observed for all users. Some users received duplicate event deliveries. No events were lost, and all were delivered as part of our "at least once delivery" guarantee. Customers do not need to take any corrective action, as workflows have returned to normal and preventive fixes are deployed.

From the builder: does your app depend on Upstash? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=upstash) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention Upstash.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-d94c7f1398), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.