Very slow from Hong Kong this few days

#1

Hi Guys,

My Hong Kong Server using CF and very fast but this few days very slow, I have 2 domains using same CF DNS and point to same origin Hong Kong server, but the speed are quite different, following is my tracert result:

Slow [104.24.111.43]

Tracing route to slowone.com [104.24.111.43]
over a maximum of 30 hops:

  1    17 ms    15 ms    15 ms  ***
  2    13 ms    14 ms    31 ms  10.30.28.9
  3    14 ms    14 ms    15 ms  10.28.21.25
  4    14 ms    13 ms    13 ms  218.188.28.69
  5     *        *        *     Request timed out.
  6    33 ms    30 ms    14 ms  203.131.243.121
  7    15 ms    15 ms    14 ms  ae-1.r24.tkokhk01.hk.bb.gin.ntt.net [129.250.2.114]
  8    60 ms    60 ms    60 ms  ae-18.r30.tokyjp05.jp.bb.gin.ntt.net [129.250.2.96]
  9   179 ms   179 ms   179 ms  ae-4.r23.snjsca04.us.bb.gin.ntt.net [129.250.5.78]
 10   168 ms   168 ms   168 ms  ae-45.r01.snjsca04.us.bb.gin.ntt.net [129.250.3.175]
 11   174 ms   174 ms   198 ms  ae-0.cloudflare.snjsca04.us.bb.gin.ntt.net [131.103.117.82]
 12   176 ms   175 ms   175 ms  104.24.111.43

Trace complete.

Fast [104.28.31.209]

Tracing route to fastone.com [104.28.31.209]
over a maximum of 30 hops:

  1    15 ms    29 ms    15 ms  ***
  2    15 ms    23 ms    15 ms  10.30.28.9
  3    15 ms    14 ms    14 ms  10.28.21.25
  4    13 ms    14 ms    14 ms  218.188.28.89
  5    14 ms    14 ms    14 ms  218.188.28.85
  6     *        *        *     Request timed out.
  7    14 ms    15 ms    16 ms  202.84.153.149
  8    15 ms    15 ms    15 ms  202.84.156.54
  9    14 ms    14 ms    14 ms  unknown.telstraglobal.net [210.57.81.22]
 10    13 ms    13 ms    13 ms  104.28.31.209

Trace complete.

Any one know why? it’s Cloudflare or ISP issue? and how to improve/fix that?

Thanks a lot!

0 Likes

#2

That is a routing issue which you can possibly trace back to your ISP.

Are these two domains on different Cloudflare plans?

0 Likes

#3

The same free plan. So in this case, it’s ISP issue no cloudflare?

0 Likes

#4

Primarily it likely is an ISP issue. There is some chance that Cloudflare might be announcing something incorrectly, but you could clarify this only with support.

@cloonan @cscharff, anything known in this regard?

0 Likes

#5

Nothing offhand and I don’t see issues, but @DDdev please share the ticket number and I’ll see what the engineers say.

0 Likes

#6

The support ticket number is 1672397, thanks so much.

1 Like

#7

Thank you @DDdev, I see the ticket and added a link to this thread. Good analysis from the engineer, let us know if it’s helpful in troubleshooting.

0 Likes

#8

Hi cloonan, good analysis but misunderstanding my question, support still test on webpagetest.org and analysis my whole site resource, but I face a problem is the first server request, it’s not about other resource.

0 Likes

#9

Other than @sandro’s comment, there’s not much help we can offer without more information.

What are the results from this test:
http://www.example.com/cdn-cgi/trace (but use https if you’ve got it, and change the domain name)

0 Likes

#10

Thanks @sandro, here is the result:

slow domain (using same plan, same DNS, same server ip)

fl=4f88
h=slowone.com
ip=***
ts=1555550279.195
visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36
colo=SJC
http=http/2
loc=HK
tls=TLSv1.3
sni=plaintext
warp=off

fast domain (using same plan, same DNS, same server ip)

fl=23f236
h=fastone.com
ip=***
ts=1555550277.156
visit_scheme=https
uag=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36
colo=HKG
http=http/2
loc=HK
tls=TLSv1.3
sni=plaintext
warp=off

The result show the slow server colo is SJC, routed to San Jose, CA, United States - (SJC).

So it’s a CF routeing issue?

Thanks a lot!

0 Likes

#11

Cloudflare doesn’t control your ISP’s routing. It looks like you’re doing this from a desktop computer going through your ISP. Can you try that same trace url from your cellphone using the cellular network? Let us know which colo they hit.

Regardless, this doesn’t explain why one free plan is different from the other free plan.

Maybe @cloonan can push things in the right direction to figure out why one free plan hits San Jose, but the other hits Hong Kong.

0 Likes

#12

@sdayman, I using cellphone cellular network but the colo still SJC

0 Likes

#13

Could you see what you get for the different plans on https://cloudflare-test.judge.sh/ ?

4 Likes

#14

Thanks @Judge, here is the result:

Slow one

Fast one

0 Likes

#15

Today the colo changed to KIX (Japan), it’s better but still not HKG.

Cloudflare will not always be served by the closest geographic colo, unless you upgrade the plan (This info is come from official support, I still asking which plan)

Anyway, it’s free plan, fair enough, but everyone need a plan B, who know when the colo routed to SJC again…

0 Likes

#16

(sorry for the late reply) Unfortunately, this is the case, Cloudflare will prioritize their Enterprise and (usually) Business customers while sending free plan websites to less congested datacenters depending on the circumstances. As per the DC test, it’s not a blanket statement so there are probably a lot of factors at play when Cloudflare chooses which IP (and which datacenters) browsers should contact.

2 Likes