oof, I got bit by this issue this morning. if you're using cloudflare, set your domain's apex (`@`) as a CNAME pointing to the default subdomain (sitename.netlify.app) and use CNAME Flattening. It's the A record pointing to the CDN IP address that's broken.
Netlify Status – CDN Issues
21–30 of 90 posts
Re: Netlify Status – CDN Issues
#22This 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…
You should checkout Cloudflare Pages. For static stuff it’s a dream to setup, and you get previews out of the box.
Cloudflare pages is in beta and right now lacks many features that Netlify has, while also containing some showstopping issues (https://developers.cloudflare.com/pages/platform/known-issue...)
Re: Netlify Status – CDN Issues
#23This 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…
Why wouldn't CloudFront be quite as quick, out of interest?
Re: Netlify Status – CDN Issues
#24Re: Netlify Status – CDN Issues
#25This 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…
Why wouldn't CloudFront be quite as quick, out of interest?
I think they're talking about the setup/configuration time. Netlify is pretty much one click.
Re: Netlify Status – CDN Issues
#26Shameless 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.
Re: Netlify Status – CDN Issues
#27This hit me, as someone using A records to point to the Netlify IPs. If you are using GitHub, I found switching over to Github pages quite easy for my static site. I used this guide: https://docs.github.com/en/github/working-with-github-pages/...
Re: Netlify Status – CDN Issues
#28Netlify 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/
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.
Re: Netlify Status – CDN Issues
#29Update 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] now includes the same IP.
[0] https://www.netlifystatus.com/
[1] https://docs.netlify.com/domains-https/custom-domains/config...
Re: Netlify Status – CDN Issues
#30This 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.
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.