Upstash unavailability in FRA region

Zeitverlauf

1. 12:42 UTC Statusseite von Fly.io · Reported Upstash unavailability in FRA region
2. 12:42 UTC Statusseite von Fly.io · Wird untersucht 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.
3. 13:08 UTC Statusseite von Fly.io · Wird beobachtet A fix has been implemented and we are monitoring the results.
4. 14:03 UTC Statusseite von Fly.io · Behoben This incident has been resolved.
5. 07:22 UTC Statusseite von Fly.io · Behoben 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…