Live data from Hacker News

Netlify Status – CDN Issues

netlifystatus.com

51–60 of 90 posts

Re: Netlify Status – CDN Issues

#51
post #41

Earlier quoted context omitted.

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!

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

Re: Netlify Status – CDN Issues

#52
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…

Depending on your config, another DNS related issue with Netlify is the way NS1.com (their vendor) handles domain names. A domain can only be added to one NS1 account. So if Netlify adds to their account internally, you can't use NS1 and vice versa.

Re: Netlify Status – CDN Issues

#54
post #15

Earlier quoted context omitted.

We're in the same boat, and when Netlify blames an "upstream provider", what I hear is that they don't have a backup plan. They're giving us plenty of time to research alternatives while our site is down though.

Based on the comment from bobfunk, it seems they do have a backup plan but not all customers use a configuration which takes advantage of it.

A backup plan that does not service apex domains is not really a backup plan.

Re: Netlify Status – CDN Issues

#55
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"

You're right. I'm using Cloudflare's DNS. I trust them more than I trust Netlify and that's just a function of their size vs Netlify's size. This response needed better wording.

Re: Netlify Status – CDN Issues

#56
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" You're right. I'm using Cloudflare's DNS. I trust them more than I trust Netlify and that's just a function of their size vs Netlify's size. This response needed better wording.

Cloudflare DNS supports CNAME flattening and you won't be needing the fixed IP address if setting up DNS with them.

Re: Netlify Status – CDN Issues

#57
post #51

Earlier quoted context omitted.

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

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?

Re: Netlify Status – CDN Issues

#58
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…

This could've been avoided with an HTTP LB, vs a L4 one...

Re: Netlify Status – CDN Issues

#59

Earlier quoted context omitted.

Based on the comment from bobfunk, it seems they do have a backup plan but not all customers use a configuration which takes advantage of it.

A backup plan that does not service apex domains is not really a backup plan.

It sounds like it does handle apex domains, but only if you're using Netlify DNS or a provider which supports CNAME flattening. Assuming the potential problems with not doing so are disclosed during setup (not sure if they were) that actually seems pretty reasonable to me.

Re: Netlify Status – CDN Issues

#60

Update on the Netlify Status page [0] -- TLDR anyone experiencing this issue should point their apex domain to 75.2.60.5 --- Full announcement: Our team have created a new load balancer instance which is not associated with the upstream provider who is currently experiencing issues. Please update A record values for your site(s) bare domain to 75.2.60.5 to mitigate against this outage. --- Their documentation page [1…

thanks for the TLDR - i pointed it over and can verify that it fixes the problem. annoying to wait out the caching on mobile devices though, i am not sure how to clear DNS cache on mobile but am not too bothered.
Post reply on HN