Network Pool advertisement on Cloudflare routing from SG colocation instead of KHI

What is the name of the domain?

What is the error number?

latency

What is the error message?

latency

What is the issue you’re encountering

Traffic is routing from international colocation instead of local colocation.

Cloudflare advertises its IP addresses from every data centre using Anycast. The route your requests take to Cloudflare is determined by your ISP’s peering and routing arrangements so ask them to improve their routes to Cloudflare.

Hi
Thanks for your response, Cloudflare may advertise their IPs from anywhere, but for customer network it should be advertise as per the requirement. Our clients are here in PAK and we do not want our networks to be advertised from SG or any other international location, we only want those routes to be advertise from KHI, ISB, LHR colocations.

Cloudflare has no control over how your own network routes are announced or how they are routed, that is down to your ISP.

Requests will be received from clients at the Cloudflare colo that their ISP routes them to (hopefully the closest to them, but as I said that’s down to the ISP), and origin requests will go from there to your origin.

If traffic is re-routed from a colo due to maintenance or other issues, routes may get longer again depending on ISP routing.

The only way to restrict location use is to limit the data encryption and storage points using the Data Localisation Suite which requires an Enterprise plan.

How is it possible the APNIC pool which we gave and authorize Cloudflare to advertise and Cloudflare (enterprise plan) has no control over its customize its advertisement configuration as per customer needs?

Obviously ISP will receive routes which it consider best, but if those routes are from SG instead of KHI then ISP will route traffic of local PAK user to SG and request to application hosted in PAK will be routed to SG causing unnecessary extra delays and latency.

You didn’t mention you were using Cloudflare with BYOIP, you merely gave a domain so I assumed you were talking about connections to your website.

BYOIP announces all your IPs from every Cloudflare location, that’s the point of using it…

That brings caching close to users globally and allows the spread of attack traffic across data centres near the attack source, not your origin. If you wanted your IPs advertised only in Pakistan, I’m not sure why you’d use Cloudflare.

Whether they are your own IPs, or Cloudflare’s, the route taken to get to them will be determined by the ISP.

Yes, it’s called tromboning…

Cloudflare (unless a colo is rerouted) is announcing your IPs from every location. If an ISP in Pakistan doesn’t route to a Cloudflare colo in Pakistan, but opts for a cheaper or less congested route for them, then Cloudflare can’t do anything about that.

One of the 3 data centres in Pakistan is currently re-routed, another partically re-routed so again depending on ISP peering, that may be affecting things.

If your IPs weren’t announced out of Singapore, routes could be even longer as your ISP takes another cheap route. With an Enterprise plan, your traffic has highest priority within Cloudflare.

You have an Enterprise plan so talk to your CSM to see if a custom solution is possible for you.

1 Like

Thanks for detailed response. So you mean it is possible to customize route advertisement of our IP pools and we can restrict advertisement from only local colos so that ISPs learn those routes from colos we want. And we can stop advertisement from SG or other international Colocations…
Cloudlflare has three colocations in Pakistan, from where we can get caching optimizing and other features.
By the way, how it is configured on colo to advertise? There must be some route parameters such as priority, preference, AD etc. that can be attached with routes so that ISP can always give preference to routes what we have set.

I don’t know, I suspect not since if your IP addresses were attacked, all traffic would end up at just a few colos and that is not the way Cloudflare is designed to work. You are better to push the local ISPs to peer directly with Cloudflare.

Can we customize route preference different on different colocations? E.g high preference set on local colos and low preference set on international colos.

You should contact your account team. The community is volunteers primarily. They don’t have access to or understanding of Cloudflare routing particulars.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.