Cloudflare Analytics dropped to Zero, No Traffic is filtered by Cloudflare

What is the name of the domain?

What is the issue you’re encountering

No traffic is filtered through Cloudflare. Zero in Cloudflare Analytics and no filter of firewall is working past past 2 days. We are using GoDaddy WordPress hosting. Proxy of DNS record in Cloudflare is enabled. Everything was working completely fine but two days ago this issue appeared.

What steps have you taken to resolve the issue?

I have checked the DNA record. The IP address is correct, Proxy is also enabled.

Was the site working with SSL prior to adding it to Cloudflare?

Yes

What is the current SSL/TLS setting?

Full

Screenshot of the error

What A/AAAA/CNAME records have you set? Can you show a screenshot of the DNS records?

Use only “Full (strict)” or “Strict” to ensure your site is secured.

@sjr We are using “Full” only for the SSL for this website. We have not changed anything in DNS or SSL settings. We have been using Cloudflare on this website for more than 3 years without any issues. We have noticed the same issue for other websites (hosted on Godaddy) on Cloudflare for the past 2 days. We have double-checked the IP Address and other DNS settings; nothing changed, The IP address added is correct and the proxy is enabled.

Don’t. It’s not secure. Sort out SSL on your origin and use “Full (strict)”.

Can you give the IP addresses? Godaddy does use Cloudflare for some ranges so I asked for them as I wanted to see if anything has changed with the IP addresses you are using.

I have been using “Full” for the past 3 years for SSL and no issue ever happened due to that.

The IP address for one of the websites is 160.153.0.25 that is also facing the same issue from the past 2 days.

Based on that IP address and your account’s lack of analytics, it would appear that the traffic is going entirely through GoDaddy’s Cloudflare account. This request still goes through Cloudflare, and not a typical Cloudflare user account’s 104. or 172. (etc) IP address:

curl -svo /dev/null https://showbizhut.com/ --connect-to ::160.xx.xx.xx

Yes, this IP range is now being announced by Cloudflare.
https://radar.cloudflare.com/ip/160.153.0.25

It seems to be the same range that Cloudflare perhaps prematurely started treating as their own IPs a few weeks ago, then fixed. Now seems to be correctly announced…

1 Like

So is this happening because GoDaddy is using cloudflare as CDN?
What can we do now to fix it as we have implemented many firewall rules for different websites?

The issue of cloudflare treating IP as its own IP and giving 1000 error was resolved around 2 weeks ago and websites were working flawlessly till 28 August.

Although that issue occurred only to one of our websites not to website whose IP address we have mentioned above.

Yes, at that time the IPs were still on a Godaddy AS so that was an error. This is different as in the Radar link above.

So, @sjr should we contact GoDaddy for this issue or is it on Cloudflare’s end like the last time?
I guess something is wrong on Cloudflare’s side and it could be an account-level issue. All three websites in Cloudflare have the same issue (Configuration is correct, nothing changed recently).

We contacted the GoDaddy support team. They said this issue is on Cloudflare’s side. As GoDaddy is using Cloudflare as a CDN partner now, previously, Cloudflare started treating a few IPs of GoDaddy-hosted websites as their own, which was eventually fixed by the Cloudflare team.

Now this issue is also on Cloudflare’s side. We tried to contact the Cloudflare Support team and asked them to tell us at least what’s the reason for this issue. However, they did not even tell us whether this is an issue linked to our account, a backend issue of Cloudflare, or our hosting provider’s issue because we are using a free plan now.

**Although We have been using the PAID plan of Cloudflare for the past 3 years and downgraded just one month ago. We never expected this kind of behavior from their support.

We are totally stuck, Cloudflare is not working for any website in our account. Although the DNS record is correct, no changes made, it same as we have been using for 3 years. Seems like Cloudflare don’t want FREE users to use their services anymore now!

Cloudflare can’t just go an steal some provider’s IP addresses. Cloudflare and GoDaddy had to have had worked together to get it to this point. And it’s not front-line support from either side that was part of the process, which is why GoDaddy support points at the most obvious sign that it’s Cloudflare’s fault, not realizing it’s a joint effort between the two companies.

Unfortunately, GoDaddy customers are the ones who suffer. Because there is nothing wrong with your Cloudflare account, Cloudflare support can’t work with you. They’d have to kick it up the chain to get GoDaddy’s attention, which they did. You need to go back to GoDaddy support and ask them to kick it up the chain as well.

You could just as well say that it seems like GoDaddy doesn’t want PAYING users to use their services any more now.

Yes you are right and we agree with your point of view.

But Cloudflare support even did not tell us that there is no issue with our Cloudflare account and it’s an issue on GoDaddy’s end. All they replied to our email was, FREE customer can only can get support help regarding billing etc. And told us to share our problem in Cloudflare community.

We just wanted their confirmation that its not our Cloudflare account related issue, never demanded solution for this as an unpaid customer.

We hope this issue of GoDaddy with Cloudflare would be resolved soon as we are fan of Cloudflare and always appreciated its services and also want to continue using them in future.

1 Like