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

41–50 of 90 posts

Re: Netlify Status – CDN Issues

#41

Post by ukulele »

WORMS_EAT_WORMS wrote: post #37
ukulele wrote: post #34

Earlier quoted context omitted.

Honestly, "not taking advantage of our DNS management" is a garbage response. We use AWS for our DNS management. If you offer a configuration, you should support it fully. Our sites have been down for 3 hours now, and you're blaming someone else? We have 5 properties on Netlify now and will have 0 this time next week.

I'm not sure your organization's setup with Netlify but isn't the whole point of Serverless to be... "serverless"? I could migrate twice the amount of properties you have to another provider in less than 3 hours... I get your frustration but maybe cut some slack. If anything is mission critical, you should have had a backup plan if Netlify, Vercel, Cloudflare, or something else.

We use(d) Netlify for the frontend. I agree, our mistake was believing Netlify could be used for more than toy websites and took care of backup plans for us. Clearly they do not.

Re: Netlify Status – CDN Issues

#42

Post by ukulele »

oji0hub wrote: post #39
ukulele wrote: post #34

Earlier quoted context omitted.

Honestly, "not taking advantage of our DNS management" is a garbage response. We use AWS for our DNS management. If you offer a configuration, you should support it fully. Our sites have been down for 3 hours now, and you're blaming someone else? We have 5 properties on Netlify now and will have 0 this time next week.

> Our sites have been down for 3 hours now, and you're blaming someone else? Well if the issue is at Google then maybe "blaming" isn't really the right word. No need to be rude. I might as well make the same argument for your sites. - Your sites have been down for 3 hours now, and you're blaming someone else?

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.

Re: Netlify Status – CDN Issues

#43

Post by oji0hub »

ukulele wrote: post #42
oji0hub wrote: post #39

Earlier quoted context omitted.

> Our sites have been down for 3 hours now, and you're blaming someone else? Well if the issue is at Google then maybe "blaming" isn't really the right word. No need to be rude. I might as well make the same argument for your sites. - Your sites have been down for 3 hours now, and you're blaming someone else?

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.

Re: Netlify Status – CDN Issues

#44

Post by foxbarrington »

nrmitchi wrote: post #40
bobfunk wrote: post #28

Netlify CEO here. I'll try to answer the questions from the thread so far: Some of our customers are affected by an outage of Googles Load Balancer. These customers are not taking advantage of our DNS management, or they are not using a DNS provider that supports CNAME flattening and are using their root domain name for their website (ie, no www prefix). While we don't recommend the setup, we do provide a single IP a…

> These customers are not taking advantage of our DNS management I think I understand the point you are trying to make, that customers who are utilizing Netlify DNS Management are unaffected because reasons , but this is phrased in a way that implies that it is your users fault for this downtime because they didn't chose to use your related service.

Sadly, even after switching to their DNS I am still affected.

Re: Netlify Status – CDN Issues

#45

Post by WORMS_EAT_WORMS »

ukulele wrote: post #41
WORMS_EAT_WORMS wrote: post #37

Earlier quoted context omitted.

I'm not sure your organization's setup with Netlify but isn't the whole point of Serverless to be... "serverless"? I could migrate twice the amount of properties you have to another provider in less than 3 hours... I get your frustration but maybe cut some slack. If anything is mission critical, you should have had a backup plan if Netlify, Vercel, Cloudflare, or something else.

We use(d) Netlify for the frontend. I agree, our mistake was believing Netlify could be used for more than toy websites and took care of backup plans for us. Clearly they do not.

I do believe you to be trolling now by saying that. If not, congrats on the valuable lesson!

Re: Netlify Status – CDN Issues

#46

Post by ohadpr »

nrmitchi wrote: post #40
bobfunk wrote: post #28

Netlify CEO here. I'll try to answer the questions from the thread so far: Some of our customers are affected by an outage of Googles Load Balancer. These customers are not taking advantage of our DNS management, or they are not using a DNS provider that supports CNAME flattening and are using their root domain name for their website (ie, no www prefix). While we don't recommend the setup, we do provide a single IP a…

> These customers are not taking advantage of our DNS management I think I understand the point you are trying to make, that customers who are utilizing Netlify DNS Management are unaffected because reasons , but this is phrased in a way that implies that it is your users fault for this downtime because they didn't chose to use your related service.

