- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Upstash for Redis
What to do
Check whether you use Fly.io Upstash for Redis. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 22m it lasted.
Anything that failed between 2026-09-23 12:42 UTC and 2026-09-23 14:03 UTC may need a replay.Subscribe to Fly.io's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=fly works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Root cause
We are working with Upstash to identify the cause and restore service.Read the postmortem
Updates from Fly.io 4
- investigating
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.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved.
provider
- resolved
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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-ec3fce863e
Is Fly.io still down?
No, this incident was resolved 2026-09-23 14:03 UTC. For Fly.io's live state, see https://down.guide/fly.
How long did it last?
1h 22m, from 2026-09-23 12:42 UTC to 2026-09-23 14:03 UTC, by the times Fly.io posted.
What was affected?
Fly.io named Upstash for Redis.
What caused it?
Fly.io wrote: "We are working with Upstash to identify the cause and restore service." The postmortem: https://status.flyio.net/incidents/01M376272WGYT2F3BJ9ZK1WDYB
Where does this come from?
Fly.io's official status page, https://status.flyio.net, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.