- Level
- confirmed
- Worst impact
- Partial outage
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 3h 17m it lasted.
Anything that failed between 2026-05-11 15:05 UTC and 2026-05-11 18:22 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 5
- investigating
Some databases may experience increased latency or timeouts in Fly.io’s FRA region.
provider
- investigating
We are continuing to investigate the issue.
provider
- investigating
We are working with Fly team to investigate the root cause.
provider
- resolved
The incident has been resolved. We are working with Fly team on RCA.
provider
- postmortem
On May 12th and 13th at various times, a subset of Upstash Redis instances on [Fly.io](http://Fly.io) experienced intermittent hangs and elevated error rates. The Redis process would stall inside a logging syscall — alive but not making progress — which made the issue hard to spot from our usual telemetry. After investigating with Fly's team, we identified the root cause as a bad interaction between a recent guest kernel update on Fly's newer machines and an upstream Cloud Hypervisor bug \([cloud-hypervisor#7672](https://github.com/cloud-hypervisor/cloud-hypervisor/issues/7672)\) affecting log writes from inside the VM. We mitigated by disabling the affected logging paths, and Fly has since rolled out a hypervisor-side patch, fully resolving the issue. No data was lost. Sorry for the disruption.
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-cf07724895
Is Upstash still down?
No, this incident was resolved 2026-05-11 18:22 UTC. For Upstash's live state, see https://down.guide/upstash.
How long did it last?
3h 17m, from 2026-05-11 15:05 UTC to 2026-05-11 18:22 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.