I migrated from Heroku to fly two months ago, and while I was super happy about how fly worked for the first few weeks, I have had enough. If you go through forums, you’ll find many occurrences of proxy issues, connectivity issues, hang-up deployments, etc. Two or three weeks ago, there was an iss…

I would like to address the broader points separately, but I don’t have time right now. A host had to be rebooted. Unfortunately it looks like some postgres clusters did not come back up gracefully and we’re looking into it. This should not affect apps that don’t need to connect to a postgres clust…

[image] mkozak: I do like this platform, it works really well when it’s working, but the amount of issues I have to deal with is simply too much. Agreed. When we started using fly.io , we swiftly migrated a signifant portion of our infrastructure over. The simplicity and painlessnes sold us. B…

Same here, I haven’t decided where to migrate yet, but I definitely have to. Maybe I’ll come back in the future. The biggest issue I see here is a lack of communication from fly side or no way to declare an incident from the customer’s perspective. I know covering all timezones with a small team is…

True. There’s nothing on https://status.flyio.net/ even though this has been going on for 2+ hours. There’s also zero activity from fly.io staff on the forums here within the same time. Yes, covering all timezones with a small team is difficult, but then (and that’s the harsh truth) it’s also simply…

Thanks @jerome . I’m looking forward to hearing your take on this & what fly.io has in store to be more reliable and responsive going forward. I’m genuinely bummed out that we have to migrate off of fly.io for the time being and I hope we can return in the future. As friends & colleagues can attest, …

I too have been affected by the PG issues lately. My production environment is running in AMS. I have a single user casually trying out the product and unfortunately he has been affected with 500 errors multiple times when the server couldn’t connect with PG. We’re not even in alpha so luckily this…

I will acknowledge things have been bumpy lately. The experience of each user on our platform depends a lot on what region they’re deployed to and what products they use. As a biased example: my closest region is YUL (Montreal) and I’ve been running a few apps there + a postgres cluster and I’ve on…

[image] jerome: Our stance was that our users are expected to launch highly-available applications So increasing flyctl scale count and/or adding more regions? [image] jerome: This includes Postgres clusters which were intended to be highly available if they were launched in a 3-node con…

[image] pier: So increasing flyctl scale count and/or adding more regions? Yes, that should always be good. Unless you scale to regions too far from your database then you might be in trouble. If this isn’t helping, then it is on us. [image] pier: What is a 3 node configuration? 3 VMs a…

Thank you a lot, @jerome , for such a thorough response! I’d like to clarify I don’t blame fly for all of this, I know how systems and platforms can be a mess, especially if there are issues in data centers, networking is down, etc. I have migrated from heroku for the simple reason - fly is way mor…

[image] mkozak: I hope things will get better soon, A wise man once said: [image] App stuck in pending state after restarts, rescaling It is, litestream will solve every problem anyone’s ever had.