- Level
- confirmed
- Worst impact
- Degraded
- Components
- N. Virginia, USA (us-east-1), N. California, USA (us-west-1), Oregon, USA (us-west-2), Frankfurt, Germany (eu-central-1), Ireland (eu-west-1), Singapore (ap-southeast-1), Sydney, Australia (ap-southeast-2), Mumbai, India (ap-south-1), Tokyo, Japan (ap-northeast-1), São Paulo, Brazil (sa-east-1), Ohio, USA (us-east-2), London, UK (eu-west-2), Council Bluffs, Iowa, North America (us-central1), Ashburn, Virginia, North America (us-east4), Tokyo, Japan, APAC (asia-northeast1), St. Ghislain, Belgium, Europe (europe-west1)
- Regions
- ap-northeast-1, ap-south-1, ap-southeast-1, ap-southeast-2, apac, asia-northeast1, au, eu, eu-central-1, eu-west-1, eu-west-2, europe-west1, in, jp, latam, sa-east-1, us, us-central1, us-east-1, us-east-2, us-east4, us-west-1, us-west-2
- Down Index
- 36of 100
What to do
Check whether you use Upstash N. Virginia, USA (us-east-1), N. California, USA (us-west-1), Oregon, USA (us-west-2), Frankfurt, Germany (eu-central-1) and 12 more in ap-northeast-1, ap-south-1, ap-southeast-1, ap-southeast-2. 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 32m it lasted.
Anything that failed between 2026-05-22 23:27 UTC and 2026-05-23 00:00 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 3
- investigating
New database provisioning is currently failing due to an ongoing upstream provider issue affecting DNS. Existing databases and connections are unaffected — only the creation flow is impacted. We're monitoring the situation and will update once the upstream issue is resolved.
provider
- monitoring
Upstream issue resolved — new database creation is working again. We're monitoring to confirm full recovery.
provider
- resolved
This incident has been resolved.
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-d7638541df
Is Upstash still down?
No, this incident was resolved 2026-05-23 00:00 UTC. For Upstash's live state, see https://down.guide/upstash.
How long did it last?
32m, from 2026-05-22 23:27 UTC to 2026-05-23 00:00 UTC, by the times Upstash posted.
What was affected?
Upstash named N. Virginia, USA (us-east-1), N. California, USA (us-west-1), Oregon, USA (us-west-2), Frankfurt, Germany (eu-central-1) and 12 more in ap-northeast-1, ap-south-1, ap-southeast-1, ap-southeast-2.
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.