| 监测点 |
ISP |
省份 |
解析IP |
解析IP所在地 |
发送 |
接收 |
丢弃 |
最大时间 |
最小时间 |
平均时间 |
包大小 |
详细信息 |
操作 |
| 共162个点 |
6个 |
共36个 |
共2个独立IP |
共2个独立节点 |
10 |
9 |
1 |
211.201ms |
167.827ms |
181.699ms |
|
|
|
| 内蒙古通辽市移动 |
移动 |
内蒙古 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
803.66ms |
376.637ms |
650.624ms |
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=377ms TTL=48
Reply from 38.49.39.136: bytes=32 time=747ms TTL=48
Reply from 38.49.39.136: bytes=32 time=715ms TTL=48
Reply from 38.49.39.136: bytes=32 time=663ms TTL=48
Reply from 38.49.39.136: bytes=32 time=744ms TTL=48
Reply from 38.49.39.136: bytes=32 time=804ms TTL=48
Reply from 38.49.39.136: bytes=32 time=479ms TTL=48
Reply from 38.49.39.136: bytes=32 time=569ms TTL=48
Reply from 38.49.39.136: bytes=32 time=657ms TTL=48
Reply from 38.49.39.136: bytes=32 time=753ms 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 = 377ms, Maximum = 804ms, Average = 651ms查看 |
GET PING Trace Dig |
|
| 广东河源市移动 |
移动 |
广东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
975.498ms |
185.6ms |
533.305ms |
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=496ms TTL=47
Reply from 38.49.39.136: bytes=32 time=838ms TTL=47
Reply from 38.49.39.136: bytes=32 time=555ms TTL=47
Reply from 38.49.39.136: bytes=32 time=975ms TTL=47
Reply from 38.49.39.136: bytes=32 time=721ms TTL=47
Reply from 38.49.39.136: bytes=32 time=387ms TTL=47
Reply from 38.49.39.136: bytes=32 time=186ms TTL=47
Reply from 38.49.39.136: bytes=32 time=377ms TTL=47
Reply from 38.49.39.136: bytes=32 time=215ms TTL=47
Reply from 38.49.39.136: bytes=32 time=584ms 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 = 186ms, Maximum = 975ms, Average = 533ms查看 |
GET PING Trace Dig |
|
| 福建泉州移动 |
移动 |
福建 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
749.561ms |
153.85ms |
395.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=154ms TTL=48
Reply from 38.49.39.136: bytes=32 time=156ms TTL=48
Reply from 38.49.39.136: bytes=32 time=750ms TTL=48
Reply from 38.49.39.136: bytes=32 time=636ms TTL=48
Reply from 38.49.39.136: bytes=32 time=312ms TTL=48
Reply from 38.49.39.136: bytes=32 time=241ms TTL=48
Reply from 38.49.39.136: bytes=32 time=605ms TTL=48
Reply from 38.49.39.136: bytes=32 time=363ms TTL=48
Reply from 38.49.39.136: bytes=32 time=338ms TTL=48
Reply from 38.49.39.136: bytes=32 time=398ms 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 = 154ms, Maximum = 750ms, Average = 395ms查看 |
GET PING Trace Dig |
|
| 四川成都市电信 |
电信 |
四川 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
9 |
1 |
878.48ms |
109.216ms |
378.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=286ms TTL=50
Reply from 38.49.39.136: bytes=32 time=224ms TTL=50
Reply from 38.49.39.136: bytes=32 time=179ms TTL=50
Reply from 38.49.39.136: bytes=32 time=297ms TTL=50
Reply from 38.49.39.136: bytes=32 time=561ms TTL=50
Reply from 38.49.39.136: bytes=32 time=109ms TTL=50
Request timed out.
Reply from 38.49.39.136: bytes=32 time=878ms TTL=50
Reply from 38.49.39.136: bytes=32 time=490ms TTL=50
Reply from 38.49.39.136: bytes=32 time=380ms TTL=50
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 9, Lost = 1 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 109ms, Maximum = 878ms, Average = 378ms查看 |
GET PING Trace Dig |
|
| 宁夏银川电信 |
电信 |
宁夏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
9 |
1 |
620.488ms |
132.308ms |
341.698ms |
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=356ms TTL=50
Reply from 38.49.39.136: bytes=32 time=333ms TTL=50
Reply from 38.49.39.136: bytes=32 time=421ms TTL=50
Request timed out.
Reply from 38.49.39.136: bytes=32 time=132ms TTL=50
Reply from 38.49.39.136: bytes=32 time=287ms TTL=50
Reply from 38.49.39.136: bytes=32 time=186ms TTL=50
Reply from 38.49.39.136: bytes=32 time=620ms TTL=50
Reply from 38.49.39.136: bytes=32 time=458ms TTL=50
Reply from 38.49.39.136: bytes=32 time=281ms TTL=50
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 9, Lost = 1 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 132ms, Maximum = 620ms, Average = 342ms查看 |
GET PING Trace Dig |
|
| 新疆吐鲁番市电信 |
电信 |
新疆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
8 |
2 |
784.184ms |
203.936ms |
332.455ms |
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=409ms TTL=49
Reply from 38.49.39.136: bytes=32 time=784ms TTL=49
Reply from 38.49.39.136: bytes=32 time=304ms TTL=49
Reply from 38.49.39.136: bytes=32 time=339ms TTL=49
Request timed out.
Request timed out.
Reply from 38.49.39.136: bytes=32 time=205ms TTL=49
Reply from 38.49.39.136: bytes=32 time=209ms TTL=49
Reply from 38.49.39.136: bytes=32 time=206ms TTL=49
Reply from 38.49.39.136: bytes=32 time=204ms TTL=49
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 8, Lost = 2 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 204ms, Maximum = 784ms, Average = 332ms查看 |
GET PING Trace Dig |
|
| 青海西宁市电信 |
电信 |
青海 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
764.451ms |
179.891ms |
246.975ms |
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=193ms TTL=50
Reply from 38.49.39.136: bytes=32 time=188ms TTL=50
Reply from 38.49.39.136: bytes=32 time=185ms TTL=50
Reply from 38.49.39.136: bytes=32 time=182ms TTL=50
Reply from 38.49.39.136: bytes=32 time=185ms TTL=50
Reply from 38.49.39.136: bytes=32 time=224ms 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=180ms TTL=50
Reply from 38.49.39.136: bytes=32 time=764ms 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 = 764ms, Average = 247ms查看 |
GET PING Trace Dig |
|
| 河南濮阳市联通 |
联通 |
河南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
319.172ms |
214.415ms |
238.66ms |
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=223ms TTL=65
Reply from 38.49.39.136: bytes=32 time=214ms TTL=65
Reply from 38.49.39.136: bytes=32 time=225ms TTL=65
Reply from 38.49.39.136: bytes=32 time=250ms TTL=65
Reply from 38.49.39.136: bytes=32 time=229ms TTL=65
Reply from 38.49.39.136: bytes=32 time=234ms TTL=65
Reply from 38.49.39.136: bytes=32 time=319ms TTL=65
Reply from 38.49.39.136: bytes=32 time=231ms TTL=65
Reply from 38.49.39.136: bytes=32 time=224ms TTL=65
Reply from 38.49.39.136: bytes=32 time=238ms TTL=65
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 214ms, Maximum = 319ms, Average = 239ms查看 |
GET PING Trace Dig |
|
| 宁夏银川市联通 |
联通 |
宁夏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
309.745ms |
208.868ms |
236.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=209ms TTL=47
Reply from 38.49.39.136: bytes=32 time=212ms TTL=47
Reply from 38.49.39.136: bytes=32 time=308ms TTL=47
Reply from 38.49.39.136: bytes=32 time=310ms TTL=47
Reply from 38.49.39.136: bytes=32 time=238ms TTL=47
Reply from 38.49.39.136: bytes=32 time=229ms TTL=47
Reply from 38.49.39.136: bytes=32 time=223ms TTL=47
Reply from 38.49.39.136: bytes=32 time=212ms TTL=47
Reply from 38.49.39.136: bytes=32 time=212ms TTL=47
Reply from 38.49.39.136: bytes=32 time=215ms 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 = 209ms, Maximum = 310ms, Average = 237ms查看 |
GET PING Trace Dig |
|
| 黑龙江哈尔滨市移动 |
移动 |
黑龙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
244.685ms |
231.416ms |
236.433ms |
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=242ms TTL=64
Reply from 38.49.39.136: bytes=32 time=242ms TTL=64
Reply from 38.49.39.136: bytes=32 time=239ms TTL=64
Reply from 38.49.39.136: bytes=32 time=231ms TTL=64
Reply from 38.49.39.136: bytes=32 time=235ms TTL=64
Reply from 38.49.39.136: bytes=32 time=232ms TTL=64
Reply from 38.49.39.136: bytes=32 time=245ms TTL=64
Reply from 38.49.39.136: bytes=32 time=233ms TTL=64
Reply from 38.49.39.136: bytes=32 time=233ms TTL=64
Reply from 38.49.39.136: bytes=32 time=234ms TTL=64
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 = 245ms, Average = 236ms查看 |
GET PING Trace Dig |
|
| 新疆乌鲁木齐市电信 |
电信 |
新疆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
261.139ms |
198.179ms |
228.705ms |
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=261ms TTL=48
Reply from 38.49.39.136: bytes=32 time=258ms TTL=48
Reply from 38.49.39.136: bytes=32 time=260ms TTL=48
Reply from 38.49.39.136: bytes=32 time=250ms TTL=48
Reply from 38.49.39.136: bytes=32 time=260ms TTL=48
Reply from 38.49.39.136: bytes=32 time=201ms 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=203ms 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 = 261ms, Average = 229ms查看 |
GET PING Trace Dig |
|
| 西藏拉萨市移动 |
移动 |
西藏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
224.899ms |
224.299ms |
224.497ms |
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=224ms TTL=50
Reply from 38.49.39.136: bytes=32 time=224ms TTL=50
Reply from 38.49.39.136: bytes=32 time=224ms TTL=50
Reply from 38.49.39.136: bytes=32 time=224ms TTL=50
Reply from 38.49.39.136: bytes=32 time=225ms TTL=50
Reply from 38.49.39.136: bytes=32 time=225ms TTL=50
Reply from 38.49.39.136: bytes=32 time=225ms TTL=50
Reply from 38.49.39.136: bytes=32 time=225ms TTL=50
Reply from 38.49.39.136: bytes=32 time=224ms TTL=50
Reply from 38.49.39.136: bytes=32 time=225ms 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 = 224ms, Maximum = 225ms, Average = 224ms查看 |
GET PING Trace Dig |
|
| 黑龙江齐齐哈尔市联通 |
联通 |
黑龙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
230.333ms |
220.981ms |
223.568ms |
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=230ms TTL=49
Reply from 38.49.39.136: bytes=32 time=222ms TTL=49
Reply from 38.49.39.136: bytes=32 time=221ms TTL=49
Reply from 38.49.39.136: bytes=32 time=224ms TTL=49
Reply from 38.49.39.136: bytes=32 time=223ms TTL=49
Reply from 38.49.39.136: bytes=32 time=223ms TTL=49
Reply from 38.49.39.136: bytes=32 time=223ms TTL=49
Reply from 38.49.39.136: bytes=32 time=224ms TTL=49
Reply from 38.49.39.136: bytes=32 time=223ms TTL=49
Reply from 38.49.39.136: bytes=32 time=222ms 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 = 221ms, Maximum = 230ms, Average = 224ms查看 |
GET PING Trace Dig |
|
| 安徽淮北市移动 |
移动 |
安徽 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
539.433ms |
155.095ms |
220.598ms |
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=539ms TTL=50
Reply from 38.49.39.136: bytes=32 time=165ms TTL=50
Reply from 38.49.39.136: bytes=32 time=162ms TTL=50
Reply from 38.49.39.136: bytes=32 time=254ms 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=188ms TTL=50
Reply from 38.49.39.136: bytes=32 time=155ms TTL=50
Reply from 38.49.39.136: bytes=32 time=174ms 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 = 155ms, Maximum = 539ms, Average = 221ms查看 |
GET PING Trace Dig |
|
| 新疆阿克苏地区移动 |
移动 |
新疆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
219.107ms |
217.838ms |
218.358ms |
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=219ms TTL=49
Reply from 38.49.39.136: bytes=32 time=219ms TTL=49
Reply from 38.49.39.136: bytes=32 time=218ms TTL=49
Reply from 38.49.39.136: bytes=32 time=218ms TTL=49
Reply from 38.49.39.136: bytes=32 time=218ms TTL=49
Reply from 38.49.39.136: bytes=32 time=219ms TTL=49
Reply from 38.49.39.136: bytes=32 time=218ms TTL=49
Reply from 38.49.39.136: bytes=32 time=218ms TTL=49
Reply from 38.49.39.136: bytes=32 time=218ms TTL=49
Reply from 38.49.39.136: bytes=32 time=218ms 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 = 218ms, Maximum = 219ms, Average = 218ms查看 |
GET PING Trace Dig |
|
| 辽宁丹东市联通 |
联通 |
辽宁 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
340.27ms |
187.546ms |
216.673ms |
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=188ms TTL=50
Reply from 38.49.39.136: bytes=32 time=197ms TTL=50
Reply from 38.49.39.136: bytes=32 time=207ms TTL=50
Reply from 38.49.39.136: bytes=32 time=292ms TTL=50
Reply from 38.49.39.136: bytes=32 time=340ms TTL=50
Reply from 38.49.39.136: bytes=32 time=191ms TTL=50
Reply from 38.49.39.136: bytes=32 time=188ms TTL=50
Reply from 38.49.39.136: bytes=32 time=188ms TTL=50
Reply from 38.49.39.136: bytes=32 time=188ms 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 = 188ms, Maximum = 340ms, Average = 217ms查看 |
GET PING Trace Dig |
|
| 黑龙江哈尔滨市电信 |
电信 |
黑龙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
218.619ms |
208.619ms |
212.013ms |
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=209ms TTL=49
Reply from 38.49.39.136: bytes=32 time=209ms TTL=49
Reply from 38.49.39.136: bytes=32 time=215ms TTL=49
Reply from 38.49.39.136: bytes=32 time=214ms TTL=49
Reply from 38.49.39.136: bytes=32 time=213ms TTL=49
Reply from 38.49.39.136: bytes=32 time=211ms TTL=49
Reply from 38.49.39.136: bytes=32 time=210ms TTL=49
Reply from 38.49.39.136: bytes=32 time=219ms TTL=49
Reply from 38.49.39.136: bytes=32 time=211ms TTL=49
Reply from 38.49.39.136: bytes=32 time=211ms 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 = 209ms, Maximum = 219ms, Average = 212ms查看 |
GET PING Trace Dig |
|
| 吉林松原市联通 |
联通 |
吉林 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
215.988ms |
208.767ms |
209.849ms |
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=209ms TTL=49
Reply from 38.49.39.136: bytes=32 time=209ms TTL=49
Reply from 38.49.39.136: bytes=32 time=209ms TTL=49
Reply from 38.49.39.136: bytes=32 time=209ms TTL=49
Reply from 38.49.39.136: bytes=32 time=209ms TTL=49
Reply from 38.49.39.136: bytes=32 time=210ms TTL=49
Reply from 38.49.39.136: bytes=32 time=216ms TTL=49
Reply from 38.49.39.136: bytes=32 time=209ms TTL=49
Reply from 38.49.39.136: bytes=32 time=209ms TTL=49
Reply from 38.49.39.136: bytes=32 time=209ms 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 = 209ms, Maximum = 216ms, Average = 210ms查看 |
GET PING Trace Dig |
|
| 黑龙江哈尔滨市联通 |
联通 |
黑龙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
214.647ms |
207.159ms |
209.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=208ms TTL=48
Reply from 38.49.39.136: bytes=32 time=209ms TTL=48
Reply from 38.49.39.136: bytes=32 time=210ms TTL=48
Reply from 38.49.39.136: bytes=32 time=208ms TTL=48
Reply from 38.49.39.136: bytes=32 time=207ms TTL=48
Reply from 38.49.39.136: bytes=32 time=215ms TTL=48
Reply from 38.49.39.136: bytes=32 time=212ms TTL=48
Reply from 38.49.39.136: bytes=32 time=210ms TTL=48
Reply from 38.49.39.136: bytes=32 time=209ms TTL=48
Reply from 38.49.39.136: bytes=32 time=210ms 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 = 207ms, Maximum = 215ms, Average = 210ms查看 |
GET PING Trace Dig |
|
| 广东广州市电信 |
电信 |
广东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
375.22ms |
161.48ms |
209.394ms |
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=219ms TTL=52
Reply from 38.49.39.136: bytes=32 time=200ms TTL=52
Reply from 38.49.39.136: bytes=32 time=172ms TTL=52
Reply from 38.49.39.136: bytes=32 time=205ms TTL=52
Reply from 38.49.39.136: bytes=32 time=174ms TTL=52
Reply from 38.49.39.136: bytes=32 time=161ms TTL=52
Reply from 38.49.39.136: bytes=32 time=187ms TTL=52
Reply from 38.49.39.136: bytes=32 time=193ms TTL=52
Reply from 38.49.39.136: bytes=32 time=208ms TTL=52
Reply from 38.49.39.136: bytes=32 time=375ms 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 = 161ms, Maximum = 375ms, Average = 209ms查看 |
GET PING Trace Dig |
|
| 吉林四平市联通 |
联通 |
吉林 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
211.681ms |
207.54ms |
208.52ms |
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=209ms TTL=44
Reply from 38.49.39.136: bytes=32 time=210ms TTL=44
Reply from 38.49.39.136: bytes=32 time=208ms TTL=44
Reply from 38.49.39.136: bytes=32 time=208ms TTL=44
Reply from 38.49.39.136: bytes=32 time=208ms TTL=44
Reply from 38.49.39.136: bytes=32 time=208ms TTL=44
Reply from 38.49.39.136: bytes=32 time=208ms TTL=44
Reply from 38.49.39.136: bytes=32 time=208ms TTL=44
Reply from 38.49.39.136: bytes=32 time=208ms TTL=44
Reply from 38.49.39.136: bytes=32 time=212ms TTL=44
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 208ms, Maximum = 212ms, Average = 209ms查看 |
GET PING Trace Dig |
|
| 山东济南市电信 |
电信 |
山东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
7 |
3 |
216.861ms |
200.781ms |
207.537ms |
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=208ms TTL=48
Request timed out.
Reply from 38.49.39.136: bytes=32 time=208ms TTL=48
Reply from 38.49.39.136: bytes=32 time=201ms TTL=48
Request timed out.
Reply from 38.49.39.136: bytes=32 time=204ms TTL=48
Reply from 38.49.39.136: bytes=32 time=213ms TTL=48
Reply from 38.49.39.136: bytes=32 time=202ms TTL=48
Request timed out.
Reply from 38.49.39.136: bytes=32 time=217ms TTL=48
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 7, Lost = 3 (30% loss),
Approximate round trip times in milli-seconds:
Minimum = 201ms, Maximum = 217ms, Average = 208ms查看 |
GET PING Trace Dig |
|
| 云南昆明市联通 |
联通 |
云南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
235.803ms |
196.246ms |
207.092ms |
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=214ms TTL=47
Reply from 38.49.39.136: bytes=32 time=200ms TTL=47
Reply from 38.49.39.136: bytes=32 time=200ms TTL=47
Reply from 38.49.39.136: bytes=32 time=196ms TTL=47
Reply from 38.49.39.136: bytes=32 time=210ms TTL=47
Reply from 38.49.39.136: bytes=32 time=201ms TTL=47
Reply from 38.49.39.136: bytes=32 time=205ms TTL=47
Reply from 38.49.39.136: bytes=32 time=203ms TTL=47
Reply from 38.49.39.136: bytes=32 time=205ms TTL=47
Reply from 38.49.39.136: bytes=32 time=236ms 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 = 196ms, Maximum = 236ms, Average = 207ms查看 |
GET PING Trace Dig |
|
| 广东广州市联通 |
联通 |
广东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
281.414ms |
180.557ms |
206.228ms |
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=194ms TTL=47
Reply from 38.49.39.136: bytes=32 time=191ms TTL=47
Reply from 38.49.39.136: bytes=32 time=196ms TTL=47
Reply from 38.49.39.136: bytes=32 time=190ms TTL=47
Reply from 38.49.39.136: bytes=32 time=181ms TTL=47
Reply from 38.49.39.136: bytes=32 time=181ms TTL=47
Reply from 38.49.39.136: bytes=32 time=281ms TTL=47
Reply from 38.49.39.136: bytes=32 time=264ms TTL=47
Reply from 38.49.39.136: bytes=32 time=202ms TTL=47
Reply from 38.49.39.136: bytes=32 time=181ms 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 = 181ms, Maximum = 281ms, Average = 206ms查看 |
GET PING Trace Dig |
|
| 北京北京市移动 |
移动 |
北京 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
275.181ms |
188.92ms |
202.331ms |
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=50
Reply from 38.49.39.136: bytes=32 time=205ms TTL=50
Reply from 38.49.39.136: bytes=32 time=195ms TTL=50
Reply from 38.49.39.136: bytes=32 time=200ms TTL=50
Reply from 38.49.39.136: bytes=32 time=189ms TTL=50
Reply from 38.49.39.136: bytes=32 time=198ms TTL=50
Reply from 38.49.39.136: bytes=32 time=275ms TTL=50
Reply from 38.49.39.136: bytes=32 time=192ms TTL=50
Reply from 38.49.39.136: bytes=32 time=190ms TTL=50
Reply from 38.49.39.136: bytes=32 time=190ms 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 = 189ms, Maximum = 275ms, Average = 202ms查看 |
GET PING Trace Dig |
|
| 云南大理白族自治州电信 |
电信 |
云南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
328.284ms |
187.482ms |
202.224ms |
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=51
Reply from 38.49.39.136: bytes=32 time=189ms TTL=51
Reply from 38.49.39.136: bytes=32 time=187ms TTL=51
Reply from 38.49.39.136: bytes=32 time=188ms TTL=51
Reply from 38.49.39.136: bytes=32 time=188ms TTL=51
Reply from 38.49.39.136: bytes=32 time=188ms TTL=51
Reply from 38.49.39.136: bytes=32 time=189ms TTL=51
Reply from 38.49.39.136: bytes=32 time=188ms TTL=51
Reply from 38.49.39.136: bytes=32 time=189ms TTL=51
Reply from 38.49.39.136: bytes=32 time=328ms 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 = 187ms, Maximum = 328ms, Average = 202ms查看 |
GET PING Trace Dig |
|
| 湖南长沙市联通 |
联通 |
湖南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
260.455ms |
178.011ms |
200.456ms |
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=193ms TTL=45
Reply from 38.49.39.136: bytes=32 time=210ms TTL=45
Reply from 38.49.39.136: bytes=32 time=191ms TTL=45
Reply from 38.49.39.136: bytes=32 time=178ms TTL=45
Reply from 38.49.39.136: bytes=32 time=188ms TTL=45
Reply from 38.49.39.136: bytes=32 time=178ms TTL=45
Reply from 38.49.39.136: bytes=32 time=189ms TTL=45
Reply from 38.49.39.136: bytes=32 time=260ms TTL=45
Reply from 38.49.39.136: bytes=32 time=228ms TTL=45
Reply from 38.49.39.136: bytes=32 time=188ms TTL=45
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 = 260ms, Average = 200ms查看 |
GET PING Trace Dig |
|
| 辽宁沈阳市移动 |
移动 |
辽宁 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
211.379ms |
196.894ms |
199.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=197ms TTL=50
Reply from 38.49.39.136: bytes=32 time=200ms TTL=50
Reply from 38.49.39.136: bytes=32 time=197ms TTL=50
Reply from 38.49.39.136: bytes=32 time=197ms TTL=50
Reply from 38.49.39.136: bytes=32 time=197ms TTL=50
Reply from 38.49.39.136: bytes=32 time=197ms TTL=50
Reply from 38.49.39.136: bytes=32 time=198ms TTL=50
Reply from 38.49.39.136: bytes=32 time=197ms TTL=50
Reply from 38.49.39.136: bytes=32 time=211ms TTL=50
Reply from 38.49.39.136: bytes=32 time=207ms 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 = 197ms, Maximum = 211ms, Average = 200ms查看 |
GET PING Trace Dig |
|
| 辽宁沈阳市联通 |
联通 |
辽宁 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
200.84ms |
195.52ms |
196.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=196ms 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=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=197ms TTL=50
Reply from 38.49.39.136: bytes=32 time=196ms TTL=50
Reply from 38.49.39.136: bytes=32 time=197ms 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 |
195.882ms |
193.892ms |
194.47ms |
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=194ms TTL=48
Reply from 38.49.39.136: bytes=32 time=194ms TTL=48
Reply from 38.49.39.136: bytes=32 time=194ms TTL=48
Reply from 38.49.39.136: bytes=32 time=195ms TTL=48
Reply from 38.49.39.136: bytes=32 time=194ms TTL=48
Reply from 38.49.39.136: bytes=32 time=196ms TTL=48
Reply from 38.49.39.136: bytes=32 time=194ms TTL=48
Reply from 38.49.39.136: bytes=32 time=194ms TTL=48
Reply from 38.49.39.136: bytes=32 time=194ms TTL=48
Reply from 38.49.39.136: bytes=32 time=195ms 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 = 194ms, Maximum = 196ms, Average = 194ms查看 |
GET PING Trace Dig |
|
| 云南玉溪市电信 |
电信 |
云南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
9 |
1 |
200.259ms |
183.399ms |
190.732ms |
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=194ms TTL=50
Request timed out.
Reply from 38.49.39.136: bytes=32 time=185ms TTL=50
Reply from 38.49.39.136: bytes=32 time=189ms TTL=50
Reply from 38.49.39.136: bytes=32 time=188ms TTL=50
Reply from 38.49.39.136: bytes=32 time=183ms TTL=50
Reply from 38.49.39.136: bytes=32 time=186ms TTL=50
Reply from 38.49.39.136: bytes=32 time=196ms 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 = 9, Lost = 1 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 183ms, Maximum = 200ms, Average = 191ms查看 |
GET PING Trace Dig |
|
| 西藏拉萨市电信 |
电信 |
西藏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
191.081ms |
189.382ms |
190.152ms |
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=190ms 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
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=190ms 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
Reply from 38.49.39.136: bytes=32 time=190ms 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 = 191ms, Average = 190ms查看 |
GET PING Trace Dig |
|
| 贵州铜仁市电信 |
电信 |
贵州 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
189.79ms |
189.41ms |
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=190ms TTL=51
Reply from 38.49.39.136: bytes=32 time=189ms TTL=51
Reply from 38.49.39.136: bytes=32 time=189ms TTL=51
Reply from 38.49.39.136: bytes=32 time=190ms TTL=51
Reply from 38.49.39.136: bytes=32 time=190ms TTL=51
Reply from 38.49.39.136: bytes=32 time=190ms TTL=51
Reply from 38.49.39.136: bytes=32 time=189ms TTL=51
Reply from 38.49.39.136: bytes=32 time=190ms TTL=51
Reply from 38.49.39.136: bytes=32 time=189ms TTL=51
Reply from 38.49.39.136: bytes=32 time=190ms 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 = 189ms, Maximum = 190ms, Average = 190ms查看 |
GET PING Trace Dig |
|
| 陕西西安市移动 |
移动 |
陕西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
9 |
1 |
194.085ms |
185.144ms |
189.366ms |
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=191ms TTL=47
Reply from 38.49.39.136: bytes=32 time=194ms TTL=47
Request timed out.
Reply from 38.49.39.136: bytes=32 time=186ms 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=191ms TTL=47
Reply from 38.49.39.136: bytes=32 time=192ms TTL=47
Reply from 38.49.39.136: bytes=32 time=186ms TTL=47
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 9, Lost = 1 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 185ms, Maximum = 194ms, Average = 189ms查看 |
GET PING Trace Dig |
|
| 内蒙古呼和浩特电信 |
电信 |
内蒙古 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
189.941ms |
187.681ms |
188.801ms |
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=189ms TTL=47
Reply from 38.49.39.136: bytes=32 time=188ms TTL=47
Reply from 38.49.39.136: bytes=32 time=188ms TTL=47
Reply from 38.49.39.136: bytes=32 time=188ms 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=189ms TTL=47
Reply from 38.49.39.136: bytes=32 time=189ms 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 = 190ms, Average = 189ms查看 |
GET PING Trace Dig |
|
| 贵州贵阳市联通 |
联通 |
贵州 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
194.999ms |
184.199ms |
187.67ms |
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=194ms TTL=50
Reply from 38.49.39.136: bytes=32 time=195ms TTL=50
Reply from 38.49.39.136: bytes=32 time=191ms TTL=50
Reply from 38.49.39.136: bytes=32 time=187ms TTL=50
Reply from 38.49.39.136: bytes=32 time=187ms TTL=50
Reply from 38.49.39.136: bytes=32 time=184ms TTL=50
Reply from 38.49.39.136: bytes=32 time=184ms TTL=50
Reply from 38.49.39.136: bytes=32 time=184ms TTL=50
Reply from 38.49.39.136: bytes=32 time=184ms TTL=50
Reply from 38.49.39.136: bytes=32 time=185ms 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 = 195ms, Average = 188ms查看 |
GET PING Trace Dig |
|
| 黑龙江鸡西市移动 |
移动 |
黑龙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
225.781ms |
180.941ms |
187.614ms |
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=47
Reply from 38.49.39.136: bytes=32 time=181ms TTL=47
Reply from 38.49.39.136: bytes=32 time=182ms TTL=47
Reply from 38.49.39.136: bytes=32 time=187ms TTL=47
Reply from 38.49.39.136: bytes=32 time=181ms TTL=47
Reply from 38.49.39.136: bytes=32 time=226ms TTL=47
Reply from 38.49.39.136: bytes=32 time=184ms TTL=47
Reply from 38.49.39.136: bytes=32 time=187ms TTL=47
Reply from 38.49.39.136: bytes=32 time=185ms TTL=47
Reply from 38.49.39.136: bytes=32 time=182ms 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 = 181ms, Maximum = 226ms, Average = 188ms查看 |
GET PING Trace Dig |
|
| 甘肃武威移动 |
移动 |
甘肃 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
300.401ms |
171.981ms |
186.261ms |
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=172ms TTL=47
Reply from 38.49.39.136: bytes=32 time=173ms TTL=47
Reply from 38.49.39.136: bytes=32 time=300ms TTL=47
Reply from 38.49.39.136: bytes=32 time=177ms TTL=47
Reply from 38.49.39.136: bytes=32 time=175ms TTL=47
Reply from 38.49.39.136: bytes=32 time=173ms TTL=47
Reply from 38.49.39.136: bytes=32 time=173ms TTL=47
Reply from 38.49.39.136: bytes=32 time=173ms 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 = 172ms, Maximum = 300ms, Average = 186ms查看 |
GET PING Trace Dig |
|
| 广西玉林市联通 |
联通 |
广西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
212.611ms |
179.571ms |
185.881ms |
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=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=185ms TTL=50
Reply from 38.49.39.136: bytes=32 time=196ms TTL=50
Reply from 38.49.39.136: bytes=32 time=181ms TTL=50
Reply from 38.49.39.136: bytes=32 time=183ms TTL=50
Reply from 38.49.39.136: bytes=32 time=213ms 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
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 = 213ms, Average = 186ms查看 |
GET PING Trace Dig |
|
| 福建漳州市电信 |
电信 |
福建 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
197.36ms |
180.481ms |
185.853ms |
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=190ms TTL=50
Reply from 38.49.39.136: bytes=32 time=185ms TTL=50
Reply from 38.49.39.136: bytes=32 time=184ms TTL=50
Reply from 38.49.39.136: bytes=32 time=183ms TTL=50
Reply from 38.49.39.136: bytes=32 time=184ms TTL=50
Reply from 38.49.39.136: bytes=32 time=180ms TTL=50
Reply from 38.49.39.136: bytes=32 time=197ms TTL=50
Reply from 38.49.39.136: bytes=32 time=185ms TTL=50
Reply from 38.49.39.136: bytes=32 time=187ms 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 = 197ms, Average = 186ms查看 |
GET PING Trace Dig |
|
| 云南保山市移动 |
移动 |
云南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
185.139ms |
184.038ms |
184.31ms |
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=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=184ms 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=184ms TTL=47
Reply from 38.49.39.136: bytes=32 time=184ms 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 = 184ms查看 |
GET PING Trace Dig |
|
| 天津天津市联通 |
联通 |
天津 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
187.679ms |
182.136ms |
184.23ms |
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=183ms TTL=50
Reply from 38.49.39.136: bytes=32 time=187ms 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=188ms TTL=50
Reply from 38.49.39.136: bytes=32 time=183ms TTL=50
Reply from 38.49.39.136: bytes=32 time=184ms TTL=50
Reply from 38.49.39.136: bytes=32 time=187ms TTL=50
Reply from 38.49.39.136: bytes=32 time=182ms 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 = 188ms, Average = 184ms查看 |
GET PING Trace Dig |
|
| 广西未知联通 |
联通 |
广西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
215.407ms |
178.01ms |
183.869ms |
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=44
Reply from 38.49.39.136: bytes=32 time=182ms TTL=44
Reply from 38.49.39.136: bytes=32 time=180ms TTL=44
Reply from 38.49.39.136: bytes=32 time=180ms TTL=44
Reply from 38.49.39.136: bytes=32 time=179ms TTL=44
Reply from 38.49.39.136: bytes=32 time=179ms TTL=44
Reply from 38.49.39.136: bytes=32 time=178ms TTL=44
Reply from 38.49.39.136: bytes=32 time=180ms TTL=44
Reply from 38.49.39.136: bytes=32 time=215ms TTL=44
Reply from 38.49.39.136: bytes=32 time=185ms TTL=44
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 = 215ms, Average = 184ms查看 |
GET PING Trace Dig |
|
| 河北张家口市联通 |
联通 |
河北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
187.316ms |
182.625ms |
183.66ms |
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=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=183ms TTL=50
Reply from 38.49.39.136: bytes=32 time=183ms TTL=50
Reply from 38.49.39.136: bytes=32 time=187ms 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=183ms 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 = 183ms, Maximum = 187ms, Average = 184ms查看 |
GET PING Trace Dig |
|
| 河南郑州市电信 |
电信 |
河南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
183.48ms |
182.611ms |
183.126ms |
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=183ms 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=183ms 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=183ms 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
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 = 183ms, Average = 183ms查看 |
GET PING Trace Dig |
|
| 吉林长春电信 |
电信 |
吉林 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
197.491ms |
174.372ms |
182.405ms |
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=50
Reply from 38.49.39.136: bytes=32 time=192ms TTL=50
Reply from 38.49.39.136: bytes=32 time=183ms TTL=50
Reply from 38.49.39.136: bytes=32 time=197ms TTL=50
Reply from 38.49.39.136: bytes=32 time=176ms 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=174ms TTL=50
Reply from 38.49.39.136: bytes=32 time=174ms 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 = 174ms, Maximum = 197ms, Average = 182ms查看 |
GET PING Trace Dig |
|
| 青海西宁市电信 |
电信 |
青海 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
9 |
1 |
188.105ms |
180.439ms |
182.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=181ms TTL=49
Reply from 38.49.39.136: bytes=32 time=183ms TTL=49
Reply from 38.49.39.136: bytes=32 time=188ms TTL=49
Reply from 38.49.39.136: bytes=32 time=184ms TTL=49
Request timed out.
Reply from 38.49.39.136: bytes=32 time=180ms TTL=49
Reply from 38.49.39.136: bytes=32 time=180ms TTL=49
Reply from 38.49.39.136: bytes=32 time=181ms TTL=49
Reply from 38.49.39.136: bytes=32 time=181ms 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 = 9, Lost = 1 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 180ms, Maximum = 188ms, Average = 182ms查看 |
GET PING Trace Dig |
|
| 印度尼西亚国外 |
国外 |
印度尼西亚 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
182.338ms |
181.298ms |
181.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=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=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=182ms TTL=50
Reply from 38.49.39.136: bytes=32 time=182ms TTL=50
Reply from 38.49.39.136: bytes=32 time=181ms TTL=50
Reply from 38.49.39.136: bytes=32 time=181ms 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 = 181ms, Maximum = 182ms, Average = 182ms查看 |
GET PING Trace Dig |
|
| 四川德阳市电信 |
电信 |
四川 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
183.123ms |
179.542ms |
181.568ms |
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=51
Reply from 38.49.39.136: bytes=32 time=180ms TTL=51
Reply from 38.49.39.136: bytes=32 time=182ms TTL=51
Reply from 38.49.39.136: bytes=32 time=182ms TTL=51
Reply from 38.49.39.136: bytes=32 time=183ms TTL=51
Reply from 38.49.39.136: bytes=32 time=180ms TTL=51
Reply from 38.49.39.136: bytes=32 time=183ms 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=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 = 183ms, Average = 182ms查看 |
GET PING Trace Dig |
|
| 贵州遵义市联通 |
联通 |
贵州 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
181.442ms |
180.942ms |
181.196ms |
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=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=181ms 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=181ms 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=181ms 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 = 181ms, Average = 181ms查看 |
GET PING Trace Dig |
|
| 北京北京市联通 |
联通 |
北京 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
187.906ms |
179.268ms |
180.887ms |
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=179ms TTL=49
Reply from 38.49.39.136: bytes=32 time=188ms TTL=49
Reply from 38.49.39.136: bytes=32 time=180ms TTL=49
Reply from 38.49.39.136: bytes=32 time=180ms 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
Reply from 38.49.39.136: bytes=32 time=181ms 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 = 179ms, Maximum = 188ms, Average = 181ms查看 |
GET PING Trace Dig |
|
| 四川成都市联通 |
联通 |
四川 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
187.537ms |
178.56ms |
180.862ms |
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=46
Reply from 38.49.39.136: bytes=32 time=179ms TTL=46
Reply from 38.49.39.136: bytes=32 time=188ms TTL=46
Reply from 38.49.39.136: bytes=32 time=179ms TTL=46
Reply from 38.49.39.136: bytes=32 time=179ms TTL=46
Reply from 38.49.39.136: bytes=32 time=180ms TTL=46
Reply from 38.49.39.136: bytes=32 time=182ms TTL=46
Reply from 38.49.39.136: bytes=32 time=181ms TTL=46
Reply from 38.49.39.136: bytes=32 time=179ms TTL=46
Reply from 38.49.39.136: bytes=32 time=183ms 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 = 179ms, Maximum = 188ms, Average = 181ms查看 |
GET PING Trace Dig |
|
| 内蒙古赤峰市联通 |
联通 |
内蒙古 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
183.483ms |
179.142ms |
180.764ms |
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=45
Reply from 38.49.39.136: bytes=32 time=180ms TTL=45
Reply from 38.49.39.136: bytes=32 time=183ms TTL=45
Reply from 38.49.39.136: bytes=32 time=179ms TTL=45
Reply from 38.49.39.136: bytes=32 time=180ms TTL=45
Reply from 38.49.39.136: bytes=32 time=179ms TTL=45
Reply from 38.49.39.136: bytes=32 time=180ms TTL=45
Reply from 38.49.39.136: bytes=32 time=181ms TTL=45
Reply from 38.49.39.136: bytes=32 time=183ms TTL=45
Reply from 38.49.39.136: bytes=32 time=179ms TTL=45
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 = 183ms, Average = 181ms查看 |
GET PING Trace Dig |
|
| 陕西榆林市移动 |
移动 |
陕西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
181.26ms |
180.46ms |
180.676ms |
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=48
Reply from 38.49.39.136: bytes=32 time=181ms TTL=48
Reply from 38.49.39.136: bytes=32 time=180ms TTL=48
Reply from 38.49.39.136: bytes=32 time=181ms TTL=48
Reply from 38.49.39.136: bytes=32 time=181ms TTL=48
Reply from 38.49.39.136: bytes=32 time=181ms TTL=48
Reply from 38.49.39.136: bytes=32 time=181ms TTL=48
Reply from 38.49.39.136: bytes=32 time=181ms TTL=48
Reply from 38.49.39.136: bytes=32 time=181ms TTL=48
Reply from 38.49.39.136: bytes=32 time=181ms 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 = 180ms, Maximum = 181ms, Average = 181ms查看 |
GET PING Trace Dig |
|
| 贵州贵阳电信 |
电信 |
贵州 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
181.182ms |
179.766ms |
180.29ms |
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=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=181ms TTL=51
Reply from 38.49.39.136: bytes=32 time=180ms TTL=51
Reply from 38.49.39.136: bytes=32 time=181ms 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 = 181ms, Average = 180ms查看 |
GET PING Trace Dig |
|
| 黑龙江绥化市电信 |
电信 |
黑龙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
181.282ms |
178.762ms |
179.895ms |
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=181ms TTL=49
Reply from 38.49.39.136: bytes=32 time=181ms TTL=49
Reply from 38.49.39.136: bytes=32 time=180ms 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
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=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 = 179ms, Maximum = 181ms, Average = 180ms查看 |
GET PING Trace Dig |
|
| 北京北京市联通 |
联通 |
北京 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
186.701ms |
176.592ms |
179.153ms |
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=49
Reply from 38.49.39.136: bytes=32 time=178ms TTL=49
Reply from 38.49.39.136: bytes=32 time=181ms 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=179ms TTL=49
Reply from 38.49.39.136: bytes=32 time=179ms TTL=49
Reply from 38.49.39.136: bytes=32 time=187ms 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 = 177ms, Maximum = 187ms, Average = 179ms查看 |
GET PING Trace Dig |
|
| 广西河池市移动 |
移动 |
广西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
182.717ms |
177.201ms |
179.126ms |
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=49
Reply from 38.49.39.136: bytes=32 time=181ms TTL=49
Reply from 38.49.39.136: bytes=32 time=178ms 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=183ms 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=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 = 183ms, Average = 179ms查看 |
GET PING Trace Dig |
|
| 四川宜宾移动 |
移动 |
四川 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
179.686ms |
178.464ms |
178.978ms |
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=179ms TTL=48
Reply from 38.49.39.136: bytes=32 time=178ms 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=179ms 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=179ms TTL=48
Reply from 38.49.39.136: bytes=32 time=179ms 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 = 180ms, Average = 179ms查看 |
GET PING Trace Dig |
|
| 贵州黔南布依族苗族自治州移动 |
移动 |
贵州 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
182.144ms |
177.4ms |
178.191ms |
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=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=182ms 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=178ms TTL=48
Reply from 38.49.39.136: bytes=32 time=178ms TTL=48
Reply from 38.49.39.136: bytes=32 time=177ms TTL=48
Reply from 38.49.39.136: bytes=32 time=178ms 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 = 177ms, Maximum = 182ms, Average = 178ms查看 |
GET PING Trace Dig |
|
| 贵州黔西南移动 |
移动 |
贵州 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
194.069ms |
171.284ms |
178.132ms |
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=171ms TTL=47
Reply from 38.49.39.136: bytes=32 time=172ms TTL=47
Reply from 38.49.39.136: bytes=32 time=192ms TTL=47
Reply from 38.49.39.136: bytes=32 time=194ms TTL=47
Reply from 38.49.39.136: bytes=32 time=175ms TTL=47
Reply from 38.49.39.136: bytes=32 time=171ms TTL=47
Reply from 38.49.39.136: bytes=32 time=173ms TTL=47
Reply from 38.49.39.136: bytes=32 time=186ms TTL=47
Reply from 38.49.39.136: bytes=32 time=172ms 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 = 171ms, Maximum = 194ms, Average = 178ms查看 |
GET PING Trace Dig |
|
| 山东临沂市联通 |
联通 |
山东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
179.741ms |
177.162ms |
178.023ms |
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=48
Reply from 38.49.39.136: bytes=32 time=177ms TTL=48
Reply from 38.49.39.136: bytes=32 time=178ms TTL=48
Reply from 38.49.39.136: bytes=32 time=179ms TTL=48
Reply from 38.49.39.136: bytes=32 time=177ms TTL=48
Reply from 38.49.39.136: bytes=32 time=177ms TTL=48
Reply from 38.49.39.136: bytes=32 time=178ms TTL=48
Reply from 38.49.39.136: bytes=32 time=177ms TTL=48
Reply from 38.49.39.136: bytes=32 time=180ms TTL=48
Reply from 38.49.39.136: bytes=32 time=178ms 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 = 177ms, Maximum = 180ms, Average = 178ms查看 |
GET PING Trace Dig |
|
| 湖北武汉市联通 |
联通 |
湖北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
178.439ms |
177.459ms |
177.798ms |
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=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=178ms TTL=50
Reply from 38.49.39.136: bytes=32 time=178ms 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=177ms 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
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 |
177.9ms |
177.521ms |
177.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=178ms 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=178ms 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=178ms 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=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 = 178ms, Maximum = 178ms, Average = 178ms查看 |
GET PING Trace Dig |
|
| 广西南宁市电信 |
电信 |
广西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
179.485ms |
176.02ms |
177.629ms |
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=44
Reply from 38.49.39.136: bytes=32 time=178ms TTL=44
Reply from 38.49.39.136: bytes=32 time=176ms TTL=44
Reply from 38.49.39.136: bytes=32 time=177ms TTL=44
Reply from 38.49.39.136: bytes=32 time=177ms TTL=44
Reply from 38.49.39.136: bytes=32 time=176ms TTL=44
Reply from 38.49.39.136: bytes=32 time=178ms TTL=44
Reply from 38.49.39.136: bytes=32 time=179ms TTL=44
Reply from 38.49.39.136: bytes=32 time=179ms TTL=44
Reply from 38.49.39.136: bytes=32 time=178ms TTL=44
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 |
179.166ms |
174.898ms |
177.531ms |
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=175ms 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=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=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
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 = 179ms, Average = 178ms查看 |
GET PING Trace Dig |
|
| 湖南永州市移动 |
移动 |
湖南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
179.62ms |
176.161ms |
177.244ms |
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=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=179ms 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=176ms 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
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 |
180.762ms |
174.506ms |
176.938ms |
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=48
Reply from 38.49.39.136: bytes=32 time=176ms TTL=48
Reply from 38.49.39.136: bytes=32 time=175ms TTL=48
Reply from 38.49.39.136: bytes=32 time=178ms TTL=48
Reply from 38.49.39.136: bytes=32 time=181ms TTL=48
Reply from 38.49.39.136: bytes=32 time=177ms 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=176ms TTL=48
Reply from 38.49.39.136: bytes=32 time=180ms 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 = 177ms查看 |
GET PING Trace Dig |
|
| 江苏南京联通 |
联通 |
江苏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
178.439ms |
176.308ms |
176.917ms |
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=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=177ms TTL=47
Reply from 38.49.39.136: bytes=32 time=176ms TTL=47
Reply from 38.49.39.136: bytes=32 time=176ms TTL=47
Reply from 38.49.39.136: bytes=32 time=177ms TTL=47
Reply from 38.49.39.136: bytes=32 time=177ms TTL=47
Reply from 38.49.39.136: bytes=32 time=177ms TTL=47
Reply from 38.49.39.136: bytes=32 time=176ms 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 = 176ms, Maximum = 178ms, Average = 177ms查看 |
GET PING Trace Dig |
|
| 云南曲靖市移动 |
移动 |
云南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
176.401ms |
175.565ms |
175.815ms |
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=47
Reply from 38.49.39.136: bytes=32 time=176ms TTL=47
Reply from 38.49.39.136: bytes=32 time=176ms TTL=47
Reply from 38.49.39.136: bytes=32 time=176ms TTL=47
Reply from 38.49.39.136: bytes=32 time=176ms TTL=47
Reply from 38.49.39.136: bytes=32 time=176ms TTL=47
Reply from 38.49.39.136: bytes=32 time=176ms TTL=47
Reply from 38.49.39.136: bytes=32 time=176ms TTL=47
Reply from 38.49.39.136: bytes=32 time=176ms TTL=47
Reply from 38.49.39.136: bytes=32 time=176ms 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 = 176ms, Maximum = 176ms, Average = 176ms查看 |
GET PING Trace Dig |
|
| 天津天津市移动 |
移动 |
天津 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
179.136ms |
174.075ms |
175.049ms |
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=176ms 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=175ms TTL=48
Reply from 38.49.39.136: bytes=32 time=174ms TTL=48
Reply from 38.49.39.136: bytes=32 time=179ms 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=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 = 174ms, Maximum = 179ms, Average = 175ms查看 |
GET PING Trace Dig |
|
| 吉林长春市移动 |
移动 |
吉林 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
175.641ms |
174.821ms |
175.003ms |
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=176ms 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 = 176ms, Average = 175ms查看 |
GET PING Trace Dig |
|
| 海南海口市移动 |
移动 |
海南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
176.965ms |
173.692ms |
174.474ms |
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=174ms TTL=47
Reply from 38.49.39.136: bytes=32 time=174ms TTL=47
Reply from 38.49.39.136: bytes=32 time=174ms 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=174ms TTL=47
Reply from 38.49.39.136: bytes=32 time=175ms TTL=47
Reply from 38.49.39.136: bytes=32 time=177ms 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 = 177ms, Average = 174ms查看 |
GET PING Trace Dig |
|
| 陕西渭南市联通 |
联通 |
陕西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
175.898ms |
174.058ms |
174.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=174ms TTL=50
Reply from 38.49.39.136: bytes=32 time=175ms 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
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.849ms |
174.16ms |
174.36ms |
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=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=175ms 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 = 175ms, Average = 174ms查看 |
GET PING Trace Dig |
|
| 江西南昌市联通 |
联通 |
江西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
174.802ms |
172.741ms |
174.073ms |
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=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
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
Reply from 38.49.39.136: bytes=32 time=174ms TTL=51
Reply from 38.49.39.136: bytes=32 time=173ms 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 = 173ms, Maximum = 175ms, Average = 174ms查看 |
GET PING Trace Dig |
|
| 天津天津市联通 |
联通 |
天津 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
175.774ms |
172.996ms |
173.742ms |
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=173ms TTL=49
Reply from 38.49.39.136: bytes=32 time=173ms TTL=49
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=175ms 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 = 176ms, Average = 174ms查看 |
GET PING Trace Dig |
|
| 重庆重庆市移动 |
移动 |
重庆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
173.681ms |
172.581ms |
173.041ms |
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=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
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 |
174.12ms |
172.42ms |
172.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=172ms TTL=48
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=173ms TTL=48
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=173ms TTL=48
Reply from 38.49.39.136: bytes=32 time=173ms 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 = 172ms, Maximum = 174ms, Average = 173ms查看 |
GET PING Trace Dig |
|
| 海南海口市电信 |
电信 |
海南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
173.742ms |
172.262ms |
172.688ms |
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=174ms TTL=52
Reply from 38.49.39.136: bytes=32 time=173ms TTL=52
Reply from 38.49.39.136: bytes=32 time=172ms TTL=52
Reply from 38.49.39.136: bytes=32 time=173ms TTL=52
Reply from 38.49.39.136: bytes=32 time=172ms TTL=52
Reply from 38.49.39.136: bytes=32 time=173ms TTL=52
Reply from 38.49.39.136: bytes=32 time=172ms 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
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 172ms, Maximum = 174ms, Average = 173ms查看 |
GET PING Trace Dig |
|
| 广东茂名市联通 |
联通 |
广东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
174.439ms |
171.316ms |
172.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=174ms TTL=51
Reply from 38.49.39.136: bytes=32 time=172ms TTL=51
Reply from 38.49.39.136: bytes=32 time=173ms TTL=51
Reply from 38.49.39.136: bytes=32 time=174ms TTL=51
Reply from 38.49.39.136: bytes=32 time=173ms 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=173ms 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 = 171ms, Maximum = 174ms, Average = 173ms查看 |
GET PING Trace Dig |
|
| 上海上海市联通 |
联通 |
上海 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
181.377ms |
168.434ms |
172.599ms |
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=168ms TTL=51
Reply from 38.49.39.136: bytes=32 time=169ms 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=181ms TTL=51
Reply from 38.49.39.136: bytes=32 time=170ms TTL=51
Reply from 38.49.39.136: bytes=32 time=174ms TTL=51
Reply from 38.49.39.136: bytes=32 time=178ms 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 = 168ms, Maximum = 181ms, Average = 173ms查看 |
GET PING Trace Dig |
|
| 河南南阳市移动 |
移动 |
河南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
186.698ms |
164.319ms |
172.2ms |
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=167ms TTL=49
Reply from 38.49.39.136: bytes=32 time=164ms TTL=49
Reply from 38.49.39.136: bytes=32 time=176ms TTL=49
Reply from 38.49.39.136: bytes=32 time=181ms TTL=49
Reply from 38.49.39.136: bytes=32 time=167ms TTL=49
Reply from 38.49.39.136: bytes=32 time=172ms TTL=49
Reply from 38.49.39.136: bytes=32 time=165ms TTL=49
Reply from 38.49.39.136: bytes=32 time=172ms TTL=49
Reply from 38.49.39.136: bytes=32 time=187ms 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 = 187ms, Average = 172ms查看 |
GET PING Trace Dig |
|
| 上海上海市移动 |
移动 |
上海 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
174.698ms |
170.541ms |
172.16ms |
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=171ms 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=171ms TTL=51
Reply from 38.49.39.136: bytes=32 time=174ms TTL=51
Reply from 38.49.39.136: bytes=32 time=171ms TTL=51
Reply from 38.49.39.136: bytes=32 time=173ms TTL=51
Reply from 38.49.39.136: bytes=32 time=175ms TTL=51
Reply from 38.49.39.136: bytes=32 time=171ms 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 = 171ms, Maximum = 175ms, Average = 172ms查看 |
GET PING Trace Dig |
|
| 湖南长沙市电信 |
电信 |
湖南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
173.766ms |
170.355ms |
171.544ms |
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=171ms TTL=52
Reply from 38.49.39.136: bytes=32 time=172ms TTL=52
Reply from 38.49.39.136: bytes=32 time=171ms TTL=52
Reply from 38.49.39.136: bytes=32 time=174ms TTL=52
Reply from 38.49.39.136: bytes=32 time=171ms TTL=52
Reply from 38.49.39.136: bytes=32 time=172ms TTL=52
Reply from 38.49.39.136: bytes=32 time=172ms TTL=52
Reply from 38.49.39.136: bytes=32 time=171ms 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 = 174ms, Average = 172ms查看 |
GET PING Trace Dig |
|
| 福建福州市联通 |
联通 |
福建 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
171ms |
170.6ms |
170.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=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
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 = 171ms, Average = 171ms查看 |
GET PING Trace Dig |
|
| 河南信阳市联通 |
联通 |
河南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
177.199ms |
167.56ms |
170.375ms |
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=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=170ms TTL=50
Reply from 38.49.39.136: bytes=32 time=170ms TTL=50
Reply from 38.49.39.136: bytes=32 time=168ms TTL=50
Reply from 38.49.39.136: bytes=32 time=177ms 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
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 = 170ms查看 |
GET PING Trace Dig |
|
| 辽宁朝阳市电信 |
电信 |
辽宁 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
173.236ms |
169.5ms |
170.048ms |
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=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
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
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 = 173ms, Average = 170ms查看 |
GET PING Trace Dig |
|
| 广西南宁市移动 |
移动 |
广西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
174.409ms |
168.552ms |
169.966ms |
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=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=170ms 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=173ms TTL=50
Reply from 38.49.39.136: bytes=32 time=170ms 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 = 174ms, Average = 170ms查看 |
GET PING Trace Dig |
|
| 安徽阜阳联通 |
联通 |
安徽 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
170.254ms |
169.74ms |
169.956ms |
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=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=170ms 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=170ms 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=170ms 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 = 170ms, Average = 170ms查看 |
GET PING Trace Dig |
|
| 安徽宿州市联通 |
联通 |
安徽 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
172.302ms |
167.399ms |
169.782ms |
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=170ms 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=170ms TTL=49
Reply from 38.49.39.136: bytes=32 time=168ms TTL=49
Reply from 38.49.39.136: bytes=32 time=172ms 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 = 172ms, Average = 170ms查看 |
GET PING Trace Dig |
|
| 湖南岳阳市电信 |
电信 |
湖南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
170.659ms |
168.699ms |
169.76ms |
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=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
Reply from 38.49.39.136: bytes=32 time=169ms 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
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 = 171ms, Average = 170ms查看 |
GET PING Trace Dig |
|
| 山西临汾市移动 |
移动 |
山西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
178.638ms |
164.245ms |
169.521ms |
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=52
Reply from 38.49.39.136: bytes=32 time=167ms TTL=52
Reply from 38.49.39.136: bytes=32 time=169ms TTL=52
Reply from 38.49.39.136: bytes=32 time=166ms TTL=52
Reply from 38.49.39.136: bytes=32 time=171ms TTL=52
Reply from 38.49.39.136: bytes=32 time=172ms TTL=52
Reply from 38.49.39.136: bytes=32 time=179ms TTL=52
Reply from 38.49.39.136: bytes=32 time=164ms TTL=52
Reply from 38.49.39.136: bytes=32 time=166ms TTL=52
Reply from 38.49.39.136: bytes=32 time=177ms 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 = 164ms, Maximum = 179ms, Average = 170ms查看 |
GET PING Trace Dig |
|
| 辽宁营口市移动 |
移动 |
辽宁 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
170.007ms |
167.371ms |
168.171ms |
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=168ms TTL=49
Reply from 38.49.39.136: bytes=32 time=168ms TTL=49
Reply from 38.49.39.136: bytes=32 time=167ms 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=169ms TTL=49
Reply from 38.49.39.136: bytes=32 time=167ms TTL=49
Reply from 38.49.39.136: bytes=32 time=168ms 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 = 170ms, Average = 168ms查看 |
GET PING Trace Dig |
|
| 重庆重庆市联通 |
联通 |
重庆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
169.96ms |
166.421ms |
167.457ms |
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=170ms TTL=48
Reply from 38.49.39.136: bytes=32 time=168ms TTL=48
Reply from 38.49.39.136: bytes=32 time=166ms TTL=48
Reply from 38.49.39.136: bytes=32 time=169ms 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=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 = 166ms, Maximum = 170ms, Average = 167ms查看 |
GET PING Trace Dig |
|
| 香港香港 |
香港 |
香港 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
168.245ms |
167.22ms |
167.408ms |
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=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=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=167ms 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=167ms 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 = 168ms, Average = 167ms查看 |
GET PING Trace Dig |
|
| 广西南宁市电信 |
电信 |
广西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
174.22ms |
163.58ms |
167.407ms |
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=51
Reply from 38.49.39.136: bytes=32 time=165ms 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=172ms TTL=51
Reply from 38.49.39.136: bytes=32 time=164ms TTL=51
Reply from 38.49.39.136: bytes=32 time=166ms 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=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 = 164ms, Maximum = 174ms, Average = 167ms查看 |
GET PING Trace Dig |
|
| 江苏连云港市联通 |
联通 |
江苏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
167.322ms |
166.827ms |
167.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=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=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=167ms 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 = 167ms, Average = 167ms查看 |
GET PING Trace Dig |
|
| 香港香港 |
香港 |
香港 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
167.669ms |
166.613ms |
166.85ms |
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=52
Reply from 38.49.39.136: bytes=32 time=167ms TTL=52
Reply from 38.49.39.136: bytes=32 time=167ms TTL=52
Reply from 38.49.39.136: bytes=32 time=168ms TTL=52
Reply from 38.49.39.136: bytes=32 time=167ms TTL=52
Reply from 38.49.39.136: bytes=32 time=167ms TTL=52
Reply from 38.49.39.136: bytes=32 time=167ms TTL=52
Reply from 38.49.39.136: bytes=32 time=167ms TTL=52
Reply from 38.49.39.136: bytes=32 time=167ms TTL=52
Reply from 38.49.39.136: bytes=32 time=167ms 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 = 167ms, Maximum = 168ms, Average = 167ms查看 |
GET PING Trace Dig |
|
| 甘肃定西市电信 |
电信 |
甘肃 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
169.939ms |
166.1ms |
166.784ms |
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=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=166ms TTL=50
Reply from 38.49.39.136: bytes=32 time=166ms TTL=50
Reply from 38.49.39.136: bytes=32 time=170ms 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 = 170ms, Average = 167ms查看 |
GET PING Trace Dig |
|
| 甘肃武威市移动 |
移动 |
甘肃 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
168.682ms |
165.721ms |
166.607ms |
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=168ms TTL=47
Reply from 38.49.39.136: bytes=32 time=167ms 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=167ms TTL=47
Reply from 38.49.39.136: bytes=32 time=169ms 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 = 166ms, Maximum = 169ms, Average = 167ms查看 |
GET PING Trace Dig |
|
| 广东东莞市移动 |
移动 |
广东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
167.92ms |
165.16ms |
165.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=166ms TTL=48
Reply from 38.49.39.136: bytes=32 time=165ms TTL=48
Reply from 38.49.39.136: bytes=32 time=165ms TTL=48
Reply from 38.49.39.136: bytes=32 time=166ms TTL=48
Reply from 38.49.39.136: bytes=32 time=165ms TTL=48
Reply from 38.49.39.136: bytes=32 time=168ms TTL=48
Reply from 38.49.39.136: bytes=32 time=166ms TTL=48
Reply from 38.49.39.136: bytes=32 time=165ms TTL=48
Reply from 38.49.39.136: bytes=32 time=166ms TTL=48
Reply from 38.49.39.136: bytes=32 time=166ms 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 = 165ms, Maximum = 168ms, Average = 166ms查看 |
GET PING Trace Dig |
|
| 重庆重庆市联通 |
联通 |
重庆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
166.26ms |
165.399ms |
165.847ms |
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=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=165ms 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
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 = 166ms查看 |
GET PING Trace Dig |
|
| 宁夏银川移动 |
移动 |
宁夏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
179.382ms |
157.281ms |
165.835ms |
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=51
Reply from 38.49.39.136: bytes=32 time=157ms TTL=51
Reply from 38.49.39.136: bytes=32 time=164ms TTL=51
Reply from 38.49.39.136: bytes=32 time=161ms TTL=51
Reply from 38.49.39.136: bytes=32 time=161ms TTL=51
Reply from 38.49.39.136: bytes=32 time=160ms TTL=51
Reply from 38.49.39.136: bytes=32 time=179ms 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=171ms 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 = 157ms, Maximum = 179ms, Average = 166ms查看 |
GET PING Trace Dig |
|
| 福建南平电信 |
电信 |
福建 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
182.94ms |
157.9ms |
165.443ms |
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=51
Reply from 38.49.39.136: bytes=32 time=166ms TTL=51
Reply from 38.49.39.136: bytes=32 time=168ms TTL=51
Reply from 38.49.39.136: bytes=32 time=159ms TTL=51
Reply from 38.49.39.136: bytes=32 time=159ms TTL=51
Reply from 38.49.39.136: bytes=32 time=164ms TTL=51
Reply from 38.49.39.136: bytes=32 time=159ms TTL=51
Reply from 38.49.39.136: bytes=32 time=158ms TTL=51
Reply from 38.49.39.136: bytes=32 time=165ms TTL=51
Reply from 38.49.39.136: bytes=32 time=183ms 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 = 183ms, Average = 165ms查看 |
GET PING Trace Dig |
|
| 江西南昌市电信 |
电信 |
江西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
166.22ms |
164.58ms |
165.136ms |
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=41
Reply from 38.49.39.136: bytes=32 time=166ms TTL=41
Reply from 38.49.39.136: bytes=32 time=165ms TTL=41
Reply from 38.49.39.136: bytes=32 time=166ms TTL=41
Reply from 38.49.39.136: bytes=32 time=165ms TTL=41
Reply from 38.49.39.136: bytes=32 time=165ms TTL=41
Reply from 38.49.39.136: bytes=32 time=165ms TTL=41
Reply from 38.49.39.136: bytes=32 time=165ms TTL=41
Reply from 38.49.39.136: bytes=32 time=166ms TTL=41
Reply from 38.49.39.136: bytes=32 time=165ms TTL=41
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 |
200.223ms |
151.51ms |
164.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=155ms TTL=51
Reply from 38.49.39.136: bytes=32 time=155ms TTL=51
Reply from 38.49.39.136: bytes=32 time=153ms TTL=51
Reply from 38.49.39.136: bytes=32 time=152ms TTL=51
Reply from 38.49.39.136: bytes=32 time=153ms TTL=51
Reply from 38.49.39.136: bytes=32 time=193ms TTL=51
Reply from 38.49.39.136: bytes=32 time=152ms TTL=51
Reply from 38.49.39.136: bytes=32 time=200ms TTL=51
Reply from 38.49.39.136: bytes=32 time=176ms TTL=51
Reply from 38.49.39.136: bytes=32 time=159ms 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 = 152ms, Maximum = 200ms, Average = 165ms查看 |
GET PING Trace Dig |
|
| 内蒙古包头市电信 |
电信 |
内蒙古 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
164.326ms |
164.141ms |
164.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=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
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 = 164ms, Average = 164ms查看 |
GET PING Trace Dig |
|
| 重庆重庆市电信 |
电信 |
重庆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
167.12ms |
162.958ms |
163.811ms |
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=167ms 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=163ms 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=163ms 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 = 167ms, Average = 164ms查看 |
GET PING Trace Dig |
|
| 辽宁沈阳市电信 |
电信 |
辽宁 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
163.88ms |
163.4ms |
163.693ms |
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=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
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 |
167.4ms |
160.84ms |
163.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=164ms TTL=48
Reply from 38.49.39.136: bytes=32 time=167ms TTL=48
Reply from 38.49.39.136: bytes=32 time=161ms TTL=48
Reply from 38.49.39.136: bytes=32 time=163ms TTL=48
Reply from 38.49.39.136: bytes=32 time=161ms 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=161ms TTL=48
Reply from 38.49.39.136: bytes=32 time=165ms 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 = 161ms, Maximum = 167ms, Average = 163ms查看 |
GET PING Trace Dig |
|
| 江西上饶市移动 |
移动 |
江西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
172.354ms |
159.417ms |
163.034ms |
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=161ms TTL=48
Reply from 38.49.39.136: bytes=32 time=159ms TTL=48
Reply from 38.49.39.136: bytes=32 time=166ms TTL=48
Reply from 38.49.39.136: bytes=32 time=160ms TTL=48
Reply from 38.49.39.136: bytes=32 time=163ms TTL=48
Reply from 38.49.39.136: bytes=32 time=160ms TTL=48
Reply from 38.49.39.136: bytes=32 time=164ms TTL=48
Reply from 38.49.39.136: bytes=32 time=163ms TTL=48
Reply from 38.49.39.136: bytes=32 time=161ms TTL=48
Reply from 38.49.39.136: bytes=32 time=172ms 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 = 159ms, Maximum = 172ms, Average = 163ms查看 |
GET PING Trace Dig |
|
| 天津天津市电信 |
电信 |
天津 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
177.035ms |
155.821ms |
161.801ms |
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=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=165ms TTL=49
Reply from 38.49.39.136: bytes=32 time=171ms TTL=49
Reply from 38.49.39.136: bytes=32 time=157ms TTL=49
Reply from 38.49.39.136: bytes=32 time=162ms TTL=49
Reply from 38.49.39.136: bytes=32 time=156ms TTL=49
Reply from 38.49.39.136: bytes=32 time=158ms 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 = 177ms, Average = 162ms查看 |
GET PING Trace Dig |
|
| 重庆重庆市电信 |
电信 |
重庆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
162.811ms |
160.931ms |
161.284ms |
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=161ms TTL=52
Reply from 38.49.39.136: bytes=32 time=161ms TTL=52
Reply from 38.49.39.136: bytes=32 time=163ms TTL=52
Reply from 38.49.39.136: bytes=32 time=161ms TTL=52
Reply from 38.49.39.136: bytes=32 time=161ms TTL=52
Reply from 38.49.39.136: bytes=32 time=161ms TTL=52
Reply from 38.49.39.136: bytes=32 time=161ms TTL=52
Reply from 38.49.39.136: bytes=32 time=161ms TTL=52
Reply from 38.49.39.136: bytes=32 time=161ms TTL=52
Reply from 38.49.39.136: bytes=32 time=161ms 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 = 161ms, Maximum = 163ms, Average = 161ms查看 |
GET PING Trace Dig |
|
| 内蒙古呼和浩特移动 |
移动 |
内蒙古 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
161.802ms |
160.902ms |
161.104ms |
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=161ms TTL=48
Reply from 38.49.39.136: bytes=32 time=161ms TTL=48
Reply from 38.49.39.136: bytes=32 time=161ms TTL=48
Reply from 38.49.39.136: bytes=32 time=161ms TTL=48
Reply from 38.49.39.136: bytes=32 time=161ms TTL=48
Reply from 38.49.39.136: bytes=32 time=161ms TTL=48
Reply from 38.49.39.136: bytes=32 time=162ms TTL=48
Reply from 38.49.39.136: bytes=32 time=161ms TTL=48
Reply from 38.49.39.136: bytes=32 time=161ms TTL=48
Reply from 38.49.39.136: bytes=32 time=161ms 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 = 161ms, Maximum = 162ms, Average = 161ms查看 |
GET PING Trace Dig |
|
| 河北邢台市联通 |
联通 |
河北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
160.243ms |
158.311ms |
159.298ms |
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=51
Reply from 38.49.39.136: bytes=32 time=159ms TTL=51
Reply from 38.49.39.136: bytes=32 time=159ms 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=158ms TTL=51
Reply from 38.49.39.136: bytes=32 time=159ms 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=159ms 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 = 160ms, Average = 159ms查看 |
GET PING Trace Dig |
|
| 湖南岳阳市移动 |
移动 |
湖南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
167.641ms |
155.721ms |
159.287ms |
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=168ms TTL=50
Reply from 38.49.39.136: bytes=32 time=156ms TTL=50
Reply from 38.49.39.136: bytes=32 time=156ms TTL=50
Reply from 38.49.39.136: bytes=32 time=162ms TTL=50
Reply from 38.49.39.136: bytes=32 time=165ms TTL=50
Reply from 38.49.39.136: bytes=32 time=156ms TTL=50
Reply from 38.49.39.136: bytes=32 time=157ms 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 = 156ms, Maximum = 168ms, Average = 159ms查看 |
GET PING Trace Dig |
|
| 河北邢台市移动 |
移动 |
河北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
168.371ms |
157.407ms |
159.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=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=157ms TTL=50
Reply from 38.49.39.136: bytes=32 time=157ms TTL=50
Reply from 38.49.39.136: bytes=32 time=159ms TTL=50
Reply from 38.49.39.136: bytes=32 time=159ms TTL=50
Reply from 38.49.39.136: bytes=32 time=159ms TTL=50
Reply from 38.49.39.136: bytes=32 time=168ms 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 = 157ms, Maximum = 168ms, Average = 159ms查看 |
GET PING Trace Dig |
|
| 山西太原市移动 |
移动 |
山西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
179.06ms |
154.269ms |
159.077ms |
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=158ms TTL=49
Reply from 38.49.39.136: bytes=32 time=179ms TTL=49
Reply from 38.49.39.136: bytes=32 time=161ms TTL=49
Reply from 38.49.39.136: bytes=32 time=156ms 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=155ms TTL=49
Reply from 38.49.39.136: bytes=32 time=154ms 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 = 154ms, Maximum = 179ms, Average = 159ms查看 |
GET PING Trace Dig |
|
| 意大利国外 |
国外 |
意大利 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
163.6ms |
157.621ms |
158.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=161ms TTL=48
Reply from 38.49.39.136: bytes=32 time=158ms TTL=48
Reply from 38.49.39.136: bytes=32 time=164ms TTL=48
Reply from 38.49.39.136: bytes=32 time=158ms TTL=48
Reply from 38.49.39.136: bytes=32 time=158ms TTL=48
Reply from 38.49.39.136: bytes=32 time=158ms TTL=48
Reply from 38.49.39.136: bytes=32 time=158ms TTL=48
Reply from 38.49.39.136: bytes=32 time=158ms TTL=48
Reply from 38.49.39.136: bytes=32 time=158ms TTL=48
Reply from 38.49.39.136: bytes=32 time=158ms 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 = 158ms, Maximum = 164ms, Average = 159ms查看 |
GET PING Trace Dig |
|
| 湖北十堰市联通 |
联通 |
湖北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
163.882ms |
155.622ms |
158.516ms |
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=51
Reply from 38.49.39.136: bytes=32 time=157ms TTL=51
Reply from 38.49.39.136: bytes=32 time=159ms TTL=51
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=162ms TTL=51
Reply from 38.49.39.136: bytes=32 time=156ms TTL=51
Reply from 38.49.39.136: bytes=32 time=159ms TTL=51
Reply from 38.49.39.136: bytes=32 time=157ms TTL=51
Reply from 38.49.39.136: bytes=32 time=157ms 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 = 156ms, Maximum = 164ms, Average = 159ms查看 |
GET PING Trace Dig |
|
| 重庆重庆市移动 |
移动 |
重庆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
160.381ms |
157.04ms |
158.269ms |
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=49
Reply from 38.49.39.136: bytes=32 time=159ms TTL=49
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=159ms 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=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 = 160ms, Average = 158ms查看 |
GET PING Trace Dig |
|
| 山西太原市电信 |
电信 |
山西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
166.025ms |
155.025ms |
158.019ms |
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=156ms 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
Reply from 38.49.39.136: bytes=32 time=166ms 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=164ms TTL=50
Reply from 38.49.39.136: bytes=32 time=162ms 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 = 166ms, Average = 158ms查看 |
GET PING Trace Dig |
|
| 山西忻州市电信 |
电信 |
山西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
162.881ms |
156.78ms |
157.734ms |
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=163ms 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=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=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
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 = 163ms, Average = 158ms查看 |
GET PING Trace Dig |
|
| 北京北京市移动 |
移动 |
北京 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
164.463ms |
155.414ms |
157.318ms |
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=156ms TTL=50
Reply from 38.49.39.136: bytes=32 time=155ms 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=155ms TTL=50
Reply from 38.49.39.136: bytes=32 time=164ms TTL=50
Reply from 38.49.39.136: bytes=32 time=156ms TTL=50
Reply from 38.49.39.136: bytes=32 time=156ms 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 = 155ms, Maximum = 164ms, Average = 157ms查看 |
GET PING Trace Dig |
|
| 广东深圳电信 |
电信 |
广东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
155.756ms |
155.468ms |
155.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=155ms 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
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=156ms 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
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 = 156ms, Average = 156ms查看 |
GET PING Trace Dig |
|
| 湖南永州市联通 |
联通 |
湖南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
158.899ms |
154.859ms |
155.557ms |
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=155ms 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
Reply from 38.49.39.136: bytes=32 time=155ms TTL=49
Reply from 38.49.39.136: bytes=32 time=159ms 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
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 = 159ms, Average = 156ms查看 |
GET PING Trace Dig |
|
| 河北邯郸市电信 |
电信 |
河北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
155.562ms |
155.122ms |
155.284ms |
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=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
Reply from 38.49.39.136: bytes=32 time=155ms 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
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=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 = 156ms, Average = 155ms查看 |
GET PING Trace Dig |
|
| 天津天津市移动 |
移动 |
天津 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
155.48ms |
153.28ms |
154.929ms |
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=44
Reply from 38.49.39.136: bytes=32 time=155ms TTL=44
Reply from 38.49.39.136: bytes=32 time=153ms TTL=44
Reply from 38.49.39.136: bytes=32 time=155ms TTL=44
Reply from 38.49.39.136: bytes=32 time=155ms TTL=44
Reply from 38.49.39.136: bytes=32 time=154ms TTL=44
Reply from 38.49.39.136: bytes=32 time=155ms TTL=44
Reply from 38.49.39.136: bytes=32 time=155ms TTL=44
Reply from 38.49.39.136: bytes=32 time=155ms TTL=44
Reply from 38.49.39.136: bytes=32 time=155ms TTL=44
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 = 155ms, Average = 155ms查看 |
GET PING Trace Dig |
|
| 河南洛阳市电信 |
电信 |
河南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
153.427ms |
153.262ms |
153.354ms |
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=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 = 153ms, Average = 153ms查看 |
GET PING Trace Dig |
|
| 湖北潜江市移动 |
移动 |
湖北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
156.053ms |
150.12ms |
152.562ms |
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=154ms TTL=49
Reply from 38.49.39.136: bytes=32 time=151ms TTL=49
Reply from 38.49.39.136: bytes=32 time=151ms TTL=49
Reply from 38.49.39.136: bytes=32 time=155ms TTL=49
Reply from 38.49.39.136: bytes=32 time=151ms TTL=49
Reply from 38.49.39.136: bytes=32 time=151ms TTL=49
Reply from 38.49.39.136: bytes=32 time=150ms TTL=49
Reply from 38.49.39.136: bytes=32 time=151ms 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 = 150ms, Maximum = 156ms, Average = 153ms查看 |
GET PING Trace Dig |
|
| 湖北武汉移动 |
移动 |
湖北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
175.444ms |
148.698ms |
152.42ms |
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=49
Reply from 38.49.39.136: bytes=32 time=153ms TTL=49
Reply from 38.49.39.136: bytes=32 time=175ms TTL=49
Reply from 38.49.39.136: bytes=32 time=150ms 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=151ms 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 = 175ms, Average = 152ms查看 |
GET PING Trace Dig |
|
| 山东聊城市移动 |
移动 |
山东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
154.89ms |
150.949ms |
151.923ms |
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=151ms TTL=48
Reply from 38.49.39.136: bytes=32 time=151ms TTL=48
Reply from 38.49.39.136: bytes=32 time=151ms TTL=48
Reply from 38.49.39.136: bytes=32 time=155ms TTL=48
Reply from 38.49.39.136: bytes=32 time=151ms 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=151ms 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 = 151ms, Maximum = 155ms, Average = 152ms查看 |
GET PING Trace Dig |
|
| 山东滨州市电信 |
电信 |
山东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
153.362ms |
149.462ms |
150.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=153ms TTL=48
Reply from 38.49.39.136: bytes=32 time=150ms TTL=48
Reply from 38.49.39.136: bytes=32 time=150ms TTL=48
Reply from 38.49.39.136: bytes=32 time=149ms TTL=48
Reply from 38.49.39.136: bytes=32 time=152ms TTL=48
Reply from 38.49.39.136: bytes=32 time=150ms TTL=48
Reply from 38.49.39.136: bytes=32 time=151ms TTL=48
Reply from 38.49.39.136: bytes=32 time=153ms TTL=48
Reply from 38.49.39.136: bytes=32 time=150ms TTL=48
Reply from 38.49.39.136: bytes=32 time=150ms 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 = 149ms, Maximum = 153ms, Average = 151ms查看 |
GET PING Trace Dig |
|
| 福建泉州市联通 |
联通 |
福建 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
155.96ms |
147.92ms |
150.269ms |
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=51
Reply from 38.49.39.136: bytes=32 time=153ms TTL=51
Reply from 38.49.39.136: bytes=32 time=148ms TTL=51
Reply from 38.49.39.136: bytes=32 time=156ms TTL=51
Reply from 38.49.39.136: bytes=32 time=150ms TTL=51
Reply from 38.49.39.136: bytes=32 time=150ms TTL=51
Reply from 38.49.39.136: bytes=32 time=148ms TTL=51
Reply from 38.49.39.136: bytes=32 time=149ms TTL=51
Reply from 38.49.39.136: bytes=32 time=151ms TTL=51
Reply from 38.49.39.136: bytes=32 time=148ms 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 = 148ms, Maximum = 156ms, Average = 150ms查看 |
GET PING Trace Dig |
|
| 陕西西安市电信 |
电信 |
陕西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
149.4ms |
149.26ms |
149.311ms |
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=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=149ms 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=149ms 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=149ms 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 = 149ms, Average = 149ms查看 |
GET PING Trace Dig |
|
| 安徽合肥市电信 |
电信 |
安徽 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
184.029ms |
138.881ms |
147.81ms |
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=145ms TTL=49
Reply from 38.49.39.136: bytes=32 time=142ms TTL=49
Reply from 38.49.39.136: bytes=32 time=139ms TTL=49
Reply from 38.49.39.136: bytes=32 time=184ms TTL=49
Reply from 38.49.39.136: bytes=32 time=164ms TTL=49
Reply from 38.49.39.136: bytes=32 time=142ms TTL=49
Reply from 38.49.39.136: bytes=32 time=142ms TTL=49
Reply from 38.49.39.136: bytes=32 time=141ms TTL=49
Reply from 38.49.39.136: bytes=32 time=140ms TTL=49
Reply from 38.49.39.136: bytes=32 time=140ms 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 = 139ms, Maximum = 184ms, Average = 148ms查看 |
GET PING Trace Dig |
|
| 江西上饶市电信 |
电信 |
江西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
147.482ms |
146.682ms |
147.22ms |
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=147ms TTL=52
Reply from 38.49.39.136: bytes=32 time=147ms TTL=52
Reply from 38.49.39.136: bytes=32 time=147ms TTL=52
Reply from 38.49.39.136: bytes=32 time=147ms TTL=52
Reply from 38.49.39.136: bytes=32 time=147ms TTL=52
Reply from 38.49.39.136: bytes=32 time=147ms TTL=52
Reply from 38.49.39.136: bytes=32 time=147ms TTL=52
Reply from 38.49.39.136: bytes=32 time=147ms TTL=52
Reply from 38.49.39.136: bytes=32 time=147ms TTL=52
Reply from 38.49.39.136: bytes=32 time=147ms 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 = 147ms, Maximum = 147ms, Average = 147ms查看 |
GET PING Trace Dig |
|
| 浙江杭州市联通 |
联通 |
浙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
149.153ms |
145.371ms |
147.118ms |
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=146ms TTL=43
Reply from 38.49.39.136: bytes=32 time=145ms TTL=43
Reply from 38.49.39.136: bytes=32 time=146ms TTL=43
Reply from 38.49.39.136: bytes=32 time=145ms TTL=43
Reply from 38.49.39.136: bytes=32 time=149ms TTL=43
Reply from 38.49.39.136: bytes=32 time=147ms TTL=43
Reply from 38.49.39.136: bytes=32 time=148ms TTL=43
Reply from 38.49.39.136: bytes=32 time=148ms TTL=43
Reply from 38.49.39.136: bytes=32 time=148ms TTL=43
Reply from 38.49.39.136: bytes=32 time=149ms 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 = 145ms, Maximum = 149ms, Average = 147ms查看 |
GET PING Trace Dig |
|
| 江西南昌移动 |
移动 |
江西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
150.797ms |
144.837ms |
146.723ms |
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=147ms TTL=48
Reply from 38.49.39.136: bytes=32 time=145ms TTL=48
Reply from 38.49.39.136: bytes=32 time=146ms TTL=48
Reply from 38.49.39.136: bytes=32 time=148ms TTL=48
Reply from 38.49.39.136: bytes=32 time=151ms TTL=48
Reply from 38.49.39.136: bytes=32 time=146ms TTL=48
Reply from 38.49.39.136: bytes=32 time=145ms TTL=48
Reply from 38.49.39.136: bytes=32 time=148ms TTL=48
Reply from 38.49.39.136: bytes=32 time=145ms TTL=48
Reply from 38.49.39.136: bytes=32 time=145ms 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 = 145ms, Maximum = 151ms, Average = 147ms查看 |
GET PING Trace Dig |
|
| 湖北鄂州市电信 |
电信 |
湖北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
147.639ms |
145.359ms |
146.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=147ms TTL=51
Reply from 38.49.39.136: bytes=32 time=147ms TTL=51
Reply from 38.49.39.136: bytes=32 time=146ms TTL=51
Reply from 38.49.39.136: bytes=32 time=145ms TTL=51
Reply from 38.49.39.136: bytes=32 time=146ms TTL=51
Reply from 38.49.39.136: bytes=32 time=146ms TTL=51
Reply from 38.49.39.136: bytes=32 time=146ms TTL=51
Reply from 38.49.39.136: bytes=32 time=146ms TTL=51
Reply from 38.49.39.136: bytes=32 time=145ms TTL=51
Reply from 38.49.39.136: bytes=32 time=148ms 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 = 145ms, Maximum = 148ms, Average = 146ms查看 |
GET PING Trace Dig |
|
| 湖北黄冈市电信 |
电信 |
湖北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
147.16ms |
145.7ms |
146.21ms |
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=147ms TTL=51
Reply from 38.49.39.136: bytes=32 time=147ms TTL=51
Reply from 38.49.39.136: bytes=32 time=146ms TTL=51
Reply from 38.49.39.136: bytes=32 time=146ms TTL=51
Reply from 38.49.39.136: bytes=32 time=146ms TTL=51
Reply from 38.49.39.136: bytes=32 time=146ms TTL=51
Reply from 38.49.39.136: bytes=32 time=146ms TTL=51
Reply from 38.49.39.136: bytes=32 time=146ms TTL=51
Reply from 38.49.39.136: bytes=32 time=146ms TTL=51
Reply from 38.49.39.136: bytes=32 time=146ms 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 = 146ms, Maximum = 147ms, Average = 146ms查看 |
GET PING Trace Dig |
|
| 江苏南通移动 |
移动 |
江苏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
148.122ms |
145.302ms |
146.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=147ms TTL=50
Reply from 38.49.39.136: bytes=32 time=146ms TTL=50
Reply from 38.49.39.136: bytes=32 time=146ms TTL=50
Reply from 38.49.39.136: bytes=32 time=148ms TTL=50
Reply from 38.49.39.136: bytes=32 time=146ms TTL=50
Reply from 38.49.39.136: bytes=32 time=145ms TTL=50
Reply from 38.49.39.136: bytes=32 time=145ms TTL=50
Reply from 38.49.39.136: bytes=32 time=146ms TTL=50
Reply from 38.49.39.136: bytes=32 time=146ms TTL=50
Reply from 38.49.39.136: bytes=32 time=146ms 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 = 145ms, Maximum = 148ms, Average = 146ms查看 |
GET PING Trace Dig |
|
| 浙江金华市电信 |
电信 |
浙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
151.091ms |
141.73ms |
145.078ms |
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=148ms TTL=50
Reply from 38.49.39.136: bytes=32 time=148ms TTL=50
Reply from 38.49.39.136: bytes=32 time=151ms TTL=50
Reply from 38.49.39.136: bytes=32 time=142ms TTL=50
Reply from 38.49.39.136: bytes=32 time=144ms TTL=50
Reply from 38.49.39.136: bytes=32 time=142ms TTL=50
Reply from 38.49.39.136: bytes=32 time=143ms TTL=50
Reply from 38.49.39.136: bytes=32 time=142ms TTL=50
Reply from 38.49.39.136: bytes=32 time=147ms TTL=50
Reply from 38.49.39.136: bytes=32 time=144ms 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 = 142ms, Maximum = 151ms, Average = 145ms查看 |
GET PING Trace Dig |
|
| 浙江温州市电信 |
电信 |
浙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
145.156ms |
144.394ms |
144.779ms |
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=145ms TTL=50
Reply from 38.49.39.136: bytes=32 time=145ms TTL=50
Reply from 38.49.39.136: bytes=32 time=145ms TTL=50
Reply from 38.49.39.136: bytes=32 time=145ms TTL=50
Reply from 38.49.39.136: bytes=32 time=145ms TTL=50
Reply from 38.49.39.136: bytes=32 time=145ms TTL=50
Reply from 38.49.39.136: bytes=32 time=145ms TTL=50
Reply from 38.49.39.136: bytes=32 time=145ms TTL=50
Reply from 38.49.39.136: bytes=32 time=145ms TTL=50
Reply from 38.49.39.136: bytes=32 time=144ms 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 = 144ms, Maximum = 145ms, Average = 145ms查看 |
GET PING Trace Dig |
|
| 浙江宁波移动 |
移动 |
浙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
148.058ms |
141.987ms |
144.694ms |
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=148ms TTL=49
Reply from 38.49.39.136: bytes=32 time=146ms TTL=49
Reply from 38.49.39.136: bytes=32 time=146ms TTL=49
Reply from 38.49.39.136: bytes=32 time=143ms TTL=49
Reply from 38.49.39.136: bytes=32 time=148ms TTL=49
Reply from 38.49.39.136: bytes=32 time=145ms TTL=49
Reply from 38.49.39.136: bytes=32 time=142ms TTL=49
Reply from 38.49.39.136: bytes=32 time=143ms TTL=49
Reply from 38.49.39.136: bytes=32 time=144ms TTL=49
Reply from 38.49.39.136: bytes=32 time=142ms 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 = 142ms, Maximum = 148ms, Average = 145ms查看 |
GET PING Trace Dig |
|
| 上海上海市电信 |
电信 |
上海 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
147.436ms |
142.045ms |
143.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=146ms TTL=50
Reply from 38.49.39.136: bytes=32 time=144ms TTL=50
Reply from 38.49.39.136: bytes=32 time=145ms TTL=50
Reply from 38.49.39.136: bytes=32 time=147ms TTL=50
Reply from 38.49.39.136: bytes=32 time=143ms TTL=50
Reply from 38.49.39.136: bytes=32 time=142ms TTL=50
Reply from 38.49.39.136: bytes=32 time=143ms TTL=50
Reply from 38.49.39.136: bytes=32 time=143ms TTL=50
Reply from 38.49.39.136: bytes=32 time=143ms TTL=50
Reply from 38.49.39.136: bytes=32 time=143ms 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 = 142ms, Maximum = 147ms, Average = 144ms查看 |
GET PING Trace Dig |
|
| 江苏无锡市移动 |
移动 |
江苏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
157.982ms |
140.521ms |
143.338ms |
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=141ms TTL=49
Reply from 38.49.39.136: bytes=32 time=142ms TTL=49
Reply from 38.49.39.136: bytes=32 time=141ms TTL=49
Reply from 38.49.39.136: bytes=32 time=141ms TTL=49
Reply from 38.49.39.136: bytes=32 time=141ms TTL=49
Reply from 38.49.39.136: bytes=32 time=143ms TTL=49
Reply from 38.49.39.136: bytes=32 time=142ms TTL=49
Reply from 38.49.39.136: bytes=32 time=141ms TTL=49
Reply from 38.49.39.136: bytes=32 time=144ms 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 = 141ms, Maximum = 158ms, Average = 143ms查看 |
GET PING Trace Dig |
|
| 浙江杭州市移动 |
移动 |
浙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
143.281ms |
142.621ms |
142.855ms |
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=143ms TTL=44
Reply from 38.49.39.136: bytes=32 time=143ms TTL=44
Reply from 38.49.39.136: bytes=32 time=143ms TTL=44
Reply from 38.49.39.136: bytes=32 time=143ms TTL=44
Reply from 38.49.39.136: bytes=32 time=143ms TTL=44
Reply from 38.49.39.136: bytes=32 time=143ms TTL=44
Reply from 38.49.39.136: bytes=32 time=143ms TTL=44
Reply from 38.49.39.136: bytes=32 time=143ms TTL=44
Reply from 38.49.39.136: bytes=32 time=143ms TTL=44
Reply from 38.49.39.136: bytes=32 time=143ms TTL=44
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 143ms, Maximum = 143ms, Average = 143ms查看 |
GET PING Trace Dig |
|
| 台湾台湾 |
台湾 |
台湾 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
145.282ms |
137.162ms |
139.314ms |
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=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=138ms TTL=51
Reply from 38.49.39.136: bytes=32 time=137ms TTL=51
Reply from 38.49.39.136: bytes=32 time=145ms TTL=51
Reply from 38.49.39.136: bytes=32 time=141ms 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 = 145ms, Average = 139ms查看 |
GET PING Trace Dig |
|
| 江苏南京市电信 |
电信 |
江苏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
139.682ms |
136.301ms |
137.628ms |
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=136ms TTL=49
Reply from 38.49.39.136: bytes=32 time=138ms TTL=49
Reply from 38.49.39.136: bytes=32 time=140ms TTL=49
Reply from 38.49.39.136: bytes=32 time=137ms TTL=49
Reply from 38.49.39.136: bytes=32 time=139ms 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=138ms 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 = 140ms, Average = 138ms查看 |
GET PING Trace Dig |
|
| 上海上海市移动 |
移动 |
上海 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
138.701ms |
134.373ms |
136.113ms |
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=138ms TTL=51
Reply from 38.49.39.136: bytes=32 time=139ms 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=134ms 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=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 = 134ms, Maximum = 139ms, Average = 136ms查看 |
GET PING Trace Dig |
|
| 安徽合肥移动 |
移动 |
安徽 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
139.431ms |
134.809ms |
135.772ms |
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=51
Reply from 38.49.39.136: bytes=32 time=135ms TTL=51
Reply from 38.49.39.136: bytes=32 time=139ms 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
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
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 = 139ms, Average = 136ms查看 |
GET PING Trace Dig |
|
| 上海上海市电信 |
电信 |
上海 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
136.198ms |
134.406ms |
135.516ms |
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=50
Reply from 38.49.39.136: bytes=32 time=136ms TTL=50
Reply from 38.49.39.136: bytes=32 time=135ms TTL=50
Reply from 38.49.39.136: bytes=32 time=136ms TTL=50
Reply from 38.49.39.136: bytes=32 time=136ms TTL=50
Reply from 38.49.39.136: bytes=32 time=136ms TTL=50
Reply from 38.49.39.136: bytes=32 time=135ms TTL=50
Reply from 38.49.39.136: bytes=32 time=136ms TTL=50
Reply from 38.49.39.136: bytes=32 time=136ms TTL=50
Reply from 38.49.39.136: bytes=32 time=134ms 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 = 134ms, Maximum = 136ms, Average = 136ms查看 |
GET PING Trace Dig |
|
| 江苏常州市电信 |
电信 |
江苏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
130.549ms |
130.288ms |
130.369ms |
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=131ms 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 = 131ms, Average = 130ms查看 |
GET PING Trace Dig |
|
| 浙江宁波市联通 |
联通 |
浙江 |
61.184.8.29 |
中国湖北襄阳电信 |
10 |
7 |
3 |
54.26ms |
0ms |
53.441ms |
32B |
PING hmshu.com
PING hmshu.com (61.184.8.29) with 32 bytes of data:
Request timed out.
Reply from 61.184.8.29: bytes=32 time=53ms TTL=50
Reply from 61.184.8.29: bytes=32 time=54ms TTL=50
Reply from 61.184.8.29: bytes=32 time=54ms TTL=50
Reply from 61.184.8.29: bytes=32 time=52ms TTL=50
Reply from 61.184.8.29: bytes=32 time=54ms TTL=50
Request timed out.
Reply from 61.184.8.29: bytes=32 time=53ms TTL=50
Reply from 61.184.8.29: bytes=32 time=53ms TTL=50
Request timed out.
Ping statistics for 61.184.8.29:
Packets: Sent = 10, Received = 7, Lost = 3 (30% loss),
Approximate round trip times in milli-seconds:
Minimum <1ms , Maximum = 54ms, Average = 53ms查看 |
GET PING Trace Dig |
|
| 美国国外 |
国外 |
美国 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
13.862ms |
13.745ms |
13.793ms |
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 |
|
| 美国国外 |
国外 |
美国 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
1.445ms |
0.748ms |
0.936ms |
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=1ms TTL=56
Reply from 38.49.39.136: bytes=32 time=1ms TTL=56
Reply from 38.49.39.136: bytes=32 time=1ms TTL=56
Reply from 38.49.39.136: bytes=32 time=1ms TTL=56
Reply from 38.49.39.136: bytes=32 time=1ms TTL=56
Reply from 38.49.39.136: bytes=32 time=1ms TTL=56
Reply from 38.49.39.136: bytes=32 time=1ms TTL=56
Reply from 38.49.39.136: bytes=32 time=1ms TTL=56
Reply from 38.49.39.136: bytes=32 time=1ms TTL=56
Reply from 38.49.39.136: bytes=32 time=1ms TTL=56
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms查看 |
GET PING Trace Dig |
|
| 海南琼海市电信 |
电信 |
海南 |
|
* |
0 |
0 |
0 |
0ms |
0ms |
0ms |
|
PING hmshu.com
PING hmshu.com () with 0 bytes of data:
Reply from : bytes=0 time=170ms TTL=51
Reply from : bytes=0 time=168ms TTL=51
Reply from : bytes=0 time=169ms TTL=51
Reply from : bytes=0 time=172ms TTL=51
Reply from : bytes=0 time=172ms TTL=51
Reply from : bytes=0 time=181ms TTL=51
Reply from : bytes=0 time=170ms TTL=51
Reply from : bytes=0 time=174ms TTL=51
Reply from : bytes=0 time=178ms TTL=51
Reply from : bytes=0 time=170ms TTL=51
Ping statistics for :
Packets: Sent = 0, Received = 0, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum <1ms , Maximum <1ms , Average <1ms 查看 |
GET PING Trace Dig |
|
| 台湾台湾 |
台湾 |
台湾 |
|
* |
0 |
0 |
0 |
0ms |
0ms |
0ms |
|
PING hmshu.com
PING hmshu.com () with 0 bytes of data:
Reply from : bytes=0 time=177ms TTL=49
Reply from : bytes=0 time=157ms TTL=49
Reply from : bytes=0 time=158ms TTL=49
Reply from : bytes=0 time=157ms TTL=49
Reply from : bytes=0 time=165ms TTL=49
Reply from : bytes=0 time=171ms TTL=49
Reply from : bytes=0 time=157ms TTL=49
Reply from : bytes=0 time=162ms TTL=49
Reply from : bytes=0 time=156ms TTL=49
Reply from : bytes=0 time=158ms TTL=49
Ping statistics for :
Packets: Sent = 0, Received = 0, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum <1ms , Maximum <1ms , Average <1ms 查看 |
GET PING Trace Dig |
|
| 安徽安庆市电信 |
电信 |
安徽 |
|
* |
0 |
0 |
0 |
0ms |
0ms |
0ms |
|
PING hmshu.com
PING hmshu.com () with 0 bytes of data:
Reply from : bytes=0 time=146ms TTL=43
Reply from : bytes=0 time=145ms TTL=43
Reply from : bytes=0 time=146ms TTL=43
Reply from : bytes=0 time=145ms TTL=43
Reply from : bytes=0 time=149ms TTL=43
Reply from : bytes=0 time=147ms TTL=43
Reply from : bytes=0 time=148ms TTL=43
Reply from : bytes=0 time=148ms TTL=43
Reply from : bytes=0 time=148ms TTL=43
Reply from : bytes=0 time=149ms TTL=43
Ping statistics for :
Packets: Sent = 0, Received = 0, Lost = 0 (0% 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 |
|
