- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us, us-east-1
- Down Index
- 16of 100
What to do
Check whether you use Upstash 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-10-10 16:47 UTC and 2025-10-10 15:46 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 15:46–15:55 UTC, some client connection attempts to databases in us-east-1 timed out due to unexpected high load on a server. The node was recovered at 15:50 UTC, and the updated DNS record propagated by 15:55 UTC. Services are operating normally.
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-d568225afe
Is Upstash still down?
No, this incident was resolved 2025-10-10 15:46 UTC. For Upstash's live state, see https://down.guide/upstash.
How long did it last?
0m, from 2025-10-10 16:47 UTC to 2025-10-10 15:46 UTC, by the times Upstash posted.
What was affected?
Upstash named 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.