Phrasing can always be better but the point is that there's a way to map your DNS to Netlify which is risky and Netlify hasn't made the aggressive decision of blocking it. They outline in their docs all the reasons why you shouldn't do it, provide instructions for how to avoid it and also offer (but do not require) a hosted DNS setup which avoids this pitfall by design.

Some folks still choose to use this way, some have no other choice for various reasons and some don't care/comprehend the potential pitfalls. I do believe most users avoid using a root domain name for their website.

Re: Netlify Status – CDN Issues

#47

Post by gtirloni »

ohadpr wrote: post #46
nrmitchi wrote: post #40

Earlier quoted context omitted.

> These customers are not taking advantage of our DNS management I think I understand the point you are trying to make, that customers who are utilizing Netlify DNS Management are unaffected because reasons , but this is phrased in a way that implies that it is your users fault for this downtime because they didn't chose to use your related service.

Phrasing can always be better but the point is that there's a way to map your DNS to Netlify which is risky and Netlify hasn't made the aggressive decision of blocking it. They outline in their docs all the reasons why you shouldn't do it, provide instructions for how to avoid it and also offer (but do not require) a hosted DNS setup which avoids this pitfall by design. Some folks still choose to use this way, some h…

> I do believe most users avoid using a root domain name for their website.

This is where you're definitely wrong.

Re: Netlify Status – CDN Issues

#48

Post by bobfunk »

nrmitchi wrote: post #40
bobfunk wrote: post #28

Netlify CEO here. I'll try to answer the questions from the thread so far: Some of our customers are affected by an outage of Googles Load Balancer. These customers are not taking advantage of our DNS management, or they are not using a DNS provider that supports CNAME flattening and are using their root domain name for their website (ie, no www prefix). While we don't recommend the setup, we do provide a single IP a…

> These customers are not taking advantage of our DNS management I think I understand the point you are trying to make, that customers who are utilizing Netlify DNS Management are unaffected because reasons , but this is phrased in a way that implies that it is your users fault for this downtime because they didn't chose to use your related service.

Full RCA with the steps the team has taken to improve this setup will be coming soon. The main issue with AWS's DNS solution, in this context, is that they don't support ALIAS records or similar techniques (CNAME flattening, etc) for A records pointing to any external provider. That limits our options a lot in terms of what we can do, since anyone using this setup need to point all their traffic to one or more fixed IP addresses.

Our current solution for the free/self-serve tier of Netlify has been to rely on Google's load balancer product to give people a stable IP pointing to a highly available solution. In light of recent issues, our team has setup a new permanent IP for A records (75.2.60.5) backed by a different solution, but due to the way DNS providers with no ALIAS record support work, it does require our customers to manually change their A records.

I totally get that moving DNS providers is a big deal and we want to give the best experience we can regardless of what provider you're on, but we have to work within the technical limitations of those providers and it's the nature of things that we do have more options to deliver a completely seemless experience when we operate both the DNS and the edge layer for customers.

Re: Netlify Status – CDN Issues

#49

Post by [deleted] »

foxbarrington wrote: post #44
nrmitchi wrote: post #40

Earlier quoted context omitted.

> These customers are not taking advantage of our DNS management I think I understand the point you are trying to make, that customers who are utilizing Netlify DNS Management are unaffected because reasons , but this is phrased in a way that implies that it is your users fault for this downtime because they didn't chose to use your related service.

Sadly, even after switching to their DNS I am still affected.

[deleted]

Re: Netlify Status – CDN Issues

#50

Post by ohadpr »

gtirloni wrote: post #47
ohadpr wrote: post #46

Earlier quoted context omitted.

Phrasing can always be better but the point is that there's a way to map your DNS to Netlify which is risky and Netlify hasn't made the aggressive decision of blocking it. They outline in their docs all the reasons why you shouldn't do it, provide instructions for how to avoid it and also offer (but do not require) a hosted DNS setup which avoids this pitfall by design. Some folks still choose to use this way, some h…

> I do believe most users avoid using a root domain name for their website. This is where you're definitely wrong.

I could be. Are you saying this based on data or intuition?
Post reply on HN