The pinging time is fast, but loading webs is lowly

I checking the ping time which is the fastest (the Asian line was fast, like Hong Kong line, Japan line, etc), but I can’t connect sometimes, or if line was connected loading the webs is lowly, even sometimes couldn’t loading.

BTW, If I connect the American line, like Miami, LA, Settle, just the problem which I talk about was figured out.

Can u tell me why? Anyone knows?

PS: am from China.

Hello,

I apologize but I am having a hard time understanding the issue you are experiencing. If my understanding is correct, then you are inquiring as to why you experience connection issues or issues loading websites when you are connected to one of our Asia VPN servers although the in-app ping times indicate fast ping times to those VPN server locations. Is my understanding correct?

Also, do you mean that you experience such issue when connecting to one of our Asia VPN servers but do not experience the issue when connecting to one of our United States VPN servers?

Thank you in advance for the clarification so that we can best address your concerns.

Samuel

Yeah, actually sometimes it’s difficult to load the Facebook or Twitter or the others when I connected the Asia VPN servers fast ping times (in-app ping); but there is no issue like that when I connecting to one of our United States VPN servers.

Hello @subem,

Thank you again for the clarification!

The in-app ping times are ping times to our VPN servers. Those ping times are irrelevant to what you should expect when loading websites. I would like to investigate your routing, network latency, and packet loss to Facebook’s website both when you are connected to our Hong Kong VPN server and to our Miami VPN server. Please connect to these servers and then run a ping test and traceroute to Facebook’s website.

Instructions for running a ping and traceroute in Windows and Mac:

----------WINDOWS OS------------------------

Please open the Command Prompt by pressing the Windows Key + “r” , then in the “Run” box that pops up, type in “cmd” (w/o the quotes) then press enter. Then the black window of the Command Prompt should pop up.

HOW TO RUN A PING TEST:
At the Command Prompt, type in :
ping -n 25 www.facebook.com

HOW TO RUN A TRACEROUTE:
At the command prompt, enter:
tracert www.facebook.com

-------------------------------Mac OS X---------------------------------------------

HOW TO RUN A PING TEST:
Open your Harddrive.
Open the Applications folder.
Open the Utilities folder.
Double click Terminal.
Then enter: ping -c 25 www.facebook.com

HOW TO RUN A TRACEROUTE:
Open your Harddrive.
Open the Applications folder.
Open the Utilities folder.
Double click Terminal.
Then enter: traceroute www.facebook.com

Thanks for providing this information so that we can investigate this concern further.

Samuel

Happy Friday,

