Whom are they using? In 2021 for static sites behind a CDN being down is... odd. Pretty much all CDNs by now should support equivalent of serve stale.
think this is a DNS issue, not CDN. bobfunk noted it is Google, scroll up
Netlify Status – CDN Issues
61–70 of 90 posts
Re: Netlify Status – CDN Issues
#62Shameless 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.
Re: Netlify Status – CDN Issues
#63This has been the third major outage for Netlify in the last few weeks. I like the company, they have good people on their team, and their interface and functionality is great (deploy previews are so nice!). But this is probably the last straw, as the static portion of our company's website has been down for 45 minutes now. Fortunately, the beauty of a static site is they're quite easy to host anywhere. We're already…
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.
It seems that a lot of people didn't have backup plans either. I'm not sure if it's a good idea to rely on just one provider for something critical.
Re: Netlify Status – CDN Issues
#64This got me today. Probably could be characterized as the classic case of: Company says a certain use case is unsupported, but tries hard to accommodate users who are stuck with the unsupported use case, so they hack up a decent work around under the hood. Then the technically unsupported use case blows up, so they then have to scramble to support it with a quick work around...for the workaround.
The workaround worked. I think at this point it makes me more likely to keep using Netlify. I love the product. And I think I love the support for unsupported un-recommended feature that they supported today.
Thanks Netlify Ops!
Re: Netlify Status – CDN Issues
#65Whom are they using? In 2021 for static sites behind a CDN being down is... odd. Pretty much all CDNs by now should support equivalent of serve stale.
think this is a DNS issue, not CDN. bobfunk noted it is Google, scroll up
So they implemented their own CDN-ish thing on top of GCP without doing anycast and serve stale and they have a non-trivial number non-mom and pop customers?!
Re: Netlify Status – CDN Issues
#66My 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 do you think?
- it seems like the multi cloud approach to CDN
- but at the same time I'll have a problem if this Load Balancer fails (single point of failure)
Re: Netlify Status – CDN Issues
#67Earlier 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.
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"!
Re: Netlify Status – CDN Issues
#68Earlier quoted context omitted.
"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.
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-g...
Re: Netlify Status – CDN Issues
#69Earlier quoted context omitted.
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.
I run the Netlify Support team, and this statement from @michaelmior is correct: apex domains are served using redundant, global CDN if you use Netlify's DNS hosting, or Flattened CNAMEs from Cloudflare.
Re: Netlify Status – CDN Issues
#70Shameless 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.
Cloudflare CTO telling off the open source project guy, while ignoring all the other comments suggesting cloudflare?