All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
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.
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
@jpeng do a
traceroute hk.myhostnames.comAs 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.
Might be direct bandwidth to China issue? It can be Guangdong -> USA -> Hong Kong, which increased the latency.
Heres what I am getting from Texas.
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.comfor clues.>
Here is traceroute by my friend from Guangdong Province:
can you give more suggestion?
Thanks.
Looks like they took him to Takeshi's Castle.
lols. naniii.
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.
>
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..
11 202.97.60.214 (202.97.60.214) 395.250 ms * 331.369 ms
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!
19 * * *
why no.18 and 19 nodes can't be viewable? thanks.
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.
If I traceroute from server in US, it is routed to HostHatch data center in HK. Latency is normal.