Skip to content
OutageDeck

Incident detail

Fly.io Upstash Redis service distruption (FRA region)

Fly.io Upstash Redis service distruption (FRA region)

Resolved incidentMajor0 affected services

Timeline window

to

Timeline

Incident updates

Updates are normalized from the official source chronology so timeline changes remain easy to scan.

  1. Investigating

    Some databases may experience increased latency or timeouts in Fly.io’s FRA region.

  2. Investigating

    We are continuing to investigate the issue.

  3. Investigating

    We are working with Fly team to investigate the root cause.

  4. Resolved

    The incident has been resolved. We are working with Fly team on RCA.

  5. Resolved

    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.