Live data from Hacker News

Fly.io Postgres cluster down for 3 days, no word from them about it

webcache.googleusercontent.com

491–493 of 493 posts

Re: Fly.io Postgres cluster down for 3 days, no word from them about it

#491

Earlier quoted context omitted.

I moved from DO to Hetzner ( cheaper), I am happy about it.

I use both and am very satisfied, especially by Hetzner.

Hey would you be into trying a manage service platform I'm building for Hetzner? It's called Nimbus[0].

I'd love some feedback, specifically:

- Which services do you most want to use/have managed

- What databases do you find yourself using the most

- Concerning caches, do you use memcached or mostly Redis?

[0]: https://nimbusws.com

Re: Fly.io Postgres cluster down for 3 days, no word from them about it

#492
post #136

Earlier quoted context omitted.

I moved from DO to Hetzner ( cheaper), I am happy about it.

I'm enjoying the DO App Platform (Heroku alternative). Do you know if Hetzner has a similar service that I could compare?

Hey I'm building a managed service platform (not quite an app store!) on top of Hetzner -- would you be interested in trying it out?

Contact is in my profile but I'd love to have some more people kick the tires and tell me what they want built the most.

Re: Fly.io Postgres cluster down for 3 days, no word from them about it

#493
I (like many others) want fly to succeed and have even moved a couple of (smaller) production apps to Fly.

But it's very clear that over the last few months, the (already quite capable) fly team is just in over their heads and have bitten off way way more than they can chew.

I've had nothing but headaches after they auto-migrated our app to v2. My build machine had to be forcibly destroyed to even work. Then it allowed me to easily just delete an app cuz I wasn't able to deploy to it.

Then the deploys kept failing due to some VM provisioning error (it thinks I want to add another app when I just want to deploy to an existing app within the 3 machine limit) and honestly, I just don't care to troubleshoot this anymore. That was the point of using a platform like this... Any time I would've saved by using this platform has been wasted with these random errors that I don't have the time to troubleshoot.

I destroyed the app thinking "ok maybe I'll also recreate that one" because clearly the migration to v2 failed. And now that all my secrets were destroyed, when I try to attach the new app to postgres (with the existing username and existing database), it won't let me.

I genuinely wish you guys the best of luck with what has to be a tough time for your company, and will reconsider if you build something demonstrably more stable. But right now I just can't afford to drown with you with clients breathing down my neck.

Post reply on HN