I’m having a similar issue. I travel for my job, recently alot within china, and location does not seem to matter (within the last month, I have been to Chengdu [Telecom 100Mb/s fiber connection], Xi’an [Hotel unknown], Zhengzhou [12Mb/s cable connection], Shenzhen [Telecom 100Mb/s fiber connection], and my SIM card is from Yunnan.

Hong Kong always get the lowest ping, but load time are horrible. Below is the two tests request, however, i used US8 instead of USA miami, let me know if you need the other one.

Taipei also seems to have a similar issue but it’s a little better.

Also, these are using PPTP via Windows natively. The “VyprVPN client service” likes to constantly eat CPU time, even when i;m not using VyprVPN app, so i uninstalled it.

I have a home in ShenZhen, where all these results are from. I will be in japan next week and will test when there also.

Just as i was about to post this, my connection droppped to VPN :(disappointed: , so i connected to taiwan and added a thrid set of results

Really hope we can get this sorted out.

Thank you

US8

Pinging star-mini.c10r.facebook.com [31.13.73.36] with 32 bytes of data:
Reply from 31.13.73.36: bytes=32 time=294ms TTL=86
Reply from 31.13.73.36: bytes=32 time=513ms TTL=86
Reply from 31.13.73.36: bytes=32 time=267ms TTL=86
Reply from 31.13.73.36: bytes=32 time=338ms TTL=86
Reply from 31.13.73.36: bytes=32 time=558ms TTL=86
Reply from 31.13.73.36: bytes=32 time=375ms TTL=86
Reply from 31.13.73.36: bytes=32 time=257ms TTL=86
Reply from 31.13.73.36: bytes=32 time=297ms TTL=86
Reply from 31.13.73.36: bytes=32 time=517ms TTL=86
Reply from 31.13.73.36: bytes=32 time=297ms TTL=86
Reply from 31.13.73.36: bytes=32 time=340ms TTL=86
Reply from 31.13.73.36: bytes=32 time=560ms TTL=86
Reply from 31.13.73.36: bytes=32 time=256ms TTL=86
Reply from 31.13.73.36: bytes=32 time=256ms TTL=86
Reply from 31.13.73.36: bytes=32 time=298ms TTL=86
Reply from 31.13.73.36: bytes=32 time=517ms TTL=86
Reply from 31.13.73.36: bytes=32 time=430ms TTL=86
Reply from 31.13.73.36: bytes=32 time=343ms TTL=86
Reply from 31.13.73.36: bytes=32 time=563ms TTL=86
Reply from 31.13.73.36: bytes=32 time=477ms TTL=86
Reply from 31.13.73.36: bytes=32 time=302ms TTL=86
Reply from 31.13.73.36: bytes=32 time=300ms TTL=86
Reply from 31.13.73.36: bytes=32 time=518ms TTL=86
Reply from 31.13.73.36: bytes=32 time=433ms TTL=86
Reply from 31.13.73.36: bytes=32 time=345ms TTL=86

Ping statistics for 31.13.73.36:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 256ms, Maximum = 563ms, Average = 386ms

Tracing route to star-mini.c10r.facebook.com [31.13.73.36]
over a maximum of 30 hops:

1 185 ms 185 ms 186 ms 192.168.68.28
2 187 ms 186 ms 186 ms 192.168.64.2
3 187 ms 186 ms 185 ms gw2.sea.goldenfrog.com [209.99.94.3]
4 187 ms 189 ms 192 ms sea-b2-link.telia.net [213.248.88.17]
5 412 ms 305 ms 304 ms level3-ic-304311-sea-b1.c.telia.net [62.115.37.118]
6 * * * Request timed out.
7 276 ms 306 ms 255 ms 4.15.152.70
8 277 ms 304 ms 305 ms po102.psw01a.mia1.tfbnw.net [74.119.79.179]
9 547 ms 306 ms 305 ms msw1ac.01.mia1.tfbnw.net [173.252.65.215]
10 311 ms 304 ms 305 ms edge-star-mini-shv-01-mia1.facebook.com [31.13.73.36]

Trace complete.

~Hong Kong

Pinging star-mini.c10r.facebook.com [69.171.230.68] with 32 bytes of data:
Reply from 69.171.230.68: bytes=32 time=253ms TTL=76
Reply from 69.171.230.68: bytes=32 time=255ms TTL=76
Reply from 69.171.230.68: bytes=32 time=253ms TTL=76
Reply from 69.171.230.68: bytes=32 time=253ms TTL=76
Reply from 69.171.230.68: bytes=32 time=253ms TTL=76
Reply from 69.171.230.68: bytes=32 time=256ms TTL=76
Reply from 69.171.230.68: bytes=32 time=258ms TTL=76
Reply from 69.171.230.68: bytes=32 time=257ms TTL=76
Reply from 69.171.230.68: bytes=32 time=255ms TTL=76
Reply from 69.171.230.68: bytes=32 time=254ms TTL=76
Reply from 69.171.230.68: bytes=32 time=258ms TTL=76
Reply from 69.171.230.68: bytes=32 time=254ms TTL=76
Reply from 69.171.230.68: bytes=32 time=259ms TTL=76
Reply from 69.171.230.68: bytes=32 time=255ms TTL=76
Reply from 69.171.230.68: bytes=32 time=253ms TTL=76
Reply from 69.171.230.68: bytes=32 time=255ms TTL=76
Reply from 69.171.230.68: bytes=32 time=253ms TTL=76
Reply from 69.171.230.68: bytes=32 time=257ms TTL=76
Reply from 69.171.230.68: bytes=32 time=254ms TTL=76
Reply from 69.171.230.68: bytes=32 time=254ms TTL=76
Request timed out.
Reply from 69.171.230.68: bytes=32 time=254ms TTL=76
Reply from 69.171.230.68: bytes=32 time=256ms TTL=76
Reply from 69.171.230.68: bytes=32 time=253ms TTL=76
Reply from 69.171.230.68: bytes=32 time=255ms TTL=76

Ping statistics for 69.171.230.68:
Packets: Sent = 25, Received = 24, Lost = 1 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 253ms, Maximum = 259ms, Average = 254ms

Tracing route to star-mini.c10r.facebook.com [69.171.230.68]
over a maximum of 30 hops:

1 72 ms 72 ms 72 ms 192.168.35.25
2 72 ms 74 ms 74 ms 192.168.32.2
3 320 ms * 80 ms ge9-4.br01.hkg12.pccwbtn.net [63.218.175.21]
4 76 ms * 78 ms TenGE0-5-0-1.br04.hkg15.pccwbtn.net [63.223.15.186]
5 77 ms 88 ms 78 ms facebook2-lacp-10G.hkix.net [123.255.90.79]
6 75 ms 74 ms 78 ms ae4.bb02.hkg1.tfbnw.net [74.119.76.246]
7 255 ms 231 ms 230 ms ae9.bb01.hnd1.tfbnw.net [31.13.27.251]
8 229 ms 227 ms 228 ms be6.bb02.lax1.tfbnw.net [31.13.24.153]
9 246 ms 249 ms 253 ms ae7.bb03.prn2.tfbnw.net [31.13.24.3]
10 241 ms 262 ms 244 ms ae43.dr08.prn2.tfbnw.net [31.13.31.127]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 256 ms 254 ms 257 ms edge-star-mini-shv-17-prn1.facebook.com [69.171.230.68]

Taiwan

C:\WINDOWS\system32>ping -n 25 www.facebook.com

Pinging star-mini.c10r.facebook.com [69.171.230.68] with 32 bytes of data:
Reply from 69.171.230.68: bytes=32 time=245ms TTL=76
Reply from 69.171.230.68: bytes=32 time=245ms TTL=76
Reply from 69.171.230.68: bytes=32 time=245ms TTL=76
Request timed out.
Reply from 69.171.230.68: bytes=32 time=244ms TTL=76
Reply from 69.171.230.68: bytes=32 time=245ms TTL=76
Request timed out.
Reply from 69.171.230.68: bytes=32 time=246ms TTL=76
Reply from 69.171.230.68: bytes=32 time=246ms TTL=76
Reply from 69.171.230.68: bytes=32 time=245ms TTL=76
Reply from 69.171.230.68: bytes=32 time=244ms TTL=76
Request timed out.
Reply from 69.171.230.68: bytes=32 time=245ms TTL=76
Reply from 69.171.230.68: bytes=32 time=245ms TTL=76
Reply from 69.171.230.68: bytes=32 time=245ms TTL=76
Reply from 69.171.230.68: bytes=32 time=245ms TTL=76
Reply from 69.171.230.68: bytes=32 time=246ms TTL=76
Request timed out.
Reply from 69.171.230.68: bytes=32 time=245ms TTL=76
Reply from 69.171.230.68: bytes=32 time=245ms TTL=76
Reply from 69.171.230.68: bytes=32 time=244ms TTL=76
Reply from 69.171.230.68: bytes=32 time=245ms TTL=76
Reply from 69.171.230.68: bytes=32 time=244ms TTL=76
Reply from 69.171.230.68: bytes=32 time=245ms TTL=76
Reply from 69.171.230.68: bytes=32 time=245ms TTL=76

Ping statistics for 69.171.230.68:
Packets: Sent = 25, Received = 21, Lost = 4 (16% loss),
Approximate round trip times in milli-seconds:
Minimum = 244ms, Maximum = 246ms, Average = 244ms

C:\WINDOWS\system32>tracert www.facebook.com

Tracing route to star-mini.c10r.facebook.com [69.171.230.68]
over a maximum of 30 hops:

1 64 ms 64 ms * 192.168.35.21
2 65 ms 65 ms 65 ms 192.168.32.2
3 239 ms 243 ms 228 ms ge9-4.br01.hkg12.pccwbtn.net [63.218.175.21]
4 66 ms 66 ms 66 ms facebook1-lacp-10G.hkix.net [123.255.91.110]
5 68 ms 66 ms 67 ms ae0.bb02.hkg1.tfbnw.net [31.13.28.242]
6 221 ms 226 ms 221 ms ae9.bb01.hnd1.tfbnw.net [31.13.27.251]
7 217 ms 217 ms 216 ms be10.bb01.lax1.tfbnw.net [31.13.29.63]
8 * 246 ms 247 ms ae7.bb04.prn2.tfbnw.net [204.15.20.61]
9 245 ms 244 ms * ae3.dr12.prn1.tfbnw.net [31.13.28.73]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 245 ms 244 ms 244 ms edge-star-mini-shv-17-prn1.facebook.com [69.171.230.68]

Trace complete.

FYI, i couldn’t even post my previous post when connected to Hong Kong or Taiwan

@LinRui It looks like there may be some underlying network problems in your case. I reached out to you via an email ticket with some further tests. Please reply back to the ticket with the requested results and we will be glad to investigate further.

Thank you for helping out.

I have sent a reply with the tests requested, however, they don’t show much.

Please remember I am in china, and without VPN, i can not access goldenfrog.com, or vyprvpn.com.

cheers,