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

81–90 of 90 posts

Re: Netlify Status – CDN Issues

#81

Post by 1123581321 »

evrydayhustling wrote: post #80
1123581321 wrote: post #76

Earlier quoted context omitted.

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 (thoug…

Yes, I’ve visited that page before today. I admit my familiarity with these DNS setups may have made the tradeoff jump out at me. No problem invalidating the complaint.

Re: Netlify Status – CDN Issues

#82

Post by WORMS_EAT_WORMS »

jpbow wrote: post #79
WORMS_EAT_WORMS wrote: post #17

Earlier quoted context omitted.

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

They lack a framework and crystal clear way to start developing apps. Nothing exists that taps their features beyond maybe Flarereact.

Re: Netlify Status – CDN Issues

#83

Post by SahAssar »

MaggiD wrote: post #66

My startup has also suffered from the recent Netlify outages with our main landing page. Last time I already did the research for potential alternatives: - Cloudflare Pages is now available in public beta - even more interesting seemed this offering by PerfOps to put my CDN behind a Load Balancer that can monitor uptime and dynamically shift traffic between multiple CDN sources: https://perfops.net/flexbalancer What…

> CDN behind a Load Balancer

This sounds crazy to me. Besides the obvious superfluous network/layer hops, complexity and points of failure it would also partition the cache, right? So working against the very thing CDN's optimize for.

Re: Netlify Status – CDN Issues

#84

Post by dwrodri »

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…

As someone who is a little clueless about network infrastructure: if I own "dwrodri.com", and I'm not running a bunch of other services which need to point to this domain, is there any reason why I wouldn't have my root domain pointed to my personal website?

I would personally imagine that any individual or SOHO business hosting their website on GitHub/GitLab would just buy "MomAndPopShop.com" and point it there. I guess I don't know off the top of my head how many of those sorts of places on the web still exist...

Re: Netlify Status – CDN Issues

#85

Post by sgrove »

_fool wrote: post #67
foxbarrington wrote: post #44

Earlier quoted context omitted.

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

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 ) and ensure that you are "futureproofed"!

I can heartily recommend contacting _fool for support at Netlify. Always an absolute pleasure.

Re: Netlify Status – CDN Issues

#86

Post by LambdaComplex »

dwrodri wrote: post #84
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…

As someone who is a little clueless about network infrastructure: if I own "dwrodri.com", and I'm not running a bunch of other services which need to point to this domain, is there any reason why I wouldn't have my root domain pointed to my personal website? I would personally imagine that any individual or SOHO business hosting their website on GitHub/GitLab would just buy "MomAndPopShop.com" and point it there. I g…

The problem is not that they're pointing their apex domain to a personal website; the problem is that they have a CNAME record in place for their apex domain, which is not actually allowed per the DNS standards

Re: Netlify Status – CDN Issues

#87

Post by sofixa »

MaggiD wrote: post #66

My startup has also suffered from the recent Netlify outages with our main landing page. Last time I already did the research for potential alternatives: - Cloudflare Pages is now available in public beta - even more interesting seemed this offering by PerfOps to put my CDN behind a Load Balancer that can monitor uptime and dynamically shift traffic between multiple CDN sources: https://perfops.net/flexbalancer What…

There's also Vercel and Firebase ( Hosting ) which are stable ( not in beta as Cloudflare Pages).

Re: Netlify Status – CDN Issues

#88

Post by avianlyric »

juliansimioni wrote: post #11
avianlyric wrote: post #9

Earlier quoted context omitted.

You should checkout Cloudflare Pages. For static stuff it’s a dream to setup, and you get previews out of the box.

The main advantage that AWS will have for us over anything else is that, since AWS already manages our DNS, we are going to be able to offer our visitors the best performance by using geo-specific IP addresses. The static site in question for us lives at the apex record (mywebsite.com), so it's generally not possible for other providers to do this without having them manage our entire DNS infrastructure, which we are…

I think cloudflare can do it. They give you the option to set A records for your domain, in your own DNS.

Cloudflare runs an AnyCast[0] network and multiple peers, so even through your using static IPs, the traffic will still get routed to Cloudflare nearest PoP, and pages is served by their edge network, so your site will be served from the location nearest to your customer. All without DNS shenanigans.

[0] https://www.cloudflare.com/en-gb/learning/cdn/glossary/anyca...

Re: Netlify Status – CDN Issues

#89

Post by ahpeterson »

bobfunk wrote: post #48
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.

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…

Route 53 General Manager here. Flattening of external provider CNAMEs has a number of availability and accuracy risks. Route 53 offers a 100% availability SLA, and we really mean it. We’ve heard over and over from customers that reliability is our most valuable feature. We can’t provide that same reliability when external queries are in the mix; if we query asynchronously then features such as geo-based routing don’t work as expected for customers. If we query synchronously, then latency and availability are impacted directly.

We do offer ALIAS records between Route 53 hosted zones, and this capability is open to providers such as Netlify. We’d be happy to have customers ALIAS to a hosted zone managed and updated by Netlify. It sounds like your IP addresses are relatively stable, keeping these in sync doesn’t sound like it would be a big deal, and would give you a lever you could pull to change your customer DNS quickly in an event such as this. You could also configure health checks on your own DNS records, which any customer ALIAS records that point to your DNS records in Route 53 would inherit.

If you’re interested in going this route, please contact me at alecpete amazon com.

Re: Netlify Status – CDN Issues

#90

Post by rob-olmos »

ahpeterson wrote: post #89
bobfunk wrote: post #48

Earlier quoted context omitted.

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…

Route 53 General Manager here. Flattening of external provider CNAMEs has a number of availability and accuracy risks. Route 53 offers a 100% availability SLA, and we really mean it. We’ve heard over and over from customers that reliability is our most valuable feature. We can’t provide that same reliability when external queries are in the mix; if we query asynchronously then features such as geo-based routing don’t…

If each Route 53 POP is already close to the querying DNS client, then things like geo routing with cached answers might just work well enough in most cases? With each POP having its own cache.

Auto-refreshing the popular records in the background before the TTL expires to help smooth over any temporary issues?

Other big name DNS providers have ALIAS type records. I imagine according to the SLA, AWS Route 53 is still "available", even if it can't resolve a "target address record" (as the ANAME draft calls them) but Route 53 is still able to respond.

Post reply on HN