监测点 |
ISP |
省份 |
解析IP |
解析IP所在地 |
发送 |
接收 |
丢弃 |
最大时间 |
最小时间 |
平均时间 |
包大小 |
详细信息 |
操作 |
共170个点 |
8个 |
共37个 |
共1个独立IP |
共1个独立节点 |
10 |
9 |
1 |
189.891ms |
166.287ms |
175.763ms |
|
|
|
上海上海市联通 |
联通 |
上海 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
705.017ms |
178.26ms |
499.606ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=602ms TTL=51 Reply from 38.49.39.136: bytes=32 time=178ms TTL=51 Reply from 38.49.39.136: bytes=32 time=520ms TTL=51 Reply from 38.49.39.136: bytes=32 time=494ms TTL=51 Reply from 38.49.39.136: bytes=32 time=705ms TTL=51 Reply from 38.49.39.136: bytes=32 time=534ms TTL=51 Reply from 38.49.39.136: bytes=32 time=557ms TTL=51 Reply from 38.49.39.136: bytes=32 time=470ms TTL=51 Reply from 38.49.39.136: bytes=32 time=430ms TTL=51 Reply from 38.49.39.136: bytes=32 time=506ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 178ms, Maximum = 705ms, Average = 500ms查看 |
GET PING Trace Dig |
|
重庆重庆市移动 |
移动 |
重庆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
7 |
3 |
702.188ms |
0ms |
459.973ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Request timed out. Request timed out. Reply from 38.49.39.136: bytes=32 time=540ms TTL=48 Reply from 38.49.39.136: bytes=32 time=260ms TTL=48 Reply from 38.49.39.136: bytes=32 time=563ms TTL=48 Reply from 38.49.39.136: bytes=32 time=343ms TTL=48 Reply from 38.49.39.136: bytes=32 time=323ms TTL=48 Reply from 38.49.39.136: bytes=32 time=490ms TTL=48 Reply from 38.49.39.136: bytes=32 time=702ms TTL=48 Request timed out.
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 7, Lost = 3 (30% loss), Approximate round trip times in milli-seconds: Minimum <1ms , Maximum = 702ms, Average = 460ms查看 |
GET PING Trace Dig |
|
宁夏银川移动 |
移动 |
宁夏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
447.083ms |
184.302ms |
313.621ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=345ms TTL=50 Reply from 38.49.39.136: bytes=32 time=302ms TTL=50 Reply from 38.49.39.136: bytes=32 time=299ms TTL=50 Reply from 38.49.39.136: bytes=32 time=299ms TTL=50 Reply from 38.49.39.136: bytes=32 time=447ms TTL=50 Reply from 38.49.39.136: bytes=32 time=184ms TTL=50 Reply from 38.49.39.136: bytes=32 time=374ms TTL=50 Reply from 38.49.39.136: bytes=32 time=193ms TTL=50 Reply from 38.49.39.136: bytes=32 time=298ms TTL=50 Reply from 38.49.39.136: bytes=32 time=394ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 184ms, Maximum = 447ms, Average = 314ms查看 |
GET PING Trace Dig |
|
内蒙古兴安盟联通 |
联通 |
内蒙古 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
626.46ms |
199.46ms |
264.774ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=276ms TTL=47 Reply from 38.49.39.136: bytes=32 time=206ms TTL=47 Reply from 38.49.39.136: bytes=32 time=244ms TTL=47 Reply from 38.49.39.136: bytes=32 time=199ms TTL=47 Reply from 38.49.39.136: bytes=32 time=201ms TTL=47 Reply from 38.49.39.136: bytes=32 time=199ms TTL=47 Reply from 38.49.39.136: bytes=32 time=201ms TTL=47 Reply from 38.49.39.136: bytes=32 time=292ms TTL=47 Reply from 38.49.39.136: bytes=32 time=203ms TTL=47 Reply from 38.49.39.136: bytes=32 time=626ms TTL=47
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 199ms, Maximum = 626ms, Average = 265ms查看 |
GET PING Trace Dig |
|
贵州贵阳市联通 |
联通 |
贵州 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
406.796ms |
185.319ms |
234.483ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=187ms TTL=49 Reply from 38.49.39.136: bytes=32 time=203ms TTL=49 Reply from 38.49.39.136: bytes=32 time=198ms TTL=49 Reply from 38.49.39.136: bytes=32 time=315ms TTL=49 Reply from 38.49.39.136: bytes=32 time=407ms TTL=49 Reply from 38.49.39.136: bytes=32 time=188ms TTL=49 Reply from 38.49.39.136: bytes=32 time=199ms TTL=49 Reply from 38.49.39.136: bytes=32 time=274ms TTL=49 Reply from 38.49.39.136: bytes=32 time=188ms TTL=49 Reply from 38.49.39.136: bytes=32 time=185ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 185ms, Maximum = 407ms, Average = 234ms查看 |
GET PING Trace Dig |
|
新疆喀什地区移动 |
移动 |
新疆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
245.839ms |
231.479ms |
234.376ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=232ms TTL=49 Reply from 38.49.39.136: bytes=32 time=241ms TTL=49 Reply from 38.49.39.136: bytes=32 time=246ms TTL=49 Reply from 38.49.39.136: bytes=32 time=231ms TTL=49 Reply from 38.49.39.136: bytes=32 time=232ms TTL=49 Reply from 38.49.39.136: bytes=32 time=232ms TTL=49 Reply from 38.49.39.136: bytes=32 time=233ms TTL=49 Reply from 38.49.39.136: bytes=32 time=232ms TTL=49 Reply from 38.49.39.136: bytes=32 time=232ms TTL=49 Reply from 38.49.39.136: bytes=32 time=232ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 231ms, Maximum = 246ms, Average = 234ms查看 |
GET PING Trace Dig |
|
广东茂名移动 |
移动 |
广东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
323.82ms |
175.344ms |
228.009ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=179ms TTL=49 Reply from 38.49.39.136: bytes=32 time=176ms TTL=49 Reply from 38.49.39.136: bytes=32 time=324ms TTL=49 Reply from 38.49.39.136: bytes=32 time=301ms TTL=49 Reply from 38.49.39.136: bytes=32 time=293ms TTL=49 Reply from 38.49.39.136: bytes=32 time=292ms TTL=49 Reply from 38.49.39.136: bytes=32 time=180ms TTL=49 Reply from 38.49.39.136: bytes=32 time=178ms TTL=49 Reply from 38.49.39.136: bytes=32 time=175ms TTL=49 Reply from 38.49.39.136: bytes=32 time=182ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 175ms, Maximum = 324ms, Average = 228ms查看 |
GET PING Trace Dig |
|
北京北京市移动 |
移动 |
北京 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
229.639ms |
200.28ms |
213.957ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=210ms TTL=46 Reply from 38.49.39.136: bytes=32 time=230ms TTL=46 Reply from 38.49.39.136: bytes=32 time=212ms TTL=46 Reply from 38.49.39.136: bytes=32 time=207ms TTL=46 Reply from 38.49.39.136: bytes=32 time=226ms TTL=46 Reply from 38.49.39.136: bytes=32 time=220ms TTL=46 Reply from 38.49.39.136: bytes=32 time=200ms TTL=46 Reply from 38.49.39.136: bytes=32 time=216ms TTL=46 Reply from 38.49.39.136: bytes=32 time=207ms TTL=46 Reply from 38.49.39.136: bytes=32 time=212ms TTL=46
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 200ms, Maximum = 230ms, Average = 214ms查看 |
GET PING Trace Dig |
|
新疆和田地区移动 |
移动 |
新疆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
213.08ms |
212.782ms |
212.918ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=213ms TTL=48 Reply from 38.49.39.136: bytes=32 time=213ms TTL=48 Reply from 38.49.39.136: bytes=32 time=213ms TTL=48 Reply from 38.49.39.136: bytes=32 time=213ms TTL=48 Reply from 38.49.39.136: bytes=32 time=213ms TTL=48 Reply from 38.49.39.136: bytes=32 time=213ms TTL=48 Reply from 38.49.39.136: bytes=32 time=213ms TTL=48 Reply from 38.49.39.136: bytes=32 time=213ms TTL=48 Reply from 38.49.39.136: bytes=32 time=213ms TTL=48 Reply from 38.49.39.136: bytes=32 time=213ms TTL=48
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 213ms, Maximum = 213ms, Average = 213ms查看 |
GET PING Trace Dig |
|
宁夏银川市联通 |
联通 |
宁夏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
222.747ms |
204.536ms |
212.079ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=213ms TTL=47 Reply from 38.49.39.136: bytes=32 time=215ms TTL=47 Reply from 38.49.39.136: bytes=32 time=213ms TTL=47 Reply from 38.49.39.136: bytes=32 time=213ms TTL=47 Reply from 38.49.39.136: bytes=32 time=223ms TTL=47 Reply from 38.49.39.136: bytes=32 time=215ms TTL=47 Reply from 38.49.39.136: bytes=32 time=210ms TTL=47 Reply from 38.49.39.136: bytes=32 time=208ms TTL=47 Reply from 38.49.39.136: bytes=32 time=207ms TTL=47 Reply from 38.49.39.136: bytes=32 time=205ms TTL=47
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 205ms, Maximum = 223ms, Average = 212ms查看 |
GET PING Trace Dig |
|
内蒙古兴安盟移动 |
移动 |
内蒙古 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
228.381ms |
206.141ms |
210.583ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=206ms TTL=49 Reply from 38.49.39.136: bytes=32 time=207ms TTL=49 Reply from 38.49.39.136: bytes=32 time=206ms TTL=49 Reply from 38.49.39.136: bytes=32 time=206ms TTL=49 Reply from 38.49.39.136: bytes=32 time=206ms TTL=49 Reply from 38.49.39.136: bytes=32 time=207ms TTL=49 Reply from 38.49.39.136: bytes=32 time=211ms TTL=49 Reply from 38.49.39.136: bytes=32 time=218ms TTL=49 Reply from 38.49.39.136: bytes=32 time=210ms TTL=49 Reply from 38.49.39.136: bytes=32 time=228ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 206ms, Maximum = 228ms, Average = 211ms查看 |
GET PING Trace Dig |
|
新疆乌鲁木齐市电信 |
电信 |
新疆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
299.659ms |
196.539ms |
207.944ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=198ms TTL=49 Reply from 38.49.39.136: bytes=32 time=199ms TTL=49 Reply from 38.49.39.136: bytes=32 time=197ms TTL=49 Reply from 38.49.39.136: bytes=32 time=200ms TTL=49 Reply from 38.49.39.136: bytes=32 time=300ms TTL=49 Reply from 38.49.39.136: bytes=32 time=197ms TTL=49 Reply from 38.49.39.136: bytes=32 time=199ms TTL=49 Reply from 38.49.39.136: bytes=32 time=197ms TTL=49 Reply from 38.49.39.136: bytes=32 time=197ms TTL=49 Reply from 38.49.39.136: bytes=32 time=197ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 197ms, Maximum = 300ms, Average = 208ms查看 |
GET PING Trace Dig |
|
吉林松原市联通 |
联通 |
吉林 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
234.852ms |
197.592ms |
207.661ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=227ms TTL=49 Reply from 38.49.39.136: bytes=32 time=223ms TTL=49 Reply from 38.49.39.136: bytes=32 time=202ms TTL=49 Reply from 38.49.39.136: bytes=32 time=235ms TTL=49 Reply from 38.49.39.136: bytes=32 time=199ms TTL=49 Reply from 38.49.39.136: bytes=32 time=198ms TTL=49 Reply from 38.49.39.136: bytes=32 time=198ms TTL=49 Reply from 38.49.39.136: bytes=32 time=198ms TTL=49 Reply from 38.49.39.136: bytes=32 time=199ms TTL=49 Reply from 38.49.39.136: bytes=32 time=198ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 198ms, Maximum = 235ms, Average = 208ms查看 |
GET PING Trace Dig |
|
黑龙江哈尔滨市电信 |
电信 |
黑龙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
206.822ms |
205.502ms |
205.845ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=206ms TTL=49 Reply from 38.49.39.136: bytes=32 time=206ms TTL=49 Reply from 38.49.39.136: bytes=32 time=206ms TTL=49 Reply from 38.49.39.136: bytes=32 time=206ms TTL=49 Reply from 38.49.39.136: bytes=32 time=207ms TTL=49 Reply from 38.49.39.136: bytes=32 time=206ms TTL=49 Reply from 38.49.39.136: bytes=32 time=206ms TTL=49 Reply from 38.49.39.136: bytes=32 time=206ms TTL=49 Reply from 38.49.39.136: bytes=32 time=206ms TTL=49 Reply from 38.49.39.136: bytes=32 time=206ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 206ms, Maximum = 207ms, Average = 206ms查看 |
GET PING Trace Dig |
|
西藏拉萨市移动 |
移动 |
西藏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
203.52ms |
203.08ms |
203.25ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=203ms TTL=49 Reply from 38.49.39.136: bytes=32 time=203ms TTL=49 Reply from 38.49.39.136: bytes=32 time=203ms TTL=49 Reply from 38.49.39.136: bytes=32 time=203ms TTL=49 Reply from 38.49.39.136: bytes=32 time=203ms TTL=49 Reply from 38.49.39.136: bytes=32 time=203ms TTL=49 Reply from 38.49.39.136: bytes=32 time=203ms TTL=49 Reply from 38.49.39.136: bytes=32 time=204ms TTL=49 Reply from 38.49.39.136: bytes=32 time=203ms TTL=49 Reply from 38.49.39.136: bytes=32 time=203ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 203ms, Maximum = 204ms, Average = 203ms查看 |
GET PING Trace Dig |
|
黑龙江齐齐哈尔市联通 |
联通 |
黑龙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
204.524ms |
199.771ms |
200.781ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=205ms TTL=49 Reply from 38.49.39.136: bytes=32 time=201ms TTL=49 Reply from 38.49.39.136: bytes=32 time=200ms TTL=49 Reply from 38.49.39.136: bytes=32 time=200ms TTL=49 Reply from 38.49.39.136: bytes=32 time=200ms TTL=49 Reply from 38.49.39.136: bytes=32 time=200ms TTL=49 Reply from 38.49.39.136: bytes=32 time=201ms TTL=49 Reply from 38.49.39.136: bytes=32 time=202ms TTL=49 Reply from 38.49.39.136: bytes=32 time=200ms TTL=49 Reply from 38.49.39.136: bytes=32 time=200ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 200ms, Maximum = 205ms, Average = 201ms查看 |
GET PING Trace Dig |
|
湖南郴州市电信 |
电信 |
湖南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
9 |
1 |
244.741ms |
179.721ms |
199.066ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=200ms TTL=51 Reply from 38.49.39.136: bytes=32 time=195ms TTL=51 Reply from 38.49.39.136: bytes=32 time=245ms TTL=51 Reply from 38.49.39.136: bytes=32 time=195ms TTL=51 Reply from 38.49.39.136: bytes=32 time=205ms TTL=51 Reply from 38.49.39.136: bytes=32 time=188ms TTL=51 Reply from 38.49.39.136: bytes=32 time=180ms TTL=51 Reply from 38.49.39.136: bytes=32 time=189ms TTL=51 Request timed out. Reply from 38.49.39.136: bytes=32 time=196ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 9, Lost = 1 (10% loss), Approximate round trip times in milli-seconds: Minimum = 180ms, Maximum = 245ms, Average = 199ms查看 |
GET PING Trace Dig |
|
吉林吉林市移动 |
移动 |
吉林 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
202.861ms |
197.781ms |
198.822ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=199ms TTL=49 Reply from 38.49.39.136: bytes=32 time=198ms TTL=49 Reply from 38.49.39.136: bytes=32 time=199ms TTL=49 Reply from 38.49.39.136: bytes=32 time=199ms TTL=49 Reply from 38.49.39.136: bytes=32 time=198ms TTL=49 Reply from 38.49.39.136: bytes=32 time=198ms TTL=49 Reply from 38.49.39.136: bytes=32 time=203ms TTL=49 Reply from 38.49.39.136: bytes=32 time=199ms TTL=49 Reply from 38.49.39.136: bytes=32 time=198ms TTL=49 Reply from 38.49.39.136: bytes=32 time=198ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 198ms, Maximum = 203ms, Average = 199ms查看 |
GET PING Trace Dig |
|
吉林长春市联通 |
联通 |
吉林 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
199.38ms |
198.2ms |
198.602ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=199ms TTL=48 Reply from 38.49.39.136: bytes=32 time=199ms TTL=48 Reply from 38.49.39.136: bytes=32 time=198ms TTL=48 Reply from 38.49.39.136: bytes=32 time=199ms TTL=48 Reply from 38.49.39.136: bytes=32 time=198ms TTL=48 Reply from 38.49.39.136: bytes=32 time=199ms TTL=48 Reply from 38.49.39.136: bytes=32 time=199ms TTL=48 Reply from 38.49.39.136: bytes=32 time=198ms TTL=48 Reply from 38.49.39.136: bytes=32 time=198ms TTL=48 Reply from 38.49.39.136: bytes=32 time=198ms TTL=48
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 198ms, Maximum = 199ms, Average = 199ms查看 |
GET PING Trace Dig |
|
德国国外 |
国外 |
德国 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
219.186ms |
191.243ms |
197.912ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=192ms TTL=48 Reply from 38.49.39.136: bytes=32 time=194ms TTL=48 Reply from 38.49.39.136: bytes=32 time=192ms TTL=48 Reply from 38.49.39.136: bytes=32 time=192ms TTL=48 Reply from 38.49.39.136: bytes=32 time=219ms TTL=48 Reply from 38.49.39.136: bytes=32 time=193ms TTL=48 Reply from 38.49.39.136: bytes=32 time=195ms TTL=48 Reply from 38.49.39.136: bytes=32 time=191ms TTL=48 Reply from 38.49.39.136: bytes=32 time=218ms TTL=48 Reply from 38.49.39.136: bytes=32 time=194ms TTL=48
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 191ms, Maximum = 219ms, Average = 198ms查看 |
GET PING Trace Dig |
|
吉林通化市联通 |
联通 |
吉林 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
200.582ms |
195.522ms |
197.371ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=196ms TTL=50 Reply from 38.49.39.136: bytes=32 time=197ms TTL=50 Reply from 38.49.39.136: bytes=32 time=199ms TTL=50 Reply from 38.49.39.136: bytes=32 time=196ms TTL=50 Reply from 38.49.39.136: bytes=32 time=196ms TTL=50 Reply from 38.49.39.136: bytes=32 time=196ms TTL=50 Reply from 38.49.39.136: bytes=32 time=201ms TTL=50 Reply from 38.49.39.136: bytes=32 time=198ms TTL=50 Reply from 38.49.39.136: bytes=32 time=198ms TTL=50 Reply from 38.49.39.136: bytes=32 time=196ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 196ms, Maximum = 201ms, Average = 197ms查看 |
GET PING Trace Dig |
|
辽宁阜新市联通 |
联通 |
辽宁 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
208.614ms |
190.673ms |
195.04ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=192ms TTL=50 Reply from 38.49.39.136: bytes=32 time=195ms TTL=50 Reply from 38.49.39.136: bytes=32 time=195ms TTL=50 Reply from 38.49.39.136: bytes=32 time=192ms TTL=50 Reply from 38.49.39.136: bytes=32 time=194ms TTL=50 Reply from 38.49.39.136: bytes=32 time=196ms TTL=50 Reply from 38.49.39.136: bytes=32 time=193ms TTL=50 Reply from 38.49.39.136: bytes=32 time=209ms TTL=50 Reply from 38.49.39.136: bytes=32 time=191ms TTL=50 Reply from 38.49.39.136: bytes=32 time=195ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 191ms, Maximum = 209ms, Average = 195ms查看 |
GET PING Trace Dig |
|
云南大理白族自治州电信 |
电信 |
云南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
197.52ms |
190.419ms |
192.872ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=190ms TTL=51 Reply from 38.49.39.136: bytes=32 time=191ms TTL=51 Reply from 38.49.39.136: bytes=32 time=193ms TTL=51 Reply from 38.49.39.136: bytes=32 time=194ms TTL=51 Reply from 38.49.39.136: bytes=32 time=194ms TTL=51 Reply from 38.49.39.136: bytes=32 time=198ms TTL=51 Reply from 38.49.39.136: bytes=32 time=191ms TTL=51 Reply from 38.49.39.136: bytes=32 time=194ms TTL=51 Reply from 38.49.39.136: bytes=32 time=193ms TTL=51 Reply from 38.49.39.136: bytes=32 time=191ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 190ms, Maximum = 198ms, Average = 193ms查看 |
GET PING Trace Dig |
|
辽宁沈阳市联通 |
联通 |
辽宁 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
206.956ms |
189.361ms |
192.566ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=190ms TTL=49 Reply from 38.49.39.136: bytes=32 time=190ms TTL=49 Reply from 38.49.39.136: bytes=32 time=189ms TTL=49 Reply from 38.49.39.136: bytes=32 time=194ms TTL=49 Reply from 38.49.39.136: bytes=32 time=190ms TTL=49 Reply from 38.49.39.136: bytes=32 time=193ms TTL=49 Reply from 38.49.39.136: bytes=32 time=207ms TTL=49 Reply from 38.49.39.136: bytes=32 time=191ms TTL=49 Reply from 38.49.39.136: bytes=32 time=190ms TTL=49 Reply from 38.49.39.136: bytes=32 time=191ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 189ms, Maximum = 207ms, Average = 193ms查看 |
GET PING Trace Dig |
|
新疆昌吉回族自治州电信 |
电信 |
新疆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
191.14ms |
190.92ms |
191.018ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=191ms TTL=51 Reply from 38.49.39.136: bytes=32 time=191ms TTL=51 Reply from 38.49.39.136: bytes=32 time=191ms TTL=51 Reply from 38.49.39.136: bytes=32 time=191ms TTL=51 Reply from 38.49.39.136: bytes=32 time=191ms TTL=51 Reply from 38.49.39.136: bytes=32 time=191ms TTL=51 Reply from 38.49.39.136: bytes=32 time=191ms TTL=51 Reply from 38.49.39.136: bytes=32 time=191ms TTL=51 Reply from 38.49.39.136: bytes=32 time=191ms TTL=51 Reply from 38.49.39.136: bytes=32 time=191ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 191ms, Maximum = 191ms, Average = 191ms查看 |
GET PING Trace Dig |
|
四川德阳市联通 |
联通 |
四川 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
251.483ms |
179.502ms |
190.733ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=181ms TTL=50 Reply from 38.49.39.136: bytes=32 time=206ms TTL=50 Reply from 38.49.39.136: bytes=32 time=180ms TTL=50 Reply from 38.49.39.136: bytes=32 time=180ms TTL=50 Reply from 38.49.39.136: bytes=32 time=181ms TTL=50 Reply from 38.49.39.136: bytes=32 time=184ms TTL=50 Reply from 38.49.39.136: bytes=32 time=181ms TTL=50 Reply from 38.49.39.136: bytes=32 time=251ms TTL=50 Reply from 38.49.39.136: bytes=32 time=180ms TTL=50 Reply from 38.49.39.136: bytes=32 time=184ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 180ms, Maximum = 251ms, Average = 191ms查看 |
GET PING Trace Dig |
|
辽宁大连市电信 |
电信 |
辽宁 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
200.062ms |
179.345ms |
189.725ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=200ms TTL=50 Reply from 38.49.39.136: bytes=32 time=179ms TTL=50 Reply from 38.49.39.136: bytes=32 time=188ms TTL=50 Reply from 38.49.39.136: bytes=32 time=196ms TTL=50 Reply from 38.49.39.136: bytes=32 time=198ms TTL=50 Reply from 38.49.39.136: bytes=32 time=191ms TTL=50 Reply from 38.49.39.136: bytes=32 time=185ms TTL=50 Reply from 38.49.39.136: bytes=32 time=186ms TTL=50 Reply from 38.49.39.136: bytes=32 time=182ms TTL=50 Reply from 38.49.39.136: bytes=32 time=191ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 179ms, Maximum = 200ms, Average = 190ms查看 |
GET PING Trace Dig |
|
内蒙古呼和浩特电信 |
电信 |
内蒙古 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
190.661ms |
188.422ms |
189.54ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=191ms TTL=47 Reply from 38.49.39.136: bytes=32 time=189ms TTL=47 Reply from 38.49.39.136: bytes=32 time=188ms TTL=47 Reply from 38.49.39.136: bytes=32 time=191ms TTL=47 Reply from 38.49.39.136: bytes=32 time=189ms TTL=47 Reply from 38.49.39.136: bytes=32 time=190ms TTL=47 Reply from 38.49.39.136: bytes=32 time=189ms TTL=47 Reply from 38.49.39.136: bytes=32 time=189ms TTL=47 Reply from 38.49.39.136: bytes=32 time=190ms TTL=47 Reply from 38.49.39.136: bytes=32 time=190ms TTL=47
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 188ms, Maximum = 191ms, Average = 190ms查看 |
GET PING Trace Dig |
|
西藏拉萨市电信 |
电信 |
西藏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
190.543ms |
186.083ms |
187.281ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=191ms TTL=49 Reply from 38.49.39.136: bytes=32 time=188ms TTL=49 Reply from 38.49.39.136: bytes=32 time=186ms TTL=49 Reply from 38.49.39.136: bytes=32 time=186ms TTL=49 Reply from 38.49.39.136: bytes=32 time=187ms TTL=49 Reply from 38.49.39.136: bytes=32 time=186ms TTL=49 Reply from 38.49.39.136: bytes=32 time=187ms TTL=49 Reply from 38.49.39.136: bytes=32 time=186ms TTL=49 Reply from 38.49.39.136: bytes=32 time=187ms TTL=49 Reply from 38.49.39.136: bytes=32 time=188ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 186ms, Maximum = 191ms, Average = 187ms查看 |
GET PING Trace Dig |
|
吉林长春移动 |
移动 |
吉林 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
187.172ms |
184.526ms |
185.035ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=186ms TTL=49 Reply from 38.49.39.136: bytes=32 time=185ms TTL=49 Reply from 38.49.39.136: bytes=32 time=185ms TTL=49 Reply from 38.49.39.136: bytes=32 time=185ms TTL=49 Reply from 38.49.39.136: bytes=32 time=185ms TTL=49 Reply from 38.49.39.136: bytes=32 time=185ms TTL=49 Reply from 38.49.39.136: bytes=32 time=185ms TTL=49 Reply from 38.49.39.136: bytes=32 time=187ms TTL=49 Reply from 38.49.39.136: bytes=32 time=185ms TTL=49 Reply from 38.49.39.136: bytes=32 time=185ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 185ms, Maximum = 187ms, Average = 185ms查看 |
GET PING Trace Dig |
|
北京北京市联通 |
联通 |
北京 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
192.448ms |
181.384ms |
184.713ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=192ms TTL=51 Reply from 38.49.39.136: bytes=32 time=186ms TTL=51 Reply from 38.49.39.136: bytes=32 time=181ms TTL=51 Reply from 38.49.39.136: bytes=32 time=182ms TTL=51 Reply from 38.49.39.136: bytes=32 time=181ms TTL=51 Reply from 38.49.39.136: bytes=32 time=181ms TTL=51 Reply from 38.49.39.136: bytes=32 time=182ms TTL=51 Reply from 38.49.39.136: bytes=32 time=187ms TTL=51 Reply from 38.49.39.136: bytes=32 time=192ms TTL=51 Reply from 38.49.39.136: bytes=32 time=182ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 181ms, Maximum = 192ms, Average = 185ms查看 |
GET PING Trace Dig |
|
上海上海市移动 |
移动 |
上海 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
233.029ms |
170.499ms |
184.696ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=170ms TTL=51 Reply from 38.49.39.136: bytes=32 time=172ms TTL=51 Reply from 38.49.39.136: bytes=32 time=171ms TTL=51 Reply from 38.49.39.136: bytes=32 time=171ms TTL=51 Reply from 38.49.39.136: bytes=32 time=171ms TTL=51 Reply from 38.49.39.136: bytes=32 time=171ms TTL=51 Reply from 38.49.39.136: bytes=32 time=208ms TTL=51 Reply from 38.49.39.136: bytes=32 time=233ms TTL=51 Reply from 38.49.39.136: bytes=32 time=202ms TTL=51 Reply from 38.49.39.136: bytes=32 time=177ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 170ms, Maximum = 233ms, Average = 185ms查看 |
GET PING Trace Dig |
|
山西运城市联通 |
联通 |
山西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
190.751ms |
182.523ms |
184.686ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=184ms TTL=51 Reply from 38.49.39.136: bytes=32 time=185ms TTL=51 Reply from 38.49.39.136: bytes=32 time=183ms TTL=51 Reply from 38.49.39.136: bytes=32 time=186ms TTL=51 Reply from 38.49.39.136: bytes=32 time=183ms TTL=51 Reply from 38.49.39.136: bytes=32 time=191ms TTL=51 Reply from 38.49.39.136: bytes=32 time=184ms TTL=51 Reply from 38.49.39.136: bytes=32 time=185ms TTL=51 Reply from 38.49.39.136: bytes=32 time=184ms TTL=51 Reply from 38.49.39.136: bytes=32 time=184ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 183ms, Maximum = 191ms, Average = 185ms查看 |
GET PING Trace Dig |
|
内蒙古呼和浩特移动 |
移动 |
内蒙古 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
185.081ms |
184.258ms |
184.68ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=185ms TTL=47 Reply from 38.49.39.136: bytes=32 time=185ms TTL=47 Reply from 38.49.39.136: bytes=32 time=184ms TTL=47 Reply from 38.49.39.136: bytes=32 time=185ms TTL=47 Reply from 38.49.39.136: bytes=32 time=184ms TTL=47 Reply from 38.49.39.136: bytes=32 time=184ms TTL=47 Reply from 38.49.39.136: bytes=32 time=185ms TTL=47 Reply from 38.49.39.136: bytes=32 time=184ms TTL=47 Reply from 38.49.39.136: bytes=32 time=185ms TTL=47 Reply from 38.49.39.136: bytes=32 time=185ms TTL=47
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 184ms, Maximum = 185ms, Average = 185ms查看 |
GET PING Trace Dig |
|
天津天津市电信 |
电信 |
天津 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
187.939ms |
183.779ms |
184.589ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=188ms TTL=48 Reply from 38.49.39.136: bytes=32 time=184ms TTL=48 Reply from 38.49.39.136: bytes=32 time=185ms TTL=48 Reply from 38.49.39.136: bytes=32 time=184ms TTL=48 Reply from 38.49.39.136: bytes=32 time=184ms TTL=48 Reply from 38.49.39.136: bytes=32 time=184ms TTL=48 Reply from 38.49.39.136: bytes=32 time=184ms TTL=48 Reply from 38.49.39.136: bytes=32 time=185ms TTL=48 Reply from 38.49.39.136: bytes=32 time=184ms TTL=48 Reply from 38.49.39.136: bytes=32 time=184ms TTL=48
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 184ms, Maximum = 188ms, Average = 185ms查看 |
GET PING Trace Dig |
|
河南郑州市电信 |
电信 |
河南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
184.803ms |
184.124ms |
184.371ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=185ms TTL=48 Reply from 38.49.39.136: bytes=32 time=184ms TTL=48 Reply from 38.49.39.136: bytes=32 time=184ms TTL=48 Reply from 38.49.39.136: bytes=32 time=184ms TTL=48 Reply from 38.49.39.136: bytes=32 time=185ms TTL=48 Reply from 38.49.39.136: bytes=32 time=184ms TTL=48 Reply from 38.49.39.136: bytes=32 time=185ms TTL=48 Reply from 38.49.39.136: bytes=32 time=184ms TTL=48 Reply from 38.49.39.136: bytes=32 time=185ms TTL=48 Reply from 38.49.39.136: bytes=32 time=184ms TTL=48
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 184ms, Maximum = 185ms, Average = 184ms查看 |
GET PING Trace Dig |
|
河北廊坊市移动 |
移动 |
河北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
9 |
1 |
190.1ms |
181.434ms |
183.84ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=190ms TTL=42 Reply from 38.49.39.136: bytes=32 time=182ms TTL=42 Reply from 38.49.39.136: bytes=32 time=185ms TTL=42 Reply from 38.49.39.136: bytes=32 time=184ms TTL=42 Reply from 38.49.39.136: bytes=32 time=182ms TTL=42 Reply from 38.49.39.136: bytes=32 time=182ms TTL=42 Reply from 38.49.39.136: bytes=32 time=183ms TTL=42 Request timed out. Reply from 38.49.39.136: bytes=32 time=186ms TTL=42 Reply from 38.49.39.136: bytes=32 time=181ms TTL=42
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 9, Lost = 1 (10% loss), Approximate round trip times in milli-seconds: Minimum = 181ms, Maximum = 190ms, Average = 184ms查看 |
GET PING Trace Dig |
|
陕西渭南市联通 |
联通 |
陕西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
184.098ms |
183.442ms |
183.729ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=184ms TTL=51 Reply from 38.49.39.136: bytes=32 time=184ms TTL=51 Reply from 38.49.39.136: bytes=32 time=184ms TTL=51 Reply from 38.49.39.136: bytes=32 time=184ms TTL=51 Reply from 38.49.39.136: bytes=32 time=183ms TTL=51 Reply from 38.49.39.136: bytes=32 time=184ms TTL=51 Reply from 38.49.39.136: bytes=32 time=183ms TTL=51 Reply from 38.49.39.136: bytes=32 time=184ms TTL=51 Reply from 38.49.39.136: bytes=32 time=184ms TTL=51 Reply from 38.49.39.136: bytes=32 time=184ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 183ms, Maximum = 184ms, Average = 184ms查看 |
GET PING Trace Dig |
|
广西玉林移动 |
移动 |
广西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
221.501ms |
175.163ms |
182.719ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=181ms TTL=49 Reply from 38.49.39.136: bytes=32 time=176ms TTL=49 Reply from 38.49.39.136: bytes=32 time=222ms TTL=49 Reply from 38.49.39.136: bytes=32 time=176ms TTL=49 Reply from 38.49.39.136: bytes=32 time=184ms TTL=49 Reply from 38.49.39.136: bytes=32 time=175ms TTL=49 Reply from 38.49.39.136: bytes=32 time=181ms TTL=49 Reply from 38.49.39.136: bytes=32 time=177ms TTL=49 Reply from 38.49.39.136: bytes=32 time=175ms TTL=49 Reply from 38.49.39.136: bytes=32 time=180ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 175ms, Maximum = 222ms, Average = 183ms查看 |
GET PING Trace Dig |
|
天津天津市联通 |
联通 |
天津 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
205.285ms |
178.026ms |
182.639ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=183ms TTL=48 Reply from 38.49.39.136: bytes=32 time=205ms TTL=48 Reply from 38.49.39.136: bytes=32 time=179ms TTL=48 Reply from 38.49.39.136: bytes=32 time=179ms TTL=48 Reply from 38.49.39.136: bytes=32 time=181ms TTL=48 Reply from 38.49.39.136: bytes=32 time=179ms TTL=48 Reply from 38.49.39.136: bytes=32 time=179ms TTL=48 Reply from 38.49.39.136: bytes=32 time=178ms TTL=48 Reply from 38.49.39.136: bytes=32 time=178ms TTL=48 Reply from 38.49.39.136: bytes=32 time=184ms TTL=48
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 178ms, Maximum = 205ms, Average = 183ms查看 |
GET PING Trace Dig |
|
江苏泰州市联通 |
联通 |
江苏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
182.755ms |
182.242ms |
182.476ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=182ms TTL=49 Reply from 38.49.39.136: bytes=32 time=183ms TTL=49 Reply from 38.49.39.136: bytes=32 time=182ms TTL=49 Reply from 38.49.39.136: bytes=32 time=182ms TTL=49 Reply from 38.49.39.136: bytes=32 time=182ms TTL=49 Reply from 38.49.39.136: bytes=32 time=183ms TTL=49 Reply from 38.49.39.136: bytes=32 time=182ms TTL=49 Reply from 38.49.39.136: bytes=32 time=183ms TTL=49 Reply from 38.49.39.136: bytes=32 time=182ms TTL=49 Reply from 38.49.39.136: bytes=32 time=183ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 182ms, Maximum = 183ms, Average = 182ms查看 |
GET PING Trace Dig |
|
印度尼西亚国外 |
国外 |
印度尼西亚 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
182.657ms |
181.657ms |
182.275ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=182ms TTL=50 Reply from 38.49.39.136: bytes=32 time=183ms TTL=50 Reply from 38.49.39.136: bytes=32 time=183ms TTL=50 Reply from 38.49.39.136: bytes=32 time=182ms TTL=50 Reply from 38.49.39.136: bytes=32 time=182ms TTL=50 Reply from 38.49.39.136: bytes=32 time=182ms TTL=50 Reply from 38.49.39.136: bytes=32 time=183ms TTL=50 Reply from 38.49.39.136: bytes=32 time=183ms TTL=50 Reply from 38.49.39.136: bytes=32 time=182ms TTL=50 Reply from 38.49.39.136: bytes=32 time=183ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 182ms, Maximum = 183ms, Average = 182ms查看 |
GET PING Trace Dig |
|
黑龙江伊春市移动 |
移动 |
黑龙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
182.901ms |
181.5ms |
181.984ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=182ms TTL=48 Reply from 38.49.39.136: bytes=32 time=182ms TTL=48 Reply from 38.49.39.136: bytes=32 time=182ms TTL=48 Reply from 38.49.39.136: bytes=32 time=182ms TTL=48 Reply from 38.49.39.136: bytes=32 time=182ms TTL=48 Reply from 38.49.39.136: bytes=32 time=182ms TTL=48 Reply from 38.49.39.136: bytes=32 time=182ms TTL=48 Reply from 38.49.39.136: bytes=32 time=183ms TTL=48 Reply from 38.49.39.136: bytes=32 time=183ms TTL=48 Reply from 38.49.39.136: bytes=32 time=182ms TTL=48
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 182ms, Maximum = 183ms, Average = 182ms查看 |
GET PING Trace Dig |
|
贵州毕节市电信 |
电信 |
贵州 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
188.867ms |
179.183ms |
181.316ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=180ms TTL=52 Reply from 38.49.39.136: bytes=32 time=179ms TTL=52 Reply from 38.49.39.136: bytes=32 time=184ms TTL=52 Reply from 38.49.39.136: bytes=32 time=179ms TTL=52 Reply from 38.49.39.136: bytes=32 time=180ms TTL=52 Reply from 38.49.39.136: bytes=32 time=182ms TTL=52 Reply from 38.49.39.136: bytes=32 time=180ms TTL=52 Reply from 38.49.39.136: bytes=32 time=180ms TTL=52 Reply from 38.49.39.136: bytes=32 time=180ms TTL=52 Reply from 38.49.39.136: bytes=32 time=189ms TTL=52
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 179ms, Maximum = 189ms, Average = 181ms查看 |
GET PING Trace Dig |
|
重庆重庆市移动 |
移动 |
重庆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
197.726ms |
172.797ms |
181.281ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=175ms TTL=49 Reply from 38.49.39.136: bytes=32 time=197ms TTL=49 Reply from 38.49.39.136: bytes=32 time=198ms TTL=49 Reply from 38.49.39.136: bytes=32 time=179ms TTL=49 Reply from 38.49.39.136: bytes=32 time=176ms TTL=49 Reply from 38.49.39.136: bytes=32 time=173ms TTL=49 Reply from 38.49.39.136: bytes=32 time=182ms TTL=49 Reply from 38.49.39.136: bytes=32 time=177ms TTL=49 Reply from 38.49.39.136: bytes=32 time=174ms TTL=49 Reply from 38.49.39.136: bytes=32 time=181ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 173ms, Maximum = 198ms, Average = 181ms查看 |
GET PING Trace Dig |
|
黑龙江哈尔滨市电信 |
电信 |
黑龙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
181.422ms |
180.381ms |
180.767ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=181ms TTL=46 Reply from 38.49.39.136: bytes=32 time=180ms TTL=46 Reply from 38.49.39.136: bytes=32 time=181ms TTL=46 Reply from 38.49.39.136: bytes=32 time=181ms TTL=46 Reply from 38.49.39.136: bytes=32 time=181ms TTL=46 Reply from 38.49.39.136: bytes=32 time=180ms TTL=46 Reply from 38.49.39.136: bytes=32 time=181ms TTL=46 Reply from 38.49.39.136: bytes=32 time=181ms TTL=46 Reply from 38.49.39.136: bytes=32 time=181ms TTL=46 Reply from 38.49.39.136: bytes=32 time=181ms TTL=46
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 180ms, Maximum = 181ms, Average = 181ms查看 |
GET PING Trace Dig |
|
云南红河哈尼族彝族自治州其他 |
其他 |
云南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
194.293ms |
177.445ms |
180.634ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=182ms TTL=49 Reply from 38.49.39.136: bytes=32 time=179ms TTL=49 Reply from 38.49.39.136: bytes=32 time=178ms TTL=49 Reply from 38.49.39.136: bytes=32 time=185ms TTL=49 Reply from 38.49.39.136: bytes=32 time=177ms TTL=49 Reply from 38.49.39.136: bytes=32 time=178ms TTL=49 Reply from 38.49.39.136: bytes=32 time=178ms TTL=49 Reply from 38.49.39.136: bytes=32 time=178ms TTL=49 Reply from 38.49.39.136: bytes=32 time=194ms TTL=49 Reply from 38.49.39.136: bytes=32 time=178ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 177ms, Maximum = 194ms, Average = 181ms查看 |
GET PING Trace Dig |
|
北京北京市联通 |
联通 |
北京 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
181.859ms |
180.038ms |
180.469ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=180ms TTL=43 Reply from 38.49.39.136: bytes=32 time=180ms TTL=43 Reply from 38.49.39.136: bytes=32 time=181ms TTL=43 Reply from 38.49.39.136: bytes=32 time=180ms TTL=43 Reply from 38.49.39.136: bytes=32 time=180ms TTL=43 Reply from 38.49.39.136: bytes=32 time=181ms TTL=43 Reply from 38.49.39.136: bytes=32 time=181ms TTL=43 Reply from 38.49.39.136: bytes=32 time=180ms TTL=43 Reply from 38.49.39.136: bytes=32 time=180ms TTL=43 Reply from 38.49.39.136: bytes=32 time=182ms TTL=43
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 180ms, Maximum = 182ms, Average = 180ms查看 |
GET PING Trace Dig |
|
贵州遵义市联通 |
联通 |
贵州 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
180.342ms |
180.142ms |
180.248ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=180ms TTL=52 Reply from 38.49.39.136: bytes=32 time=180ms TTL=52 Reply from 38.49.39.136: bytes=32 time=180ms TTL=52 Reply from 38.49.39.136: bytes=32 time=180ms TTL=52 Reply from 38.49.39.136: bytes=32 time=180ms TTL=52 Reply from 38.49.39.136: bytes=32 time=180ms TTL=52 Reply from 38.49.39.136: bytes=32 time=180ms TTL=52 Reply from 38.49.39.136: bytes=32 time=180ms TTL=52 Reply from 38.49.39.136: bytes=32 time=180ms TTL=52 Reply from 38.49.39.136: bytes=32 time=180ms TTL=52
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 180ms, Maximum = 180ms, Average = 180ms查看 |
GET PING Trace Dig |
|
四川德阳市电信 |
电信 |
四川 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
211.163ms |
173.542ms |
179.854ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=174ms TTL=52 Reply from 38.49.39.136: bytes=32 time=175ms TTL=52 Reply from 38.49.39.136: bytes=32 time=175ms TTL=52 Reply from 38.49.39.136: bytes=32 time=178ms TTL=52 Reply from 38.49.39.136: bytes=32 time=175ms TTL=52 Reply from 38.49.39.136: bytes=32 time=178ms TTL=52 Reply from 38.49.39.136: bytes=32 time=211ms TTL=52 Reply from 38.49.39.136: bytes=32 time=180ms TTL=52 Reply from 38.49.39.136: bytes=32 time=175ms TTL=52 Reply from 38.49.39.136: bytes=32 time=178ms TTL=52
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 174ms, Maximum = 211ms, Average = 180ms查看 |
GET PING Trace Dig |
|
湖北襄阳市联通 |
联通 |
湖北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
179.901ms |
179.502ms |
179.652ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=180ms TTL=51 Reply from 38.49.39.136: bytes=32 time=180ms TTL=51 Reply from 38.49.39.136: bytes=32 time=180ms TTL=51 Reply from 38.49.39.136: bytes=32 time=180ms TTL=51 Reply from 38.49.39.136: bytes=32 time=180ms TTL=51 Reply from 38.49.39.136: bytes=32 time=180ms TTL=51 Reply from 38.49.39.136: bytes=32 time=180ms TTL=51 Reply from 38.49.39.136: bytes=32 time=180ms TTL=51 Reply from 38.49.39.136: bytes=32 time=180ms TTL=51 Reply from 38.49.39.136: bytes=32 time=180ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 180ms, Maximum = 180ms, Average = 180ms查看 |
GET PING Trace Dig |
|
湖南长沙联通 |
联通 |
湖南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
271.177ms |
155.466ms |
179.517ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=160ms TTL=49 Reply from 38.49.39.136: bytes=32 time=158ms TTL=49 Reply from 38.49.39.136: bytes=32 time=185ms TTL=49 Reply from 38.49.39.136: bytes=32 time=156ms TTL=49 Reply from 38.49.39.136: bytes=32 time=202ms TTL=49 Reply from 38.49.39.136: bytes=32 time=195ms TTL=49 Reply from 38.49.39.136: bytes=32 time=271ms TTL=49 Reply from 38.49.39.136: bytes=32 time=158ms TTL=49 Reply from 38.49.39.136: bytes=32 time=155ms TTL=49 Reply from 38.49.39.136: bytes=32 time=155ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 155ms, Maximum = 271ms, Average = 180ms查看 |
GET PING Trace Dig |
|
河南周口市联通 |
联通 |
河南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
179.582ms |
179.021ms |
179.216ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=179ms TTL=49 Reply from 38.49.39.136: bytes=32 time=179ms TTL=49 Reply from 38.49.39.136: bytes=32 time=179ms TTL=49 Reply from 38.49.39.136: bytes=32 time=179ms TTL=49 Reply from 38.49.39.136: bytes=32 time=179ms TTL=49 Reply from 38.49.39.136: bytes=32 time=179ms TTL=49 Reply from 38.49.39.136: bytes=32 time=179ms TTL=49 Reply from 38.49.39.136: bytes=32 time=180ms TTL=49 Reply from 38.49.39.136: bytes=32 time=179ms TTL=49 Reply from 38.49.39.136: bytes=32 time=179ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 179ms, Maximum = 180ms, Average = 179ms查看 |
GET PING Trace Dig |
|
重庆重庆市联通 |
联通 |
重庆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
180.94ms |
178.404ms |
178.776ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=179ms TTL=50 Reply from 38.49.39.136: bytes=32 time=179ms TTL=50 Reply from 38.49.39.136: bytes=32 time=178ms TTL=50 Reply from 38.49.39.136: bytes=32 time=178ms TTL=50 Reply from 38.49.39.136: bytes=32 time=179ms TTL=50 Reply from 38.49.39.136: bytes=32 time=178ms TTL=50 Reply from 38.49.39.136: bytes=32 time=178ms TTL=50 Reply from 38.49.39.136: bytes=32 time=181ms TTL=50 Reply from 38.49.39.136: bytes=32 time=179ms TTL=50 Reply from 38.49.39.136: bytes=32 time=179ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 178ms, Maximum = 181ms, Average = 179ms查看 |
GET PING Trace Dig |
|
西藏拉萨市电信 |
电信 |
西藏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
184.785ms |
176.27ms |
178.362ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=176ms TTL=49 Reply from 38.49.39.136: bytes=32 time=177ms TTL=49 Reply from 38.49.39.136: bytes=32 time=176ms TTL=49 Reply from 38.49.39.136: bytes=32 time=177ms TTL=49 Reply from 38.49.39.136: bytes=32 time=179ms TTL=49 Reply from 38.49.39.136: bytes=32 time=178ms TTL=49 Reply from 38.49.39.136: bytes=32 time=185ms TTL=49 Reply from 38.49.39.136: bytes=32 time=177ms TTL=49 Reply from 38.49.39.136: bytes=32 time=176ms TTL=49 Reply from 38.49.39.136: bytes=32 time=182ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 176ms, Maximum = 185ms, Average = 178ms查看 |
GET PING Trace Dig |
|
广西南宁市联通 |
联通 |
广西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
178.115ms |
177.426ms |
177.844ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=178ms TTL=47 Reply from 38.49.39.136: bytes=32 time=178ms TTL=47 Reply from 38.49.39.136: bytes=32 time=178ms TTL=47 Reply from 38.49.39.136: bytes=32 time=178ms TTL=47 Reply from 38.49.39.136: bytes=32 time=178ms TTL=47 Reply from 38.49.39.136: bytes=32 time=178ms TTL=47 Reply from 38.49.39.136: bytes=32 time=178ms TTL=47 Reply from 38.49.39.136: bytes=32 time=177ms TTL=47 Reply from 38.49.39.136: bytes=32 time=178ms TTL=47 Reply from 38.49.39.136: bytes=32 time=178ms TTL=47
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 177ms, Maximum = 178ms, Average = 178ms查看 |
GET PING Trace Dig |
|
青海西宁市电信 |
电信 |
青海 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
179.332ms |
176.114ms |
177.595ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=177ms TTL=50 Reply from 38.49.39.136: bytes=32 time=177ms TTL=50 Reply from 38.49.39.136: bytes=32 time=179ms TTL=50 Reply from 38.49.39.136: bytes=32 time=177ms TTL=50 Reply from 38.49.39.136: bytes=32 time=178ms TTL=50 Reply from 38.49.39.136: bytes=32 time=179ms TTL=50 Reply from 38.49.39.136: bytes=32 time=177ms TTL=50 Reply from 38.49.39.136: bytes=32 time=176ms TTL=50 Reply from 38.49.39.136: bytes=32 time=177ms TTL=50 Reply from 38.49.39.136: bytes=32 time=178ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 176ms, Maximum = 179ms, Average = 178ms查看 |
GET PING Trace Dig |
|
四川眉山市电信 |
电信 |
四川 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
177.886ms |
177.221ms |
177.561ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=178ms TTL=52 Reply from 38.49.39.136: bytes=32 time=178ms TTL=52 Reply from 38.49.39.136: bytes=32 time=177ms TTL=52 Reply from 38.49.39.136: bytes=32 time=178ms TTL=52 Reply from 38.49.39.136: bytes=32 time=177ms TTL=52 Reply from 38.49.39.136: bytes=32 time=178ms TTL=52 Reply from 38.49.39.136: bytes=32 time=178ms TTL=52 Reply from 38.49.39.136: bytes=32 time=177ms TTL=52 Reply from 38.49.39.136: bytes=32 time=177ms TTL=52 Reply from 38.49.39.136: bytes=32 time=178ms TTL=52
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 177ms, Maximum = 178ms, Average = 178ms查看 |
GET PING Trace Dig |
|
河南安阳市联通 |
联通 |
河南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
179.884ms |
175.923ms |
177.273ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=177ms TTL=51 Reply from 38.49.39.136: bytes=32 time=178ms TTL=51 Reply from 38.49.39.136: bytes=32 time=178ms TTL=51 Reply from 38.49.39.136: bytes=32 time=178ms TTL=51 Reply from 38.49.39.136: bytes=32 time=180ms TTL=51 Reply from 38.49.39.136: bytes=32 time=176ms TTL=51 Reply from 38.49.39.136: bytes=32 time=176ms TTL=51 Reply from 38.49.39.136: bytes=32 time=178ms TTL=51 Reply from 38.49.39.136: bytes=32 time=178ms TTL=51 Reply from 38.49.39.136: bytes=32 time=176ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 176ms, Maximum = 180ms, Average = 177ms查看 |
GET PING Trace Dig |
|
黑龙江哈尔滨市移动 |
移动 |
黑龙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
179.679ms |
175.68ms |
177.02ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=179ms TTL=50 Reply from 38.49.39.136: bytes=32 time=176ms TTL=50 Reply from 38.49.39.136: bytes=32 time=177ms TTL=50 Reply from 38.49.39.136: bytes=32 time=176ms TTL=50 Reply from 38.49.39.136: bytes=32 time=180ms TTL=50 Reply from 38.49.39.136: bytes=32 time=176ms TTL=50 Reply from 38.49.39.136: bytes=32 time=177ms TTL=50 Reply from 38.49.39.136: bytes=32 time=179ms TTL=50 Reply from 38.49.39.136: bytes=32 time=177ms TTL=50 Reply from 38.49.39.136: bytes=32 time=176ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 176ms, Maximum = 180ms, Average = 177ms查看 |
GET PING Trace Dig |
|
云南昆明市电信 |
电信 |
云南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
178.398ms |
176.424ms |
176.902ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=178ms TTL=49 Reply from 38.49.39.136: bytes=32 time=177ms TTL=49 Reply from 38.49.39.136: bytes=32 time=176ms TTL=49 Reply from 38.49.39.136: bytes=32 time=177ms TTL=49 Reply from 38.49.39.136: bytes=32 time=177ms TTL=49 Reply from 38.49.39.136: bytes=32 time=177ms TTL=49 Reply from 38.49.39.136: bytes=32 time=178ms TTL=49 Reply from 38.49.39.136: bytes=32 time=177ms TTL=49 Reply from 38.49.39.136: bytes=32 time=177ms TTL=49 Reply from 38.49.39.136: bytes=32 time=177ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 176ms, Maximum = 178ms, Average = 177ms查看 |
GET PING Trace Dig |
|
吉林长春电信 |
电信 |
吉林 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
176.86ms |
176.6ms |
176.664ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=177ms TTL=51 Reply from 38.49.39.136: bytes=32 time=177ms TTL=51 Reply from 38.49.39.136: bytes=32 time=177ms TTL=51 Reply from 38.49.39.136: bytes=32 time=177ms TTL=51 Reply from 38.49.39.136: bytes=32 time=177ms TTL=51 Reply from 38.49.39.136: bytes=32 time=177ms TTL=51 Reply from 38.49.39.136: bytes=32 time=177ms TTL=51 Reply from 38.49.39.136: bytes=32 time=177ms TTL=51 Reply from 38.49.39.136: bytes=32 time=177ms TTL=51 Reply from 38.49.39.136: bytes=32 time=177ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 177ms, Maximum = 177ms, Average = 177ms查看 |
GET PING Trace Dig |
|
湖南永州市电信 |
电信 |
湖南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
185.963ms |
172.823ms |
176.498ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=183ms TTL=50 Reply from 38.49.39.136: bytes=32 time=175ms TTL=50 Reply from 38.49.39.136: bytes=32 time=173ms TTL=50 Reply from 38.49.39.136: bytes=32 time=174ms TTL=50 Reply from 38.49.39.136: bytes=32 time=186ms TTL=50 Reply from 38.49.39.136: bytes=32 time=173ms TTL=50 Reply from 38.49.39.136: bytes=32 time=179ms TTL=50 Reply from 38.49.39.136: bytes=32 time=173ms TTL=50 Reply from 38.49.39.136: bytes=32 time=176ms TTL=50 Reply from 38.49.39.136: bytes=32 time=173ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 173ms, Maximum = 186ms, Average = 176ms查看 |
GET PING Trace Dig |
|
江西南昌市联通 |
联通 |
江西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
192.941ms |
174.182ms |
176.291ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=174ms TTL=51 Reply from 38.49.39.136: bytes=32 time=175ms TTL=51 Reply from 38.49.39.136: bytes=32 time=193ms TTL=51 Reply from 38.49.39.136: bytes=32 time=174ms TTL=51 Reply from 38.49.39.136: bytes=32 time=174ms TTL=51 Reply from 38.49.39.136: bytes=32 time=175ms TTL=51 Reply from 38.49.39.136: bytes=32 time=175ms TTL=51 Reply from 38.49.39.136: bytes=32 time=174ms TTL=51 Reply from 38.49.39.136: bytes=32 time=174ms TTL=51 Reply from 38.49.39.136: bytes=32 time=174ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 174ms, Maximum = 193ms, Average = 176ms查看 |
GET PING Trace Dig |
|
广东汕尾市移动 |
移动 |
广东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
184.602ms |
174.163ms |
176.02ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=174ms TTL=49 Reply from 38.49.39.136: bytes=32 time=175ms TTL=49 Reply from 38.49.39.136: bytes=32 time=174ms TTL=49 Reply from 38.49.39.136: bytes=32 time=178ms TTL=49 Reply from 38.49.39.136: bytes=32 time=176ms TTL=49 Reply from 38.49.39.136: bytes=32 time=174ms TTL=49 Reply from 38.49.39.136: bytes=32 time=185ms TTL=49 Reply from 38.49.39.136: bytes=32 time=175ms TTL=49 Reply from 38.49.39.136: bytes=32 time=174ms TTL=49 Reply from 38.49.39.136: bytes=32 time=174ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 174ms, Maximum = 185ms, Average = 176ms查看 |
GET PING Trace Dig |
|
云南红河哈尼族彝族自治州移动 |
移动 |
云南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
180.823ms |
174.563ms |
175.479ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=175ms TTL=48 Reply from 38.49.39.136: bytes=32 time=175ms TTL=48 Reply from 38.49.39.136: bytes=32 time=175ms TTL=48 Reply from 38.49.39.136: bytes=32 time=175ms TTL=48 Reply from 38.49.39.136: bytes=32 time=175ms TTL=48 Reply from 38.49.39.136: bytes=32 time=175ms TTL=48 Reply from 38.49.39.136: bytes=32 time=175ms TTL=48 Reply from 38.49.39.136: bytes=32 time=175ms TTL=48 Reply from 38.49.39.136: bytes=32 time=181ms TTL=48 Reply from 38.49.39.136: bytes=32 time=175ms TTL=48
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 175ms, Maximum = 181ms, Average = 175ms查看 |
GET PING Trace Dig |
|
甘肃武威移动 |
移动 |
甘肃 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
176.219ms |
174.279ms |
175.037ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=175ms TTL=47 Reply from 38.49.39.136: bytes=32 time=174ms TTL=47 Reply from 38.49.39.136: bytes=32 time=176ms TTL=47 Reply from 38.49.39.136: bytes=32 time=175ms TTL=47 Reply from 38.49.39.136: bytes=32 time=175ms TTL=47 Reply from 38.49.39.136: bytes=32 time=175ms TTL=47 Reply from 38.49.39.136: bytes=32 time=176ms TTL=47 Reply from 38.49.39.136: bytes=32 time=174ms TTL=47 Reply from 38.49.39.136: bytes=32 time=175ms TTL=47 Reply from 38.49.39.136: bytes=32 time=174ms TTL=47
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 174ms, Maximum = 176ms, Average = 175ms查看 |
GET PING Trace Dig |
|
山西太原市电信 |
电信 |
山西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
175.459ms |
174.819ms |
174.993ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=175ms TTL=50 Reply from 38.49.39.136: bytes=32 time=175ms TTL=50 Reply from 38.49.39.136: bytes=32 time=175ms TTL=50 Reply from 38.49.39.136: bytes=32 time=175ms TTL=50 Reply from 38.49.39.136: bytes=32 time=175ms TTL=50 Reply from 38.49.39.136: bytes=32 time=175ms TTL=50 Reply from 38.49.39.136: bytes=32 time=175ms TTL=50 Reply from 38.49.39.136: bytes=32 time=175ms TTL=50 Reply from 38.49.39.136: bytes=32 time=175ms TTL=50 Reply from 38.49.39.136: bytes=32 time=175ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 175ms, Maximum = 175ms, Average = 175ms查看 |
GET PING Trace Dig |
|
陕西西安市联通 |
联通 |
陕西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
175.259ms |
174.639ms |
174.804ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=175ms TTL=49 Reply from 38.49.39.136: bytes=32 time=175ms TTL=49 Reply from 38.49.39.136: bytes=32 time=175ms TTL=49 Reply from 38.49.39.136: bytes=32 time=175ms TTL=49 Reply from 38.49.39.136: bytes=32 time=175ms TTL=49 Reply from 38.49.39.136: bytes=32 time=175ms TTL=49 Reply from 38.49.39.136: bytes=32 time=175ms TTL=49 Reply from 38.49.39.136: bytes=32 time=175ms TTL=49 Reply from 38.49.39.136: bytes=32 time=175ms TTL=49 Reply from 38.49.39.136: bytes=32 time=175ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 175ms, Maximum = 175ms, Average = 175ms查看 |
GET PING Trace Dig |
|
美国国外 |
国外 |
美国 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
176.349ms |
173.964ms |
174.431ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=176ms TTL=50 Reply from 38.49.39.136: bytes=32 time=174ms TTL=50 Reply from 38.49.39.136: bytes=32 time=174ms TTL=50 Reply from 38.49.39.136: bytes=32 time=174ms TTL=50 Reply from 38.49.39.136: bytes=32 time=174ms TTL=50 Reply from 38.49.39.136: bytes=32 time=174ms TTL=50 Reply from 38.49.39.136: bytes=32 time=176ms TTL=50 Reply from 38.49.39.136: bytes=32 time=174ms TTL=50 Reply from 38.49.39.136: bytes=32 time=174ms TTL=50 Reply from 38.49.39.136: bytes=32 time=174ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 174ms, Maximum = 176ms, Average = 174ms查看 |
GET PING Trace Dig |
|
福建福州市移动 |
移动 |
福建 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
174.842ms |
173.141ms |
174.036ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=174ms TTL=48 Reply from 38.49.39.136: bytes=32 time=174ms TTL=48 Reply from 38.49.39.136: bytes=32 time=175ms TTL=48 Reply from 38.49.39.136: bytes=32 time=174ms TTL=48 Reply from 38.49.39.136: bytes=32 time=174ms TTL=48 Reply from 38.49.39.136: bytes=32 time=174ms TTL=48 Reply from 38.49.39.136: bytes=32 time=173ms TTL=48 Reply from 38.49.39.136: bytes=32 time=175ms TTL=48 Reply from 38.49.39.136: bytes=32 time=175ms TTL=48 Reply from 38.49.39.136: bytes=32 time=173ms TTL=48
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 173ms, Maximum = 175ms, Average = 174ms查看 |
GET PING Trace Dig |
|
天津天津市联通 |
联通 |
天津 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
179.287ms |
172.589ms |
173.981ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=173ms TTL=50 Reply from 38.49.39.136: bytes=32 time=176ms TTL=50 Reply from 38.49.39.136: bytes=32 time=175ms TTL=50 Reply from 38.49.39.136: bytes=32 time=173ms TTL=50 Reply from 38.49.39.136: bytes=32 time=173ms TTL=50 Reply from 38.49.39.136: bytes=32 time=173ms TTL=50 Reply from 38.49.39.136: bytes=32 time=173ms TTL=50 Reply from 38.49.39.136: bytes=32 time=173ms TTL=50 Reply from 38.49.39.136: bytes=32 time=174ms TTL=50 Reply from 38.49.39.136: bytes=32 time=179ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 173ms, Maximum = 179ms, Average = 174ms查看 |
GET PING Trace Dig |
|
湖北武汉市联通 |
联通 |
湖北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
174.02ms |
173.58ms |
173.792ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=174ms TTL=49 Reply from 38.49.39.136: bytes=32 time=174ms TTL=49 Reply from 38.49.39.136: bytes=32 time=174ms TTL=49 Reply from 38.49.39.136: bytes=32 time=174ms TTL=49 Reply from 38.49.39.136: bytes=32 time=174ms TTL=49 Reply from 38.49.39.136: bytes=32 time=174ms TTL=49 Reply from 38.49.39.136: bytes=32 time=174ms TTL=49 Reply from 38.49.39.136: bytes=32 time=174ms TTL=49 Reply from 38.49.39.136: bytes=32 time=174ms TTL=49 Reply from 38.49.39.136: bytes=32 time=174ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 174ms, Maximum = 174ms, Average = 174ms查看 |
GET PING Trace Dig |
|
广东云浮市电信 |
电信 |
广东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
206.659ms |
166.82ms |
173.401ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=173ms TTL=48 Reply from 38.49.39.136: bytes=32 time=170ms TTL=48 Reply from 38.49.39.136: bytes=32 time=207ms TTL=48 Reply from 38.49.39.136: bytes=32 time=176ms TTL=48 Reply from 38.49.39.136: bytes=32 time=171ms TTL=48 Reply from 38.49.39.136: bytes=32 time=167ms TTL=48 Reply from 38.49.39.136: bytes=32 time=167ms TTL=48 Reply from 38.49.39.136: bytes=32 time=168ms TTL=48 Reply from 38.49.39.136: bytes=32 time=167ms TTL=48 Reply from 38.49.39.136: bytes=32 time=167ms TTL=48
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 167ms, Maximum = 207ms, Average = 173ms查看 |
GET PING Trace Dig |
|
云南昆明市移动 |
移动 |
云南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
173.757ms |
173.075ms |
173.359ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=173ms TTL=52 Reply from 38.49.39.136: bytes=32 time=173ms TTL=52 Reply from 38.49.39.136: bytes=32 time=173ms TTL=52 Reply from 38.49.39.136: bytes=32 time=173ms TTL=52 Reply from 38.49.39.136: bytes=32 time=173ms TTL=52 Reply from 38.49.39.136: bytes=32 time=173ms TTL=52 Reply from 38.49.39.136: bytes=32 time=174ms TTL=52 Reply from 38.49.39.136: bytes=32 time=173ms TTL=52 Reply from 38.49.39.136: bytes=32 time=174ms TTL=52 Reply from 38.49.39.136: bytes=32 time=174ms TTL=52
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 173ms, Maximum = 174ms, Average = 173ms查看 |
GET PING Trace Dig |
|
广西梧州市联通 |
联通 |
广西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
173.681ms |
173.121ms |
173.289ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=174ms TTL=49 Reply from 38.49.39.136: bytes=32 time=173ms TTL=49 Reply from 38.49.39.136: bytes=32 time=173ms TTL=49 Reply from 38.49.39.136: bytes=32 time=173ms TTL=49 Reply from 38.49.39.136: bytes=32 time=173ms TTL=49 Reply from 38.49.39.136: bytes=32 time=173ms TTL=49 Reply from 38.49.39.136: bytes=32 time=173ms TTL=49 Reply from 38.49.39.136: bytes=32 time=173ms TTL=49 Reply from 38.49.39.136: bytes=32 time=173ms TTL=49 Reply from 38.49.39.136: bytes=32 time=173ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 173ms, Maximum = 174ms, Average = 173ms查看 |
GET PING Trace Dig |
|
四川成都市联通 |
联通 |
四川 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
173.14ms |
172.58ms |
172.722ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=173ms TTL=51 Reply from 38.49.39.136: bytes=32 time=173ms TTL=51 Reply from 38.49.39.136: bytes=32 time=173ms TTL=51 Reply from 38.49.39.136: bytes=32 time=173ms TTL=51 Reply from 38.49.39.136: bytes=32 time=173ms TTL=51 Reply from 38.49.39.136: bytes=32 time=173ms TTL=51 Reply from 38.49.39.136: bytes=32 time=173ms TTL=51 Reply from 38.49.39.136: bytes=32 time=173ms TTL=51 Reply from 38.49.39.136: bytes=32 time=173ms TTL=51 Reply from 38.49.39.136: bytes=32 time=173ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 173ms, Maximum = 173ms, Average = 173ms查看 |
GET PING Trace Dig |
|
陕西西安市电信 |
电信 |
陕西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
174.909ms |
171.115ms |
172.707ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=173ms TTL=48 Reply from 38.49.39.136: bytes=32 time=173ms TTL=48 Reply from 38.49.39.136: bytes=32 time=174ms TTL=48 Reply from 38.49.39.136: bytes=32 time=175ms TTL=48 Reply from 38.49.39.136: bytes=32 time=172ms TTL=48 Reply from 38.49.39.136: bytes=32 time=173ms TTL=48 Reply from 38.49.39.136: bytes=32 time=172ms TTL=48 Reply from 38.49.39.136: bytes=32 time=171ms TTL=48 Reply from 38.49.39.136: bytes=32 time=171ms TTL=48 Reply from 38.49.39.136: bytes=32 time=173ms TTL=48
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 171ms, Maximum = 175ms, Average = 173ms查看 |
GET PING Trace Dig |
|
贵州黔西南布依族苗族自治州移动 |
移动 |
贵州 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
183.361ms |
170.678ms |
172.658ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=183ms TTL=49 Reply from 38.49.39.136: bytes=32 time=172ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49 Reply from 38.49.39.136: bytes=32 time=177ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 171ms, Maximum = 183ms, Average = 173ms查看 |
GET PING Trace Dig |
|
内蒙古巴彦淖尔市电信 |
电信 |
内蒙古 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
173.5ms |
171.3ms |
171.922ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=172ms TTL=50 Reply from 38.49.39.136: bytes=32 time=174ms TTL=50 Reply from 38.49.39.136: bytes=32 time=172ms TTL=50 Reply from 38.49.39.136: bytes=32 time=171ms TTL=50 Reply from 38.49.39.136: bytes=32 time=172ms TTL=50 Reply from 38.49.39.136: bytes=32 time=172ms TTL=50 Reply from 38.49.39.136: bytes=32 time=172ms TTL=50 Reply from 38.49.39.136: bytes=32 time=171ms TTL=50 Reply from 38.49.39.136: bytes=32 time=172ms TTL=50 Reply from 38.49.39.136: bytes=32 time=171ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 171ms, Maximum = 174ms, Average = 172ms查看 |
GET PING Trace Dig |
|
宁夏银川电信 |
电信 |
宁夏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
187.899ms |
168.808ms |
171.902ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=188ms TTL=50 Reply from 38.49.39.136: bytes=32 time=170ms TTL=50 Reply from 38.49.39.136: bytes=32 time=170ms TTL=50 Reply from 38.49.39.136: bytes=32 time=171ms TTL=50 Reply from 38.49.39.136: bytes=32 time=170ms TTL=50 Reply from 38.49.39.136: bytes=32 time=169ms TTL=50 Reply from 38.49.39.136: bytes=32 time=173ms TTL=50 Reply from 38.49.39.136: bytes=32 time=169ms TTL=50 Reply from 38.49.39.136: bytes=32 time=169ms TTL=50 Reply from 38.49.39.136: bytes=32 time=171ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 169ms, Maximum = 188ms, Average = 172ms查看 |
GET PING Trace Dig |
|
河南平顶山市移动 |
移动 |
河南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
173.64ms |
170.78ms |
171.333ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=171ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49 Reply from 38.49.39.136: bytes=32 time=174ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 171ms, Maximum = 174ms, Average = 171ms查看 |
GET PING Trace Dig |
|
浙江温州市联通 |
联通 |
浙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
172.403ms |
170.127ms |
171.309ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=170ms TTL=51 Reply from 38.49.39.136: bytes=32 time=172ms TTL=51 Reply from 38.49.39.136: bytes=32 time=172ms TTL=51 Reply from 38.49.39.136: bytes=32 time=171ms TTL=51 Reply from 38.49.39.136: bytes=32 time=170ms TTL=51 Reply from 38.49.39.136: bytes=32 time=172ms TTL=51 Reply from 38.49.39.136: bytes=32 time=171ms TTL=51 Reply from 38.49.39.136: bytes=32 time=172ms TTL=51 Reply from 38.49.39.136: bytes=32 time=172ms TTL=51 Reply from 38.49.39.136: bytes=32 time=172ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 170ms, Maximum = 172ms, Average = 171ms查看 |
GET PING Trace Dig |
|
四川内江市电信 |
电信 |
四川 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
171.188ms |
170.998ms |
171.085ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=171ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49 Reply from 38.49.39.136: bytes=32 time=171ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 171ms, Maximum = 171ms, Average = 171ms查看 |
GET PING Trace Dig |
|
山西运城市电信 |
电信 |
山西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
9 |
1 |
207.737ms |
0ms |
171.017ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Request timed out. Reply from 38.49.39.136: bytes=32 time=208ms TTL=51 Reply from 38.49.39.136: bytes=32 time=162ms TTL=51 Reply from 38.49.39.136: bytes=32 time=163ms TTL=51 Reply from 38.49.39.136: bytes=32 time=163ms TTL=51 Reply from 38.49.39.136: bytes=32 time=163ms TTL=51 Reply from 38.49.39.136: bytes=32 time=169ms TTL=51 Reply from 38.49.39.136: bytes=32 time=182ms TTL=51 Reply from 38.49.39.136: bytes=32 time=168ms TTL=51 Reply from 38.49.39.136: bytes=32 time=162ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 9, Lost = 1 (10% loss), Approximate round trip times in milli-seconds: Minimum <1ms , Maximum = 208ms, Average = 171ms查看 |
GET PING Trace Dig |
|
福建福州市联通 |
联通 |
福建 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
171.977ms |
170.671ms |
170.896ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=171ms TTL=50 Reply from 38.49.39.136: bytes=32 time=171ms TTL=50 Reply from 38.49.39.136: bytes=32 time=172ms TTL=50 Reply from 38.49.39.136: bytes=32 time=171ms TTL=50 Reply from 38.49.39.136: bytes=32 time=171ms TTL=50 Reply from 38.49.39.136: bytes=32 time=171ms TTL=50 Reply from 38.49.39.136: bytes=32 time=171ms TTL=50 Reply from 38.49.39.136: bytes=32 time=171ms TTL=50 Reply from 38.49.39.136: bytes=32 time=171ms TTL=50 Reply from 38.49.39.136: bytes=32 time=171ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 171ms, Maximum = 172ms, Average = 171ms查看 |
GET PING Trace Dig |
|
贵州贵阳电信 |
电信 |
贵州 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
170.998ms |
170.405ms |
170.744ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=171ms TTL=50 Reply from 38.49.39.136: bytes=32 time=171ms TTL=50 Reply from 38.49.39.136: bytes=32 time=171ms TTL=50 Reply from 38.49.39.136: bytes=32 time=171ms TTL=50 Reply from 38.49.39.136: bytes=32 time=170ms TTL=50 Reply from 38.49.39.136: bytes=32 time=171ms TTL=50 Reply from 38.49.39.136: bytes=32 time=171ms TTL=50 Reply from 38.49.39.136: bytes=32 time=171ms TTL=50 Reply from 38.49.39.136: bytes=32 time=171ms TTL=50 Reply from 38.49.39.136: bytes=32 time=171ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 170ms, Maximum = 171ms, Average = 171ms查看 |
GET PING Trace Dig |
|
广东广州市联通 |
联通 |
广东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
176.579ms |
167.84ms |
170.715ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=173ms TTL=47 Reply from 38.49.39.136: bytes=32 time=168ms TTL=47 Reply from 38.49.39.136: bytes=32 time=169ms TTL=47 Reply from 38.49.39.136: bytes=32 time=170ms TTL=47 Reply from 38.49.39.136: bytes=32 time=168ms TTL=47 Reply from 38.49.39.136: bytes=32 time=172ms TTL=47 Reply from 38.49.39.136: bytes=32 time=168ms TTL=47 Reply from 38.49.39.136: bytes=32 time=177ms TTL=47 Reply from 38.49.39.136: bytes=32 time=173ms TTL=47 Reply from 38.49.39.136: bytes=32 time=168ms TTL=47
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 168ms, Maximum = 177ms, Average = 171ms查看 |
GET PING Trace Dig |
|
江苏连云港市联通 |
联通 |
江苏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
170.725ms |
170.206ms |
170.453ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=171ms TTL=51 Reply from 38.49.39.136: bytes=32 time=170ms TTL=51 Reply from 38.49.39.136: bytes=32 time=171ms TTL=51 Reply from 38.49.39.136: bytes=32 time=171ms TTL=51 Reply from 38.49.39.136: bytes=32 time=170ms TTL=51 Reply from 38.49.39.136: bytes=32 time=171ms TTL=51 Reply from 38.49.39.136: bytes=32 time=170ms TTL=51 Reply from 38.49.39.136: bytes=32 time=170ms TTL=51 Reply from 38.49.39.136: bytes=32 time=170ms TTL=51 Reply from 38.49.39.136: bytes=32 time=170ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 170ms, Maximum = 171ms, Average = 170ms查看 |
GET PING Trace Dig |
|
海南陵水黎族自治县电信 |
电信 |
海南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
170.906ms |
169.975ms |
170.24ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=170ms TTL=52 Reply from 38.49.39.136: bytes=32 time=171ms TTL=52 Reply from 38.49.39.136: bytes=32 time=170ms TTL=52 Reply from 38.49.39.136: bytes=32 time=170ms TTL=52 Reply from 38.49.39.136: bytes=32 time=170ms TTL=52 Reply from 38.49.39.136: bytes=32 time=171ms TTL=52 Reply from 38.49.39.136: bytes=32 time=170ms TTL=52 Reply from 38.49.39.136: bytes=32 time=170ms TTL=52 Reply from 38.49.39.136: bytes=32 time=170ms TTL=52 Reply from 38.49.39.136: bytes=32 time=170ms TTL=52
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 170ms, Maximum = 171ms, Average = 170ms查看 |
GET PING Trace Dig |
|
辽宁沈阳市移动 |
移动 |
辽宁 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
179.72ms |
167.52ms |
169.894ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=180ms TTL=48 Reply from 38.49.39.136: bytes=32 time=169ms TTL=48 Reply from 38.49.39.136: bytes=32 time=168ms TTL=48 Reply from 38.49.39.136: bytes=32 time=170ms TTL=48 Reply from 38.49.39.136: bytes=32 time=170ms TTL=48 Reply from 38.49.39.136: bytes=32 time=169ms TTL=48 Reply from 38.49.39.136: bytes=32 time=169ms TTL=48 Reply from 38.49.39.136: bytes=32 time=168ms TTL=48 Reply from 38.49.39.136: bytes=32 time=168ms TTL=48 Reply from 38.49.39.136: bytes=32 time=169ms TTL=48
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 168ms, Maximum = 180ms, Average = 170ms查看 |
GET PING Trace Dig |
|
甘肃庆阳市电信 |
电信 |
甘肃 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
172.729ms |
168.69ms |
169.805ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=173ms TTL=50 Reply from 38.49.39.136: bytes=32 time=169ms TTL=50 Reply from 38.49.39.136: bytes=32 time=170ms TTL=50 Reply from 38.49.39.136: bytes=32 time=170ms TTL=50 Reply from 38.49.39.136: bytes=32 time=172ms TTL=50 Reply from 38.49.39.136: bytes=32 time=169ms TTL=50 Reply from 38.49.39.136: bytes=32 time=169ms TTL=50 Reply from 38.49.39.136: bytes=32 time=169ms TTL=50 Reply from 38.49.39.136: bytes=32 time=169ms TTL=50 Reply from 38.49.39.136: bytes=32 time=169ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 169ms, Maximum = 173ms, Average = 170ms查看 |
GET PING Trace Dig |
|
重庆重庆市电信 |
电信 |
重庆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
170.339ms |
169.14ms |
169.664ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=170ms TTL=52 Reply from 38.49.39.136: bytes=32 time=170ms TTL=52 Reply from 38.49.39.136: bytes=32 time=170ms TTL=52 Reply from 38.49.39.136: bytes=32 time=170ms TTL=52 Reply from 38.49.39.136: bytes=32 time=170ms TTL=52 Reply from 38.49.39.136: bytes=32 time=170ms TTL=52 Reply from 38.49.39.136: bytes=32 time=169ms TTL=52 Reply from 38.49.39.136: bytes=32 time=169ms TTL=52 Reply from 38.49.39.136: bytes=32 time=170ms TTL=52 Reply from 38.49.39.136: bytes=32 time=170ms TTL=52
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 169ms, Maximum = 170ms, Average = 170ms查看 |
GET PING Trace Dig |
|
四川泸州市移动 |
移动 |
四川 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
169.412ms |
169.122ms |
169.239ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=169ms TTL=49 Reply from 38.49.39.136: bytes=32 time=169ms TTL=49 Reply from 38.49.39.136: bytes=32 time=169ms TTL=49 Reply from 38.49.39.136: bytes=32 time=169ms TTL=49 Reply from 38.49.39.136: bytes=32 time=169ms TTL=49 Reply from 38.49.39.136: bytes=32 time=169ms TTL=49 Reply from 38.49.39.136: bytes=32 time=169ms TTL=49 Reply from 38.49.39.136: bytes=32 time=169ms TTL=49 Reply from 38.49.39.136: bytes=32 time=169ms TTL=49 Reply from 38.49.39.136: bytes=32 time=169ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 169ms, Maximum = 169ms, Average = 169ms查看 |
GET PING Trace Dig |
|
贵州铜仁市移动 |
移动 |
贵州 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
169.962ms |
167.721ms |
168.891ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=169ms TTL=49 Reply from 38.49.39.136: bytes=32 time=169ms TTL=49 Reply from 38.49.39.136: bytes=32 time=168ms TTL=49 Reply from 38.49.39.136: bytes=32 time=168ms TTL=49 Reply from 38.49.39.136: bytes=32 time=170ms TTL=49 Reply from 38.49.39.136: bytes=32 time=170ms TTL=49 Reply from 38.49.39.136: bytes=32 time=168ms TTL=49 Reply from 38.49.39.136: bytes=32 time=168ms TTL=49 Reply from 38.49.39.136: bytes=32 time=170ms TTL=49 Reply from 38.49.39.136: bytes=32 time=170ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 168ms, Maximum = 170ms, Average = 169ms查看 |
GET PING Trace Dig |
|
海南海口市移动 |
移动 |
海南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
169.262ms |
168.738ms |
168.854ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=169ms TTL=50 Reply from 38.49.39.136: bytes=32 time=169ms TTL=50 Reply from 38.49.39.136: bytes=32 time=169ms TTL=50 Reply from 38.49.39.136: bytes=32 time=169ms TTL=50 Reply from 38.49.39.136: bytes=32 time=169ms TTL=50 Reply from 38.49.39.136: bytes=32 time=169ms TTL=50 Reply from 38.49.39.136: bytes=32 time=169ms TTL=50 Reply from 38.49.39.136: bytes=32 time=169ms TTL=50 Reply from 38.49.39.136: bytes=32 time=169ms TTL=50 Reply from 38.49.39.136: bytes=32 time=169ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 169ms, Maximum = 169ms, Average = 169ms查看 |
GET PING Trace Dig |
|
陕西商洛市移动 |
移动 |
陕西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
175.739ms |
166.659ms |
168.791ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=168ms TTL=48 Reply from 38.49.39.136: bytes=32 time=167ms TTL=48 Reply from 38.49.39.136: bytes=32 time=168ms TTL=48 Reply from 38.49.39.136: bytes=32 time=169ms TTL=48 Reply from 38.49.39.136: bytes=32 time=168ms TTL=48 Reply from 38.49.39.136: bytes=32 time=171ms TTL=48 Reply from 38.49.39.136: bytes=32 time=167ms TTL=48 Reply from 38.49.39.136: bytes=32 time=167ms TTL=48 Reply from 38.49.39.136: bytes=32 time=167ms TTL=48 Reply from 38.49.39.136: bytes=32 time=176ms TTL=48
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 167ms, Maximum = 176ms, Average = 169ms查看 |
GET PING Trace Dig |
|
海南琼海市电信 |
电信 |
海南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
171.767ms |
167.173ms |
168.532ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=167ms TTL=51 Reply from 38.49.39.136: bytes=32 time=168ms TTL=51 Reply from 38.49.39.136: bytes=32 time=168ms TTL=51 Reply from 38.49.39.136: bytes=32 time=167ms TTL=51 Reply from 38.49.39.136: bytes=32 time=171ms TTL=51 Reply from 38.49.39.136: bytes=32 time=169ms TTL=51 Reply from 38.49.39.136: bytes=32 time=168ms TTL=51 Reply from 38.49.39.136: bytes=32 time=168ms TTL=51 Reply from 38.49.39.136: bytes=32 time=172ms TTL=51 Reply from 38.49.39.136: bytes=32 time=167ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 167ms, Maximum = 172ms, Average = 169ms查看 |
GET PING Trace Dig |
|
上海上海市联通 |
联通 |
上海 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
9 |
1 |
210.184ms |
160.009ms |
168.427ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=167ms TTL=51 Reply from 38.49.39.136: bytes=32 time=160ms TTL=51 Reply from 38.49.39.136: bytes=32 time=162ms TTL=51 Reply from 38.49.39.136: bytes=32 time=160ms TTL=51 Request timed out. Reply from 38.49.39.136: bytes=32 time=210ms TTL=51 Reply from 38.49.39.136: bytes=32 time=161ms TTL=51 Reply from 38.49.39.136: bytes=32 time=171ms TTL=51 Reply from 38.49.39.136: bytes=32 time=165ms TTL=51 Reply from 38.49.39.136: bytes=32 time=160ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 9, Lost = 1 (10% loss), Approximate round trip times in milli-seconds: Minimum = 160ms, Maximum = 210ms, Average = 168ms查看 |
GET PING Trace Dig |
|
天津天津市移动 |
移动 |
天津 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
197.934ms |
163.328ms |
168.381ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=168ms TTL=46 Reply from 38.49.39.136: bytes=32 time=163ms TTL=46 Reply from 38.49.39.136: bytes=32 time=164ms TTL=46 Reply from 38.49.39.136: bytes=32 time=163ms TTL=46 Reply from 38.49.39.136: bytes=32 time=164ms TTL=46 Reply from 38.49.39.136: bytes=32 time=164ms TTL=46 Reply from 38.49.39.136: bytes=32 time=164ms TTL=46 Reply from 38.49.39.136: bytes=32 time=198ms TTL=46 Reply from 38.49.39.136: bytes=32 time=168ms TTL=46 Reply from 38.49.39.136: bytes=32 time=167ms TTL=46
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 163ms, Maximum = 198ms, Average = 168ms查看 |
GET PING Trace Dig |
|
宁夏银川市电信 |
电信 |
宁夏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
172.5ms |
166.679ms |
167.962ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=167ms TTL=51 Reply from 38.49.39.136: bytes=32 time=167ms TTL=51 Reply from 38.49.39.136: bytes=32 time=167ms TTL=51 Reply from 38.49.39.136: bytes=32 time=167ms TTL=51 Reply from 38.49.39.136: bytes=32 time=169ms TTL=51 Reply from 38.49.39.136: bytes=32 time=173ms TTL=51 Reply from 38.49.39.136: bytes=32 time=167ms TTL=51 Reply from 38.49.39.136: bytes=32 time=167ms TTL=51 Reply from 38.49.39.136: bytes=32 time=167ms TTL=51 Reply from 38.49.39.136: bytes=32 time=169ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 167ms, Maximum = 173ms, Average = 168ms查看 |
GET PING Trace Dig |
|
香港香港 |
香港 |
香港 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
168.765ms |
167.471ms |
167.65ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=168ms TTL=53 Reply from 38.49.39.136: bytes=32 time=168ms TTL=53 Reply from 38.49.39.136: bytes=32 time=168ms TTL=53 Reply from 38.49.39.136: bytes=32 time=168ms TTL=53 Reply from 38.49.39.136: bytes=32 time=168ms TTL=53 Reply from 38.49.39.136: bytes=32 time=168ms TTL=53 Reply from 38.49.39.136: bytes=32 time=168ms TTL=53 Reply from 38.49.39.136: bytes=32 time=167ms TTL=53 Reply from 38.49.39.136: bytes=32 time=167ms TTL=53 Reply from 38.49.39.136: bytes=32 time=169ms TTL=53
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 167ms, Maximum = 169ms, Average = 168ms查看 |
GET PING Trace Dig |
|
山东泰安市电信 |
电信 |
山东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
168.36ms |
167.32ms |
167.647ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=168ms TTL=51 Reply from 38.49.39.136: bytes=32 time=168ms TTL=51 Reply from 38.49.39.136: bytes=32 time=168ms TTL=51 Reply from 38.49.39.136: bytes=32 time=168ms TTL=51 Reply from 38.49.39.136: bytes=32 time=168ms TTL=51 Reply from 38.49.39.136: bytes=32 time=168ms TTL=51 Reply from 38.49.39.136: bytes=32 time=167ms TTL=51 Reply from 38.49.39.136: bytes=32 time=168ms TTL=51 Reply from 38.49.39.136: bytes=32 time=167ms TTL=51 Reply from 38.49.39.136: bytes=32 time=168ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 167ms, Maximum = 168ms, Average = 168ms查看 |
GET PING Trace Dig |
|
安徽阜阳联通 |
联通 |
安徽 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
168.75ms |
167.246ms |
167.578ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=167ms TTL=50 Reply from 38.49.39.136: bytes=32 time=168ms TTL=50 Reply from 38.49.39.136: bytes=32 time=167ms TTL=50 Reply from 38.49.39.136: bytes=32 time=167ms TTL=50 Reply from 38.49.39.136: bytes=32 time=168ms TTL=50 Reply from 38.49.39.136: bytes=32 time=167ms TTL=50 Reply from 38.49.39.136: bytes=32 time=167ms TTL=50 Reply from 38.49.39.136: bytes=32 time=167ms TTL=50 Reply from 38.49.39.136: bytes=32 time=169ms TTL=50 Reply from 38.49.39.136: bytes=32 time=168ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 167ms, Maximum = 169ms, Average = 168ms查看 |
GET PING Trace Dig |
|
广西贵港电信 |
电信 |
广西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
172.542ms |
165.382ms |
167.218ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=167ms TTL=51 Reply from 38.49.39.136: bytes=32 time=170ms TTL=51 Reply from 38.49.39.136: bytes=32 time=165ms TTL=51 Reply from 38.49.39.136: bytes=32 time=166ms TTL=51 Reply from 38.49.39.136: bytes=32 time=173ms TTL=51 Reply from 38.49.39.136: bytes=32 time=169ms TTL=51 Reply from 38.49.39.136: bytes=32 time=166ms TTL=51 Reply from 38.49.39.136: bytes=32 time=166ms TTL=51 Reply from 38.49.39.136: bytes=32 time=166ms TTL=51 Reply from 38.49.39.136: bytes=32 time=165ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 165ms, Maximum = 173ms, Average = 167ms查看 |
GET PING Trace Dig |
|
海南海口市移动 |
移动 |
海南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
167.321ms |
166.902ms |
167.015ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=167ms TTL=49 Reply from 38.49.39.136: bytes=32 time=167ms TTL=49 Reply from 38.49.39.136: bytes=32 time=167ms TTL=49 Reply from 38.49.39.136: bytes=32 time=167ms TTL=49 Reply from 38.49.39.136: bytes=32 time=167ms TTL=49 Reply from 38.49.39.136: bytes=32 time=167ms TTL=49 Reply from 38.49.39.136: bytes=32 time=167ms TTL=49 Reply from 38.49.39.136: bytes=32 time=167ms TTL=49 Reply from 38.49.39.136: bytes=32 time=167ms TTL=49 Reply from 38.49.39.136: bytes=32 time=167ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 167ms, Maximum = 167ms, Average = 167ms查看 |
GET PING Trace Dig |
|
重庆重庆市联通 |
联通 |
重庆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
166.579ms |
165.66ms |
166.193ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=166ms TTL=50 Reply from 38.49.39.136: bytes=32 time=167ms TTL=50 Reply from 38.49.39.136: bytes=32 time=167ms TTL=50 Reply from 38.49.39.136: bytes=32 time=166ms TTL=50 Reply from 38.49.39.136: bytes=32 time=166ms TTL=50 Reply from 38.49.39.136: bytes=32 time=166ms TTL=50 Reply from 38.49.39.136: bytes=32 time=166ms TTL=50 Reply from 38.49.39.136: bytes=32 time=166ms TTL=50 Reply from 38.49.39.136: bytes=32 time=167ms TTL=50 Reply from 38.49.39.136: bytes=32 time=167ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 166ms, Maximum = 167ms, Average = 166ms查看 |
GET PING Trace Dig |
|
湖南长沙移动 |
移动 |
湖南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
168.6ms |
164.98ms |
166.018ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=169ms TTL=40 Reply from 38.49.39.136: bytes=32 time=166ms TTL=40 Reply from 38.49.39.136: bytes=32 time=166ms TTL=40 Reply from 38.49.39.136: bytes=32 time=165ms TTL=40 Reply from 38.49.39.136: bytes=32 time=165ms TTL=40 Reply from 38.49.39.136: bytes=32 time=166ms TTL=40 Reply from 38.49.39.136: bytes=32 time=166ms TTL=40 Reply from 38.49.39.136: bytes=32 time=165ms TTL=40 Reply from 38.49.39.136: bytes=32 time=166ms TTL=40 Reply from 38.49.39.136: bytes=32 time=167ms TTL=40
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 165ms, Maximum = 169ms, Average = 166ms查看 |
GET PING Trace Dig |
|
意大利国外 |
国外 |
意大利 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
166.76ms |
165.301ms |
165.828ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=166ms TTL=47 Reply from 38.49.39.136: bytes=32 time=166ms TTL=47 Reply from 38.49.39.136: bytes=32 time=166ms TTL=47 Reply from 38.49.39.136: bytes=32 time=165ms TTL=47 Reply from 38.49.39.136: bytes=32 time=166ms TTL=47 Reply from 38.49.39.136: bytes=32 time=167ms TTL=47 Reply from 38.49.39.136: bytes=32 time=165ms TTL=47 Reply from 38.49.39.136: bytes=32 time=165ms TTL=47 Reply from 38.49.39.136: bytes=32 time=166ms TTL=47 Reply from 38.49.39.136: bytes=32 time=166ms TTL=47
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 165ms, Maximum = 167ms, Average = 166ms查看 |
GET PING Trace Dig |
|
福建莆田市电信 |
电信 |
福建 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
174.622ms |
162.712ms |
165.627ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=163ms TTL=50 Reply from 38.49.39.136: bytes=32 time=166ms TTL=50 Reply from 38.49.39.136: bytes=32 time=163ms TTL=50 Reply from 38.49.39.136: bytes=32 time=165ms TTL=50 Reply from 38.49.39.136: bytes=32 time=166ms TTL=50 Reply from 38.49.39.136: bytes=32 time=175ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=167ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=163ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 163ms, Maximum = 175ms, Average = 166ms查看 |
GET PING Trace Dig |
|
广东广州市联通 |
联通 |
广东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
165.6ms |
165.22ms |
165.382ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=166ms TTL=49 Reply from 38.49.39.136: bytes=32 time=165ms TTL=49 Reply from 38.49.39.136: bytes=32 time=165ms TTL=49 Reply from 38.49.39.136: bytes=32 time=165ms TTL=49 Reply from 38.49.39.136: bytes=32 time=165ms TTL=49 Reply from 38.49.39.136: bytes=32 time=165ms TTL=49 Reply from 38.49.39.136: bytes=32 time=165ms TTL=49 Reply from 38.49.39.136: bytes=32 time=165ms TTL=49 Reply from 38.49.39.136: bytes=32 time=165ms TTL=49 Reply from 38.49.39.136: bytes=32 time=165ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 165ms, Maximum = 166ms, Average = 165ms查看 |
GET PING Trace Dig |
|
河北唐山市电信 |
电信 |
河北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
169.588ms |
163.95ms |
165.289ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=166ms TTL=49 Reply from 38.49.39.136: bytes=32 time=165ms TTL=49 Reply from 38.49.39.136: bytes=32 time=164ms TTL=49 Reply from 38.49.39.136: bytes=32 time=164ms TTL=49 Reply from 38.49.39.136: bytes=32 time=164ms TTL=49 Reply from 38.49.39.136: bytes=32 time=166ms TTL=49 Reply from 38.49.39.136: bytes=32 time=170ms TTL=49 Reply from 38.49.39.136: bytes=32 time=165ms TTL=49 Reply from 38.49.39.136: bytes=32 time=164ms TTL=49 Reply from 38.49.39.136: bytes=32 time=164ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 164ms, Maximum = 170ms, Average = 165ms查看 |
GET PING Trace Dig |
|
广东广州市移动 |
移动 |
广东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
176.542ms |
162.761ms |
165.134ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=165ms TTL=43 Reply from 38.49.39.136: bytes=32 time=164ms TTL=43 Reply from 38.49.39.136: bytes=32 time=163ms TTL=43 Reply from 38.49.39.136: bytes=32 time=165ms TTL=43 Reply from 38.49.39.136: bytes=32 time=163ms TTL=43 Reply from 38.49.39.136: bytes=32 time=163ms TTL=43 Reply from 38.49.39.136: bytes=32 time=177ms TTL=43 Reply from 38.49.39.136: bytes=32 time=163ms TTL=43 Reply from 38.49.39.136: bytes=32 time=164ms TTL=43 Reply from 38.49.39.136: bytes=32 time=165ms TTL=43
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 163ms, Maximum = 177ms, Average = 165ms查看 |
GET PING Trace Dig |
|
山东济南市电信 |
电信 |
山东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
187.005ms |
156.672ms |
164.079ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=187ms TTL=49 Reply from 38.49.39.136: bytes=32 time=167ms TTL=49 Reply from 38.49.39.136: bytes=32 time=184ms TTL=49 Reply from 38.49.39.136: bytes=32 time=157ms TTL=49 Reply from 38.49.39.136: bytes=32 time=157ms TTL=49 Reply from 38.49.39.136: bytes=32 time=160ms TTL=49 Reply from 38.49.39.136: bytes=32 time=157ms TTL=49 Reply from 38.49.39.136: bytes=32 time=158ms TTL=49 Reply from 38.49.39.136: bytes=32 time=157ms TTL=49 Reply from 38.49.39.136: bytes=32 time=157ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 157ms, Maximum = 187ms, Average = 164ms查看 |
GET PING Trace Dig |
|
辽宁沈阳市电信 |
电信 |
辽宁 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
164.701ms |
163.641ms |
163.922ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=165ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 164ms, Maximum = 165ms, Average = 164ms查看 |
GET PING Trace Dig |
|
安徽亳州市联通 |
联通 |
安徽 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
164.444ms |
163.15ms |
163.816ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=163ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 163ms, Maximum = 164ms, Average = 164ms查看 |
GET PING Trace Dig |
|
甘肃兰州市电信 |
电信 |
甘肃 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
163.918ms |
162.653ms |
163.432ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=163ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=163ms TTL=50 Reply from 38.49.39.136: bytes=32 time=163ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=163ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=163ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 163ms, Maximum = 164ms, Average = 163ms查看 |
GET PING Trace Dig |
|
甘肃酒泉市移动 |
移动 |
甘肃 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
163.278ms |
162.999ms |
163.206ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=163ms TTL=49 Reply from 38.49.39.136: bytes=32 time=163ms TTL=49 Reply from 38.49.39.136: bytes=32 time=163ms TTL=49 Reply from 38.49.39.136: bytes=32 time=163ms TTL=49 Reply from 38.49.39.136: bytes=32 time=163ms TTL=49 Reply from 38.49.39.136: bytes=32 time=163ms TTL=49 Reply from 38.49.39.136: bytes=32 time=163ms TTL=49 Reply from 38.49.39.136: bytes=32 time=163ms TTL=49 Reply from 38.49.39.136: bytes=32 time=163ms TTL=49 Reply from 38.49.39.136: bytes=32 time=163ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 163ms, Maximum = 163ms, Average = 163ms查看 |
GET PING Trace Dig |
|
重庆重庆市移动 |
移动 |
重庆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
167.023ms |
162.503ms |
163.142ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=163ms TTL=48 Reply from 38.49.39.136: bytes=32 time=163ms TTL=48 Reply from 38.49.39.136: bytes=32 time=163ms TTL=48 Reply from 38.49.39.136: bytes=32 time=163ms TTL=48 Reply from 38.49.39.136: bytes=32 time=163ms TTL=48 Reply from 38.49.39.136: bytes=32 time=163ms TTL=48 Reply from 38.49.39.136: bytes=32 time=163ms TTL=48 Reply from 38.49.39.136: bytes=32 time=167ms TTL=48 Reply from 38.49.39.136: bytes=32 time=163ms TTL=48 Reply from 38.49.39.136: bytes=32 time=163ms TTL=48
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 163ms, Maximum = 167ms, Average = 163ms查看 |
GET PING Trace Dig |
|
重庆重庆市电信 |
电信 |
重庆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
164.89ms |
162.196ms |
163.072ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=163ms TTL=50 Reply from 38.49.39.136: bytes=32 time=165ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=162ms TTL=50 Reply from 38.49.39.136: bytes=32 time=162ms TTL=50 Reply from 38.49.39.136: bytes=32 time=162ms TTL=50 Reply from 38.49.39.136: bytes=32 time=163ms TTL=50 Reply from 38.49.39.136: bytes=32 time=164ms TTL=50 Reply from 38.49.39.136: bytes=32 time=162ms TTL=50 Reply from 38.49.39.136: bytes=32 time=163ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 162ms, Maximum = 165ms, Average = 163ms查看 |
GET PING Trace Dig |
|
广西南宁市电信 |
电信 |
广西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
167.486ms |
161.622ms |
163.027ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=162ms TTL=48 Reply from 38.49.39.136: bytes=32 time=162ms TTL=48 Reply from 38.49.39.136: bytes=32 time=163ms TTL=48 Reply from 38.49.39.136: bytes=32 time=162ms TTL=48 Reply from 38.49.39.136: bytes=32 time=163ms TTL=48 Reply from 38.49.39.136: bytes=32 time=167ms TTL=48 Reply from 38.49.39.136: bytes=32 time=165ms TTL=48 Reply from 38.49.39.136: bytes=32 time=162ms TTL=48 Reply from 38.49.39.136: bytes=32 time=163ms TTL=48 Reply from 38.49.39.136: bytes=32 time=162ms TTL=48
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 162ms, Maximum = 167ms, Average = 163ms查看 |
GET PING Trace Dig |
|
江西赣州市联通 |
联通 |
江西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
162.871ms |
162.494ms |
162.719ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=163ms TTL=48 Reply from 38.49.39.136: bytes=32 time=163ms TTL=48 Reply from 38.49.39.136: bytes=32 time=163ms TTL=48 Reply from 38.49.39.136: bytes=32 time=163ms TTL=48 Reply from 38.49.39.136: bytes=32 time=163ms TTL=48 Reply from 38.49.39.136: bytes=32 time=163ms TTL=48 Reply from 38.49.39.136: bytes=32 time=162ms TTL=48 Reply from 38.49.39.136: bytes=32 time=163ms TTL=48 Reply from 38.49.39.136: bytes=32 time=163ms TTL=48 Reply from 38.49.39.136: bytes=32 time=163ms TTL=48
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 162ms, Maximum = 163ms, Average = 163ms查看 |
GET PING Trace Dig |
|
陕西西安市移动 |
移动 |
陕西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
163.17ms |
161.868ms |
162.513ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=163ms TTL=49 Reply from 38.49.39.136: bytes=32 time=162ms TTL=49 Reply from 38.49.39.136: bytes=32 time=162ms TTL=49 Reply from 38.49.39.136: bytes=32 time=163ms TTL=49 Reply from 38.49.39.136: bytes=32 time=162ms TTL=49 Reply from 38.49.39.136: bytes=32 time=162ms TTL=49 Reply from 38.49.39.136: bytes=32 time=163ms TTL=49 Reply from 38.49.39.136: bytes=32 time=163ms TTL=49 Reply from 38.49.39.136: bytes=32 time=163ms TTL=49 Reply from 38.49.39.136: bytes=32 time=163ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 162ms, Maximum = 163ms, Average = 163ms查看 |
GET PING Trace Dig |
|
辽宁辽阳市移动 |
移动 |
辽宁 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
162.858ms |
161.623ms |
161.908ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=162ms TTL=49 Reply from 38.49.39.136: bytes=32 time=163ms TTL=49 Reply from 38.49.39.136: bytes=32 time=162ms TTL=49 Reply from 38.49.39.136: bytes=32 time=162ms TTL=49 Reply from 38.49.39.136: bytes=32 time=162ms TTL=49 Reply from 38.49.39.136: bytes=32 time=162ms TTL=49 Reply from 38.49.39.136: bytes=32 time=162ms TTL=49 Reply from 38.49.39.136: bytes=32 time=162ms TTL=49 Reply from 38.49.39.136: bytes=32 time=162ms TTL=49 Reply from 38.49.39.136: bytes=32 time=162ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 162ms, Maximum = 163ms, Average = 162ms查看 |
GET PING Trace Dig |
|
福建莆田市铁通 |
铁通 |
福建 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
160.262ms |
159.983ms |
160.072ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=160ms TTL=50 Reply from 38.49.39.136: bytes=32 time=160ms TTL=50 Reply from 38.49.39.136: bytes=32 time=160ms TTL=50 Reply from 38.49.39.136: bytes=32 time=160ms TTL=50 Reply from 38.49.39.136: bytes=32 time=160ms TTL=50 Reply from 38.49.39.136: bytes=32 time=160ms TTL=50 Reply from 38.49.39.136: bytes=32 time=160ms TTL=50 Reply from 38.49.39.136: bytes=32 time=160ms TTL=50 Reply from 38.49.39.136: bytes=32 time=160ms TTL=50 Reply from 38.49.39.136: bytes=32 time=160ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 160ms, Maximum = 160ms, Average = 160ms查看 |
GET PING Trace Dig |
|
河北沧州市电信 |
电信 |
河北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
162.98ms |
157.86ms |
159.515ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=159ms TTL=50 Reply from 38.49.39.136: bytes=32 time=158ms TTL=50 Reply from 38.49.39.136: bytes=32 time=159ms TTL=50 Reply from 38.49.39.136: bytes=32 time=158ms TTL=50 Reply from 38.49.39.136: bytes=32 time=163ms TTL=50 Reply from 38.49.39.136: bytes=32 time=159ms TTL=50 Reply from 38.49.39.136: bytes=32 time=163ms TTL=50 Reply from 38.49.39.136: bytes=32 time=158ms TTL=50 Reply from 38.49.39.136: bytes=32 time=159ms TTL=50 Reply from 38.49.39.136: bytes=32 time=160ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 158ms, Maximum = 163ms, Average = 160ms查看 |
GET PING Trace Dig |
|
天津天津市电信 |
电信 |
天津 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
174.118ms |
155.38ms |
159.032ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=159ms TTL=47 Reply from 38.49.39.136: bytes=32 time=159ms TTL=47 Reply from 38.49.39.136: bytes=32 time=155ms TTL=47 Reply from 38.49.39.136: bytes=32 time=160ms TTL=47 Reply from 38.49.39.136: bytes=32 time=156ms TTL=47 Reply from 38.49.39.136: bytes=32 time=158ms TTL=47 Reply from 38.49.39.136: bytes=32 time=157ms TTL=47 Reply from 38.49.39.136: bytes=32 time=174ms TTL=47 Reply from 38.49.39.136: bytes=32 time=156ms TTL=47 Reply from 38.49.39.136: bytes=32 time=156ms TTL=47
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 155ms, Maximum = 174ms, Average = 159ms查看 |
GET PING Trace Dig |
|
湖南永州市联通 |
联通 |
湖南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
159.659ms |
158.659ms |
158.884ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=160ms TTL=49 Reply from 38.49.39.136: bytes=32 time=159ms TTL=49 Reply from 38.49.39.136: bytes=32 time=159ms TTL=49 Reply from 38.49.39.136: bytes=32 time=159ms TTL=49 Reply from 38.49.39.136: bytes=32 time=159ms TTL=49 Reply from 38.49.39.136: bytes=32 time=159ms TTL=49 Reply from 38.49.39.136: bytes=32 time=159ms TTL=49 Reply from 38.49.39.136: bytes=32 time=159ms TTL=49 Reply from 38.49.39.136: bytes=32 time=159ms TTL=49 Reply from 38.49.39.136: bytes=32 time=159ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 159ms, Maximum = 160ms, Average = 159ms查看 |
GET PING Trace Dig |
|
湖南邵阳市移动 |
移动 |
湖南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
164.623ms |
156.7ms |
158.733ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=157ms TTL=49 Reply from 38.49.39.136: bytes=32 time=165ms TTL=49 Reply from 38.49.39.136: bytes=32 time=158ms TTL=49 Reply from 38.49.39.136: bytes=32 time=157ms TTL=49 Reply from 38.49.39.136: bytes=32 time=157ms TTL=49 Reply from 38.49.39.136: bytes=32 time=157ms TTL=49 Reply from 38.49.39.136: bytes=32 time=163ms TTL=49 Reply from 38.49.39.136: bytes=32 time=157ms TTL=49 Reply from 38.49.39.136: bytes=32 time=160ms TTL=49 Reply from 38.49.39.136: bytes=32 time=157ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 157ms, Maximum = 165ms, Average = 159ms查看 |
GET PING Trace Dig |
|
香港香港 |
香港 |
香港 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
158.736ms |
158.565ms |
158.615ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=159ms TTL=53 Reply from 38.49.39.136: bytes=32 time=159ms TTL=53 Reply from 38.49.39.136: bytes=32 time=159ms TTL=53 Reply from 38.49.39.136: bytes=32 time=159ms TTL=53 Reply from 38.49.39.136: bytes=32 time=159ms TTL=53 Reply from 38.49.39.136: bytes=32 time=159ms TTL=53 Reply from 38.49.39.136: bytes=32 time=159ms TTL=53 Reply from 38.49.39.136: bytes=32 time=159ms TTL=53 Reply from 38.49.39.136: bytes=32 time=159ms TTL=53 Reply from 38.49.39.136: bytes=32 time=159ms TTL=53
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 159ms, Maximum = 159ms, Average = 159ms查看 |
GET PING Trace Dig |
|
陕西咸阳市电信 |
电信 |
陕西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
166.286ms |
153.336ms |
158.362ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=156ms TTL=51 Reply from 38.49.39.136: bytes=32 time=157ms TTL=51 Reply from 38.49.39.136: bytes=32 time=166ms TTL=51 Reply from 38.49.39.136: bytes=32 time=158ms TTL=51 Reply from 38.49.39.136: bytes=32 time=160ms TTL=51 Reply from 38.49.39.136: bytes=32 time=160ms TTL=51 Reply from 38.49.39.136: bytes=32 time=157ms TTL=51 Reply from 38.49.39.136: bytes=32 time=153ms TTL=51 Reply from 38.49.39.136: bytes=32 time=154ms TTL=51 Reply from 38.49.39.136: bytes=32 time=162ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 153ms, Maximum = 166ms, Average = 158ms查看 |
GET PING Trace Dig |
|
山东菏泽市联通 |
联通 |
山东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
159.48ms |
157.42ms |
158.216ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=158ms TTL=49 Reply from 38.49.39.136: bytes=32 time=158ms TTL=49 Reply from 38.49.39.136: bytes=32 time=158ms TTL=49 Reply from 38.49.39.136: bytes=32 time=158ms TTL=49 Reply from 38.49.39.136: bytes=32 time=159ms TTL=49 Reply from 38.49.39.136: bytes=32 time=158ms TTL=49 Reply from 38.49.39.136: bytes=32 time=158ms TTL=49 Reply from 38.49.39.136: bytes=32 time=157ms TTL=49 Reply from 38.49.39.136: bytes=32 time=158ms TTL=49 Reply from 38.49.39.136: bytes=32 time=159ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 157ms, Maximum = 159ms, Average = 158ms查看 |
GET PING Trace Dig |
|
湖北黄冈移动 |
移动 |
湖北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
160.74ms |
156.493ms |
158.059ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=157ms TTL=48 Reply from 38.49.39.136: bytes=32 time=157ms TTL=48 Reply from 38.49.39.136: bytes=32 time=156ms TTL=48 Reply from 38.49.39.136: bytes=32 time=157ms TTL=48 Reply from 38.49.39.136: bytes=32 time=159ms TTL=48 Reply from 38.49.39.136: bytes=32 time=157ms TTL=48 Reply from 38.49.39.136: bytes=32 time=158ms TTL=48 Reply from 38.49.39.136: bytes=32 time=157ms TTL=48 Reply from 38.49.39.136: bytes=32 time=161ms TTL=48 Reply from 38.49.39.136: bytes=32 time=160ms TTL=48
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 156ms, Maximum = 161ms, Average = 158ms查看 |
GET PING Trace Dig |
|
安徽六安市移动 |
移动 |
安徽 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
158.221ms |
157.581ms |
157.983ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=158ms TTL=51 Reply from 38.49.39.136: bytes=32 time=158ms TTL=51 Reply from 38.49.39.136: bytes=32 time=158ms TTL=51 Reply from 38.49.39.136: bytes=32 time=158ms TTL=51 Reply from 38.49.39.136: bytes=32 time=158ms TTL=51 Reply from 38.49.39.136: bytes=32 time=158ms TTL=51 Reply from 38.49.39.136: bytes=32 time=158ms TTL=51 Reply from 38.49.39.136: bytes=32 time=158ms TTL=51 Reply from 38.49.39.136: bytes=32 time=158ms TTL=51 Reply from 38.49.39.136: bytes=32 time=158ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 158ms, Maximum = 158ms, Average = 158ms查看 |
GET PING Trace Dig |
|
河北沧州市联通 |
联通 |
河北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
158.08ms |
157.559ms |
157.78ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=158ms TTL=50 Reply from 38.49.39.136: bytes=32 time=158ms TTL=50 Reply from 38.49.39.136: bytes=32 time=158ms TTL=50 Reply from 38.49.39.136: bytes=32 time=158ms TTL=50 Reply from 38.49.39.136: bytes=32 time=158ms TTL=50 Reply from 38.49.39.136: bytes=32 time=158ms TTL=50 Reply from 38.49.39.136: bytes=32 time=158ms TTL=50 Reply from 38.49.39.136: bytes=32 time=158ms TTL=50 Reply from 38.49.39.136: bytes=32 time=158ms TTL=50 Reply from 38.49.39.136: bytes=32 time=158ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 158ms, Maximum = 158ms, Average = 158ms查看 |
GET PING Trace Dig |
|
天津移动 |
移动 |
天津 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
157.041ms |
155.7ms |
156.071ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=156ms TTL=49 Reply from 38.49.39.136: bytes=32 time=156ms TTL=49 Reply from 38.49.39.136: bytes=32 time=156ms TTL=49 Reply from 38.49.39.136: bytes=32 time=157ms TTL=49 Reply from 38.49.39.136: bytes=32 time=156ms TTL=49 Reply from 38.49.39.136: bytes=32 time=156ms TTL=49 Reply from 38.49.39.136: bytes=32 time=156ms TTL=49 Reply from 38.49.39.136: bytes=32 time=156ms TTL=49 Reply from 38.49.39.136: bytes=32 time=156ms TTL=49 Reply from 38.49.39.136: bytes=32 time=157ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 156ms, Maximum = 157ms, Average = 156ms查看 |
GET PING Trace Dig |
|
河南安阳移动 |
移动 |
河南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
157.441ms |
155.464ms |
156.07ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=157ms TTL=49 Reply from 38.49.39.136: bytes=32 time=157ms TTL=49 Reply from 38.49.39.136: bytes=32 time=156ms TTL=49 Reply from 38.49.39.136: bytes=32 time=156ms TTL=49 Reply from 38.49.39.136: bytes=32 time=156ms TTL=49 Reply from 38.49.39.136: bytes=32 time=156ms TTL=49 Reply from 38.49.39.136: bytes=32 time=156ms TTL=49 Reply from 38.49.39.136: bytes=32 time=155ms TTL=49 Reply from 38.49.39.136: bytes=32 time=156ms TTL=49 Reply from 38.49.39.136: bytes=32 time=156ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 155ms, Maximum = 157ms, Average = 156ms查看 |
GET PING Trace Dig |
|
河北邯郸市联通 |
联通 |
河北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
160.782ms |
153.702ms |
155.627ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=154ms TTL=51 Reply from 38.49.39.136: bytes=32 time=154ms TTL=51 Reply from 38.49.39.136: bytes=32 time=155ms TTL=51 Reply from 38.49.39.136: bytes=32 time=154ms TTL=51 Reply from 38.49.39.136: bytes=32 time=160ms TTL=51 Reply from 38.49.39.136: bytes=32 time=154ms TTL=51 Reply from 38.49.39.136: bytes=32 time=155ms TTL=51 Reply from 38.49.39.136: bytes=32 time=155ms TTL=51 Reply from 38.49.39.136: bytes=32 time=161ms TTL=51 Reply from 38.49.39.136: bytes=32 time=154ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 154ms, Maximum = 161ms, Average = 156ms查看 |
GET PING Trace Dig |
|
广东深圳电信 |
电信 |
广东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
155.619ms |
155.344ms |
155.425ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=156ms TTL=47 Reply from 38.49.39.136: bytes=32 time=156ms TTL=47 Reply from 38.49.39.136: bytes=32 time=155ms TTL=47 Reply from 38.49.39.136: bytes=32 time=155ms TTL=47 Reply from 38.49.39.136: bytes=32 time=155ms TTL=47 Reply from 38.49.39.136: bytes=32 time=155ms TTL=47 Reply from 38.49.39.136: bytes=32 time=155ms TTL=47 Reply from 38.49.39.136: bytes=32 time=155ms TTL=47 Reply from 38.49.39.136: bytes=32 time=155ms TTL=47 Reply from 38.49.39.136: bytes=32 time=155ms TTL=47
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 155ms, Maximum = 156ms, Average = 155ms查看 |
GET PING Trace Dig |
|
山西太原移动 |
移动 |
山西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
156.07ms |
154.608ms |
155.258ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=156ms TTL=48 Reply from 38.49.39.136: bytes=32 time=155ms TTL=48 Reply from 38.49.39.136: bytes=32 time=156ms TTL=48 Reply from 38.49.39.136: bytes=32 time=155ms TTL=48 Reply from 38.49.39.136: bytes=32 time=155ms TTL=48 Reply from 38.49.39.136: bytes=32 time=155ms TTL=48 Reply from 38.49.39.136: bytes=32 time=155ms TTL=48 Reply from 38.49.39.136: bytes=32 time=155ms TTL=48 Reply from 38.49.39.136: bytes=32 time=155ms TTL=48 Reply from 38.49.39.136: bytes=32 time=156ms TTL=48
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 155ms, Maximum = 156ms, Average = 155ms查看 |
GET PING Trace Dig |
|
湖南长沙移动 |
移动 |
湖南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
155.86ms |
154.723ms |
155.169ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=156ms TTL=52 Reply from 38.49.39.136: bytes=32 time=155ms TTL=52 Reply from 38.49.39.136: bytes=32 time=155ms TTL=52 Reply from 38.49.39.136: bytes=32 time=155ms TTL=52 Reply from 38.49.39.136: bytes=32 time=155ms TTL=52 Reply from 38.49.39.136: bytes=32 time=155ms TTL=52 Reply from 38.49.39.136: bytes=32 time=155ms TTL=52 Reply from 38.49.39.136: bytes=32 time=155ms TTL=52 Reply from 38.49.39.136: bytes=32 time=156ms TTL=52 Reply from 38.49.39.136: bytes=32 time=155ms TTL=52
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 155ms, Maximum = 156ms, Average = 155ms查看 |
GET PING Trace Dig |
|
福建南平市电信 |
电信 |
福建 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
184.06ms |
148.74ms |
154.844ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=150ms TTL=50 Reply from 38.49.39.136: bytes=32 time=184ms TTL=50 Reply from 38.49.39.136: bytes=32 time=149ms TTL=50 Reply from 38.49.39.136: bytes=32 time=149ms TTL=50 Reply from 38.49.39.136: bytes=32 time=151ms TTL=50 Reply from 38.49.39.136: bytes=32 time=158ms TTL=50 Reply from 38.49.39.136: bytes=32 time=150ms TTL=50 Reply from 38.49.39.136: bytes=32 time=154ms TTL=50 Reply from 38.49.39.136: bytes=32 time=149ms TTL=50 Reply from 38.49.39.136: bytes=32 time=156ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 149ms, Maximum = 184ms, Average = 155ms查看 |
GET PING Trace Dig |
|
山东济宁市联通 |
联通 |
山东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
162.442ms |
151.821ms |
154.786ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=156ms TTL=48 Reply from 38.49.39.136: bytes=32 time=152ms TTL=48 Reply from 38.49.39.136: bytes=32 time=152ms TTL=48 Reply from 38.49.39.136: bytes=32 time=154ms TTL=48 Reply from 38.49.39.136: bytes=32 time=162ms TTL=48 Reply from 38.49.39.136: bytes=32 time=153ms TTL=48 Reply from 38.49.39.136: bytes=32 time=153ms TTL=48 Reply from 38.49.39.136: bytes=32 time=161ms TTL=48 Reply from 38.49.39.136: bytes=32 time=152ms TTL=48 Reply from 38.49.39.136: bytes=32 time=152ms TTL=48
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 152ms, Maximum = 162ms, Average = 155ms查看 |
GET PING Trace Dig |
|
福建漳州市移动 |
移动 |
福建 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
154.861ms |
154.561ms |
154.708ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=155ms TTL=50 Reply from 38.49.39.136: bytes=32 time=155ms TTL=50 Reply from 38.49.39.136: bytes=32 time=155ms TTL=50 Reply from 38.49.39.136: bytes=32 time=155ms TTL=50 Reply from 38.49.39.136: bytes=32 time=155ms TTL=50 Reply from 38.49.39.136: bytes=32 time=155ms TTL=50 Reply from 38.49.39.136: bytes=32 time=155ms TTL=50 Reply from 38.49.39.136: bytes=32 time=155ms TTL=50 Reply from 38.49.39.136: bytes=32 time=155ms TTL=50 Reply from 38.49.39.136: bytes=32 time=155ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 155ms, Maximum = 155ms, Average = 155ms查看 |
GET PING Trace Dig |
|
湖北武汉移动 |
移动 |
湖北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
156.654ms |
151.24ms |
153.83ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=152ms TTL=50 Reply from 38.49.39.136: bytes=32 time=156ms TTL=50 Reply from 38.49.39.136: bytes=32 time=155ms TTL=50 Reply from 38.49.39.136: bytes=32 time=151ms TTL=50 Reply from 38.49.39.136: bytes=32 time=153ms TTL=50 Reply from 38.49.39.136: bytes=32 time=153ms TTL=50 Reply from 38.49.39.136: bytes=32 time=154ms TTL=50 Reply from 38.49.39.136: bytes=32 time=153ms TTL=50 Reply from 38.49.39.136: bytes=32 time=157ms TTL=50 Reply from 38.49.39.136: bytes=32 time=155ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 151ms, Maximum = 157ms, Average = 154ms查看 |
GET PING Trace Dig |
|
河南洛阳市电信 |
电信 |
河南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
153.735ms |
153.253ms |
153.373ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=153ms TTL=49 Reply from 38.49.39.136: bytes=32 time=153ms TTL=49 Reply from 38.49.39.136: bytes=32 time=154ms TTL=49 Reply from 38.49.39.136: bytes=32 time=153ms TTL=49 Reply from 38.49.39.136: bytes=32 time=153ms TTL=49 Reply from 38.49.39.136: bytes=32 time=153ms TTL=49 Reply from 38.49.39.136: bytes=32 time=153ms TTL=49 Reply from 38.49.39.136: bytes=32 time=153ms TTL=49 Reply from 38.49.39.136: bytes=32 time=153ms TTL=49 Reply from 38.49.39.136: bytes=32 time=153ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 153ms, Maximum = 154ms, Average = 153ms查看 |
GET PING Trace Dig |
|
台湾台湾 |
台湾 |
台湾 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
158.457ms |
149.634ms |
153.181ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=158ms TTL=43 Reply from 38.49.39.136: bytes=32 time=153ms TTL=43 Reply from 38.49.39.136: bytes=32 time=152ms TTL=43 Reply from 38.49.39.136: bytes=32 time=154ms TTL=43 Reply from 38.49.39.136: bytes=32 time=152ms TTL=43 Reply from 38.49.39.136: bytes=32 time=150ms TTL=43 Reply from 38.49.39.136: bytes=32 time=153ms TTL=43 Reply from 38.49.39.136: bytes=32 time=153ms TTL=43 Reply from 38.49.39.136: bytes=32 time=156ms TTL=43 Reply from 38.49.39.136: bytes=32 time=151ms TTL=43
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 150ms, Maximum = 158ms, Average = 153ms查看 |
GET PING Trace Dig |
|
江西赣州市移动 |
移动 |
江西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
153.84ms |
152.96ms |
153.168ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=154ms TTL=49 Reply from 38.49.39.136: bytes=32 time=153ms TTL=49 Reply from 38.49.39.136: bytes=32 time=153ms TTL=49 Reply from 38.49.39.136: bytes=32 time=153ms TTL=49 Reply from 38.49.39.136: bytes=32 time=153ms TTL=49 Reply from 38.49.39.136: bytes=32 time=153ms TTL=49 Reply from 38.49.39.136: bytes=32 time=153ms TTL=49 Reply from 38.49.39.136: bytes=32 time=153ms TTL=49 Reply from 38.49.39.136: bytes=32 time=153ms TTL=49 Reply from 38.49.39.136: bytes=32 time=153ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 153ms, Maximum = 154ms, Average = 153ms查看 |
GET PING Trace Dig |
|
江西南昌市移动 |
移动 |
江西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
156.04ms |
151.534ms |
152.976ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=152ms TTL=48 Reply from 38.49.39.136: bytes=32 time=156ms TTL=48 Reply from 38.49.39.136: bytes=32 time=152ms TTL=48 Reply from 38.49.39.136: bytes=32 time=153ms TTL=48 Reply from 38.49.39.136: bytes=32 time=155ms TTL=48 Reply from 38.49.39.136: bytes=32 time=152ms TTL=48 Reply from 38.49.39.136: bytes=32 time=153ms TTL=48 Reply from 38.49.39.136: bytes=32 time=153ms TTL=48 Reply from 38.49.39.136: bytes=32 time=152ms TTL=48 Reply from 38.49.39.136: bytes=32 time=153ms TTL=48
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 152ms, Maximum = 156ms, Average = 153ms查看 |
GET PING Trace Dig |
|
江西抚州市电信 |
电信 |
江西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
163.418ms |
149.802ms |
151.819ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=152ms TTL=50 Reply from 38.49.39.136: bytes=32 time=150ms TTL=50 Reply from 38.49.39.136: bytes=32 time=150ms TTL=50 Reply from 38.49.39.136: bytes=32 time=150ms TTL=50 Reply from 38.49.39.136: bytes=32 time=163ms TTL=50 Reply from 38.49.39.136: bytes=32 time=150ms TTL=50 Reply from 38.49.39.136: bytes=32 time=152ms TTL=50 Reply from 38.49.39.136: bytes=32 time=150ms TTL=50 Reply from 38.49.39.136: bytes=32 time=151ms TTL=50 Reply from 38.49.39.136: bytes=32 time=150ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 150ms, Maximum = 163ms, Average = 152ms查看 |
GET PING Trace Dig |
|
安徽合肥移动 |
移动 |
安徽 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
149.294ms |
148.81ms |
148.989ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=149ms TTL=49 Reply from 38.49.39.136: bytes=32 time=149ms TTL=49 Reply from 38.49.39.136: bytes=32 time=149ms TTL=49 Reply from 38.49.39.136: bytes=32 time=149ms TTL=49 Reply from 38.49.39.136: bytes=32 time=149ms TTL=49 Reply from 38.49.39.136: bytes=32 time=149ms TTL=49 Reply from 38.49.39.136: bytes=32 time=149ms TTL=49 Reply from 38.49.39.136: bytes=32 time=149ms TTL=49 Reply from 38.49.39.136: bytes=32 time=149ms TTL=49 Reply from 38.49.39.136: bytes=32 time=149ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 149ms, Maximum = 149ms, Average = 149ms查看 |
GET PING Trace Dig |
|
浙江丽水市电信 |
电信 |
浙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
142.858ms |
141.052ms |
141.669ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=142ms TTL=51 Reply from 38.49.39.136: bytes=32 time=141ms TTL=51 Reply from 38.49.39.136: bytes=32 time=142ms TTL=51 Reply from 38.49.39.136: bytes=32 time=142ms TTL=51 Reply from 38.49.39.136: bytes=32 time=141ms TTL=51 Reply from 38.49.39.136: bytes=32 time=141ms TTL=51 Reply from 38.49.39.136: bytes=32 time=141ms TTL=51 Reply from 38.49.39.136: bytes=32 time=142ms TTL=51 Reply from 38.49.39.136: bytes=32 time=142ms TTL=51 Reply from 38.49.39.136: bytes=32 time=143ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 141ms, Maximum = 143ms, Average = 142ms查看 |
GET PING Trace Dig |
|
湖北黄冈市电信 |
电信 |
湖北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
141.541ms |
140.361ms |
140.925ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=141ms TTL=52 Reply from 38.49.39.136: bytes=32 time=141ms TTL=52 Reply from 38.49.39.136: bytes=32 time=142ms TTL=52 Reply from 38.49.39.136: bytes=32 time=142ms TTL=52 Reply from 38.49.39.136: bytes=32 time=140ms TTL=52 Reply from 38.49.39.136: bytes=32 time=140ms TTL=52 Reply from 38.49.39.136: bytes=32 time=140ms TTL=52 Reply from 38.49.39.136: bytes=32 time=141ms TTL=52 Reply from 38.49.39.136: bytes=32 time=141ms TTL=52 Reply from 38.49.39.136: bytes=32 time=140ms TTL=52
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 140ms, Maximum = 142ms, Average = 141ms查看 |
GET PING Trace Dig |
|
上海上海市电信 |
电信 |
上海 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
143.834ms |
138.455ms |
140.656ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=138ms TTL=51 Reply from 38.49.39.136: bytes=32 time=142ms TTL=51 Reply from 38.49.39.136: bytes=32 time=144ms TTL=51 Reply from 38.49.39.136: bytes=32 time=140ms TTL=51 Reply from 38.49.39.136: bytes=32 time=141ms TTL=51 Reply from 38.49.39.136: bytes=32 time=141ms TTL=51 Reply from 38.49.39.136: bytes=32 time=141ms TTL=51 Reply from 38.49.39.136: bytes=32 time=139ms TTL=51 Reply from 38.49.39.136: bytes=32 time=141ms TTL=51 Reply from 38.49.39.136: bytes=32 time=140ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 138ms, Maximum = 144ms, Average = 141ms查看 |
GET PING Trace Dig |
|
湖北黄冈市电信 |
电信 |
湖北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
140.88ms |
139.92ms |
140.415ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=141ms TTL=51 Reply from 38.49.39.136: bytes=32 time=140ms TTL=51 Reply from 38.49.39.136: bytes=32 time=140ms TTL=51 Reply from 38.49.39.136: bytes=32 time=140ms TTL=51 Reply from 38.49.39.136: bytes=32 time=140ms TTL=51 Reply from 38.49.39.136: bytes=32 time=140ms TTL=51 Reply from 38.49.39.136: bytes=32 time=141ms TTL=51 Reply from 38.49.39.136: bytes=32 time=140ms TTL=51 Reply from 38.49.39.136: bytes=32 time=140ms TTL=51 Reply from 38.49.39.136: bytes=32 time=140ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 140ms, Maximum = 141ms, Average = 140ms查看 |
GET PING Trace Dig |
|
浙江杭州市联通 |
联通 |
浙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
141.653ms |
139.048ms |
139.902ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=140ms TTL=51 Reply from 38.49.39.136: bytes=32 time=140ms TTL=51 Reply from 38.49.39.136: bytes=32 time=140ms TTL=51 Reply from 38.49.39.136: bytes=32 time=142ms TTL=51 Reply from 38.49.39.136: bytes=32 time=139ms TTL=51 Reply from 38.49.39.136: bytes=32 time=139ms TTL=51 Reply from 38.49.39.136: bytes=32 time=140ms TTL=51 Reply from 38.49.39.136: bytes=32 time=140ms TTL=51 Reply from 38.49.39.136: bytes=32 time=140ms TTL=51 Reply from 38.49.39.136: bytes=32 time=140ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 139ms, Maximum = 142ms, Average = 140ms查看 |
GET PING Trace Dig |
|
浙江杭州市电信 |
电信 |
浙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
140.183ms |
139.625ms |
139.778ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=140ms TTL=50 Reply from 38.49.39.136: bytes=32 time=140ms TTL=50 Reply from 38.49.39.136: bytes=32 time=140ms TTL=50 Reply from 38.49.39.136: bytes=32 time=140ms TTL=50 Reply from 38.49.39.136: bytes=32 time=140ms TTL=50 Reply from 38.49.39.136: bytes=32 time=140ms TTL=50 Reply from 38.49.39.136: bytes=32 time=140ms TTL=50 Reply from 38.49.39.136: bytes=32 time=140ms TTL=50 Reply from 38.49.39.136: bytes=32 time=140ms TTL=50 Reply from 38.49.39.136: bytes=32 time=140ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 140ms, Maximum = 140ms, Average = 140ms查看 |
GET PING Trace Dig |
|
台湾台湾 |
台湾 |
台湾 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
148.661ms |
134.521ms |
138.941ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=138ms TTL=51 Reply from 38.49.39.136: bytes=32 time=136ms TTL=51 Reply from 38.49.39.136: bytes=32 time=149ms TTL=51 Reply from 38.49.39.136: bytes=32 time=135ms TTL=51 Reply from 38.49.39.136: bytes=32 time=138ms TTL=51 Reply from 38.49.39.136: bytes=32 time=142ms TTL=51 Reply from 38.49.39.136: bytes=32 time=137ms TTL=51 Reply from 38.49.39.136: bytes=32 time=138ms TTL=51 Reply from 38.49.39.136: bytes=32 time=138ms TTL=51 Reply from 38.49.39.136: bytes=32 time=139ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 135ms, Maximum = 149ms, Average = 139ms查看 |
GET PING Trace Dig |
|
江苏淮安市移动 |
移动 |
江苏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
138.92ms |
138.1ms |
138.612ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=138ms TTL=50 Reply from 38.49.39.136: bytes=32 time=139ms TTL=50 Reply from 38.49.39.136: bytes=32 time=138ms TTL=50 Reply from 38.49.39.136: bytes=32 time=139ms TTL=50 Reply from 38.49.39.136: bytes=32 time=139ms TTL=50 Reply from 38.49.39.136: bytes=32 time=138ms TTL=50 Reply from 38.49.39.136: bytes=32 time=139ms TTL=50 Reply from 38.49.39.136: bytes=32 time=139ms TTL=50 Reply from 38.49.39.136: bytes=32 time=139ms TTL=50 Reply from 38.49.39.136: bytes=32 time=139ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 138ms, Maximum = 139ms, Average = 139ms查看 |
GET PING Trace Dig |
|
上海上海市移动 |
移动 |
上海 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
144.316ms |
135.876ms |
138.233ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=144ms TTL=51 Reply from 38.49.39.136: bytes=32 time=136ms TTL=51 Reply from 38.49.39.136: bytes=32 time=138ms TTL=51 Reply from 38.49.39.136: bytes=32 time=137ms TTL=51 Reply from 38.49.39.136: bytes=32 time=136ms TTL=51 Reply from 38.49.39.136: bytes=32 time=136ms TTL=51 Reply from 38.49.39.136: bytes=32 time=136ms TTL=51 Reply from 38.49.39.136: bytes=32 time=136ms TTL=51 Reply from 38.49.39.136: bytes=32 time=139ms TTL=51 Reply from 38.49.39.136: bytes=32 time=144ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 136ms, Maximum = 144ms, Average = 138ms查看 |
GET PING Trace Dig |
|
江苏南京市移动 |
移动 |
江苏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
138.881ms |
136.481ms |
137.164ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=137ms TTL=49 Reply from 38.49.39.136: bytes=32 time=137ms TTL=49 Reply from 38.49.39.136: bytes=32 time=138ms TTL=49 Reply from 38.49.39.136: bytes=32 time=137ms TTL=49 Reply from 38.49.39.136: bytes=32 time=136ms TTL=49 Reply from 38.49.39.136: bytes=32 time=139ms TTL=49 Reply from 38.49.39.136: bytes=32 time=138ms TTL=49 Reply from 38.49.39.136: bytes=32 time=137ms TTL=49 Reply from 38.49.39.136: bytes=32 time=137ms TTL=49 Reply from 38.49.39.136: bytes=32 time=137ms TTL=49
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 136ms, Maximum = 139ms, Average = 137ms查看 |
GET PING Trace Dig |
|
安徽合肥市电信 |
电信 |
安徽 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
137.061ms |
136.781ms |
136.889ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=137ms TTL=51 Reply from 38.49.39.136: bytes=32 time=137ms TTL=51 Reply from 38.49.39.136: bytes=32 time=137ms TTL=51 Reply from 38.49.39.136: bytes=32 time=137ms TTL=51 Reply from 38.49.39.136: bytes=32 time=137ms TTL=51 Reply from 38.49.39.136: bytes=32 time=137ms TTL=51 Reply from 38.49.39.136: bytes=32 time=137ms TTL=51 Reply from 38.49.39.136: bytes=32 time=137ms TTL=51 Reply from 38.49.39.136: bytes=32 time=137ms TTL=51 Reply from 38.49.39.136: bytes=32 time=137ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 137ms, Maximum = 137ms, Average = 137ms查看 |
GET PING Trace Dig |
|
上海上海市电信 |
电信 |
上海 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
143.513ms |
134.352ms |
136.804ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=136ms TTL=47 Reply from 38.49.39.136: bytes=32 time=136ms TTL=47 Reply from 38.49.39.136: bytes=32 time=140ms TTL=47 Reply from 38.49.39.136: bytes=32 time=137ms TTL=47 Reply from 38.49.39.136: bytes=32 time=135ms TTL=47 Reply from 38.49.39.136: bytes=32 time=135ms TTL=47 Reply from 38.49.39.136: bytes=32 time=144ms TTL=47 Reply from 38.49.39.136: bytes=32 time=134ms TTL=47 Reply from 38.49.39.136: bytes=32 time=135ms TTL=47 Reply from 38.49.39.136: bytes=32 time=136ms TTL=47
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 134ms, Maximum = 144ms, Average = 137ms查看 |
GET PING Trace Dig |
|
浙江衢州市移动 |
移动 |
浙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
136.681ms |
136.281ms |
136.436ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=137ms TTL=51 Reply from 38.49.39.136: bytes=32 time=136ms TTL=51 Reply from 38.49.39.136: bytes=32 time=136ms TTL=51 Reply from 38.49.39.136: bytes=32 time=136ms TTL=51 Reply from 38.49.39.136: bytes=32 time=136ms TTL=51 Reply from 38.49.39.136: bytes=32 time=137ms TTL=51 Reply from 38.49.39.136: bytes=32 time=137ms TTL=51 Reply from 38.49.39.136: bytes=32 time=136ms TTL=51 Reply from 38.49.39.136: bytes=32 time=136ms TTL=51 Reply from 38.49.39.136: bytes=32 time=136ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 136ms, Maximum = 137ms, Average = 136ms查看 |
GET PING Trace Dig |
|
安徽安庆市电信 |
电信 |
安徽 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
135.529ms |
135.132ms |
135.304ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=135ms TTL=51 Reply from 38.49.39.136: bytes=32 time=135ms TTL=51 Reply from 38.49.39.136: bytes=32 time=135ms TTL=51 Reply from 38.49.39.136: bytes=32 time=135ms TTL=51 Reply from 38.49.39.136: bytes=32 time=135ms TTL=51 Reply from 38.49.39.136: bytes=32 time=135ms TTL=51 Reply from 38.49.39.136: bytes=32 time=135ms TTL=51 Reply from 38.49.39.136: bytes=32 time=135ms TTL=51 Reply from 38.49.39.136: bytes=32 time=135ms TTL=51 Reply from 38.49.39.136: bytes=32 time=136ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 135ms, Maximum = 136ms, Average = 135ms查看 |
GET PING Trace Dig |
|
浙江杭州市移动 |
移动 |
浙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
133.136ms |
132.727ms |
132.9ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=133ms TTL=50 Reply from 38.49.39.136: bytes=32 time=133ms TTL=50 Reply from 38.49.39.136: bytes=32 time=133ms TTL=50 Reply from 38.49.39.136: bytes=32 time=133ms TTL=50 Reply from 38.49.39.136: bytes=32 time=133ms TTL=50 Reply from 38.49.39.136: bytes=32 time=133ms TTL=50 Reply from 38.49.39.136: bytes=32 time=133ms TTL=50 Reply from 38.49.39.136: bytes=32 time=133ms TTL=50 Reply from 38.49.39.136: bytes=32 time=133ms TTL=50 Reply from 38.49.39.136: bytes=32 time=133ms TTL=50
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 133ms, Maximum = 133ms, Average = 133ms查看 |
GET PING Trace Dig |
|
江苏常州市电信 |
电信 |
江苏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
130.464ms |
130.302ms |
130.384ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=130ms TTL=52 Reply from 38.49.39.136: bytes=32 time=130ms TTL=52 Reply from 38.49.39.136: bytes=32 time=130ms TTL=52 Reply from 38.49.39.136: bytes=32 time=130ms TTL=52 Reply from 38.49.39.136: bytes=32 time=130ms TTL=52 Reply from 38.49.39.136: bytes=32 time=130ms TTL=52 Reply from 38.49.39.136: bytes=32 time=130ms TTL=52 Reply from 38.49.39.136: bytes=32 time=130ms TTL=52 Reply from 38.49.39.136: bytes=32 time=130ms TTL=52 Reply from 38.49.39.136: bytes=32 time=130ms TTL=52
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 130ms, Maximum = 130ms, Average = 130ms查看 |
GET PING Trace Dig |
|
美国国外 |
国外 |
美国 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
13.904ms |
13.665ms |
13.816ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Reply from 38.49.39.136: bytes=32 time=14ms TTL=51 Reply from 38.49.39.136: bytes=32 time=14ms TTL=51 Reply from 38.49.39.136: bytes=32 time=14ms TTL=51 Reply from 38.49.39.136: bytes=32 time=14ms TTL=51 Reply from 38.49.39.136: bytes=32 time=14ms TTL=51 Reply from 38.49.39.136: bytes=32 time=14ms TTL=51 Reply from 38.49.39.136: bytes=32 time=14ms TTL=51 Reply from 38.49.39.136: bytes=32 time=14ms TTL=51 Reply from 38.49.39.136: bytes=32 time=14ms TTL=51 Reply from 38.49.39.136: bytes=32 time=14ms TTL=51
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 14ms, Maximum = 14ms, Average = 14ms查看 |
GET PING Trace Dig |
|
吉林长春电信 |
电信 |
吉林 |
0.0.0.0 |
保留地址 |
10 |
0 |
10 |
0ms |
0ms |
0ms |
32B |
PING hmshu.com PING hmshu.com (0.0.0.0) with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out.
Ping statistics for 0.0.0.0: Packets: Sent = 10, Received = 0, Lost = 10 (100% loss), Approximate round trip times in milli-seconds: Minimum <1ms , Maximum <1ms , Average <1ms 查看 |
GET PING Trace Dig |
|
江苏南京市电信 |
电信 |
江苏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
0 |
10 |
0ms |
0ms |
0ms |
32B |
PING hmshu.com PING hmshu.com (38.49.39.136) with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out.
Ping statistics for 38.49.39.136: Packets: Sent = 10, Received = 0, Lost = 10 (100% loss), Approximate round trip times in milli-seconds: Minimum <1ms , Maximum <1ms , Average <1ms 查看 |
GET PING Trace Dig |
|