Upstash incident: Performance degradation on QStash

Affected components

• EU-CENTRAL-1

1. postmortemMar 12, 2025, 12:26 UTC

   On 09:43 UTC, QStash experienced degraded service when a high number of requests to a specific domain were throttled, resulting in timeouts during an unexpected phase of the TCP connection establishment. These requests and resulting retries triggered excessive consumption of network resources and negatively impacted all users. We have added more resources to QStash as a quick remediation and as for the resolution, we have improved the timeout mechanism to detect and fail-faster in such cases.

2. resolvedMar 12, 2025, 10:16 UTC

   This incident has been resolved.

3. monitoringMar 12, 2025, 10:08 UTC

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

4. investigatingMar 12, 2025, 09:43 UTC

   We are currently investigating this issue.

What APIStatus.watch saw

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.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Airtable: Some jira sync are only pulling in 100 rows of dataMinor · Mar 11, 2025, 23:59 UTC

How often does Upstash have incidents?

Upstash reported 3 incidents in the last 90 days, 1 of them major or critical. See Upstash's uptime and incident history