- Level
- confirmed
- Worst impact
- Degraded
- Components
- Box
- Down Index
- 9of 100
What to do
Check whether you use Upstash Box. 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 2026-06-23 06:05 UTC and 2026-06-23 06:05 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
Between 01:18 and 04:03 UTC, customers were unable to access running boxes or perform create, read, update, or delete operations. Running containers were not affected and continued operating throughout. The issue has been fully resolved and all box operations are functioning normally. We are taking all necessary measures to prevent this from happening again. We apologize for the disruption.
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-f04a041d9b
Is Upstash still down?
No, this incident was resolved 2026-06-23 06:05 UTC. For Upstash's live state, see https://down.guide/upstash.
How long did it last?
0m, from 2026-06-23 06:05 UTC to 2026-06-23 06:05 UTC, by the times Upstash posted.
What was affected?
Upstash named Box.
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.