Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Advertise on LowEndTalk.com
Question about a ping issue
New on LowEndTalk? Please Register and read our Community Rules.

Question about a ping issue

I am in Hong Kong, ping speed to HostHatch Hong Kong node is quite fast:

$ ping hk.myhostnames.com
PING hk.myhostnames.com (103.73.67.135): 56 data bytes
64 bytes from 103.73.67.135: icmp_seq=0 ttl=52 time=17.989 ms
64 bytes from 103.73.67.135: icmp_seq=1 ttl=52 time=26.519 ms
64 bytes from 103.73.67.135: icmp_seq=2 ttl=52 time=25.339 ms
64 bytes from 103.73.67.135: icmp_seq=3 ttl=52 time=25.782 ms

But my friend from Guangdong Telecom which is close to Hong Kong from geo location, his ping is quite slow and package losing:

PING hk.myhostnames.com (103.73.67.135): 56 data bytes
64 bytes from 103.73.67.135: icmp_seq=0 ttl=46 time=403.000 ms
64 bytes from 103.73.67.135: icmp_seq=1 ttl=46 time=404.126 ms
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
64 bytes from 103.73.67.135: icmp_seq=4 ttl=46 time=410.121 ms

Can you help explain this? thank you.

Free secure email: https://tls-mail.com/

