- Level
- confirmed
- Worst impact
- Degraded
What to do
Check whether your product depends on Upstash. 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 15m it lasted.
Anything that failed between 2026-07-22 08:50 UTC and 2026-07-22 10: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 3
- identified
We are investigating connectivity issues affecting a subset of Redis databases hosted on Fly.io. The issue is related to an ongoing Fly.io infrastructure disruption in the DFW region (https://status.flyio.net/incidents/n4z2my6qw4sb). We are working to restore availability and will provide updates soon.
provider
- monitoring
The affected Fly.io-hosted machines recovered at 08:48 UTC, and service availability has been restored. We are monitoring the systems to confirm continued stability.
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-fcc04c4b71
Is Upstash still down?
No, this incident was resolved 2026-07-22 10:05 UTC. For Upstash's live state, see https://down.guide/upstash.
How long did it last?
1h 15m, from 2026-07-22 08:50 UTC to 2026-07-22 10:05 UTC, by the times Upstash posted.
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.