Fly.io Upstash Redis Service Distruption
Final update
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.
Timeline
- Postmortem · May 15, 12:43 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.
- Resolved · May 12, 13:48 UTC
This incident has been resolved.
- Monitoring · May 12, 12:05 UTC
A fix has been implemented and we are monitoring the results.
- Identified · May 12, 10:50 UTC
The issue has been identified and the fix is being implemented.
- Investigating · May 12, 09:49 UTC
Some regions are experiencing connectivity issues due to an ongoing network problem. We are currently investigating
More from Upstash
Full history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 913:00 UTC | Intermittent DNS Resolution Errors for Upstash Vector in US East (us-east-1) | minor | 0m |
| Sep 308:29 UTC | Upstash Console login issue | none | 0m |
| Aug 2822:56 UTC | Message Persistence Issue , QStash us-east-1 | major | 0m |
| Jul 2208:50 UTC | Fly.io infrastructure disruption affecting some Upstash Redis databases on Fly.io DFW Region | none | 1h 15m |
| Jul 1608:35 UTC | QStash us-east-1 - URL Publish Errors | none | 0m |
| Jun 2515:23 UTC | Upstash Redis Partial Service Disruption | major | 1h 12m |
Also caused by network
All| Started | Vendor | Incident | Impact | Duration |
|---|---|---|---|---|
| Sep 1901:36 UTC |  Cloudflare | Elevated errors in Ashburn, VA (IAD)Cloudflare | none | 0m |
| Sep 1411:59 UTC |  CircleCI | Increased wait times for macOS jobsCircleCI | minor | 1h |
| Sep 410:57 UTC |  Netlify | Increased errors on High Performance Edge Network - FRA RegionNetlify | minor | 0m |
| Sep 214:18 UTC |  Fly.io | Upstream network issuesFly.io | minor | 1h 39m |
| Sep 116:11 UTC |  ClickHouse | Service degradation in GCP us-central-1ClickHouse | none | 19m |
| Sep 114:44 UTC |  Google Cloud | Multiple products in us-central1-b are experiencing network service degradation.Google Cloud | major | 4h 8m |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.