Tracert from hong kong gets routed to singapore?

I Set up Cloudflare for the Hong Kong CDN (where our application is hosted). Response times seem longer with Cloudflare 900ms vs 600ms ( i know this is okay for the first 4 - 6 hours) but a tracert is showing it bypassing hong kong and onward to Singapore.

Below is the trace removing the first two. It should have stopped at 8 in Cloudflare hong kong service, but it continued to Singapore, any reasons why?

 2     4 ms     3 ms     2 ms  n119237145253.netvigator.com [119.237.145.253]
  3     4 ms     3 ms     3 ms  10.193.232.21
  4     4 ms     4 ms     3 ms  wtsc3a058.netvigator.com [218.102.40.58]
  5     3 ms     5 ms     5 ms  ten0-3-0-0.br04.hkg05.pccwbtn.net [63.218.56.185]
  6    11 ms    10 ms     9 ms  HundredGE0-3-0-0.br02.hkg08.pccwbtn.net [63.223.29.194]
  7    18 ms    20 ms    20 ms  63.218.205.154
  8    20 ms    20 ms    20 ms  ae-11.r24.tkokhk01.hk.bb.gin.ntt.net [129.250.6.99]
  9    41 ms    41 ms    41 ms  ae-6.r20.sngpsi07.sg.bb.gin.ntt.net [129.250.7.66]
 10    55 ms    56 ms    53 ms  ae-1.r01.sngpsi07.sg.bb.gin.ntt.net [129.250.3.100]
 11    54 ms    56 ms    55 ms  ae-1.a01.sngpsi07.sg.bb.gin.ntt.net [129.250.2.240]
 12    42 ms    40 ms    40 ms  ae-0.Cloudflare.sngpsi07.sg.bb.gin.ntt.net [116.51.17.86]
 13    42 ms    41 ms    41 ms  104.31.79.21

It’s most likely plan dependent. On low tier plans (free in particular) they will drop some sites on some high traffic locations for some amounts of time to not disrupt paying (or higher paying) customers. That’s to be expected. It will resolve itself in a while or not depending on the network conditions at HK.

matteo, that is positive news, atleast i know its not broken… on the other hand its a bit sad, as i imagine the free plan is also for non development users to test Cloudflare cdn. I plan to retest this over the next few days.

i also searched for documentation to check if this was the case but nothing can be found if indeed low tier plans will drop some locations…

i imagine Singapore be higher traffic than hong kong. Thanks for your help.

Yeah, but there is no SLA for Free and Pro accounts. Also this can be due to ISP peering policies (I for example don’t always go to the closest datacenter myself).

It is relative load: if one location has 100Gbps and uses 95 it’s at an higher load than one with 10Gbps using 1.

It sems to me that only the final destination is maintained by Cloudflare, all other hops are internet hubs (phone, cable companies etc). So if your ISP routes their traffic via Singapore, the best CDN available would be the one in Singapore. (You can test using example.com/cdn-cgi/trace)

From my home in Brazil, the phone company that provides me internet service routes traffic via Spain, and from Spain, then back to the US (don’t ask me why :), where requests to my websites are most often served by EWR, IAD, MIA, all US locations, instead of GRU or RIO, their locations in Brazil.

1 Like

That is a nice utility, i ran it on my subdomain which is routed via cf, and here are the results, i am not sure how parse this information?

fl=71f335
h=b2.sinosend.com
ip=116.49.190.204
ts=1544585073.85
visit_scheme=http
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.80 Safari/537.36
colo=FRA
http=http/1.1
loc=HK
tls=off
sni=off

tracert still shows final destination is in Singapore. As a test for kicks, i singed up with NETLIFY, i pinged the sample domain and it was 2ms , tracert shows Hong Kong! pretty amazing…

With Cloudflare i am getting 200ms (sad face) will keep trying.

Thanks
Rishi

The colo=FRA line says your request was served out of FRA (Frankfurt, Germany). Why would CF fetch your response from a CDN so far away from HK and SG, I don’t know, but it may have to do with the ISP peering policies @matteo referred to. You can try to run that same utility with 4G to see which datacenter will respond.

Also, you may want to run online tests such as GTMetrix for your website. On a GTMetrix report, in any page’s waterfall chart, when you click on the first asset (the html), you will see from which datacenter CF is serving their cached assets, identified by the three last letters under header cf-ray. This way you will have a better notion of what users in general are getting, without the ISP peering bias.

1 Like

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