Fly.io reported this major-impact incident on its official status page on Sep 23, 2026, 13:07 UTC. It was resolved after 56 min.
Right now Fly.io is operational. Live Fly.io status →
**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 incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are investigating an issue affecting Upstash services in the fra region. Customers may experience connection failures or service unavailability. We are working with Upstash to identify the cause and restore service. We’ll provide an update as soon as we have more information.
Overlapping incidents aren't necessarily related.
Fly.io reported 19 incidents in the last 90 days, 11 of them major or critical. A typical incident lasted 57 min. See Fly.io's uptime and incident history