Two Websites on Cloudflare with two different Pings

Hi Cloudflare community,

I recently came across something interesting and was hoping to get some more insights about the issue.

I have two websites that are hosted on the same server and served through Cloudflare. When I ping the two domains, the ping times for the first one are about 70-80ms while the ping times for the second are 300-400ms. Any idea why that would be.

Both websites have a lot of similarities.

  • Both are .com domains
  • Both are hosted on the same Digital Ocean server in NYC3 (that I manage)
  • Both are WordPress websites
  • Both are running the same caching system
  • Both are orange-clouded
  • Both have the same config in Cloudflare
  • Both DO NOT have Argo enabled.

For this test, I am accessing them from my home in Mumbai, India.

Yet, domain1.com appears to load very fast in the browser and has 70-80ms of ping times in Terminal while domain2.com appears to be slower and has 300-400ms of ping times in the Terminal.

I ran the traceroute on both the domains and saw the following difference.

Can someone help me understand why this is the case? I understand it’s hitting two different Cloudflare IPs, but I’m accessing them from the same location, shouldn’t they give me same results?

Thank you.

One question before giving guesses, can you try the /cdn-cgi/trace path for both domains and posting back here the contents?

Ah, good call. Here are the results.

fl=35f349
h=domain1.com
ip=49.36.3.208
ts=1588444375.591
visit_scheme=https
uag=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1 Safari/605.1.15
colo=SIN
http=http/2
loc=IN
tls=TLSv1.3
sni=plaintext
warp=off

And…

fl=17f200
h=domain2.com
ip=49.36.3.208
ts=1588444388.169
visit_scheme=https
uag=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_4) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1 Safari/605.1.15
colo=MIA
http=http/2
loc=IN
tls=TLSv1.3
sni=plaintext
warp=off

They are both in the same plan, correct?

Two options, if the above is true (and if it isn’t, but with different chances each):

  1. Cloudflare for some reason decided to not advertise the domain in Mumbai, forcing you to go to Singapore. This may be for various reasons (traffic usage, chance, etc.), it may also change in time if some of those constraints are gone. You could ask support for a check, but it may be impossibile to be moved. Asking may not hurt.
  2. Your ISP decided to split the routing to Cloudflare’s POP for similar reasons as above. This may also change and it’s harder to fix. To test this though you can easily just test from a different ISP (friend, office, mobile phone, whatever). If that fixes it then 1. is not true and this is the case. You can try contacting your ISP to fix the routing and/or Cloudflare support to change IP, but you are not likely to succeed unfortunately.

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