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.