Why I do not hit BD/DAC data center?

Website, Application, Performance
1

I am located in Dhaka, Bangladesh.

I have several sites on CF Free plan. When accessing my sites from my location, I do not hit the DAC/BD data center.

For example with cdn-cgi/trace:

fl=35f961
h=domaindokan . com
ip=103.106.236.xx
ts=1661020160.84
visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:103.0) Gecko/20100101 Firefox/103.0
colo=SIN
sliver=none
http=http/2
loc=BD
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
kex=X25519

fl=453f38
h=easyearnbd . com
ip=103.106.236.xx
ts=1661021075.571
visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:103.0) Gecko/20100101 Firefox/103.0
colo=BOM
sliver=none
http=http/3
loc=BD
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
kex=X25519

fl=376f291
h=eknojore . com
ip=103.106.236.xx
ts=1661021821.131
visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:103.0) Gecko/20100101 Firefox/103.0
colo=LHR
sliver=none
http=http/3
loc=BD
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
kex=X25519

I have one domain where I am using CF Access on one subdomain. For that subdomain and other subdomains on that domain (not using CF Access with them) I get routed far away.

fl=533f66
h=ads . felinetech . net
ip=103.106.236.xx
ts=1661022001.977
visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:103.0) Gecko/20100101 Firefox/103.0
colo=CDG
sliver=none
http=http/2
loc=BD
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
kex=X25519

For Cloudflare, sometimes I am hitting DAC and sometimes SIN
fl=35f1007
h=Cloudflare . com
ip=103.106.236.xx
ts=1661022111.404
visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:103.0) Gecko/20100101 Firefox/103.0
colo=SIN
sliver=none
http=http/3
loc=BD
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
kex=X25519

fl=362f6
h=community . Cloudflare . com
ip=103.106.236.xx
ts=1661020204.513
visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:103.0) Gecko/20100101 Firefox/103.0
colo=DAC
sliver=none
http=http/3
loc=BD
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
kex=X25519

For medium

fl=362f2
h=medium . com
ip=103.106.236.xx
ts=1661022092.1
visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:103.0) Gecko/20100101 Firefox/103.0
colo=DAC
sliver=none
http=http/3
loc=BD
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
kex=X25519

What can I do to ensure visitors to my sites from Bangladesh gets routed to DAC/BD data center?

2

Greetings,

Thank you for asking.

Cloudflare is an anycast network and has many servers around the World, meaning the network/web traffic would go through the closest possible and fastest available Cloudflare Edge point (datacenter) to the website visitor (you) to serve the web content.

Regarding checking through which Cloudflare colocation you are connecting and being routed while visiting some website on the Cloudflare network, or your own, there is a simple way to check this as you’ve already did by using /cdn-cgi/trace/.

Furthermore, it might depend a bit which plan you’re using, Free or some higher paid plan, therefore the better routes/DCs might be selected and being prioritized for the delivery.

I believe Cloudflare is choosing it’s route based on a multiple different factors.

It could happen that our network traffic is being differently routed, but that could depend on the peering of our local ISP provider. More about it in the article from below:

1 Like
3

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