Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Fly.io outage – resolved

status.flyio.net

Post reply on HN
Print view View original

71–80 of 287 posts

Re: Fly.io outage – resolved

#71

Post by [deleted] »

fragmede wrote: post #64
SOLAR_FIELDS wrote: post #38

Earlier quoted context omitted.

I get this but I think if people can give GitHub a pass for shitting the bed every two weeks maybe Fly should get a bit of goodwill here. I am not affiliated with Fly at all but I do think that people should temper their expectations when even mega corp can’t get it right I guess the secret is to be the incumbent with no suitable replacement. Then you can be complete garbage in terms of reliability and everyone will…

Who's giving GitHub a pass on shitting the bed? They go down often enough that if you don't have an internal git server setup for your CICD to hit, that's on you.

[deleted]

Re: Fly.io outage – resolved

#72

Post by fulafel »

runako wrote: post #66
kachapopopow wrote: post #40

Earlier quoted context omitted.

It's still 99.99+% SLA? Would you really pay 100% more for <0.01% more uptime?

No dog in this fight, all props to the Fly.io team for having the gumption to do what they are doing, I genuinely hope they are successful... > It's still 99.99+% SLA But this is simply not accurate. 99.99% uptime is annually of downtime. They apparently blew well through that today. Looks like they essentially had the equivalent of 4 years of 99.99% uptime equivalent this evening. Four nines is so unforgiving that i…

99.99+% SLA typically means you get some billing credits for the downtime exceeding 99.99+ availability. So technically do get a "99.99+% SLA", but you don't get 99.99+% availability.

Other circles use "SLO" (where the O stands for objective).

(Anyone know what the details in fly.io SLA are?)

Re: Fly.io outage – resolved

#73

Post by eviks »

totetsu wrote: post #34
rascul wrote: post #26

Earlier quoted context omitted.

There's a link to what appears to be the actual pricing page https://fly.io/docs/about/pricing/ There's also a link to the pricing calculator https://fly.io/calculator

Is that calculator hourly or monthly?

It's right there: "Monthly Cost"

Re: Fly.io outage – resolved

#74

Post by macNchz »

cj wrote: post #58
kachapopopow wrote: post #40

Earlier quoted context omitted.

It's still 99.99+% SLA? Would you really pay 100% more for <0.01% more uptime?

I think what a lot of people fail to understand is that there are certain categories of apps that simply “can never go down” Examples include basically any PaaS, IaaS, or any company that provides a mission-critical service to another company (B2B SaaS). If you run a basic B2C CRUD app, maybe it’s not a big deal if you service goes down for 5 minutes. Unfortunately there are quite a few categories of companies where…

Every PaaS and IaaS I’ve ever used has had some amount of downtime, often considerably more than 5 minutes, and I’ve run production services on many of them. Plenty of random issues on major cloud providers as well. Certainly plenty of situations with dozens of Twitter posts happening but never any acknowledgement on the AWS status page. Nothing’s perfect.

Re: Fly.io outage – resolved

#76

Post by pier25 »

DataOverload wrote: post #28

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.

Re: Fly.io outage – resolved

#77

Post by ignoramous »

marvin-hansen wrote: post #65

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…

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?

Re: Fly.io outage – resolved

#79

Post by dilyevsky »

marvin-hansen wrote: post #65

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…

> 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.

Majority of EC2 instance types did not have live migration until very recently. Some probably still don't (they don't really spell out how and when it's supposed to work). It is also not free - there's a noticeable brown-out when your VM gets migrated on GCP for example.

Re: Fly.io outage – resolved

#80

Post by pier25 »

HellsMaddy wrote: post #20

Suspiciously, Turso started having issues around the same time. Their CEO confirmed on Discord it's due to the Fly outage: > Ok.I caught up with our oncall and This seems related to the Fly.io incident that is reported in our status page. Our login does call things in the Fly.io API > we are already in touch with Fly and will see if we can speed this up

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.

Post reply on HN