It’s showing this message. Any idea what can I do? We just re-deployed code.
Failed to proxy HTTP request (error: no known healthy instances found for route tcp/443. (hint: is your app shutdown? is there an ongoing deployment with a volume or using the 'immediate' strategy? if not, this could be a delayed state issue)). Retrying in 972 ms (attempt 10)
Yep, mine too. I don’t think it’s related to your app (and we haven’t just deployed code)
My site has just come back to life.
Mine also keeps going down today.
Starts with this concerning log:
2023-03-13T09:21:04.821 runner[8f801e03] sjc [info] Shutting down virtual machine
I restarted the app and worked for some time. It again went dead 
@kurt this is what I am talking about and I think you are also aware as per your last post that reliability is not that great. Can you please get us out of this situation? What is best way to avoid it?
no known healthy instances found for route tcp/443. (hint: is your app shutdown? is there an ongoing deployment with a volume or using the 'immediate' strategy? if not, this could be a delayed state issue)
Worst part is there is still nothing on status page.
I changed region from AMS to SIN and things seem to be working fine. This is really painful.
My app is in LON, so this definitely wasn’t AMS specific. I had some weirdness with another app not deploying at that time, but the app remained up (same region).
I also noticed that the status page has nothing about this incident. Fly needs to do better at updating that.
I also keep getting runner[eda01c74] hkg [info] Shutting down virtual machine in logs. It works when I restart it manually, but it still shutdown randomly after a while.
mine too same error restart works for sometime and dead again
We suddenly had downtime on our app after two web instances disappeared. No idea what happened there, but might be related. We are investigating.
What Fly team does not understand is that they did not try to achieve reliability of Kubernetes. If any pod goes down, Kubernetes makes it up again in seconds. When similar platform is provided, customers expect similar uptime. Unfortunately it does not work same way.
My app went dead as well. When I tried to re-deploy, it got really screwy, launching a second worker:
v600 failed - Failed due to unhealthy allocations - rolling back to job version 599
--> v600 failed - Failed due to unhealthy allocations - rolling back to job version 599 and deploying as v601
I also found a very strange line in the logs around the time of the original failure:
client problem: invalid authority (sic, without the timestamp) - we didn’t produce this log line
There’s a problem with deploys right now
My app also went dead, then up and is now dead again 
Really not cool, I hope Fly will be able to make their service reliable again
@pier the issue is that fly team posted status update after almost 3.5 hours and this is after the promised in last post that they have a team which will now frequently update status page.
Two of my instances got shut down today and didn’t get respawned. Not sure if it is the same issue mention on status page, i don’t think it has something to do with deploys or app status
Hi everyone, just so yall know, we’re currently working on fixing this issue that’s most likely affecting @adityapatadia, and this issue that may be affecting others in this thread.