Live › incident › INC-fly-01M376272WGYT2F3BJ9ZK1WDYB
Go to dashboardNot triaged yet. The sources’ own description is below.
First seen by InfraStack 2026-10-23 19:12 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| Fly.io | vendor | – | – |
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Impact
From about 12:00 to 13:05 UTC, some clients got connection timeouts to their Redis databases. Affected were databases hosted in fra or gig, and clients whose connections were routed through fra or gig, even if their database is hosted in another region.
What happened
During a planned rolling upgrade, replicas in fra and gig did not finish draining and were left out of service. They were returned to Fly routing before they were ready to accept connections. Connections routed to them then timed out.
What we're changing
• We will be adding tooling to return a replica to service safely after maintenance.
• We will be adding safety checks to our upgrade process.
• We will make the upgrade procedure more resilient to errors like this one.
This page as .md · .json · in your agent: get_signal("INC-fly-01M376272WGYT2F3BJ9ZK1WDYB")