Live data from Hacker News

Fly.io outage – resolved

status.flyio.net

201–210 of 287 posts

Re: Fly.io outage – resolved

#201
post #8

My fly.io-hosted website went down for 5 minutes (6 hours ago), but then came right back up, and has been up ever since. I use a free monitoring service that checks it every 5 minutes, so it's possible it missed another short bit of downtime. But fly.io has been pretty reliable overall for me!

Do you mind if I ask what monitoring service that is?

https://github.com/louislam/uptime-kuma

Re: Fly.io outage – resolved

#202
post #80

Earlier quoted context omitted.

Not the first time Turso goes down because of Fly issues. It must suck to have built a db service and have this downtime. Apparently Turso are going to offer an AWS tier at some point.

Last month Turso released AWS-hosted databases to the public (still in Beta): https://turso.tech/blog/turso-aws-beta

Thanks!

Re: Fly.io outage – resolved

#203

Fly.io seems to be a bit of a mixed bag: https://news.ycombinator.com/item?id=41917436 https://news.ycombinator.com/item?id=35044516 https://news.ycombinator.com/item?id=34742946 https://news.ycombinator.com/item?id=34229751 If a cloud platform doesn't really provide reliability, I'd say it's probably not worth it. You could better just rent a (virtual) server and save the cloud tax.

I don't really understand the value prop of fly.io. They seem to have an impressive engineering team despite the outages, but is edge compute really something that 99.9% of devs need? There are tons of large companies that operate out of a single AWS region and those services are used by millions around the globe. It just strikes me as something that enables premature optimization right out of the box.

I have an SSR Astro project. Using Fly makes my project fast.

For dynamic data I use SWR.

I could use Cloudflare workers but it doesn’t play so nice with Astro.

I also have a “form submission service” where I receive a Post and send an email.

I need maximum uptime to avoid revenue loss.

It’s a go service so I deploy ~6 machines across the US to ensure I don’t drop any requests.

I haven’t had downtime in years.

Re: Fly.io outage – resolved

#204
post #168

Earlier quoted context omitted.

I don't really understand the value prop of fly.io. They seem to have an impressive engineering team despite the outages, but is edge compute really something that 99.9% of devs need? There are tons of large companies that operate out of a single AWS region and those services are used by millions around the globe. It just strikes me as something that enables premature optimization right out of the box.

It's basically the new Heroku with less lock-in, because it works with Docker. You get edge computing, autoscaling, and load balancing without additional configuration. Not as flexible as AWS, but also much easier to setup and maintain. But the reliability issues suck now and then.

I have asked this multiple times but is anyone really using edge compute and getting value out of it? I am certain there are cases but I have not seen any of them written up before.

Re: Fly.io outage – resolved

#205
post #160

Earlier quoted context omitted.

On that Consul outage, Fly Infra concludes, "The moral of the story is, no more half-measures." On their careers page [1], the Fly team goes, "We're not big believers in tech debt." As an outsider, reads like a cacophony of contradictions? [1] https://fly.io/docs/hiring/working/#we-re-ruthless-about-doi...

Two contradictory statements do not read like a 'cacophony' of anything to me xD I think you need a whole lot more than two to do that word justice.

“No more half-measures” and “We’re not big believers in tech debt” aren’t even contradictory statements, let alone a cacophony of them.

Re: Fly.io outage – resolved

#206
post #168

Earlier quoted context omitted.

It's basically the new Heroku with less lock-in, because it works with Docker. You get edge computing, autoscaling, and load balancing without additional configuration. Not as flexible as AWS, but also much easier to setup and maintain. But the reliability issues suck now and then.

> Not as flexible as AWS Today, Fly.io is more or less in the same market as Lightsail , not AWS. And when you compare it to Lightsail , it blows it away.

Did you count reliability into your assesment here? I'm reading about Fly.io outages multiple times a year, whereas Lightsail seem to be as stable as AWS EC2.

Re: Fly.io outage – resolved

#207

Earlier quoted context omitted.

DigitalOcean has been doing this for years, and their value proposition is unmatched IMO For $5 you get: Latest gen CPUs and RAM HTTPS DDoS protection Cloudflare CDN Autoscale Competent support I'd say the best part is the predictable monthly prices And while most people probably don't care, they are an established public company, so there is more chance they will exist in 10 years

the $5 droplet is underpowered and can't run anything substantial. it's just the price to get you in the door.

It doesn't really need to run anything "substantial" though. Running some janky wordpress site with some scabbed-on ecommerce customizations is like 50% of the internet.

Re: Fly.io outage – resolved

#208
post #76

We switched from Fly to CF workers a while ago, and never looked back

Our stuff on CF Workers has been working non stop for years now. About 6 months ago we migrated our most critical stuff from Fly to CF and boy every time Fly has issues I'm so glad we did.

Too much custom stuff too quickly, there is a lot of efficiency in vertical integration and a fully cohesive stack but it takes a very long time to stabilize if you take that route.

We spent months trying to convince them of problems with their H2 implementation in their LB/proxy (they insisted nginx was at fault, spoiler - it wasn't) but had to leave (we also went to CF, which has its own problems). Eventually one of their employees wrong a long blog post about H2 that made it obvious they finally found and fixed those problems but months too late for my employer at the time.

It would have been infinitely better for us if they could have just fixed their stability problems, that abstraction suited us as did their LB/proxy impl and SNI pricing.

I wish them well, some really smart folk over there but I can imagine these reliability problems are probably really grinding down morale.

Re: Fly.io outage – resolved

#209

Earlier quoted context omitted.

DigitalOcean has been doing this for years, and their value proposition is unmatched IMO For $5 you get: Latest gen CPUs and RAM HTTPS DDoS protection Cloudflare CDN Autoscale Competent support I'd say the best part is the predictable monthly prices And while most people probably don't care, they are an established public company, so there is more chance they will exist in 10 years

the $5 droplet is underpowered and can't run anything substantial. it's just the price to get you in the door.

a 1vCPU 512mb instance is plenty for most base cases. Maybe you need one additional machine to act as a background worker. I am sure there are some noisy neighbors but to say its underpowered is silly.

Re: Fly.io outage – resolved

#210
post #86

No surprise. About a year ago, I looked at fly.io because of it's low pricing and I was wondering where they were cutting corners to still make some money. Ultimately, I found the answer in their tech docs where it was spelled out clearly that an fly instance is hardwired to one physical server and thus cannot fail over in case that server dies. Not sure if that part still is in the official documentation. In practic…

If you want HA on Fly you need to deploy an app to multiple regions (multiple machines). Fly might still go down completely if their proxy layer fails but it's much less common.

The proxy layer was the cause of yesterday's outage according to support.
Post reply on HN