5 ms·

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 cus

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 address to bind an A records for customers that want it. In general we run our edge infrastructure as a large multicloud setup spanning several different network providers, and offer two separate networks, one for free/self-serve customers that will get newer features faster and one for enterprise customers running mission critical projects where we guarantee very high uptime and reliability through formal SLAs. The single IP mentioned above however corresponds to a Google Load Balancer, and they are unfortunately currently having an outage for all load balancers in the relevant region. Read more on https://status.cloud.google.com/ https://status.cloud.google.com/ Again, while we generally don't recommend using the A name setup for anything mission critical, we are currently doing everything we possible can helping enterprise customers that have chosen this setup to change their configuration. Really sorry for all the trouble this are causing for our users, full RCA will be forthcoming.

martin_bech 6y ago
Hi Bob, just want to say, I like your service a lot.
- bobfunk 6y ago
  Thanks! Appreciate the kind words!
  - StavrosK 6y ago
    Seconded, I use it for all my static hosting. Great service.
WORMS_EAT_WORMS 6y ago
Are you all having shake ups within the company? I'm not going to deep dive, but I heard some rumors about some higher ups leaving. After the Cloudflare Pages release, I'd be curious of what your future road map looks like and how you all plan to compete and grow. Thanks for all you and your team does. What you have done for front-end development and the community has been nothing but awesome and inspiring.
ukulele 6y ago
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.
- gregsadetsky 6y ago
  Point your apex domain to 75.2.60.5, Netlify recommends it here [0] and in their documentation now [1]. I just did for a site that's hosted by Netlify and it solved the issue. Thankfully I had a short TTL, I hope you do too. [0] https://www.netlifystatus.com/ https://www.netlifystatus.com/ [1] https://docs.netlify.com/domains-https/custom-domains/configure-external-dns/#configure-an-apex-domain https://docs.netlify.com/domains-https/custom-domains/config...
- WORMS_EAT_WORMS 6y ago
  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.
  - ukulele 6y ago
    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.
    - WORMS_EAT_WORMS 6y ago
      I do believe you to be trolling now by saying that. If not, congrats on the valuable lesson!
      - 6y ago
foxbarrington 6y ago
I switched to using your DNS to resolve this issue, but https://js.la https://js.la is still busted and because I'm using your DNS, I can't manually set the A record to go to the workaround IP address.
nrmitchi 6y ago
> 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.
- foxbarrington 6y ago
  Sadly, even after switching to their DNS I am still affected.
  - deleted 6y ago
    [deleted]
  - _fool 6y ago
    This should not be the case; if you'd like, Netlify's Support team will be happy to review your settings to help discover why it didn't help you out (start from https://netlify.com/support https://netlify.com/support) and ensure that you are "futureproofed"!
    - sgrove 6y ago
      I can heartily recommend contacting _fool for support at Netlify. Always an absolute pleasure.
- ohadpr 6y ago
  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.
sbr464 6y ago
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.
instakill 6y ago
"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.
- bobfunk 6y ago
  Cloudflare DNS supports CNAME flattening and you won't be needing the fixed IP address if setting up DNS with them.
  - _fool 6y ago
    More details for folks who are curious about optimal config using Cloudflare's DNS hosting, can be found here: https://answers.netlify.com/t/support-guide-which-are-some-good-dns-providers-for-alias-aname-support/211 https://answers.netlify.com/t/support-guide-which-are-some-g...
gcbirzan 6y ago
This could've been avoided with an HTTP LB, vs a L4 one...

martin_bech 6y ago

Hi Bob, just want to say, I like your service a lot.

bobfunk 6y ago
Thanks! Appreciate the kind words!
- StavrosK 6y ago
  Seconded, I use it for all my static hosting. Great service.

WORMS_EAT_WORMS 6y ago

Are you all having shake ups within the company? I'm not going to deep dive, but I heard some rumors about some higher ups leaving. After the Cloudflare Pages release, I'd be curious of what your future road map looks like and how you all plan to compete and grow. Thanks for all you and your team does. What you have done for front-end development and the community has been nothing but awesome and inspiring.

ukulele 6y ago

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.

gregsadetsky 6y ago
Point your apex domain to 75.2.60.5, Netlify recommends it here [0] and in their documentation now [1]. I just did for a site that's hosted by Netlify and it solved the issue. Thankfully I had a short TTL, I hope you do too. [0] https://www.netlifystatus.com/ https://www.netlifystatus.com/ [1] https://docs.netlify.com/domains-https/custom-domains/configure-external-dns/#configure-an-apex-domain https://docs.netlify.com/domains-https/custom-domains/config...
WORMS_EAT_WORMS 6y ago
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.
- ukulele 6y ago
  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.
  - WORMS_EAT_WORMS 6y ago
    I do believe you to be trolling now by saying that. If not, congrats on the valuable lesson!
    - 6y ago

foxbarrington 6y ago

I switched to using your DNS to resolve this issue, but https://js.la https://js.la is still busted and because I'm using your DNS, I can't manually set the A record to go to the workaround IP address.

nrmitchi 6y ago

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

foxbarrington 6y ago
Sadly, even after switching to their DNS I am still affected.
- deleted 6y ago
  [deleted]
- _fool 6y ago
  This should not be the case; if you'd like, Netlify's Support team will be happy to review your settings to help discover why it didn't help you out (start from https://netlify.com/support https://netlify.com/support) and ensure that you are "futureproofed"!
  - sgrove 6y ago
    I can heartily recommend contacting _fool for support at Netlify. Always an absolute pleasure.
ohadpr 6y ago
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.

sbr464 6y ago

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.

instakill 6y ago

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

bobfunk 6y ago
Cloudflare DNS supports CNAME flattening and you won't be needing the fixed IP address if setting up DNS with them.
- _fool 6y ago
  More details for folks who are curious about optimal config using Cloudflare's DNS hosting, can be found here: https://answers.netlify.com/t/support-guide-which-are-some-good-dns-providers-for-alias-aname-support/211 https://answers.netlify.com/t/support-guide-which-are-some-g...

gcbirzan 6y ago

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