- Level
- confirmed
- Worst impact
- Partial outage
- Components
- N. Virginia, USA (us-east-1), N. California, USA (us-west-1), Sydney, Australia (ap-southeast-2), Mumbai, India (ap-south-1)
- Regions
- ap-south-1, ap-southeast-2, apac, au, in, us, us-east-1, us-west-1
What to do
Check whether you use Upstash N. Virginia, USA (us-east-1), N. California, USA (us-west-1), Sydney, Australia (ap-southeast-2), Mumbai, India (ap-south-1) in ap-south-1, ap-southeast-2, apac, au. 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 1h 44m it lasted.
Anything that failed between 2026-05-14 15:47 UTC and 2026-05-14 17:31 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 4
- monitoring
We identified intermittent connection issues affecting some regions. Fix is being deployed. We'll update the list of affected regions shortly.
provider
- identified
The issue has been identified and a fix is being implemented.
provider
- monitoring
A fix has been implemented and we are monitoring.
provider
- resolved
Earlier today, unexpected load on our proxies caused intermittent connection issues for Upstash Redis in the following regions: us-east-1, us-west-1, ap-southeast-2, and ap-south-1. During this period, some clients may have seen connection timeouts or elevated error rates when reaching their databases. Our team identified the issue quickly and applied workarounds to relieve pressure on the affected proxies. Connection health has since been restored and we've been monitoring the regions to confirm everything is stable. All systems are now operating normally. We appreciate your patience and apologize for any disruption this may have caused.
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-d0ee3146e9
Is Upstash still down?
No, this incident was resolved 2026-05-14 17:31 UTC. For Upstash's live state, see https://down.guide/upstash.
How long did it last?
1h 44m, from 2026-05-14 15:47 UTC to 2026-05-14 17:31 UTC, by the times Upstash posted.
What was affected?
Upstash named N. Virginia, USA (us-east-1), N. California, USA (us-west-1), Sydney, Australia (ap-southeast-2), Mumbai, India (ap-south-1) in ap-south-1, ap-southeast-2, apac, au.
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.