Upstash experienced a critical incident on May 12, 2026, lasting 3h 59m. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating May 12, 2026, 09:49 AM UTC
Some regions are experiencing connectivity issues due to an ongoing network problem. We are currently investigating
- identified May 12, 2026, 10:50 AM UTC
The issue has been identified and the fix is being implemented.
- monitoring May 12, 2026, 12:05 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 12, 2026, 01:48 PM UTC
This incident has been resolved.
- postmortem May 15, 2026, 12:43 PM UTC
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.