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

Netlify Status – CDN Issues

netlifystatus.com

Post reply on HN
Print view View original

71–80 of 90 posts

Re: Netlify Status – CDN Issues

#71

Post by evrydayhustling »

oji0hub wrote: post #43
ukulele wrote: post #42

Earlier quoted context omitted.

Yes, it is our fault for believing Netlify had contingency plans as hosting is their core business. We're fixing this mistake now so that our customers don't have the same experience.

By the same line of reasoning, your customers could be faulted for believing you had a contingency plan.

Nobody is telling parent's customers how to feel. But the OP suggests that Netlify customers should be faulted for choosing the the wrong setup. Broken trust goes all the way down the chain, which is why the middle links have every reason to get ticked off.

Re: Netlify Status – CDN Issues

#73

Post by pscanf »

jgrahamc wrote: post #62
pscanf wrote: post #26

Shameless plug, I can suggest StaticDeploy ( https://staticdeploy.io/ ) as an open source, self-hosted alternative to Netlify, which can give you a similar deployment workflow. It's definitely possible to just host directly on S3/CloudFront, but StaticDeploy sets you up quickly with a workflow and a dedicated management interface. Disclaimer: I'm the main developer of the project.

Honestly, don't do this. Netlify is having a bad day and it's not fun for them. The great wheel of karma turns around slowly and one day it'll be your turn to have a bad day. Submit StaticDeploy to HN some other day and tell us about it. Sounds cool.

Thanks for pointing this out, I admit I did not consider their point of view (the plug was shameless, but in the self-promotion-is-inherently-shameful sense), and I agree it's in bad taste.

Re: Netlify Status – CDN Issues

#74

Post by jgrahamc »

bigsparky wrote: post #70
jgrahamc wrote: post #62

Earlier quoted context omitted.

Honestly, don't do this. Netlify is having a bad day and it's not fun for them. The great wheel of karma turns around slowly and one day it'll be your turn to have a bad day. Submit StaticDeploy to HN some other day and tell us about it. Sounds cool.

Cloudflare CTO telling off the open source project guy, while ignoring all the other comments suggesting cloudflare?

There's a difference between self-promotion and other people making a suggestion.

Re: Netlify Status – CDN Issues

#75

Post by huy-nguyen »

sanedigital wrote: post #57
ukulele wrote: post #51

Earlier quoted context omitted.

Not trolling, just very frustrated. But yes a valuable lesson.

What's keeping you from migrating your frontends? Shouldn't that take a couple of hours at worst?

It's not just migrating the front-end if they're also using other functionalities like Netlify functions, forms, authentications etc. Netlify is not just static file hosting.

Re: Netlify Status – CDN Issues

#76

Post by 1123581321 »

evrydayhustling wrote: post #71
oji0hub wrote: post #43

Earlier quoted context omitted.

By the same line of reasoning, your customers could be faulted for believing you had a contingency plan.

Nobody is telling parent's customers how to feel. But the OP suggests that Netlify customers should be faulted for choosing the the wrong setup. Broken trust goes all the way down the chain, which is why the middle links have every reason to get ticked off.

The difference is that Netlify communicated the risks to its customers, something other parts of the chain apparently did not do, in addition to not evaluating the risks presented to them by Netlify.

Re: Netlify Status – CDN Issues

#77

Post by jpbow »

danr4 wrote: post #14

Hmmm, lots of recent outages. Has anyone else noticed erratic response times in recent months? My web vitals score sometimes dips heavily because "response time from server" (or whatever it's called). Anyone can recommend another place where I can host? (except Vercel, which has similar results)

Cloudflare Pages, begin.com, fly.io, and surge.sh are a few I've come across as alternatives (depending on what features you're after).

Re: Netlify Status – CDN Issues

#79

Post by jpbow »

WORMS_EAT_WORMS wrote: post #17
jayp wrote: post #2

They and Vercel both seem to be going thru a lot of growing pains. Quite a few outages over the past year. PS: we use both (for different sites). Probably should consolidate to one.

I’m not sure the future in this space, but I kind just wish Cloudflare and Vercel would join forces. It would make sense to me.

Cloudflare is already on the way to building out all of the features Vercel has which is exciting. Eventually their Pages product (static hosting) will integrate Workers [1] for serverside APIs.

[1] https://blog.cloudflare.com/cloudflare-pages/#oh-and-one-mor...

Re: Netlify Status – CDN Issues

#80

Post by evrydayhustling »

1123581321 wrote: post #76
evrydayhustling wrote: post #71

Earlier quoted context omitted.

Nobody is telling parent's customers how to feel. But the OP suggests that Netlify customers should be faulted for choosing the the wrong setup. Broken trust goes all the way down the chain, which is why the middle links have every reason to get ticked off.

The difference is that Netlify communicated the risks to its customers, something other parts of the chain apparently did not do, in addition to not evaluating the risks presented to them by Netlify.

Did you read the docs [1] before writing this? Putting a "(recommended)" on one branch of configuration instructions isn't the same as saying that the other option has a single point of failure. Also, people on both sides of a service don't have the same responsibilities - that's the whole point of the service.

Communicating about risks OR outages are both hard, and every company has both. I'm actually a happy (though impacted) Netlify customer. But it's completely bizarre to me to try to invalidate this customer's complaint.

[1] https://web.archive.org/web/20200303050851/https://docs.netl... (search "flattening")

Post reply on HN