Well I didn’t actually change anything in Cloudflare. I had the nameservers at IONOS (where the domain was purchased) pointing to Cloudflare, so I just updated this to point directly to Netlify nameservers instead.
I didn’t need to change anything at either Cloudflare or Netlify.
So what did you do? I’m confused. Did you delete it off cloud flare?
I haven’t, but I will eventually as it isn’t doing anything at the moment, since I changed the nameservers to Netlify at the domain registrar.
So when I load my site I can see in the browser network tab that the request is going to Netlify server rather than Cloudflare.
I’m kinda hoping that it’s an issue that gets resolved, and then I will point the domain back to Cloudflare nameservers.
Your setup could be different to mine, perhaps you have configured the DNS records individually rather than nameserver, or maybe an entirely different setup 
Hi, @rbatista191 , @Josephadam, @webdigga, @of-dev (and anyone else here). We are not aware of any changes made at Netlify to cause this and the vast majority of traffic proxying to Netlify via Cloudflare continues to do so without error.
To be clear, 99% of sites proxying to Netlify via Cloudflare continue to work correctly without any 522 status responses. Most sites using Cloudflare to point to Netlify continue to work normally.
What we would recommend here is this:
We at Netlify cannot see what is happening on Cloudflare’s side of this. We see the traffic stopped but we are not the ones blocking it. If we block traffic, we still log the blocked traffic noting it was blocked. That is not happening here. In this case, the logs just stop completely for the sites reported. Nothing hits Netlify at all.
Based on this, the only explanation that seems likely is that something at Cloudflare is the cause and, if so, Cloudflare technical support will be the only people that can find the root cause. No one at Netlify can debug the internals of Cloudflare and that is what is required here.
Hey @luke, thanks for your answer. I have contacted Cloudflare and they are throwing the ball to your court. Is there any change Netlify can take this with Cloudflare on behalf of their customers? There are several of us affected.
My next move is to move away from Netlify, as I cannot wait much longer with the website down and constant redirect fixes.
I also posted in cloud flare forums and they’re saying the same.
I posted on cloud flare forums and they are saying same as you thats it on your side. So this is going to be a constant circle.
Have you tried pausing Cloudflare or enabling Development Mode on your site(s) @Josephadam?
Where did they say that?
Looking at this thread of yours:
https://community.cloudflare.com/t/website-connected-to-netlify-isnt-loading-im-getting-a-522-error/731087
And this post:
https://community.cloudflare.com/t/522-error-domain-is-down-tried-troubleshooting-but-still-facing-issues/731045/2
All I can see are responses from a volunteer that has advised much the same as the general recommendation on Netlify’s side, which is to disable the proxy.
Is there some other thread?
I have not. How do you do that? I know it works when I use netlify domain instead.
I meant to say “what if they say the same as you” because I don’t want to go in circles.
Also @rbatista191 just said that cloudflare replied to him and said it’s in netlify court.
Click the links in @expired’s post, they are to the Cloudflare documentation for how you do it.
I’ve not seen the message that @rbatista191 is referring to, presumably it was a private communication, but if Cloudflare have said that, then it does seem to be a loop at the moment.
The Cloudflare volunteer that you spoke with said:
However, as described in the article from another forum, proxy CDN to CDN cannot work.
It’s a known issue such as Shopify, etc.
Keep it unproxied (DNS-only).
Hi all i am also now facing this issue, no DNS changes have been made and the site just went down. Definitely not with the approach of migrating away from Cloud flare… Any news as of yet? https://reward-space.co.uk/
I presume you read Netlify Support’s message above?
https://answers.netlify.com/t/sites-down-awaiting-netlify-dns/128555/24
Hey folks, we’re sorry you’re running into trouble. Be assured that folks on our engineering team are looking into this.
We haven’t been able to isolate this problem yet and it seems to only occur for a minority of customers proxying to us from Cloudflare.
My best recommendation for you at this time: If you can, turn off “proxying” in Cloudflare (the orange cloud icon in DNS config) and use the Netlify CDN directly. This is the configuration most likely to work and if there are problems, it’s a lot easier for us to debug without the Cloudflare proxy layer. In order for this to work completely you might need to refresh your Letsencrypt certificate on your Netlify site after making that change.
Please also double-check your DNS config in general. Make sure you have setup a CNAME record to <your-site>.netlify.app in your DNS. Refer to our docs for more details.
Something that would really help us in debugging this: Could you please post a screenshot of your Cloudflare config either to this thread or in a DM to me? We’re mostly interested in the DNS parts which show how you told Cloudflare to reach Netlify.
If any of you have the ability to get any debug logs out of your Cloudflare interface those can also be really helpful. We’re mostly looking for which IP addresses Cloudflare is trying to proxy to on our side.
These posts on the Cloudflare forums within the same timeframe, from a user hosting with AWS may be of interest:
I can see evidence that cloudflare is trying to connect to an origin server, but I can’t see any evidence (e.g. in AWS vpc logs) that cloudflare is trying to connect to our origin server.
I have done absolutely everything I can to eliminate a configuraton error on my part but simply cannot find any evidence whatsoever that Cloudflare is attempting to connect the origin server on either of the correct addresses. Connecting via DNS (with proxy switched off) works flawlessly but as soon as the Cloudflare proxy is switched on, Cloudflare attempts to connect to something (not my origin server) and times out.
I have been experiencing the same problem with my website. In my case, after investigating a little, I realized that the servers associated with my website have not been responding. In my case, they are these:
dns1.p07.nsone.net
dns2.p07.nsone.net
dns3.p07.nsone.net
dns4.p07.nsone.net
@ciro-mota this sounds like a different issue, could you let us know the name of the site?
Hey @marcus, here is my screenshot:
