- Level
- confirmed
- Worst impact
- Partial outage
- Components
- AWS US-EAST-1
- Regions
- us, us-east-1
- Down Index
- 26of 100
What to do
Check whether you use Upstash AWS US-EAST-1 in us, us-east-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 0m it lasted.
Anything that failed between 2025-01-29 18:03 UTC and 2025-01-29 18:03 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
We observed a disk failure on some instances on 16:52 UTC and restarted affected components to bring them back online. Issue is resolved on 17:13 UTC. During the time of the issue databases reachability are affected, no data is lost.
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-5b7bb4d3f4
Is Upstash still down?
No, this incident was resolved 2025-01-29 18:03 UTC. For Upstash's live state, see https://down.guide/upstash.
How long did it last?
0m, from 2025-01-29 18:03 UTC to 2025-01-29 18:03 UTC, by the times Upstash posted.
What was affected?
Upstash named AWS US-EAST-1 in us, us-east-1.
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.