QStash: Degraded performance

What to do

• Check whether you use Upstash EU-CENTRAL-1 in eu, eu-central-1. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 42m it lasted.

  Anything that failed between 2025-04-18 12:36 UTC and 2025-04-18 13:18 UTC may need a replay.

• Subscribe to Upstash's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=upstash works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Upstash 5

1. investigatingApr 18, 2025, 12:36 PM UTC

   We are currently investigating this issue.

   provider

2. investigatingApr 18, 2025, 12:36 PM UTC

   We are continuing to investigate this issue.

   provider

3. monitoringApr 18, 2025, 12:46 PM UTC

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

   provider

4. resolvedApr 18, 2025, 1:18 PM UTC

   This incident has been resolved.

   provider

5. postmortemApr 18, 2025, 1:19 PM UTC

   An internal cleanup task for QStash events, coinciding with disc layer compaction task has caused performance degradation to some users. ‌ Mitigation: Team has mitigated the event by pausing some of these tasks and monitored the status for a while. ‌ Fixes: Improvements are being applied to these tasks to use resources more gracefully. Disk resources are increased to be able to handle a bigger burst of load.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.