RIPE IP Range Issues after announcing on a new provider

[tom35]

Hello,

We are an ISP that recently moved some of our RIPE IPs from our old provider to our new provider.
However having done that, suddenly there’s quite a few websites we’ve found that are now flagging as access denied.

The range worked perfectly fine beforehand, the only changes were that we’ve moved from the old provider to the new provider.

I’m assuming we’ve been flagged as a datacentre range by Cloudflare rather than an ISP / Residential range. We’ve proved its not the underlaying range that our IPs that proceeds our IPs as they seem to be fine. We’ve been advised that the sites we are having issues with are backed by Cloudflare, however as we aren’t on a paid plan (or had an account before today) I don’t seem to be allowed to speak to support directly as I’m not on a paid plan.

Does anyone know the process for flagging to Cloudflare that our IPs are an ISP range?

All the best,
Tom

[yuri1]

Hi there,
We are sorry to hear the issue you are experiencing.

We are an ISP that recently moved some of our RIPE IPs from our old provider to our new provider.
However having done that, suddenly there’s quite a few websites we’ve found that are now flagging as access denied.

Can you share the screenshot of the error message?
Also, what is the zone?

[tom35]

Hello,

Sadly the errors differ depending on the site but an example is (other sites are similar or just “Access Denied” on a custom page):

We are in the UK if that helps with the zone?

All the best,
Tom

[cscharff]

That site appears to be using Akamai, not Cloudflare.

dig tui.co.uk +short
23.220.144.151
23.220.144.140

If you have access to peeringdb.com you can use that login to connect to peering.cloudflare.com and there may be a way to confirm your routing looks correct at least.