zlacker

>>tablet+(OP)
And this goes at least part of the way towards explaining why Fly.io has been the second least reliable cloud provider I've ever used, after Azure.

>>donatj+rb
"Don't be snarky."

"Please don't post shallow dismissals, especially of other people's work. A good critical comment teaches us something."

https://news.ycombinator.com/newsguidelines.html

>>dang+BL
I apologize. I genuinely did not mean snark, nor to be dismissive. It was a sincere honest-to-god "oh wow this actually explains the situation over there" mixed with an expression of frustration with their service quality.

A lot of their pages barely work and feel like first drafts, much of the UI is even labeled as a work in progress, and manytools regularly just fail to do what they're supposed to.

Deployments are routinely broken, with Twitter lit up like a light bulb about it while their status page remains all services operational.

I deploy three completely separate applications with Fly.io and have regular unscheduled downtime.

I stick with them despite all this because they're cheap and easily scale regular Go apps down to zero which is wonderful for apps that see intermittent/irregular usage patterns.

The fact that they are adamant defenders of vibe coding going so far in the post as to say "who cares about hallucinations" genuinely explains a fair deal about their unprofessional feeling service.