# Fly.io Upstash Redis service distruption (FRA region)

- Provider: [Upstash](https://down.guide/upstash)
- Level: confirmed
- Impact: Partial outage
- lasted 3h 17m
- started 2026-05-11 15:05 UTC
- id: DWN-cf07724895
- Official page: https://stspg.io/xc9fkbk20d2w

## Updates from Upstash
### 2026-05-11 15:05 UTC: investigating
Some databases may experience increased latency or timeouts in Fly.io’s FRA region.

### 2026-05-11 15:07 UTC: investigating
We are continuing to investigate the issue.

### 2026-05-11 17:19 UTC: investigating
We are working with Fly team to investigate the root cause.

### 2026-05-11 18:22 UTC: resolved
The incident has been resolved. We are working with Fly team on RCA.

### 2026-05-15 12:49 UTC: 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.

---
down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).