Upstash reported this major-impact incident on its official status page on May 11, 2026, 15:05 UTC. It was resolved after 3h 17m.
Right now Upstash is operational. Live Upstash status →
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.
The incident has been resolved. We are working with Fly team on RCA.
We are working with Fly team to investigate the root cause.
We are continuing to investigate the issue.
Some databases may experience increased latency or timeouts in Fly.io’s FRA region.
Our 5-minute checks didn't record a change in Upstash's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Upstash reported 3 incidents in the last 90 days, 1 of them major or critical. See Upstash's uptime and incident history