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!
Fly.io outage – resolved
231–240 of 287 posts
Re: Fly.io outage – resolved
#232...with not a single status update from Microsoft in sight.
Re: Fly.io outage – resolved
#233Fly.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.
in fact, you can almost get the same thing fly.io does by running firecracker on your own bare metal servers and cheaper too.
I'm afraid the public sentiment towards fly.io has been tainted for good (I can't count how many times they apologized now).
Re: Fly.io outage – resolved
#234Fly.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.
For experiments and hobby projects the value proposition is amazing. Where else can you spin up an independent instance for $1.94 per month?* *Note this is for an instance with only 256MB RAM ( https://fly.io/docs/about/pricing/ ), but it's definitely possible to run non-trivial projects on that. Rust-based web servers like Rocket require only about 10MB RAM. Basic PHP servers should also fit from what I can find.
if you are going to haggle over $2/month then you are better off just connecting your raspberry pi with wireguard/cloudflare tunnel on a residential connection
Re: Fly.io outage – resolved
#235Fly.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.
The reliability is very very bad. It was really insane that 2 times in the past few months the main dashboard was down as I’m demoing something. Not to mention the deploy outages and almost daily some random thing was unavailable or delayed. I had to leave a few months ago after the price raises and how many times my boss saw some issue in the project I had with them. They also deprecated and removed their sqlite bac…
expect to see more of these "post-mortem apologies" from fly.io in the future because it won't be the last
Re: Fly.io outage – resolved
#236Earlier 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.
but GO and pocketbase is on record for supporting 10k concurrent requests per second on low powered VPS
Re: Fly.io outage – resolved
#237Earlier quoted context omitted.
VP at Goldman is equivalent to Senior SWE according to levels.fyi and their entry level is Analyst. I'm surprised by the compensation though. I would have thought people working at a place with gold in the name would be making more. Also apparently Morgan Stanley pays their VPs $67k/year.
That VP comp number seems quite low fwiw
Re: Fly.io outage – resolved
#238Fly.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.
Re: Fly.io outage – resolved
#239Earlier 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.
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.
5G towers are a ton of compute on the edge to secure and protect the traffic passing through them.
Or if by edge you mean having stuff close to your consumers, every non trivial operation does that.
Re: Fly.io outage – resolved
#240No 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…
Fly.io can migrate vm+volume now: https://fly.io/docs/reference/machine-migration/ / https://archive.md/rAK0V > a fly instance is hardwired to one physical server and thus cannot fail over I'm having trouble understanding how else this is supposed to be? I understand that live migration is a thing, but even in those cases, a VM is "hardwired" to some physical server, no?
They mean the storage part. If your VM's storage(state) is on one server and that server dies, you have to restore from backup. If your VM's storage is on remote shared storage mounted to that server and the server dies, your VM can be restarted elsewhere that has access to that shared storage.
In AWS land it's the difference between instance store (local to a server) and EBS (remote, attached locally).
There's a tradeoff in that shared storage will be slightly slower due to having to traverse networking, and it's harder to manage properly; but the reliability gain is massive.