- Level
- confirmed
- Worst impact
- Operational
What to do
Check whether your product depends on Upstash. 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 0m it lasted.
Anything that failed between 2025-02-06 10:10 UTC and 2025-02-06 10:10 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 1
- resolved
Latest QStash release caused some Workflow runs to fail due to a bug in Workflow URL detection mechanism. Affected workflows did not start at all and moved directly to DLQ. These workflow runs, which show "detected non-workflow destination" message in the response body, can be retried from DLQ. This was a partial failure, lasted from 10:10 to 11:00 UTC, not all users' workflows were affected.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-f1aae2d2e9
Is Upstash still down?
No, this incident was resolved 2025-02-06 10:10 UTC. For Upstash's live state, see https://down.guide/upstash.
How long did it last?
0m, from 2025-02-06 10:10 UTC to 2025-02-06 10:10 UTC, by the times Upstash posted.
What caused it?
Upstash hasn't published a root cause. If it does, it shows here.
Where does this come from?
Upstash's official status page, https://status.upstash.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.