High Latency

#1

Dear All

I have setup FREE CDN for our test domain https://kapsonsretail.com and was hoping to get some better latency.However,I am getting high latency of around 150 to 200 ms.

Is that Normal ? CDN has been setup correctly.

Any inputs would be welcome.
Thanks

#2

A latency of what? How did you measure this?

Post the output of https://kapsonsretail.com/cdn-cgi/trace

#3

Hi sandro
I am getting a high latency to our site when i ping it from our location.This is the response that i get from the trace URL

fl=202f47
h=www.kapsonsretail.com
ip=103.36.77.33
ts=1584015938.86
visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36
colo=BOM
http=http/2
loc=IN
tls=TLSv1.3
sni=plaintext
warp=off

#4

Can you post the output of these commands?

ping kapsonsretail.com
tracert kapsonsretail.com
#5

Pinging kapsonsretail.com [68.66.213.11] with 32 bytes of data:
Reply from 68.66.213.11: bytes=32 time=300ms TTL=47
Reply from 68.66.213.11: bytes=32 time=302ms TTL=47
Reply from 68.66.213.11: bytes=32 time=305ms TTL=47
Reply from 68.66.213.11: bytes=32 time=299ms TTL=47
Reply from 68.66.213.11: bytes=32 time=300ms TTL=47
Reply from 68.66.213.11: bytes=32 time=302ms TTL=47
Reply from 68.66.213.11: bytes=32 time=305ms TTL=47
Reply from 68.66.213.11: bytes=32 time=299ms TTL=47

C:>tracert kapsonsretail.com

Tracing route to kapsonsretail.com [68.66.213.11]
over a maximum of 30 hops:

1 3 ms 5 ms 7 ms 192.168.0.1
2 9 ms 9 ms 9 ms 103.36.76.30.wowsolutions.in [103.36.76.30]
3 * * * Request timed out.
4 37 ms 38 ms 40 ms 103.47.157.29.wowsolutions.in [103.47.157.29]
5 53 ms 41 ms 43 ms 182.74.6.109
6 164 ms 163 ms 165 ms 116.119.44.248
7 165 ms 168 ms 173 ms 213.242.116.165
8 293 ms 280 ms 287 ms 4.69.151.134
9 300 ms 298 ms 307 ms A2-HOSTING.bar2.Detroit1.Level3.net [4.31.124.142]
10 307 ms 301 ms 302 ms 75.98.175.255.static.a2webhosting.com [75.98.175.255]
11 306 ms 305 ms 297 ms 68.66.213.11.static.a2webhosting.com [68.66.213.11]

Trace complete.

#6

Ehm, that output from before was a different one then, than what I asked. You posted the ā€œwwwā€ host instead.

Apparently you still have a DNS propagation issue and connect straight to your server for your naked domain. Probably best to wait or try to force a resolver update.

1 Like
#7

I get a 404 error if i try https://kapsonsretail.com/cdn-cgi/trace

Where should i check ?.CF DNS has all the records i need and it says the site is ā€˜activeā€™. Am i missing a record ? I can post the DNS output from CF here if thatā€™s ok.

#8

That is because you are going straight to your server.

This is not Cloudflare or Cloudflare DNS related, your local DNS server simply returns the old value. You best wait until the right value is returned or try to force an update, but that depends on your network and you best consult Google on how to do that (-> ā€œflushing DNS cacheā€ and so on)

#9

All the ā€˜Aā€™ records have the orange cloud with the Proxied status.ā€˜Aā€™ record points to our hosting provider where the site is actually hosted.What am I missingā€¦

Thanks for your help Sandro.

#10

See my earlier response.

#11

Can you check if you are getting a different response than myself.Tracert and all.I have 2-3 ISPā€™s here.I can check with everyone.

#12

Nothing to do with a response. As I said twice already, you simply connect directly to your server. Just wait a few hours and the issue should fix itself.

1 Like
#13

ok.I will wait it out.Thanks for your help Sandro.Appreciate it.