Comments

  • Have you ever done an MTR/traceroute to the destination address?

  • Besttrace from ipip.net can help you.
    https://cdn.ipip.net/17mon/besttrace.exe

  • DataIdeas-JoshDataIdeas-Josh Member, Provider

    @jpeng do a
    traceroute hk.myhostnames.com

    Thanked by 1jpeng

    Alien Data: VPS and Colo Based In Texas, Unmetered Bandwidth.
    RPIServers: Dedicated Micro Servers. Unmeterd Bandwidth

  • rubenruben Member, Provider

    As others said, do an MTR or traceroute and you will know more.

    A high ping can have multiple reasons, one is just physical - one cant increase the speed of light, another possibility is congestion on the line, which I guess will be the cause here when connecting from mainland to HK - which would also explain the packetloss.
    And dont forget that a packet has to travel back too, so you will want to run MTRs from the VPS to the Enduser and from the Enduser to the VPS.

    Thanked by 2jpeng Clouvider

    iFog GmbH - Anycast DNS & CDN; vServer in DE, UK, US, NO, CH, ES, JP, SG; IP-Transit, IXP VMs, RIPE LIR, BGP VMs
    Tunnelbroker - Free BGP v6/v4 Tunnels

  • NDTNNDTN Member, Provider

    Might be direct bandwidth to China issue? It can be Guangdong -> USA -> Hong Kong, which increased the latency.

  • DataIdeas-JoshDataIdeas-Josh Member, Provider

    Heres what I am getting from Texas.

    Tracing route to hk.myhostnames.com [103.73.67.135]
    over a maximum of 30 hops:

    6 58 ms 45 ms 50 ms te0-2-1-12.rcr51.iah04.atlas.cogentco.com [154.24.14.185]
    7 52 ms 57 ms 57 ms be2991.ccr41.iah01.atlas.cogentco.com [154.54.7.85]
    8 70 ms 58 ms 62 ms be2927.ccr21.elp01.atlas.cogentco.com [154.54.29.222]
    9 81 ms 78 ms 65 ms be2930.ccr32.phx01.atlas.cogentco.com [154.54.42.77]
    10 85 ms 89 ms 78 ms be2932.ccr42.lax01.atlas.cogentco.com [154.54.45.162]
    11 108 ms 97 ms 88 ms be3177.ccr22.sjc01.atlas.cogentco.com [154.54.40.146]
    12 94 ms 94 ms 94 ms be3144.ccr41.sjc03.atlas.cogentco.com [154.54.5.102]
    13 218 ms 193 ms 198 ms be3696.ccr21.tyo01.atlas.cogentco.com [154.54.86.138]
    14 253 ms 262 ms 254 ms be3690.ccr21.hkg02.atlas.cogentco.com [154.54.47.254]
    15 259 ms 246 ms 246 ms be2414.rcr51.hkg01.atlas.cogentco.com [154.54.88.50]
    16 260 ms 249 ms 251 ms be2044.nr12.b065790-1.hkg01.atlas.cogentco.com [154.24.37.46]
    17 255 ms 257 ms 245 ms 154.18.6.170
    18 255 ms 261 ms 251 ms 89.44.212.56
    19 262 ms 245 ms 271 ms 89.44.212.61
    20 251 ms 262 ms 256 ms te-1-1-1-0.bb1.man1.uk.m247.com [82.102.29.0]
    21 260 ms 250 ms 246 ms 193.239.86.68
    22 260 ms 263 ms 258 ms 103.73.67.135

    Trace complete.

    Alien Data: VPS and Colo Based In Texas, Unmetered Bandwidth.
    RPIServers: Dedicated Micro Servers. Unmeterd Bandwidth

  • thedpthedp Member

    Your friend is sharing his/her internet with the neighbors and they're all leaching his/her bandwidth.

    But yeah, need to see the trace/mtr results from your friend's location to hk.myhostnames.com for clues.

    Thanked by 1jpeng

    Tech/Hosting & Miscellaneous Domain Names For Sale!
    Storage-related Domain Names Auction In Progress

  • jpengjpeng Member

    @DataIdeas-Josh said: traceroute hk.myhostnames.com

    >

    Here is traceroute by my friend from Guangdong Province:

    traceroute to hk.myhostnames.com (103.73.67.135), 64 hops max, 52 byte packets
    1 172.20.120.1 (172.20.120.1) 3.652 ms 3.003 ms 2.379 ms
    2 172.20.254.13 (172.20.254.13) 3.869 ms 3.554 ms 3.133 ms
    3 172.20.255.254 (172.20.255.254) 3.884 ms 2.937 ms 3.531 ms
    4 113.106.251.81 (113.106.251.81) 3.884 ms 3.184 ms 2.888 ms
    5 14.148.22.157 (14.148.22.157) 4.530 ms
    14.148.22.153 (14.148.22.153) 15.779 ms
    14.148.22.157 (14.148.22.157) 4.064 ms
    6 117.176.37.59.broad.dg.gd.dynamic.163data.com.cn (59.37.176.117) 4.350 ms 3.589 ms 3.876 ms
    7 14.148.31.21 (14.148.31.21) 15.487 ms 13.977 ms
    14.148.31.5 (14.148.31.5) 15.476 ms
    8 113.96.251.13 (113.96.251.13) 8.189 ms
    113.96.251.53 (113.96.251.53) 14.382 ms 19.341 ms
    9 202.97.91.22 (202.97.91.22) 9.584 ms
    202.97.90.158 (202.97.90.158) 12.120 ms
    202.97.91.22 (202.97.91.22) 14.460 ms
    10 202.97.91.194 (202.97.91.194) 17.729 ms 20.500 ms
    202.97.38.93 (202.97.38.93) 22.572 ms
    11 202.97.60.214 (202.97.60.214) 395.250 ms * 331.369 ms
    12 ae-1.r30.tokyjp05.jp.bb.gin.ntt.net (129.250.2.157) 492.416 ms 311.984 ms 311.669 ms
    13 ae-4.r24.tkokhk01.hk.bb.gin.ntt.net (129.250.2.51) 416.706 ms 515.701 ms 419.235 ms
    14 * ae-1.r03.tkokhk01.hk.bb.gin.ntt.net (129.250.6.98) 554.142 ms
    ae-1.r02.tkokhk01.hk.bb.gin.ntt.net (129.250.6.92) 490.741 ms
    15 ae-1.a00.newthk03.hk.bb.gin.ntt.net (129.250.5.69) 423.882 ms * 564.578 ms
    16 * * 203.131.242.130 (203.131.242.130) 490.994 ms
    17 89.44.212.56 (89.44.212.56) 434.461 ms 578.071 ms 491.604 ms
    18 * * *
    19 * * *
    20 193.239.86.68 (193.239.86.68) 430.179 ms 446.425 ms 475.205 ms
    21 103.73.67.135 (103.73.67.135) 508.403 ms 491.328 ms 491.602 ms

    can you give more suggestion?
    Thanks.

    Free secure email: https://tls-mail.com/

  • thedpthedp Member

    @jpeng said:

    @DataIdeas-Josh said: traceroute hk.myhostnames.com

    >

    Here is traceroute by my friend from Guangdong Province:

    traceroute to hk.myhostnames.com (103.73.67.135), 64 hops max, 52 byte packets
    1 172.20.120.1 (172.20.120.1) 3.652 ms 3.003 ms 2.379 ms
    2 172.20.254.13 (172.20.254.13) 3.869 ms 3.554 ms 3.133 ms
    3 172.20.255.254 (172.20.255.254) 3.884 ms 2.937 ms 3.531 ms
    4 113.106.251.81 (113.106.251.81) 3.884 ms 3.184 ms 2.888 ms
    5 14.148.22.157 (14.148.22.157) 4.530 ms
    14.148.22.153 (14.148.22.153) 15.779 ms
    14.148.22.157 (14.148.22.157) 4.064 ms
    6 117.176.37.59.broad.dg.gd.dynamic.163data.com.cn (59.37.176.117) 4.350 ms 3.589 ms 3.876 ms
    7 14.148.31.21 (14.148.31.21) 15.487 ms 13.977 ms
    14.148.31.5 (14.148.31.5) 15.476 ms
    8 113.96.251.13 (113.96.251.13) 8.189 ms
    113.96.251.53 (113.96.251.53) 14.382 ms 19.341 ms
    9 202.97.91.22 (202.97.91.22) 9.584 ms
    202.97.90.158 (202.97.90.158) 12.120 ms
    202.97.91.22 (202.97.91.22) 14.460 ms
    10 202.97.91.194 (202.97.91.194) 17.729 ms 20.500 ms
    202.97.38.93 (202.97.38.93) 22.572 ms
    11 202.97.60.214 (202.97.60.214) 395.250 ms * 331.369 ms
    12 ae-1.r30.tokyjp05.jp.bb.gin.ntt.net (129.250.2.157) 492.416 ms 311.984 ms 311.669 ms
    13 ae-4.r24.tkokhk01.hk.bb.gin.ntt.net (129.250.2.51) 416.706 ms 515.701 ms 419.235 ms
    14 * ae-1.r03.tkokhk01.hk.bb.gin.ntt.net (129.250.6.98) 554.142 ms
    ae-1.r02.tkokhk01.hk.bb.gin.ntt.net (129.250.6.92) 490.741 ms
    15 ae-1.a00.newthk03.hk.bb.gin.ntt.net (129.250.5.69) 423.882 ms * 564.578 ms
    16 * * 203.131.242.130 (203.131.242.130) 490.994 ms
    17 89.44.212.56 (89.44.212.56) 434.461 ms 578.071 ms 491.604 ms
    18 * * *
    19 * * *
    20 193.239.86.68 (193.239.86.68) 430.179 ms 446.425 ms 475.205 ms
    21 103.73.67.135 (103.73.67.135) 508.403 ms 491.328 ms 491.602 ms

    can you give more suggestion?
    Thanks.

    Looks like they took him to Takeshi's Castle.

    Thanked by 2Erisa kkrajk

    Tech/Hosting & Miscellaneous Domain Names For Sale!
    Storage-related Domain Names Auction In Progress

  • @thedp said:

    @jpeng said:

    @DataIdeas-Josh said: traceroute hk.myhostnames.com

    >

    Here is traceroute by my friend from Guangdong Province:

    traceroute to hk.myhostnames.com (103.73.67.135), 64 hops max, 52 byte packets
    1 172.20.120.1 (172.20.120.1) 3.652 ms 3.003 ms 2.379 ms
    2 172.20.254.13 (172.20.254.13) 3.869 ms 3.554 ms 3.133 ms
    3 172.20.255.254 (172.20.255.254) 3.884 ms 2.937 ms 3.531 ms
    4 113.106.251.81 (113.106.251.81) 3.884 ms 3.184 ms 2.888 ms
    5 14.148.22.157 (14.148.22.157) 4.530 ms
    14.148.22.153 (14.148.22.153) 15.779 ms
    14.148.22.157 (14.148.22.157) 4.064 ms
    6 117.176.37.59.broad.dg.gd.dynamic.163data.com.cn (59.37.176.117) 4.350 ms 3.589 ms 3.876 ms
    7 14.148.31.21 (14.148.31.21) 15.487 ms 13.977 ms
    14.148.31.5 (14.148.31.5) 15.476 ms
    8 113.96.251.13 (113.96.251.13) 8.189 ms
    113.96.251.53 (113.96.251.53) 14.382 ms 19.341 ms
    9 202.97.91.22 (202.97.91.22) 9.584 ms
    202.97.90.158 (202.97.90.158) 12.120 ms
    202.97.91.22 (202.97.91.22) 14.460 ms
    10 202.97.91.194 (202.97.91.194) 17.729 ms 20.500 ms
    202.97.38.93 (202.97.38.93) 22.572 ms
    11 202.97.60.214 (202.97.60.214) 395.250 ms * 331.369 ms
    12 ae-1.r30.tokyjp05.jp.bb.gin.ntt.net (129.250.2.157) 492.416 ms 311.984 ms 311.669 ms
    13 ae-4.r24.tkokhk01.hk.bb.gin.ntt.net (129.250.2.51) 416.706 ms 515.701 ms 419.235 ms
    14 * ae-1.r03.tkokhk01.hk.bb.gin.ntt.net (129.250.6.98) 554.142 ms
    ae-1.r02.tkokhk01.hk.bb.gin.ntt.net (129.250.6.92) 490.741 ms
    15 ae-1.a00.newthk03.hk.bb.gin.ntt.net (129.250.5.69) 423.882 ms * 564.578 ms
    16 * * 203.131.242.130 (203.131.242.130) 490.994 ms
    17 89.44.212.56 (89.44.212.56) 434.461 ms 578.071 ms 491.604 ms
    18 * * *
    19 * * *
    20 193.239.86.68 (193.239.86.68) 430.179 ms 446.425 ms 475.205 ms
    21 103.73.67.135 (103.73.67.135) 508.403 ms 491.328 ms 491.602 ms

    can you give more suggestion?
    Thanks.

    Looks like they took him to Takeshi's Castle.

    lols. naniii.

  • jsgjsg Member

    @jpeng said:
    I am in Hong Kong, ping speed to HostHatch Hong Kong node is quite fast:

    [couple of pings]

    But my friend from Guangdong Telecom which is close to Hong Kong from geo location, his ping is quite slow and package losing:

    [couple of pings]

    Can you help explain this? thank you.

    • Your friends ping comes from mainland China while yours comes from Hongkong autonomous zone (or whatever the politically correct wording is), China.
    • Geographical distance is of almost no concern, internet geography is decisive.
    • Many large carriers/providers "collect" all outside (of their network or even outside the country) destined packets in one or a few network nodes. Typically this may add a couple of ms up to maybe 50 ms.
    • In the case of China packets leaving the country and especially those going to destinations considered "problematic" (politically) are going through some centralized inspection nodes (like the Great Firewall).
    • carriers, especially large private corporations, have their own policies too (like cheap is more important than fast) plus in the case of some countries (like China) may be bound to use only a few transfer nodes to get traffic out of or into the country.
    • As Hongkong isn't just any city but a rather special one, western intelligence services want to have a look at many of the packets too (like those to/from mainland China).
    • Intelligence services don't tend to put their organisation name in bold letters on their work and having packets seem to have gone through weird loops is one typical way to cover their tracks.

    Note btw that your friends packets are losing most of their time during "weird routing loops" (almost certainly eavesdropping) by the "good" western world "allies" and not in "evil" China.

    Thanked by 2jpeng dominame

    Thanks no.

  • John_MJohn_M Member, Provider

    @jsg said:

    @jpeng said:
    I am in Hong Kong, ping speed to HostHatch Hong Kong node is quite fast:

    [couple of pings]

    But my friend from Guangdong Telecom which is close to Hong Kong from geo location, his ping is quite slow and package losing:

    [couple of pings]

    Can you help explain this? thank you.

    • Your friends ping comes from mainland China while yours comes from Hongkong autonomous zone (or whatever the politically correct wording is), China.
    • Geographical distance is of almost no concern, internet geography is decisive.
    • Many large carriers/providers "collect" all outside (of their network or even outside the country) destined packets in one or a few network nodes. Typically this may add a couple of ms up to maybe 50 ms.
    • In the case of China packets leaving the country and especially those going to destinations considered "problematic" (politically) are going through some centralized inspection nodes (like the Great Firewall).
    • carriers, especially large private corporations, have their own policies too (like cheap is more important than fast) plus in the case of some countries (like China) may be bound to use only a few transfer nodes to get traffic out of or into the country.
    • As Hongkong isn't just any city but a rather special one, western intelligence services want to have a look at many of the packets too (like those to/from mainland China).
    • Intelligence services don't tend to put their organisation name in bold letters on their work and having packets seem to have gone through weird loops is one typical way to cover their tracks.

    Note btw that your friends packets are losing most of their time during "weird routing loops" (almost certainly eavesdropping) by the "good" western world "allies" and not in "evil" China.

    Very detailed explanations. The only reason I can see is that the packet was circling around the world instead of going to HK directly.
    PS, direct traffic going into or out of HK are very expensive.

    QuadraNet-Data Center Ingenuity Made Simple
    Dedicated Servers - Colocations - Public/Private Cloud - Backup Solutions and More
    Email: Sales[at]QuadraNet.com Sky: John-QuadraNet

  • jpengjpeng Member

    @John_M said: PS, direct traffic going into or out of HK are very expensive.

    >
    why this happens? :)

    Free secure email: https://tls-mail.com/

  • seriesnseriesn Member, Top Provider

    @jpeng said:

    @John_M said: PS, direct traffic going into or out of HK are very expensive.

    >
    why this happens? :)

    Because China and Chinese carriers are greedy. CN2/Gia charges an arm, a leg, a kidney, 3 testicle and sacrifice of a virgin father, just for some “decent” connectivity.

    Since the cost is significantly high, it comes out cheaper to take the longer route.

    Kind of like paying highway toll vs taking local route.

  • China definitely brings shame to the family with their internet situation..

    I <3 Nexus Bytes and Direct Admin <3

  • lentrolentro Member, Provider

    @jpeng said: 202.97.38.93 (202.97.38.93) 22.572 ms

    11 202.97.60.214 (202.97.60.214) 395.250 ms * 331.369 ms

    @jsg said: Note btw that your friends packets are losing most of their time during "weird routing loops" (almost certainly eavesdropping) by the "good" western world "allies" and not in "evil" China.

    Seems to me that the largest amount of time is spent in mainland China though. Just look at that -- over 300 ms for a single hop! That's insanity!

    Thanked by 1jpeng

    FluidStack: Up to $600 Monthly For Your GPU(s) or Rent Affordable GPU Machines | VC-backed | 2,000+ Machines (aff link)
    ISODME: Web hosting | Managed VPS services | U.S. based support | High Uptime | isodme.com

  • jpengjpeng Member

    @jpeng said: 18 * * *

    19 * * *

    why no.18 and 19 nodes can't be viewable? thanks.

    Free secure email: https://tls-mail.com/

  • jsgjsg Member
    edited January 14

    @lentro said:

    @jpeng said: 202.97.38.93 (202.97.38.93) 22.572 ms

    11 202.97.60.214 (202.97.60.214) 395.250 ms * 331.369 ms

    @jsg said: Note btw that your friends packets are losing most of their time during "weird routing loops" (almost certainly eavesdropping) by the "good" western world "allies" and not in "evil" China.

    Seems to me that the largest amount of time is spent in mainland China though. Just look at that -- over 300 ms for a single hop! That's insanity!

    Yes it seems so, but from what I see that's the GF and the hop to JP.You can bet that 202.97.60.214 is a IX port and part of and last hop of the Gin JP backbone. Accordingly and matching the next port is NTT 's transfer port from the Gin JP backbone. Funnily I couldn't ping it or MTR to it; no surprise as it's a node that's meant to be reached from Gin internally only, highly likely even only from a selected list of nodes (like, uhum, GF feeders).

    The prior hop 202.97.38.93, highly likely just a backbone node could be pinged by myself (from Europe). In fact the MTR was really fast, just about 265 ms with the last european hop being 65 ms, so from eastern Europa to China mainland took just about 200 ms. It seems the Chinese operate a rather fast filtering system ("GF") and hide it well.

    And yet something else can be learned here: it does make a significant difference from where and where to traffic comes/goes. Packets from Europe seem to get inspected just superficially while packets to/from Hongkong get a rather full colonoscopy - which makes sense from a chinese government perspective. The western services on the other hand have little to no interest in packets coming from Europe which is part 2 of why my packet across half the planet is much faster than OPs friends package although geographically it's just a stone throw away.

    At the end of the day both regimes, "evil China" and "the good western world (read: USA and "allies")" take about the same time for inspection but they disguise it differently; in the case of China not at all and in the western regime case via many pseudo hops plus an expensive route via Japan.
    Btw, I book the 100 - 150 ms (hidden in the 300 ms of the last chinese hop) from CN to JP on the western regime account because the Chinese certainly don't route their mainland - Hongkong packets via JP for the fun of it. They do it because the western regime demands it.

    In case that sounds anti-american/anti western: YES it is. Simple reason. Both sh_t on freedom, both inspect and eavesdrop on communication but the Chinese do it openly and don't drop "freedom, democracy, human rights" BS on you - while the "good democratic" western regime eavesdrops on you (at high cost for you at that) but while sh_tting on your "rights" dumps a load of "freedom, human rights, democracy" BS on you.

    Thanked by 1atindahause

    Thanks no.

  • mikecmikec Member

    If I traceroute from server in US, it is routed to HostHatch data center in HK. Latency is normal.

    %> ip2trace -p 103.73.67.135 -d /usr/share/ip2location/DB3.BIN
    
    IP2Location Geolocation Traceroute (ip2trace) Version 8.0.0
    Copyright (c) 2021 IP2Location.com [MIT License]
    https://www.ip2location.com/free/traceroute-application
    
    1. 50.97.82.1 0.538 ms ["US", "United States of America", "Texas", "Dallas", "SoftLayer Technologies Inc.]
    2. 173.192.118.142 0.523 ms ["US", "United States of America", "Texas", "Dallas", "SoftLayer Technologies Inc.]
    3. 173.192.18.214 1.047 ms ["US", "United States of America", "Texas", "Dallas", "SoftLayer Technologies Inc.]
    4. 157.238.224.225 1.814 ms ["US", "United States of America", "Texas", "Dallas", "NTT America Inc.]
    5. 129.250.3.31 1.880 ms ["US", "United States of America", "Texas", "Dallas", "NTT America Inc.]
    6. 129.250.4.154 44.886 ms ["US", "United States of America", "California", "San Jose", "NTT America Inc.]
    7. 129.250.5.77 141.976 ms ["JP", "Japan", "Tokyo", "Tokyo", "NTT America Inc.]
    8. 129.250.2.51 193.377 ms ["HK", "Hong Kong", "Hong Kong", "Hong Kong", "NTT America Inc.]
    9. 129.250.6.98 193.072 ms ["HK", "Hong Kong", "Hong Kong", "Hong Kong", "NTT America Inc.]
    10. 129.250.5.69 188.187 ms ["HK", "Hong Kong", "Hong Kong", "Hong Kong", "NTT America Inc.]
    11. 203.131.242.130 186.933 ms ["HK", "Hong Kong", "Hong Kong", "Hong Kong", "HKNet Company Limited]
    12. 193.239.86.68 190.600 ms ["HK", "Hong Kong", "Hong Kong", "Hong Kong", "M247 Europe SRL]
    13. 103.73.67.135 191.593 ms ["HK", "Hong Kong", "Hong Kong", "Hong Kong", "HostHatch Inc]
    
Sign In or Register to comment.