| 监测点 |
ISP |
省份 |
解析IP |
解析IP所在地 |
发送 |
接收 |
丢弃 |
最大时间 |
最小时间 |
平均时间 |
包大小 |
详细信息 |
操作 |
| 共171个点 |
7个 |
共36个 |
共3个独立IP |
共3个独立节点 |
10 |
9 |
1 |
198.933ms |
163.608ms |
176.44ms |
|
|
|
| 广东东莞市移动 |
移动 |
广东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
9 |
1 |
801.392ms |
175ms |
459.799ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=801ms TTL=47
Reply from 38.49.39.136: bytes=32 time=496ms TTL=47
Request timed out.
Reply from 38.49.39.136: bytes=32 time=611ms TTL=47
Reply from 38.49.39.136: bytes=32 time=628ms TTL=47
Reply from 38.49.39.136: bytes=32 time=724ms TTL=47
Reply from 38.49.39.136: bytes=32 time=305ms TTL=47
Reply from 38.49.39.136: bytes=32 time=191ms TTL=47
Reply from 38.49.39.136: bytes=32 time=175ms TTL=47
Reply from 38.49.39.136: bytes=32 time=206ms 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 = 175ms, Maximum = 801ms, Average = 460ms查看 |
GET PING Trace Dig |
|
| 广西梧州市联通 |
联通 |
广西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
7 |
3 |
850.221ms |
0ms |
398.825ms |
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.
Reply from 38.49.39.136: bytes=32 time=850ms TTL=47
Reply from 38.49.39.136: bytes=32 time=604ms TTL=47
Reply from 38.49.39.136: bytes=32 time=266ms TTL=47
Reply from 38.49.39.136: bytes=32 time=180ms TTL=47
Reply from 38.49.39.136: bytes=32 time=257ms TTL=47
Reply from 38.49.39.136: bytes=32 time=226ms TTL=47
Reply from 38.49.39.136: bytes=32 time=409ms TTL=47
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 7, Lost = 3 (30% loss),
Approximate round trip times in milli-seconds:
Minimum <1ms , Maximum = 850ms, Average = 399ms查看 |
GET PING Trace Dig |
|
| 辽宁葫芦岛市联通 |
联通 |
辽宁 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
9 |
1 |
589.861ms |
210.163ms |
380.946ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=210ms TTL=49
Reply from 38.49.39.136: bytes=32 time=399ms TTL=49
Reply from 38.49.39.136: bytes=32 time=456ms TTL=49
Reply from 38.49.39.136: bytes=32 time=398ms TTL=49
Reply from 38.49.39.136: bytes=32 time=397ms TTL=49
Reply from 38.49.39.136: bytes=32 time=215ms TTL=49
Reply from 38.49.39.136: bytes=32 time=253ms TTL=49
Reply from 38.49.39.136: bytes=32 time=510ms TTL=49
Reply from 38.49.39.136: bytes=32 time=590ms TTL=49
Request timed out.
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 9, Lost = 1 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 210ms, Maximum = 590ms, Average = 381ms查看 |
GET PING Trace Dig |
|
| 青海西宁市电信 |
电信 |
青海 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
778.666ms |
187.396ms |
340.341ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=221ms TTL=50
Reply from 38.49.39.136: bytes=32 time=257ms TTL=50
Reply from 38.49.39.136: bytes=32 time=220ms TTL=50
Reply from 38.49.39.136: bytes=32 time=230ms TTL=50
Reply from 38.49.39.136: bytes=32 time=779ms TTL=50
Reply from 38.49.39.136: bytes=32 time=237ms TTL=50
Reply from 38.49.39.136: bytes=32 time=363ms TTL=50
Reply from 38.49.39.136: bytes=32 time=608ms TTL=50
Reply from 38.49.39.136: bytes=32 time=187ms TTL=50
Reply from 38.49.39.136: bytes=32 time=302ms 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 = 187ms, Maximum = 779ms, Average = 340ms查看 |
GET PING Trace Dig |
|
| 四川成都市电信 |
电信 |
四川 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
256.625ms |
248.605ms |
252.022ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=255ms TTL=49
Reply from 38.49.39.136: bytes=32 time=250ms TTL=49
Reply from 38.49.39.136: bytes=32 time=253ms TTL=49
Reply from 38.49.39.136: bytes=32 time=257ms TTL=49
Reply from 38.49.39.136: bytes=32 time=249ms TTL=49
Reply from 38.49.39.136: bytes=32 time=250ms TTL=49
Reply from 38.49.39.136: bytes=32 time=253ms TTL=49
Reply from 38.49.39.136: bytes=32 time=256ms TTL=49
Reply from 38.49.39.136: bytes=32 time=249ms TTL=49
Reply from 38.49.39.136: bytes=32 time=251ms 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 = 249ms, Maximum = 257ms, Average = 252ms查看 |
GET PING Trace Dig |
|
| 广西南宁市移动 |
移动 |
广西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
439.764ms |
173.642ms |
244.012ms |
32B |
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=45
Reply from 38.49.39.136: bytes=32 time=440ms TTL=45
Reply from 38.49.39.136: bytes=32 time=265ms TTL=45
Reply from 38.49.39.136: bytes=32 time=193ms TTL=45
Reply from 38.49.39.136: bytes=32 time=176ms TTL=45
Reply from 38.49.39.136: bytes=32 time=177ms TTL=45
Reply from 38.49.39.136: bytes=32 time=175ms TTL=45
Reply from 38.49.39.136: bytes=32 time=174ms TTL=45
Reply from 38.49.39.136: bytes=32 time=350ms TTL=45
Reply from 38.49.39.136: bytes=32 time=266ms 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 = 174ms, Maximum = 440ms, Average = 244ms查看 |
GET PING Trace Dig |
|
| 北京北京市移动 |
移动 |
北京 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
249.804ms |
229.203ms |
241.558ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=229ms TTL=47
Reply from 38.49.39.136: bytes=32 time=229ms TTL=47
Reply from 38.49.39.136: bytes=32 time=230ms TTL=47
Reply from 38.49.39.136: bytes=32 time=250ms TTL=47
Reply from 38.49.39.136: bytes=32 time=249ms TTL=47
Reply from 38.49.39.136: bytes=32 time=250ms TTL=47
Reply from 38.49.39.136: bytes=32 time=250ms TTL=47
Reply from 38.49.39.136: bytes=32 time=243ms TTL=47
Reply from 38.49.39.136: bytes=32 time=237ms TTL=47
Reply from 38.49.39.136: bytes=32 time=250ms 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 = 229ms, Maximum = 250ms, Average = 242ms查看 |
GET PING Trace Dig |
|
| 新疆和田地区移动 |
移动 |
新疆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
265.64ms |
237.366ms |
240.555ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=238ms TTL=48
Reply from 38.49.39.136: bytes=32 time=237ms TTL=48
Reply from 38.49.39.136: bytes=32 time=238ms TTL=48
Reply from 38.49.39.136: bytes=32 time=238ms TTL=48
Reply from 38.49.39.136: bytes=32 time=238ms TTL=48
Reply from 38.49.39.136: bytes=32 time=238ms TTL=48
Reply from 38.49.39.136: bytes=32 time=266ms TTL=48
Reply from 38.49.39.136: bytes=32 time=238ms TTL=48
Reply from 38.49.39.136: bytes=32 time=238ms TTL=48
Reply from 38.49.39.136: bytes=32 time=238ms 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 = 237ms, Maximum = 266ms, Average = 241ms查看 |
GET PING Trace Dig |
|
| 黑龙江齐齐哈尔市移动 |
移动 |
黑龙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
383.241ms |
216.06ms |
238.527ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=216ms TTL=49
Reply from 38.49.39.136: bytes=32 time=222ms TTL=49
Reply from 38.49.39.136: bytes=32 time=235ms TTL=49
Reply from 38.49.39.136: bytes=32 time=223ms TTL=49
Reply from 38.49.39.136: bytes=32 time=218ms TTL=49
Reply from 38.49.39.136: bytes=32 time=220ms TTL=49
Reply from 38.49.39.136: bytes=32 time=220ms TTL=49
Reply from 38.49.39.136: bytes=32 time=383ms TTL=49
Reply from 38.49.39.136: bytes=32 time=225ms TTL=49
Reply from 38.49.39.136: bytes=32 time=224ms 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 = 216ms, Maximum = 383ms, Average = 239ms查看 |
GET PING Trace Dig |
|
| 四川成都市电信 |
电信 |
四川 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
9 |
1 |
399.248ms |
200.043ms |
232.164ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=213ms TTL=47
Reply from 38.49.39.136: bytes=32 time=220ms TTL=47
Reply from 38.49.39.136: bytes=32 time=220ms TTL=47
Reply from 38.49.39.136: bytes=32 time=210ms TTL=47
Reply from 38.49.39.136: bytes=32 time=216ms TTL=47
Reply from 38.49.39.136: bytes=32 time=203ms TTL=47
Reply from 38.49.39.136: bytes=32 time=399ms TTL=47
Reply from 38.49.39.136: bytes=32 time=210ms TTL=47
Reply from 38.49.39.136: bytes=32 time=200ms TTL=47
Request timed out.
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 9, Lost = 1 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 200ms, Maximum = 399ms, Average = 232ms查看 |
GET PING Trace Dig |
|
| 西藏阿里移动 |
移动 |
西藏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
9 |
1 |
235.293ms |
226.718ms |
230.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=235ms TTL=48
Reply from 38.49.39.136: bytes=32 time=235ms TTL=48
Reply from 38.49.39.136: bytes=32 time=230ms TTL=48
Reply from 38.49.39.136: bytes=32 time=233ms TTL=48
Reply from 38.49.39.136: bytes=32 time=227ms TTL=48
Reply from 38.49.39.136: bytes=32 time=230ms TTL=48
Reply from 38.49.39.136: bytes=32 time=230ms TTL=48
Reply from 38.49.39.136: bytes=32 time=233ms TTL=48
Reply from 38.49.39.136: bytes=32 time=227ms TTL=48
Request timed out.
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 9, Lost = 1 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 227ms, Maximum = 235ms, Average = 231ms查看 |
GET PING Trace Dig |
|
| 上海上海市电信 |
电信 |
上海 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
439.722ms |
142.894ms |
230.612ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=143ms TTL=49
Reply from 38.49.39.136: bytes=32 time=143ms TTL=49
Reply from 38.49.39.136: bytes=32 time=153ms TTL=49
Reply from 38.49.39.136: bytes=32 time=440ms TTL=49
Reply from 38.49.39.136: bytes=32 time=400ms TTL=49
Reply from 38.49.39.136: bytes=32 time=147ms TTL=49
Reply from 38.49.39.136: bytes=32 time=150ms TTL=49
Reply from 38.49.39.136: bytes=32 time=222ms TTL=49
Reply from 38.49.39.136: bytes=32 time=355ms TTL=49
Reply from 38.49.39.136: bytes=32 time=154ms 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 = 143ms, Maximum = 440ms, Average = 231ms查看 |
GET PING Trace Dig |
|
| 安徽合肥市联通 |
联通 |
安徽 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
258.263ms |
199.782ms |
229.054ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=244ms TTL=50
Reply from 38.49.39.136: bytes=32 time=250ms TTL=50
Reply from 38.49.39.136: bytes=32 time=216ms TTL=50
Reply from 38.49.39.136: bytes=32 time=204ms TTL=50
Reply from 38.49.39.136: bytes=32 time=234ms TTL=50
Reply from 38.49.39.136: bytes=32 time=258ms TTL=50
Reply from 38.49.39.136: bytes=32 time=240ms TTL=50
Reply from 38.49.39.136: bytes=32 time=200ms TTL=50
Reply from 38.49.39.136: bytes=32 time=208ms TTL=50
Reply from 38.49.39.136: bytes=32 time=238ms 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 = 200ms, Maximum = 258ms, Average = 229ms查看 |
GET PING Trace Dig |
|
| 江西吉安市电信 |
电信 |
江西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
397.786ms |
149.442ms |
216.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=398ms TTL=52
Reply from 38.49.39.136: bytes=32 time=219ms TTL=52
Reply from 38.49.39.136: bytes=32 time=390ms TTL=52
Reply from 38.49.39.136: bytes=32 time=187ms TTL=52
Reply from 38.49.39.136: bytes=32 time=153ms TTL=52
Reply from 38.49.39.136: bytes=32 time=150ms TTL=52
Reply from 38.49.39.136: bytes=32 time=166ms TTL=52
Reply from 38.49.39.136: bytes=32 time=194ms TTL=52
Reply from 38.49.39.136: bytes=32 time=161ms TTL=52
Reply from 38.49.39.136: bytes=32 time=149ms 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 = 149ms, Maximum = 398ms, Average = 217ms查看 |
GET PING Trace Dig |
|
| 甘肃兰州市联通 |
联通 |
甘肃 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
217.499ms |
212.358ms |
214.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=214ms TTL=44
Reply from 38.49.39.136: bytes=32 time=217ms TTL=44
Reply from 38.49.39.136: bytes=32 time=214ms TTL=44
Reply from 38.49.39.136: bytes=32 time=216ms TTL=44
Reply from 38.49.39.136: bytes=32 time=212ms TTL=44
Reply from 38.49.39.136: bytes=32 time=216ms TTL=44
Reply from 38.49.39.136: bytes=32 time=214ms TTL=44
Reply from 38.49.39.136: bytes=32 time=213ms TTL=44
Reply from 38.49.39.136: bytes=32 time=213ms TTL=44
Reply from 38.49.39.136: bytes=32 time=217ms 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 = 212ms, Maximum = 217ms, Average = 215ms查看 |
GET PING Trace Dig |
|
| 新疆乌鲁木齐移动 |
移动 |
新疆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
250.205ms |
206.237ms |
210.926ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=207ms TTL=49
Reply from 38.49.39.136: bytes=32 time=206ms TTL=49
Reply from 38.49.39.136: bytes=32 time=207ms TTL=49
Reply from 38.49.39.136: bytes=32 time=250ms TTL=49
Reply from 38.49.39.136: bytes=32 time=206ms TTL=49
Reply from 38.49.39.136: bytes=32 time=206ms TTL=49
Reply from 38.49.39.136: bytes=32 time=207ms TTL=49
Reply from 38.49.39.136: bytes=32 time=207ms TTL=49
Reply from 38.49.39.136: bytes=32 time=207ms TTL=49
Reply from 38.49.39.136: bytes=32 time=207ms TTL=49
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 206ms, Maximum = 250ms, Average = 211ms查看 |
GET PING Trace Dig |
|
| 云南昆明市联通 |
联通 |
云南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
295.066ms |
191.461ms |
208.353ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=198ms TTL=47
Reply from 38.49.39.136: bytes=32 time=193ms TTL=47
Reply from 38.49.39.136: bytes=32 time=295ms TTL=47
Reply from 38.49.39.136: bytes=32 time=202ms TTL=47
Reply from 38.49.39.136: bytes=32 time=200ms TTL=47
Reply from 38.49.39.136: bytes=32 time=214ms TTL=47
Reply from 38.49.39.136: bytes=32 time=192ms 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=206ms 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 = 191ms, Maximum = 295ms, Average = 208ms查看 |
GET PING Trace Dig |
|
| 吉林通化市联通 |
联通 |
吉林 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
223.319ms |
200.639ms |
204.701ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=203ms TTL=48
Reply from 38.49.39.136: bytes=32 time=201ms TTL=48
Reply from 38.49.39.136: bytes=32 time=202ms TTL=48
Reply from 38.49.39.136: bytes=32 time=202ms TTL=48
Reply from 38.49.39.136: bytes=32 time=201ms TTL=48
Reply from 38.49.39.136: bytes=32 time=223ms TTL=48
Reply from 38.49.39.136: bytes=32 time=202ms TTL=48
Reply from 38.49.39.136: bytes=32 time=202ms TTL=48
Reply from 38.49.39.136: bytes=32 time=209ms TTL=48
Reply from 38.49.39.136: bytes=32 time=201ms 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 = 201ms, Maximum = 223ms, Average = 205ms查看 |
GET PING Trace Dig |
|
| 内蒙古呼和浩特联通 |
联通 |
内蒙古 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
209.143ms |
201.96ms |
204.35ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=203ms TTL=47
Reply from 38.49.39.136: bytes=32 time=203ms TTL=47
Reply from 38.49.39.136: bytes=32 time=209ms TTL=47
Reply from 38.49.39.136: bytes=32 time=202ms TTL=47
Reply from 38.49.39.136: bytes=32 time=203ms TTL=47
Reply from 38.49.39.136: bytes=32 time=204ms TTL=47
Reply from 38.49.39.136: bytes=32 time=202ms TTL=47
Reply from 38.49.39.136: bytes=32 time=204ms TTL=47
Reply from 38.49.39.136: bytes=32 time=204ms TTL=47
Reply from 38.49.39.136: bytes=32 time=209ms 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 = 202ms, Maximum = 209ms, Average = 204ms查看 |
GET PING Trace Dig |
|
| 黑龙江大庆市联通 |
联通 |
黑龙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
214.303ms |
196.203ms |
204.056ms |
32B |
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=49
Reply from 38.49.39.136: bytes=32 time=204ms TTL=49
Reply from 38.49.39.136: bytes=32 time=196ms TTL=49
Reply from 38.49.39.136: bytes=32 time=198ms TTL=49
Reply from 38.49.39.136: bytes=32 time=197ms TTL=49
Reply from 38.49.39.136: bytes=32 time=206ms TTL=49
Reply from 38.49.39.136: bytes=32 time=213ms TTL=49
Reply from 38.49.39.136: bytes=32 time=206ms TTL=49
Reply from 38.49.39.136: bytes=32 time=209ms TTL=49
Reply from 38.49.39.136: bytes=32 time=214ms 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 = 196ms, Maximum = 214ms, Average = 204ms查看 |
GET PING Trace Dig |
|
| 西藏拉萨市移动 |
移动 |
西藏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
209.979ms |
196.219ms |
202.882ms |
32B |
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=49
Reply from 38.49.39.136: bytes=32 time=196ms TTL=49
Reply from 38.49.39.136: bytes=32 time=200ms TTL=49
Reply from 38.49.39.136: bytes=32 time=202ms TTL=49
Reply from 38.49.39.136: bytes=32 time=202ms TTL=49
Reply from 38.49.39.136: bytes=32 time=204ms TTL=49
Reply from 38.49.39.136: bytes=32 time=205ms TTL=49
Reply from 38.49.39.136: bytes=32 time=205ms TTL=49
Reply from 38.49.39.136: bytes=32 time=204ms TTL=49
Reply from 38.49.39.136: bytes=32 time=210ms 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 = 196ms, Maximum = 210ms, Average = 203ms查看 |
GET PING Trace Dig |
|
| 广东茂名市联通 |
联通 |
广东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
6 |
4 |
399.303ms |
163.047ms |
202.827ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=164ms TTL=50
Reply from 38.49.39.136: bytes=32 time=163ms TTL=50
Reply from 38.49.39.136: bytes=32 time=163ms TTL=50
Reply from 38.49.39.136: bytes=32 time=163ms TTL=50
Reply from 38.49.39.136: bytes=32 time=164ms TTL=50
Request timed out.
Reply from 38.49.39.136: bytes=32 time=399ms TTL=50
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 6, Lost = 4 (40% loss),
Approximate round trip times in milli-seconds:
Minimum = 163ms, Maximum = 399ms, Average = 203ms查看 |
GET PING Trace Dig |
|
| 吉林长春移动 |
移动 |
吉林 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
210.599ms |
196.472ms |
202.301ms |
32B |
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=49
Reply from 38.49.39.136: bytes=32 time=203ms TTL=49
Reply from 38.49.39.136: bytes=32 time=206ms TTL=49
Reply from 38.49.39.136: bytes=32 time=198ms TTL=49
Reply from 38.49.39.136: bytes=32 time=211ms TTL=49
Reply from 38.49.39.136: bytes=32 time=199ms TTL=49
Reply from 38.49.39.136: bytes=32 time=200ms TTL=49
Reply from 38.49.39.136: bytes=32 time=209ms TTL=49
Reply from 38.49.39.136: bytes=32 time=199ms TTL=49
Reply from 38.49.39.136: bytes=32 time=202ms 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 = 196ms, Maximum = 211ms, Average = 202ms查看 |
GET PING Trace Dig |
|
| 江苏南京联通 |
联通 |
江苏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
214.679ms |
188.939ms |
198.327ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=203ms TTL=47
Reply from 38.49.39.136: bytes=32 time=189ms TTL=47
Reply from 38.49.39.136: bytes=32 time=215ms TTL=47
Reply from 38.49.39.136: bytes=32 time=205ms TTL=47
Reply from 38.49.39.136: bytes=32 time=194ms 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=191ms TTL=47
Reply from 38.49.39.136: bytes=32 time=194ms TTL=47
Reply from 38.49.39.136: bytes=32 time=213ms 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 = 189ms, Maximum = 215ms, Average = 198ms查看 |
GET PING Trace Dig |
|
| 云南玉溪市移动 |
移动 |
云南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
198.827ms |
198ms |
198.308ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=198ms TTL=51
Reply from 38.49.39.136: bytes=32 time=198ms TTL=51
Reply from 38.49.39.136: bytes=32 time=198ms TTL=51
Reply from 38.49.39.136: bytes=32 time=198ms TTL=51
Reply from 38.49.39.136: bytes=32 time=198ms TTL=51
Reply from 38.49.39.136: bytes=32 time=198ms TTL=51
Reply from 38.49.39.136: bytes=32 time=198ms TTL=51
Reply from 38.49.39.136: bytes=32 time=198ms TTL=51
Reply from 38.49.39.136: bytes=32 time=199ms TTL=51
Reply from 38.49.39.136: bytes=32 time=198ms 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 = 198ms, Maximum = 199ms, Average = 198ms查看 |
GET PING Trace Dig |
|
| 重庆重庆市移动 |
移动 |
重庆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
9 |
1 |
225.012ms |
189.224ms |
196.758ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=225ms TTL=40
Reply from 38.49.39.136: bytes=32 time=209ms TTL=40
Reply from 38.49.39.136: bytes=32 time=192ms TTL=40
Reply from 38.49.39.136: bytes=32 time=190ms TTL=40
Request timed out.
Reply from 38.49.39.136: bytes=32 time=194ms TTL=40
Reply from 38.49.39.136: bytes=32 time=191ms TTL=40
Reply from 38.49.39.136: bytes=32 time=191ms TTL=40
Reply from 38.49.39.136: bytes=32 time=189ms TTL=40
Reply from 38.49.39.136: bytes=32 time=190ms TTL=40
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 9, Lost = 1 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 189ms, Maximum = 225ms, Average = 197ms查看 |
GET PING Trace Dig |
|
| 云南普洱市移动 |
移动 |
云南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
199.569ms |
194.111ms |
196.7ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=199ms TTL=47
Reply from 38.49.39.136: bytes=32 time=200ms TTL=47
Reply from 38.49.39.136: bytes=32 time=199ms TTL=47
Reply from 38.49.39.136: bytes=32 time=196ms TTL=47
Reply from 38.49.39.136: bytes=32 time=196ms TTL=47
Reply from 38.49.39.136: bytes=32 time=196ms TTL=47
Reply from 38.49.39.136: bytes=32 time=194ms TTL=47
Reply from 38.49.39.136: bytes=32 time=195ms TTL=47
Reply from 38.49.39.136: bytes=32 time=197ms TTL=47
Reply from 38.49.39.136: bytes=32 time=197ms 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 = 194ms, Maximum = 200ms, Average = 197ms查看 |
GET PING Trace Dig |
|
| 黑龙江哈尔滨市电信 |
电信 |
黑龙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
221.703ms |
191.311ms |
196.166ms |
32B |
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=45
Reply from 38.49.39.136: bytes=32 time=192ms TTL=45
Reply from 38.49.39.136: bytes=32 time=192ms TTL=45
Reply from 38.49.39.136: bytes=32 time=195ms TTL=45
Reply from 38.49.39.136: bytes=32 time=198ms TTL=45
Reply from 38.49.39.136: bytes=32 time=191ms TTL=45
Reply from 38.49.39.136: bytes=32 time=195ms TTL=45
Reply from 38.49.39.136: bytes=32 time=222ms TTL=45
Reply from 38.49.39.136: bytes=32 time=192ms TTL=45
Reply from 38.49.39.136: bytes=32 time=192ms 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 = 191ms, Maximum = 222ms, Average = 196ms查看 |
GET PING Trace Dig |
|
| 新疆乌鲁木齐市电信 |
电信 |
新疆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
200.381ms |
192.541ms |
195.833ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=195ms TTL=51
Reply from 38.49.39.136: bytes=32 time=194ms TTL=51
Reply from 38.49.39.136: bytes=32 time=200ms TTL=51
Reply from 38.49.39.136: bytes=32 time=194ms TTL=51
Reply from 38.49.39.136: bytes=32 time=193ms TTL=51
Reply from 38.49.39.136: bytes=32 time=198ms TTL=51
Reply from 38.49.39.136: bytes=32 time=195ms TTL=51
Reply from 38.49.39.136: bytes=32 time=200ms TTL=51
Reply from 38.49.39.136: bytes=32 time=195ms TTL=51
Reply from 38.49.39.136: bytes=32 time=194ms 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 = 193ms, Maximum = 200ms, Average = 196ms查看 |
GET PING Trace Dig |
|
| 辽宁锦州市联通 |
联通 |
辽宁 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
198.855ms |
194.689ms |
195.454ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=199ms TTL=50
Reply from 38.49.39.136: bytes=32 time=195ms TTL=50
Reply from 38.49.39.136: bytes=32 time=195ms TTL=50
Reply from 38.49.39.136: bytes=32 time=196ms TTL=50
Reply from 38.49.39.136: bytes=32 time=195ms TTL=50
Reply from 38.49.39.136: bytes=32 time=195ms TTL=50
Reply from 38.49.39.136: bytes=32 time=196ms TTL=50
Reply from 38.49.39.136: bytes=32 time=195ms TTL=50
Reply from 38.49.39.136: bytes=32 time=195ms TTL=50
Reply from 38.49.39.136: bytes=32 time=195ms TTL=50
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 195ms, Maximum = 199ms, Average = 195ms查看 |
GET PING Trace Dig |
|
| 辽宁锦州市联通 |
联通 |
辽宁 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
7 |
3 |
195.8ms |
0ms |
195.224ms |
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.
Reply from 38.49.39.136: bytes=32 time=195ms TTL=51
Reply from 38.49.39.136: bytes=32 time=196ms TTL=51
Reply from 38.49.39.136: bytes=32 time=195ms TTL=51
Reply from 38.49.39.136: bytes=32 time=195ms TTL=51
Reply from 38.49.39.136: bytes=32 time=195ms TTL=51
Reply from 38.49.39.136: bytes=32 time=195ms TTL=51
Reply from 38.49.39.136: bytes=32 time=195ms TTL=51
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 7, Lost = 3 (30% loss),
Approximate round trip times in milli-seconds:
Minimum <1ms , Maximum = 196ms, Average = 195ms查看 |
GET PING Trace Dig |
|
| 云南临沧市电信 |
电信 |
云南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
195.562ms |
193.122ms |
194.499ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
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=195ms TTL=48
Reply from 38.49.39.136: bytes=32 time=195ms TTL=48
Reply from 38.49.39.136: bytes=32 time=195ms TTL=48
Reply from 38.49.39.136: bytes=32 time=193ms TTL=48
Reply from 38.49.39.136: bytes=32 time=195ms TTL=48
Reply from 38.49.39.136: bytes=32 time=196ms TTL=48
Reply from 38.49.39.136: bytes=32 time=193ms TTL=48
Reply from 38.49.39.136: bytes=32 time=195ms TTL=48
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 193ms, Maximum = 196ms, Average = 194ms查看 |
GET PING Trace Dig |
|
| 黑龙江鹤岗市联通 |
联通 |
黑龙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
194.35ms |
193.447ms |
193.842ms |
32B |
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=193ms 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=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
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 193ms, Maximum = 194ms, Average = 194ms查看 |
GET PING Trace Dig |
|
| 西藏未知电信 |
电信 |
西藏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
194.613ms |
189.824ms |
192.954ms |
32B |
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=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
Reply from 38.49.39.136: bytes=32 time=193ms TTL=50
Reply from 38.49.39.136: bytes=32 time=195ms TTL=50
Reply from 38.49.39.136: bytes=32 time=194ms TTL=50
Reply from 38.49.39.136: bytes=32 time=194ms TTL=50
Reply from 38.49.39.136: bytes=32 time=194ms TTL=50
Reply from 38.49.39.136: bytes=32 time=194ms TTL=50
Reply from 38.49.39.136: bytes=32 time=194ms 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 = 190ms, Maximum = 195ms, Average = 193ms查看 |
GET PING Trace Dig |
|
| 广东茂名市电信 |
电信 |
广东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
246.113ms |
173.381ms |
192.903ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=210ms TTL=50
Reply from 38.49.39.136: bytes=32 time=185ms TTL=50
Reply from 38.49.39.136: bytes=32 time=199ms TTL=50
Reply from 38.49.39.136: bytes=32 time=189ms TTL=50
Reply from 38.49.39.136: bytes=32 time=173ms TTL=50
Reply from 38.49.39.136: bytes=32 time=194ms TTL=50
Reply from 38.49.39.136: bytes=32 time=246ms 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=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 = 173ms, Maximum = 246ms, Average = 193ms查看 |
GET PING Trace Dig |
|
| 吉林长春市联通 |
联通 |
吉林 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
199.619ms |
190.47ms |
192.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=49
Reply from 38.49.39.136: bytes=32 time=192ms TTL=49
Reply from 38.49.39.136: bytes=32 time=193ms TTL=49
Reply from 38.49.39.136: bytes=32 time=191ms TTL=49
Reply from 38.49.39.136: bytes=32 time=200ms TTL=49
Reply from 38.49.39.136: bytes=32 time=192ms TTL=49
Reply from 38.49.39.136: bytes=32 time=191ms TTL=49
Reply from 38.49.39.136: bytes=32 time=190ms TTL=49
Reply from 38.49.39.136: bytes=32 time=191ms TTL=49
Reply from 38.49.39.136: bytes=32 time=191ms TTL=49
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 190ms, Maximum = 200ms, Average = 192ms查看 |
GET PING Trace Dig |
|
| 印度尼西亚国外 |
国外 |
印度尼西亚 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
193.078ms |
189.977ms |
190.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=193ms TTL=55
Reply from 38.49.39.136: bytes=32 time=191ms TTL=55
Reply from 38.49.39.136: bytes=32 time=190ms TTL=55
Reply from 38.49.39.136: bytes=32 time=191ms TTL=55
Reply from 38.49.39.136: bytes=32 time=190ms TTL=55
Reply from 38.49.39.136: bytes=32 time=190ms TTL=55
Reply from 38.49.39.136: bytes=32 time=190ms TTL=55
Reply from 38.49.39.136: bytes=32 time=190ms TTL=55
Reply from 38.49.39.136: bytes=32 time=190ms TTL=55
Reply from 38.49.39.136: bytes=32 time=193ms TTL=55
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 190ms, Maximum = 193ms, Average = 191ms查看 |
GET PING Trace Dig |
|
| 河南周口联通 |
联通 |
河南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
337.639ms |
156.639ms |
189.643ms |
32B |
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=157ms TTL=49
Reply from 38.49.39.136: bytes=32 time=160ms TTL=49
Reply from 38.49.39.136: bytes=32 time=338ms TTL=49
Reply from 38.49.39.136: bytes=32 time=168ms TTL=49
Reply from 38.49.39.136: bytes=32 time=257ms TTL=49
Reply from 38.49.39.136: bytes=32 time=165ms 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=162ms TTL=49
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 157ms, Maximum = 338ms, Average = 190ms查看 |
GET PING Trace Dig |
|
| 贵州毕节市电信 |
电信 |
贵州 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
192.1ms |
187.06ms |
189.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=192ms TTL=51
Reply from 38.49.39.136: bytes=32 time=188ms 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=192ms 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=192ms TTL=51
Reply from 38.49.39.136: bytes=32 time=188ms TTL=51
Reply from 38.49.39.136: bytes=32 time=187ms 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 = 192ms, Average = 189ms查看 |
GET PING Trace Dig |
|
| 西藏拉萨市电信 |
电信 |
西藏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
192.541ms |
187.053ms |
188.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=188ms TTL=48
Reply from 38.49.39.136: bytes=32 time=187ms TTL=48
Reply from 38.49.39.136: bytes=32 time=193ms TTL=48
Reply from 38.49.39.136: bytes=32 time=188ms TTL=48
Reply from 38.49.39.136: bytes=32 time=189ms TTL=48
Reply from 38.49.39.136: bytes=32 time=188ms TTL=48
Reply from 38.49.39.136: bytes=32 time=189ms TTL=48
Reply from 38.49.39.136: bytes=32 time=190ms TTL=48
Reply from 38.49.39.136: bytes=32 time=189ms TTL=48
Reply from 38.49.39.136: bytes=32 time=188ms 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 = 187ms, Maximum = 193ms, Average = 189ms查看 |
GET PING Trace Dig |
|
| 辽宁辽阳市电信 |
电信 |
辽宁 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
201.323ms |
182.768ms |
188.194ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
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=185ms TTL=50
Reply from 38.49.39.136: bytes=32 time=183ms TTL=50
Reply from 38.49.39.136: bytes=32 time=185ms TTL=50
Reply from 38.49.39.136: bytes=32 time=186ms TTL=50
Reply from 38.49.39.136: bytes=32 time=184ms TTL=50
Reply from 38.49.39.136: bytes=32 time=184ms TTL=50
Reply from 38.49.39.136: bytes=32 time=193ms TTL=50
Reply from 38.49.39.136: bytes=32 time=186ms 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 = 201ms, Average = 188ms查看 |
GET PING Trace Dig |
|
| 宁夏银川市电信 |
电信 |
宁夏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
192.738ms |
175.294ms |
186.856ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=175ms TTL=50
Reply from 38.49.39.136: bytes=32 time=184ms TTL=50
Reply from 38.49.39.136: bytes=32 time=187ms TTL=50
Reply from 38.49.39.136: bytes=32 time=190ms TTL=50
Reply from 38.49.39.136: bytes=32 time=193ms TTL=50
Reply from 38.49.39.136: bytes=32 time=190ms TTL=50
Reply from 38.49.39.136: bytes=32 time=186ms TTL=50
Reply from 38.49.39.136: bytes=32 time=186ms TTL=50
Reply from 38.49.39.136: bytes=32 time=189ms TTL=50
Reply from 38.49.39.136: bytes=32 time=191ms TTL=50
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 175ms, Maximum = 193ms, Average = 187ms查看 |
GET PING Trace Dig |
|
| 湖北荆门市联通 |
联通 |
湖北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
187.876ms |
185.235ms |
186.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=187ms TTL=51
Reply from 38.49.39.136: bytes=32 time=185ms TTL=51
Reply from 38.49.39.136: bytes=32 time=186ms TTL=51
Reply from 38.49.39.136: bytes=32 time=186ms TTL=51
Reply from 38.49.39.136: bytes=32 time=185ms TTL=51
Reply from 38.49.39.136: bytes=32 time=186ms TTL=51
Reply from 38.49.39.136: bytes=32 time=187ms TTL=51
Reply from 38.49.39.136: bytes=32 time=186ms TTL=51
Reply from 38.49.39.136: bytes=32 time=188ms TTL=51
Reply from 38.49.39.136: bytes=32 time=187ms 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 = 185ms, Maximum = 188ms, Average = 186ms查看 |
GET PING Trace Dig |
|
| 北京北京市联通 |
联通 |
北京 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
199.277ms |
178.522ms |
185.944ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=187ms TTL=49
Reply from 38.49.39.136: bytes=32 time=199ms TTL=49
Reply from 38.49.39.136: bytes=32 time=193ms TTL=49
Reply from 38.49.39.136: bytes=32 time=188ms TTL=49
Reply from 38.49.39.136: bytes=32 time=182ms TTL=49
Reply from 38.49.39.136: bytes=32 time=179ms TTL=49
Reply from 38.49.39.136: bytes=32 time=179ms TTL=49
Reply from 38.49.39.136: bytes=32 time=180ms TTL=49
Reply from 38.49.39.136: bytes=32 time=179ms TTL=49
Reply from 38.49.39.136: bytes=32 time=194ms 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 = 199ms, Average = 186ms查看 |
GET PING Trace Dig |
|
| 广西南宁市电信 |
电信 |
广西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
195.139ms |
179.579ms |
184.254ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=184ms TTL=52
Reply from 38.49.39.136: bytes=32 time=180ms TTL=52
Reply from 38.49.39.136: bytes=32 time=182ms TTL=52
Reply from 38.49.39.136: bytes=32 time=182ms TTL=52
Reply from 38.49.39.136: bytes=32 time=195ms TTL=52
Reply from 38.49.39.136: bytes=32 time=185ms TTL=52
Reply from 38.49.39.136: bytes=32 time=186ms TTL=52
Reply from 38.49.39.136: bytes=32 time=182ms TTL=52
Reply from 38.49.39.136: bytes=32 time=181ms TTL=52
Reply from 38.49.39.136: bytes=32 time=186ms TTL=52
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 180ms, Maximum = 195ms, Average = 184ms查看 |
GET PING Trace Dig |
|
| 吉林吉林市移动 |
移动 |
吉林 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
184.3ms |
183.161ms |
183.986ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=183ms TTL=49
Reply from 38.49.39.136: bytes=32 time=184ms TTL=49
Reply from 38.49.39.136: bytes=32 time=184ms TTL=49
Reply from 38.49.39.136: bytes=32 time=184ms TTL=49
Reply from 38.49.39.136: bytes=32 time=184ms TTL=49
Reply from 38.49.39.136: bytes=32 time=184ms TTL=49
Reply from 38.49.39.136: bytes=32 time=184ms TTL=49
Reply from 38.49.39.136: bytes=32 time=184ms TTL=49
Reply from 38.49.39.136: bytes=32 time=184ms TTL=49
Reply from 38.49.39.136: bytes=32 time=184ms 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 = 183ms, Maximum = 184ms, Average = 184ms查看 |
GET PING Trace Dig |
|
| 广东湛江市移动 |
移动 |
广东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
231.2ms |
172.698ms |
183.957ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=174ms TTL=48
Reply from 38.49.39.136: bytes=32 time=186ms TTL=48
Reply from 38.49.39.136: bytes=32 time=192ms TTL=48
Reply from 38.49.39.136: bytes=32 time=231ms TTL=48
Reply from 38.49.39.136: bytes=32 time=173ms TTL=48
Reply from 38.49.39.136: bytes=32 time=175ms TTL=48
Reply from 38.49.39.136: bytes=32 time=182ms TTL=48
Reply from 38.49.39.136: bytes=32 time=175ms TTL=48
Reply from 38.49.39.136: bytes=32 time=179ms TTL=48
Reply from 38.49.39.136: bytes=32 time=173ms TTL=48
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 173ms, Maximum = 231ms, Average = 184ms查看 |
GET PING Trace Dig |
|
| 四川达州市联通 |
联通 |
四川 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
9 |
1 |
186.856ms |
182.687ms |
183.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=184ms TTL=47
Reply from 38.49.39.136: bytes=32 time=183ms TTL=47
Reply from 38.49.39.136: bytes=32 time=183ms TTL=47
Reply from 38.49.39.136: bytes=32 time=183ms TTL=47
Reply from 38.49.39.136: bytes=32 time=184ms TTL=47
Reply from 38.49.39.136: bytes=32 time=183ms TTL=47
Reply from 38.49.39.136: bytes=32 time=186ms TTL=47
Request timed out.
Reply from 38.49.39.136: bytes=32 time=183ms TTL=47
Reply from 38.49.39.136: bytes=32 time=187ms 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 = 183ms, Maximum = 187ms, Average = 184ms查看 |
GET PING Trace Dig |
|
| 广西柳州市电信 |
电信 |
广西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
214.8ms |
177.762ms |
183.832ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=181ms TTL=50
Reply from 38.49.39.136: bytes=32 time=178ms TTL=50
Reply from 38.49.39.136: bytes=32 time=178ms TTL=50
Reply from 38.49.39.136: bytes=32 time=186ms 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=178ms TTL=50
Reply from 38.49.39.136: bytes=32 time=183ms TTL=50
Reply from 38.49.39.136: bytes=32 time=178ms TTL=50
Reply from 38.49.39.136: bytes=32 time=215ms 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 = 215ms, Average = 184ms查看 |
GET PING Trace Dig |
|
| 黑龙江鹤岗市移动 |
移动 |
黑龙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
183.942ms |
182.023ms |
182.571ms |
32B |
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=182ms TTL=48
Reply from 38.49.39.136: bytes=32 time=182ms TTL=48
Reply from 38.49.39.136: bytes=32 time=184ms TTL=48
Reply from 38.49.39.136: bytes=32 time=182ms TTL=48
Reply from 38.49.39.136: bytes=32 time=183ms TTL=48
Reply from 38.49.39.136: bytes=32 time=182ms TTL=48
Reply from 38.49.39.136: bytes=32 time=182ms TTL=48
Reply from 38.49.39.136: bytes=32 time=182ms TTL=48
Reply from 38.49.39.136: bytes=32 time=182ms TTL=48
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 = 184ms, Average = 183ms查看 |
GET PING Trace Dig |
|
| 山东潍坊电信 |
电信 |
山东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
191.399ms |
177.759ms |
182.299ms |
32B |
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=44
Reply from 38.49.39.136: bytes=32 time=185ms TTL=44
Reply from 38.49.39.136: bytes=32 time=180ms TTL=44
Reply from 38.49.39.136: bytes=32 time=183ms TTL=44
Reply from 38.49.39.136: bytes=32 time=178ms TTL=44
Reply from 38.49.39.136: bytes=32 time=182ms TTL=44
Reply from 38.49.39.136: bytes=32 time=181ms TTL=44
Reply from 38.49.39.136: bytes=32 time=181ms TTL=44
Reply from 38.49.39.136: bytes=32 time=184ms TTL=44
Reply from 38.49.39.136: bytes=32 time=191ms 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 = 191ms, Average = 182ms查看 |
GET PING Trace Dig |
|
| 甘肃武威市移动 |
移动 |
甘肃 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
185.9ms |
179.799ms |
182.164ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=182ms TTL=47
Reply from 38.49.39.136: bytes=32 time=182ms TTL=47
Reply from 38.49.39.136: bytes=32 time=182ms TTL=47
Reply from 38.49.39.136: bytes=32 time=182ms TTL=47
Reply from 38.49.39.136: bytes=32 time=183ms TTL=47
Reply from 38.49.39.136: bytes=32 time=180ms TTL=47
Reply from 38.49.39.136: bytes=32 time=181ms TTL=47
Reply from 38.49.39.136: bytes=32 time=180ms TTL=47
Reply from 38.49.39.136: bytes=32 time=186ms 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 = 180ms, Maximum = 186ms, Average = 182ms查看 |
GET PING Trace Dig |
|
| 河北沧州市联通 |
联通 |
河北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
189.81ms |
179.94ms |
182.141ms |
32B |
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=185ms 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=190ms TTL=49
Reply from 38.49.39.136: bytes=32 time=180ms TTL=49
Reply from 38.49.39.136: bytes=32 time=182ms TTL=49
Reply from 38.49.39.136: bytes=32 time=181ms TTL=49
Reply from 38.49.39.136: bytes=32 time=183ms TTL=49
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 180ms, Maximum = 190ms, Average = 182ms查看 |
GET PING Trace Dig |
|
| 广东广州市移动 |
移动 |
广东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
187.762ms |
179.522ms |
181.748ms |
32B |
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=42
Reply from 38.49.39.136: bytes=32 time=181ms TTL=42
Reply from 38.49.39.136: bytes=32 time=182ms TTL=42
Reply from 38.49.39.136: bytes=32 time=181ms TTL=42
Reply from 38.49.39.136: bytes=32 time=188ms TTL=42
Reply from 38.49.39.136: bytes=32 time=181ms TTL=42
Reply from 38.49.39.136: bytes=32 time=183ms TTL=42
Reply from 38.49.39.136: bytes=32 time=180ms TTL=42
Reply from 38.49.39.136: bytes=32 time=180ms TTL=42
Reply from 38.49.39.136: bytes=32 time=180ms TTL=42
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 = 188ms, Average = 182ms查看 |
GET PING Trace Dig |
|
| 山东临沂市联通 |
联通 |
山东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
182.72ms |
179.66ms |
181.156ms |
32B |
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=183ms 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=181ms 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=181ms 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
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 = 181ms查看 |
GET PING Trace Dig |
|
| 河南洛阳市联通 |
联通 |
河南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
181.802ms |
178.542ms |
180.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=182ms TTL=50
Reply from 38.49.39.136: bytes=32 time=182ms TTL=50
Reply from 38.49.39.136: bytes=32 time=179ms TTL=50
Reply from 38.49.39.136: bytes=32 time=181ms 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=180ms TTL=50
Reply from 38.49.39.136: bytes=32 time=179ms TTL=50
Reply from 38.49.39.136: bytes=32 time=181ms 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 = 179ms, Maximum = 182ms, Average = 181ms查看 |
GET PING Trace Dig |
|
| 台湾台湾 |
台湾 |
台湾 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
7 |
3 |
190.827ms |
175.534ms |
180.541ms |
32B |
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=44
Reply from 38.49.39.136: bytes=32 time=176ms TTL=44
Request timed out.
Request timed out.
Reply from 38.49.39.136: bytes=32 time=181ms TTL=44
Reply from 38.49.39.136: bytes=32 time=179ms TTL=44
Reply from 38.49.39.136: bytes=32 time=186ms TTL=44
Reply from 38.49.39.136: bytes=32 time=176ms TTL=44
Request timed out.
Reply from 38.49.39.136: bytes=32 time=176ms TTL=44
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 7, Lost = 3 (30% loss),
Approximate round trip times in milli-seconds:
Minimum = 176ms, Maximum = 191ms, Average = 181ms查看 |
GET PING Trace Dig |
|
| 云南保山市电信 |
电信 |
云南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
180.98ms |
179.479ms |
180.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=181ms TTL=48
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=180ms TTL=48
Reply from 38.49.39.136: bytes=32 time=180ms 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=180ms 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
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 |
198.783ms |
173.663ms |
179.808ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=199ms TTL=48
Reply from 38.49.39.136: bytes=32 time=180ms TTL=48
Reply from 38.49.39.136: bytes=32 time=177ms TTL=48
Reply from 38.49.39.136: bytes=32 time=176ms TTL=48
Reply from 38.49.39.136: bytes=32 time=184ms TTL=48
Reply from 38.49.39.136: bytes=32 time=176ms TTL=48
Reply from 38.49.39.136: bytes=32 time=183ms 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
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 = 199ms, Average = 180ms查看 |
GET PING Trace Dig |
|
| 山西长治市联通 |
联通 |
山西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
184.584ms |
177.086ms |
179.738ms |
32B |
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=51
Reply from 38.49.39.136: bytes=32 time=177ms 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=178ms TTL=51
Reply from 38.49.39.136: bytes=32 time=178ms TTL=51
Reply from 38.49.39.136: bytes=32 time=178ms TTL=51
Reply from 38.49.39.136: bytes=32 time=180ms TTL=51
Reply from 38.49.39.136: bytes=32 time=181ms TTL=51
Reply from 38.49.39.136: bytes=32 time=185ms TTL=51
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 177ms, Maximum = 185ms, Average = 180ms查看 |
GET PING Trace Dig |
|
| 甘肃武威市移动 |
移动 |
甘肃 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
180.502ms |
179.142ms |
179.701ms |
32B |
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=181ms TTL=48
Reply from 38.49.39.136: bytes=32 time=180ms TTL=48
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=179ms TTL=48
Reply from 38.49.39.136: bytes=32 time=179ms TTL=48
Reply from 38.49.39.136: bytes=32 time=180ms TTL=48
Reply from 38.49.39.136: bytes=32 time=180ms 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 = 179ms, Maximum = 181ms, Average = 180ms查看 |
GET PING Trace Dig |
|
| 陕西榆林市移动 |
移动 |
陕西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
179.961ms |
179.36ms |
179.651ms |
32B |
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=180ms 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
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=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
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 179ms, Maximum = 180ms, Average = 180ms查看 |
GET PING Trace Dig |
|
| 广西北海市联通 |
联通 |
广西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
179.814ms |
179.077ms |
179.499ms |
32B |
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=51
Reply from 38.49.39.136: bytes=32 time=180ms TTL=51
Reply from 38.49.39.136: bytes=32 time=179ms TTL=51
Reply from 38.49.39.136: bytes=32 time=180ms TTL=51
Reply from 38.49.39.136: bytes=32 time=179ms 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=179ms TTL=51
Reply from 38.49.39.136: bytes=32 time=180ms TTL=51
Reply from 38.49.39.136: bytes=32 time=180ms TTL=51
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 179ms, Maximum = 180ms, Average = 179ms查看 |
GET PING Trace Dig |
|
| 河北唐山市联通 |
联通 |
河北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
184.137ms |
177.729ms |
179.335ms |
32B |
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=178ms TTL=49
Reply from 38.49.39.136: bytes=32 time=178ms 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=182ms TTL=49
Reply from 38.49.39.136: bytes=32 time=178ms TTL=49
Reply from 38.49.39.136: bytes=32 time=184ms 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 = 178ms, Maximum = 184ms, Average = 179ms查看 |
GET PING Trace Dig |
|
| 海南三亚市移动 |
移动 |
海南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
181.825ms |
178.077ms |
179.178ms |
32B |
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=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=180ms TTL=48
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=182ms TTL=48
Reply from 38.49.39.136: bytes=32 time=179ms TTL=48
Reply from 38.49.39.136: bytes=32 time=179ms TTL=48
Reply from 38.49.39.136: bytes=32 time=178ms TTL=48
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 = 182ms, Average = 179ms查看 |
GET PING Trace Dig |
|
| 黑龙江齐齐哈尔市移动 |
移动 |
黑龙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
180.94ms |
178.44ms |
178.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=179ms TTL=50
Reply from 38.49.39.136: bytes=32 time=181ms TTL=50
Reply from 38.49.39.136: bytes=32 time=179ms TTL=50
Reply from 38.49.39.136: bytes=32 time=178ms TTL=50
Reply from 38.49.39.136: bytes=32 time=179ms TTL=50
Reply from 38.49.39.136: bytes=32 time=179ms TTL=50
Reply from 38.49.39.136: bytes=32 time=179ms TTL=50
Reply from 38.49.39.136: bytes=32 time=179ms TTL=50
Reply from 38.49.39.136: bytes=32 time=179ms TTL=50
Reply from 38.49.39.136: bytes=32 time=179ms TTL=50
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 178ms, Maximum = 181ms, Average = 179ms查看 |
GET PING Trace Dig |
|
| 四川自贡市电信 |
电信 |
四川 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
188.668ms |
174.72ms |
178.336ms |
32B |
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=52
Reply from 38.49.39.136: bytes=32 time=187ms TTL=52
Reply from 38.49.39.136: bytes=32 time=176ms TTL=52
Reply from 38.49.39.136: bytes=32 time=175ms TTL=52
Reply from 38.49.39.136: bytes=32 time=175ms TTL=52
Reply from 38.49.39.136: bytes=32 time=177ms TTL=52
Reply from 38.49.39.136: bytes=32 time=178ms TTL=52
Reply from 38.49.39.136: bytes=32 time=189ms TTL=52
Reply from 38.49.39.136: bytes=32 time=175ms TTL=52
Reply from 38.49.39.136: bytes=32 time=175ms TTL=52
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 = 189ms, Average = 178ms查看 |
GET PING Trace Dig |
|
| 贵州遵义市移动 |
移动 |
贵州 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
189.258ms |
170.439ms |
177.922ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=173ms TTL=49
Reply from 38.49.39.136: bytes=32 time=187ms TTL=49
Reply from 38.49.39.136: bytes=32 time=170ms 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=182ms TTL=49
Reply from 38.49.39.136: bytes=32 time=173ms TTL=49
Reply from 38.49.39.136: bytes=32 time=183ms TTL=49
Reply from 38.49.39.136: bytes=32 time=172ms TTL=49
Reply from 38.49.39.136: bytes=32 time=189ms 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 = 170ms, Maximum = 189ms, Average = 178ms查看 |
GET PING Trace Dig |
|
| 江西南昌市联通 |
联通 |
江西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
178.021ms |
176.962ms |
177.834ms |
32B |
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=51
Reply from 38.49.39.136: bytes=32 time=178ms TTL=51
Reply from 38.49.39.136: bytes=32 time=178ms TTL=51
Reply from 38.49.39.136: bytes=32 time=178ms TTL=51
Reply from 38.49.39.136: bytes=32 time=178ms TTL=51
Reply from 38.49.39.136: bytes=32 time=177ms TTL=51
Reply from 38.49.39.136: bytes=32 time=178ms TTL=51
Reply from 38.49.39.136: bytes=32 time=178ms TTL=51
Reply from 38.49.39.136: bytes=32 time=178ms TTL=51
Reply from 38.49.39.136: bytes=32 time=178ms TTL=51
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 177ms, Maximum = 178ms, Average = 178ms查看 |
GET PING Trace Dig |
|
| 河北衡水市移动 |
移动 |
河北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
9 |
1 |
180.359ms |
176.159ms |
177.304ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=180ms TTL=49
Request timed out.
Reply from 38.49.39.136: bytes=32 time=177ms TTL=49
Reply from 38.49.39.136: bytes=32 time=177ms TTL=49
Reply from 38.49.39.136: bytes=32 time=177ms TTL=49
Reply from 38.49.39.136: bytes=32 time=176ms TTL=49
Reply from 38.49.39.136: bytes=32 time=177ms TTL=49
Reply from 38.49.39.136: bytes=32 time=176ms TTL=49
Reply from 38.49.39.136: bytes=32 time=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 = 9, Lost = 1 (10% 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 |
177.493ms |
176.143ms |
176.809ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=177ms TTL=51
Reply from 38.49.39.136: bytes=32 time=176ms TTL=51
Reply from 38.49.39.136: bytes=32 time=177ms TTL=51
Reply from 38.49.39.136: bytes=32 time=177ms TTL=51
Reply from 38.49.39.136: bytes=32 time=177ms TTL=51
Reply from 38.49.39.136: bytes=32 time=177ms TTL=51
Reply from 38.49.39.136: bytes=32 time=176ms TTL=51
Reply from 38.49.39.136: bytes=32 time=176ms 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
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 = 177ms, Average = 177ms查看 |
GET PING Trace Dig |
|
| 甘肃兰州市电信 |
电信 |
甘肃 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
176.374ms |
175.976ms |
176.199ms |
32B |
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=46
Reply from 38.49.39.136: bytes=32 time=176ms TTL=46
Reply from 38.49.39.136: bytes=32 time=176ms TTL=46
Reply from 38.49.39.136: bytes=32 time=176ms TTL=46
Reply from 38.49.39.136: bytes=32 time=176ms TTL=46
Reply from 38.49.39.136: bytes=32 time=176ms TTL=46
Reply from 38.49.39.136: bytes=32 time=176ms TTL=46
Reply from 38.49.39.136: bytes=32 time=176ms TTL=46
Reply from 38.49.39.136: bytes=32 time=176ms TTL=46
Reply from 38.49.39.136: bytes=32 time=176ms 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 = 176ms, Maximum = 176ms, Average = 176ms查看 |
GET PING Trace Dig |
|
| 甘肃陇南市电信 |
电信 |
甘肃 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
179.646ms |
173.963ms |
176.001ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=175ms TTL=50
Reply from 38.49.39.136: bytes=32 time=177ms 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=175ms TTL=50
Reply from 38.49.39.136: bytes=32 time=175ms TTL=50
Reply from 38.49.39.136: bytes=32 time=179ms 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=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 = 174ms, Maximum = 180ms, Average = 176ms查看 |
GET PING Trace Dig |
|
| 天津联通 |
联通 |
天津 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
177.67ms |
174.28ms |
175.505ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=174ms TTL=49
Reply from 38.49.39.136: bytes=32 time=175ms TTL=49
Reply from 38.49.39.136: bytes=32 time=178ms 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=174ms 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 = 174ms, Maximum = 178ms, Average = 176ms查看 |
GET PING Trace Dig |
|
| 陕西汉中市移动 |
移动 |
陕西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
177.973ms |
173.159ms |
174.203ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=174ms TTL=48
Reply from 38.49.39.136: bytes=32 time=177ms TTL=48
Reply from 38.49.39.136: bytes=32 time=178ms 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=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
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 = 178ms, Average = 174ms查看 |
GET PING Trace Dig |
|
| 重庆重庆市移动 |
移动 |
重庆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
175.354ms |
172.953ms |
173.945ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=174ms TTL=52
Reply from 38.49.39.136: bytes=32 time=174ms TTL=52
Reply from 38.49.39.136: bytes=32 time=174ms TTL=52
Reply from 38.49.39.136: bytes=32 time=174ms TTL=52
Reply from 38.49.39.136: bytes=32 time=175ms TTL=52
Reply from 38.49.39.136: bytes=32 time=174ms TTL=52
Reply from 38.49.39.136: bytes=32 time=173ms TTL=52
Reply from 38.49.39.136: bytes=32 time=174ms TTL=52
Reply from 38.49.39.136: bytes=32 time=173ms TTL=52
Reply from 38.49.39.136: bytes=32 time=174ms TTL=52
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 173ms, Maximum = 175ms, Average = 174ms查看 |
GET PING Trace Dig |
|
| 辽宁葫芦岛市移动 |
移动 |
辽宁 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
175.74ms |
172.261ms |
173.574ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=173ms TTL=50
Reply from 38.49.39.136: bytes=32 time=173ms 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=172ms TTL=50
Reply from 38.49.39.136: bytes=32 time=174ms TTL=50
Reply from 38.49.39.136: bytes=32 time=173ms TTL=50
Reply from 38.49.39.136: bytes=32 time=175ms TTL=50
Reply from 38.49.39.136: bytes=32 time=173ms TTL=50
Reply from 38.49.39.136: bytes=32 time=173ms TTL=50
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 = 176ms, Average = 174ms查看 |
GET PING Trace Dig |
|
| 重庆重庆市联通 |
联通 |
重庆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
173.39ms |
173.094ms |
173.189ms |
32B |
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=49
Reply from 38.49.39.136: bytes=32 time=173ms TTL=49
Reply from 38.49.39.136: bytes=32 time=173ms TTL=49
Reply from 38.49.39.136: bytes=32 time=173ms TTL=49
Reply from 38.49.39.136: bytes=32 time=173ms TTL=49
Reply from 38.49.39.136: bytes=32 time=173ms TTL=49
Reply from 38.49.39.136: bytes=32 time=173ms TTL=49
Reply from 38.49.39.136: bytes=32 time=173ms TTL=49
Reply from 38.49.39.136: bytes=32 time=173ms TTL=49
Reply from 38.49.39.136: bytes=32 time=173ms TTL=49
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 173ms, Maximum = 173ms, Average = 173ms查看 |
GET PING Trace Dig |
|
| 海南陵水黎族自治县移动 |
移动 |
海南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
173.581ms |
172.701ms |
173.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=173ms TTL=50
Reply from 38.49.39.136: bytes=32 time=173ms TTL=50
Reply from 38.49.39.136: bytes=32 time=173ms TTL=50
Reply from 38.49.39.136: bytes=32 time=173ms TTL=50
Reply from 38.49.39.136: bytes=32 time=173ms TTL=50
Reply from 38.49.39.136: bytes=32 time=174ms TTL=50
Reply from 38.49.39.136: bytes=32 time=174ms TTL=50
Reply from 38.49.39.136: bytes=32 time=173ms TTL=50
Reply from 38.49.39.136: bytes=32 time=173ms TTL=50
Reply from 38.49.39.136: bytes=32 time=173ms TTL=50
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 |
177.258ms |
171.086ms |
172.884ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=171ms TTL=51
Reply from 38.49.39.136: bytes=32 time=172ms TTL=51
Reply from 38.49.39.136: bytes=32 time=171ms TTL=51
Reply from 38.49.39.136: bytes=32 time=171ms TTL=51
Reply from 38.49.39.136: bytes=32 time=173ms 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=177ms TTL=51
Reply from 38.49.39.136: bytes=32 time=171ms TTL=51
Reply from 38.49.39.136: bytes=32 time=177ms TTL=51
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 171ms, Maximum = 177ms, Average = 173ms查看 |
GET PING Trace Dig |
|
| 内蒙古呼和浩特联通 |
联通 |
内蒙古 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
177.69ms |
168.976ms |
172.813ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=174ms TTL=52
Reply from 38.49.39.136: bytes=32 time=170ms TTL=52
Reply from 38.49.39.136: bytes=32 time=169ms TTL=52
Reply from 38.49.39.136: bytes=32 time=174ms TTL=52
Reply from 38.49.39.136: bytes=32 time=172ms 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=176ms TTL=52
Reply from 38.49.39.136: bytes=32 time=178ms TTL=52
Reply from 38.49.39.136: bytes=32 time=170ms TTL=52
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 169ms, Maximum = 178ms, Average = 173ms查看 |
GET PING Trace Dig |
|
| 宁夏银川市移动 |
移动 |
宁夏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
176.28ms |
171.64ms |
172.68ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=172ms TTL=48
Reply from 38.49.39.136: bytes=32 time=172ms TTL=48
Reply from 38.49.39.136: bytes=32 time=176ms TTL=48
Reply from 38.49.39.136: bytes=32 time=172ms TTL=48
Reply from 38.49.39.136: bytes=32 time=172ms TTL=48
Reply from 38.49.39.136: bytes=32 time=173ms TTL=48
Reply from 38.49.39.136: bytes=32 time=173ms TTL=48
Reply from 38.49.39.136: bytes=32 time=172ms TTL=48
Reply from 38.49.39.136: bytes=32 time=172ms TTL=48
Reply from 38.49.39.136: bytes=32 time=173ms TTL=48
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 = 176ms, Average = 173ms查看 |
GET PING Trace Dig |
|
| 贵州铜仁市电信 |
电信 |
贵州 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
173.339ms |
172.236ms |
172.608ms |
32B |
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=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=172ms TTL=49
Reply from 38.49.39.136: bytes=32 time=172ms TTL=49
Reply from 38.49.39.136: bytes=32 time=172ms 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 = 172ms, Maximum = 173ms, Average = 173ms查看 |
GET PING Trace Dig |
|
| 广西南宁市其他 |
其他 |
广西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
177.741ms |
170.241ms |
172.461ms |
32B |
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=172ms TTL=52
Reply from 38.49.39.136: bytes=32 time=172ms TTL=52
Reply from 38.49.39.136: bytes=32 time=178ms TTL=52
Reply from 38.49.39.136: bytes=32 time=175ms TTL=52
Reply from 38.49.39.136: bytes=32 time=172ms TTL=52
Reply from 38.49.39.136: bytes=32 time=170ms TTL=52
Reply from 38.49.39.136: bytes=32 time=171ms TTL=52
Reply from 38.49.39.136: bytes=32 time=171ms 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 = 178ms, Average = 172ms查看 |
GET PING Trace Dig |
|
| 湖南衡阳市联通 |
联通 |
湖南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
179.123ms |
169.042ms |
172.106ms |
32B |
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=179ms 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=174ms 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=179ms TTL=50
Reply from 38.49.39.136: bytes=32 time=169ms TTL=50
Reply from 38.49.39.136: bytes=32 time=169ms TTL=50
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 169ms, Maximum = 179ms, Average = 172ms查看 |
GET PING Trace Dig |
|
| 天津天津市联通 |
联通 |
天津 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
172.161ms |
171.921ms |
172.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=172ms TTL=50
Reply from 38.49.39.136: bytes=32 time=172ms TTL=50
Reply from 38.49.39.136: bytes=32 time=172ms TTL=50
Reply from 38.49.39.136: bytes=32 time=172ms TTL=50
Reply from 38.49.39.136: bytes=32 time=172ms TTL=50
Reply from 38.49.39.136: bytes=32 time=172ms TTL=50
Reply from 38.49.39.136: bytes=32 time=172ms TTL=50
Reply from 38.49.39.136: bytes=32 time=172ms TTL=50
Reply from 38.49.39.136: bytes=32 time=172ms TTL=50
Reply from 38.49.39.136: bytes=32 time=172ms 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 = 172ms, Maximum = 172ms, Average = 172ms查看 |
GET PING Trace Dig |
|
| 新疆喀什地区电信 |
电信 |
新疆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
171.881ms |
171.382ms |
171.636ms |
32B |
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=49
Reply from 38.49.39.136: bytes=32 time=172ms TTL=49
Reply from 38.49.39.136: bytes=32 time=172ms TTL=49
Reply from 38.49.39.136: bytes=32 time=172ms TTL=49
Reply from 38.49.39.136: bytes=32 time=172ms TTL=49
Reply from 38.49.39.136: bytes=32 time=172ms TTL=49
Reply from 38.49.39.136: bytes=32 time=171ms TTL=49
Reply from 38.49.39.136: bytes=32 time=172ms TTL=49
Reply from 38.49.39.136: bytes=32 time=172ms TTL=49
Reply from 38.49.39.136: bytes=32 time=172ms TTL=49
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 171ms, Maximum = 172ms, Average = 172ms查看 |
GET PING Trace Dig |
|
| 贵州毕节市联通 |
联通 |
贵州 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
171.551ms |
171.066ms |
171.335ms |
32B |
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=172ms TTL=50
Reply from 38.49.39.136: bytes=32 time=171ms TTL=50
Reply from 38.49.39.136: bytes=32 time=172ms TTL=50
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 171ms, Maximum = 172ms, Average = 171ms查看 |
GET PING Trace Dig |
|
| 天津天津市电信 |
电信 |
天津 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
187.34ms |
160.357ms |
171.142ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=160ms TTL=48
Reply from 38.49.39.136: bytes=32 time=187ms TTL=48
Reply from 38.49.39.136: bytes=32 time=162ms TTL=48
Reply from 38.49.39.136: bytes=32 time=187ms TTL=48
Reply from 38.49.39.136: bytes=32 time=177ms TTL=48
Reply from 38.49.39.136: bytes=32 time=165ms TTL=48
Reply from 38.49.39.136: bytes=32 time=175ms TTL=48
Reply from 38.49.39.136: bytes=32 time=166ms TTL=48
Reply from 38.49.39.136: bytes=32 time=167ms 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 = 160ms, Maximum = 187ms, Average = 171ms查看 |
GET PING Trace Dig |
|
| 陕西商洛市电信 |
电信 |
陕西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
257.917ms |
153.993ms |
170.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=156ms TTL=50
Reply from 38.49.39.136: bytes=32 time=154ms TTL=50
Reply from 38.49.39.136: bytes=32 time=155ms 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=202ms TTL=50
Reply from 38.49.39.136: bytes=32 time=258ms TTL=50
Reply from 38.49.39.136: bytes=32 time=157ms 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
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 = 258ms, Average = 171ms查看 |
GET PING Trace Dig |
|
| 湖南怀化市电信 |
电信 |
湖南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
174.721ms |
169.081ms |
170.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=170ms TTL=50
Reply from 38.49.39.136: bytes=32 time=172ms TTL=50
Reply from 38.49.39.136: bytes=32 time=171ms TTL=50
Reply from 38.49.39.136: bytes=32 time=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=169ms TTL=50
Reply from 38.49.39.136: bytes=32 time=171ms 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 = 169ms, Maximum = 175ms, Average = 171ms查看 |
GET PING Trace Dig |
|
| 青海西宁市电信 |
电信 |
青海 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
175.582ms |
166.743ms |
170.315ms |
32B |
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=47
Reply from 38.49.39.136: bytes=32 time=167ms TTL=47
Reply from 38.49.39.136: bytes=32 time=167ms TTL=47
Reply from 38.49.39.136: bytes=32 time=167ms TTL=47
Reply from 38.49.39.136: bytes=32 time=167ms TTL=47
Reply from 38.49.39.136: bytes=32 time=167ms TTL=47
Reply from 38.49.39.136: bytes=32 time=176ms TTL=47
Reply from 38.49.39.136: bytes=32 time=175ms TTL=47
Reply from 38.49.39.136: bytes=32 time=175ms TTL=47
Reply from 38.49.39.136: bytes=32 time=175ms TTL=47
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 167ms, Maximum = 176ms, Average = 170ms查看 |
GET PING Trace Dig |
|
| 吉林长春电信 |
电信 |
吉林 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
172.541ms |
169.261ms |
169.944ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=170ms TTL=51
Reply from 38.49.39.136: bytes=32 time=169ms TTL=51
Reply from 38.49.39.136: bytes=32 time=173ms TTL=51
Reply from 38.49.39.136: bytes=32 time=170ms TTL=51
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=169ms TTL=51
Reply from 38.49.39.136: bytes=32 time=169ms TTL=51
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 169ms, Maximum = 173ms, Average = 170ms查看 |
GET PING Trace Dig |
|
| 吉林长春电信 |
电信 |
吉林 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
176.713ms |
165.681ms |
169.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=166ms TTL=50
Reply from 38.49.39.136: bytes=32 time=172ms TTL=50
Reply from 38.49.39.136: bytes=32 time=170ms TTL=50
Reply from 38.49.39.136: bytes=32 time=173ms TTL=50
Reply from 38.49.39.136: bytes=32 time=167ms TTL=50
Reply from 38.49.39.136: bytes=32 time=172ms TTL=50
Reply from 38.49.39.136: bytes=32 time=177ms 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=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 = 177ms, Average = 170ms查看 |
GET PING Trace Dig |
|
| 宁夏银川市电信 |
电信 |
宁夏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
169.639ms |
169.16ms |
169.359ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=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=169ms TTL=51
Reply from 38.49.39.136: bytes=32 time=169ms TTL=51
Reply from 38.49.39.136: bytes=32 time=169ms TTL=51
Reply from 38.49.39.136: bytes=32 time=169ms TTL=51
Reply from 38.49.39.136: bytes=32 time=169ms TTL=51
Reply from 38.49.39.136: bytes=32 time=169ms TTL=51
Reply from 38.49.39.136: bytes=32 time=169ms TTL=51
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 169ms, Maximum = 170ms, Average = 169ms查看 |
GET PING Trace Dig |
|
| 四川泸州市移动 |
移动 |
四川 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
9 |
1 |
169.317ms |
168.906ms |
169.159ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=169ms TTL=49
Reply from 38.49.39.136: bytes=32 time=169ms TTL=49
Reply from 38.49.39.136: bytes=32 time=169ms TTL=49
Reply from 38.49.39.136: bytes=32 time=169ms TTL=49
Reply from 38.49.39.136: bytes=32 time=169ms TTL=49
Reply from 38.49.39.136: bytes=32 time=169ms TTL=49
Reply from 38.49.39.136: bytes=32 time=169ms TTL=49
Reply from 38.49.39.136: bytes=32 time=169ms TTL=49
Reply from 38.49.39.136: bytes=32 time=169ms TTL=49
Request timed out.
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 9, Lost = 1 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 169ms, Maximum = 169ms, Average = 169ms查看 |
GET PING Trace Dig |
|
| 四川成都市联通 |
联通 |
四川 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
169.18ms |
168.499ms |
168.955ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=169ms TTL=50
Reply from 38.49.39.136: bytes=32 time=169ms TTL=50
Reply from 38.49.39.136: bytes=32 time=169ms TTL=50
Reply from 38.49.39.136: bytes=32 time=169ms TTL=50
Reply from 38.49.39.136: bytes=32 time=169ms TTL=50
Reply from 38.49.39.136: bytes=32 time=169ms TTL=50
Reply from 38.49.39.136: bytes=32 time=168ms TTL=50
Reply from 38.49.39.136: bytes=32 time=169ms TTL=50
Reply from 38.49.39.136: bytes=32 time=169ms TTL=50
Reply from 38.49.39.136: bytes=32 time=169ms TTL=50
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 168ms, Maximum = 169ms, Average = 169ms查看 |
GET PING Trace Dig |
|
| 宁夏银川市移动 |
移动 |
宁夏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
168.576ms |
168.353ms |
168.48ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=169ms TTL=49
Reply from 38.49.39.136: bytes=32 time=169ms TTL=49
Reply from 38.49.39.136: bytes=32 time=168ms TTL=49
Reply from 38.49.39.136: bytes=32 time=169ms TTL=49
Reply from 38.49.39.136: bytes=32 time=168ms TTL=49
Reply from 38.49.39.136: bytes=32 time=169ms TTL=49
Reply from 38.49.39.136: bytes=32 time=168ms TTL=49
Reply from 38.49.39.136: bytes=32 time=168ms TTL=49
Reply from 38.49.39.136: bytes=32 time=169ms TTL=49
Reply from 38.49.39.136: bytes=32 time=168ms TTL=49
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 168ms, Maximum = 169ms, Average = 168ms查看 |
GET PING Trace Dig |
|
| 陕西渭南市联通 |
联通 |
陕西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
168.334ms |
168.169ms |
168.254ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=168ms TTL=51
Reply from 38.49.39.136: bytes=32 time=168ms TTL=51
Reply from 38.49.39.136: bytes=32 time=168ms TTL=51
Reply from 38.49.39.136: bytes=32 time=168ms TTL=51
Reply from 38.49.39.136: bytes=32 time=168ms TTL=51
Reply from 38.49.39.136: bytes=32 time=168ms TTL=51
Reply from 38.49.39.136: bytes=32 time=168ms TTL=51
Reply from 38.49.39.136: bytes=32 time=168ms TTL=51
Reply from 38.49.39.136: bytes=32 time=168ms TTL=51
Reply from 38.49.39.136: bytes=32 time=168ms TTL=51
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 = 168ms, Average = 168ms查看 |
GET PING Trace Dig |
|
| 福建莆田市联通 |
联通 |
福建 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
168.121ms |
167.481ms |
167.777ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=168ms TTL=51
Reply from 38.49.39.136: bytes=32 time=168ms TTL=51
Reply from 38.49.39.136: bytes=32 time=168ms TTL=51
Reply from 38.49.39.136: bytes=32 time=168ms TTL=51
Reply from 38.49.39.136: bytes=32 time=167ms TTL=51
Reply from 38.49.39.136: bytes=32 time=168ms TTL=51
Reply from 38.49.39.136: bytes=32 time=168ms TTL=51
Reply from 38.49.39.136: bytes=32 time=168ms TTL=51
Reply from 38.49.39.136: bytes=32 time=168ms TTL=51
Reply from 38.49.39.136: bytes=32 time=168ms TTL=51
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 167ms, Maximum = 168ms, Average = 168ms查看 |
GET PING Trace Dig |
|
| 辽宁抚顺市电信 |
电信 |
辽宁 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
167.701ms |
167.561ms |
167.605ms |
32B |
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=50
Reply from 38.49.39.136: bytes=32 time=168ms TTL=50
Reply from 38.49.39.136: bytes=32 time=168ms TTL=50
Reply from 38.49.39.136: bytes=32 time=168ms TTL=50
Reply from 38.49.39.136: bytes=32 time=168ms TTL=50
Reply from 38.49.39.136: bytes=32 time=168ms TTL=50
Reply from 38.49.39.136: bytes=32 time=168ms TTL=50
Reply from 38.49.39.136: bytes=32 time=168ms TTL=50
Reply from 38.49.39.136: bytes=32 time=168ms TTL=50
Reply from 38.49.39.136: bytes=32 time=168ms TTL=50
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 168ms, Maximum = 168ms, Average = 168ms查看 |
GET PING Trace Dig |
|
| 浙江衢州市联通 |
联通 |
浙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
172.32ms |
164.977ms |
167.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=167ms TTL=49
Reply from 38.49.39.136: bytes=32 time=169ms TTL=49
Reply from 38.49.39.136: bytes=32 time=166ms TTL=49
Reply from 38.49.39.136: bytes=32 time=172ms TTL=49
Reply from 38.49.39.136: bytes=32 time=168ms TTL=49
Reply from 38.49.39.136: bytes=32 time=166ms 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=165ms TTL=49
Reply from 38.49.39.136: bytes=32 time=166ms TTL=49
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 165ms, Maximum = 172ms, Average = 168ms查看 |
GET PING Trace Dig |
|
| 内蒙古呼和浩特市电信 |
电信 |
内蒙古 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
182.202ms |
163.211ms |
167.529ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=164ms TTL=50
Reply from 38.49.39.136: bytes=32 time=163ms TTL=50
Reply from 38.49.39.136: bytes=32 time=165ms TTL=50
Reply from 38.49.39.136: bytes=32 time=173ms TTL=50
Reply from 38.49.39.136: bytes=32 time=165ms TTL=50
Reply from 38.49.39.136: bytes=32 time=169ms TTL=50
Reply from 38.49.39.136: bytes=32 time=164ms TTL=50
Reply from 38.49.39.136: bytes=32 time=163ms TTL=50
Reply from 38.49.39.136: bytes=32 time=182ms 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 = 163ms, Maximum = 182ms, Average = 168ms查看 |
GET PING Trace Dig |
|
| 山西忻州市移动 |
移动 |
山西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
168.941ms |
164.46ms |
167.28ms |
32B |
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=48
Reply from 38.49.39.136: bytes=32 time=168ms 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=167ms TTL=48
Reply from 38.49.39.136: bytes=32 time=168ms TTL=48
Reply from 38.49.39.136: bytes=32 time=169ms TTL=48
Reply from 38.49.39.136: bytes=32 time=168ms TTL=48
Reply from 38.49.39.136: bytes=32 time=168ms TTL=48
Reply from 38.49.39.136: bytes=32 time=164ms 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 = 164ms, Maximum = 169ms, Average = 167ms查看 |
GET PING Trace Dig |
|
| 山西朔州市电信 |
电信 |
山西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
169.741ms |
165.037ms |
166.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=166ms TTL=51
Reply from 38.49.39.136: bytes=32 time=165ms TTL=51
Reply from 38.49.39.136: bytes=32 time=165ms TTL=51
Reply from 38.49.39.136: bytes=32 time=167ms TTL=51
Reply from 38.49.39.136: bytes=32 time=166ms TTL=51
Reply from 38.49.39.136: bytes=32 time=170ms TTL=51
Reply from 38.49.39.136: bytes=32 time=167ms TTL=51
Reply from 38.49.39.136: bytes=32 time=165ms TTL=51
Reply from 38.49.39.136: bytes=32 time=165ms TTL=51
Reply from 38.49.39.136: bytes=32 time=165ms TTL=51
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 165ms, Maximum = 170ms, Average = 166ms查看 |
GET PING Trace Dig |
|
| 上海上海市联通 |
联通 |
上海 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
169.632ms |
164.62ms |
166.062ms |
32B |
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=167ms TTL=51
Reply from 38.49.39.136: bytes=32 time=167ms TTL=51
Reply from 38.49.39.136: bytes=32 time=166ms TTL=51
Reply from 38.49.39.136: bytes=32 time=165ms TTL=51
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=165ms TTL=51
Reply from 38.49.39.136: bytes=32 time=170ms TTL=51
Reply from 38.49.39.136: bytes=32 time=165ms TTL=51
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 = 170ms, Average = 166ms查看 |
GET PING Trace Dig |
|
| 湖南长沙移动 |
移动 |
湖南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
206.979ms |
150.772ms |
166.024ms |
32B |
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=49
Reply from 38.49.39.136: bytes=32 time=152ms 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
Reply from 38.49.39.136: bytes=32 time=199ms TTL=49
Reply from 38.49.39.136: bytes=32 time=207ms 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=164ms 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 = 151ms, Maximum = 207ms, Average = 166ms查看 |
GET PING Trace Dig |
|
| 贵州安顺市联通 |
联通 |
贵州 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
167.416ms |
165.376ms |
165.907ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=166ms TTL=49
Reply from 38.49.39.136: bytes=32 time=166ms TTL=49
Reply from 38.49.39.136: bytes=32 time=165ms TTL=49
Reply from 38.49.39.136: bytes=32 time=167ms TTL=49
Reply from 38.49.39.136: bytes=32 time=166ms TTL=49
Reply from 38.49.39.136: bytes=32 time=166ms TTL=49
Reply from 38.49.39.136: bytes=32 time=166ms TTL=49
Reply from 38.49.39.136: bytes=32 time=166ms TTL=49
Reply from 38.49.39.136: bytes=32 time=166ms TTL=49
Reply from 38.49.39.136: bytes=32 time=165ms TTL=49
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 165ms, Maximum = 167ms, Average = 166ms查看 |
GET PING Trace Dig |
|
| 福建厦门市移动 |
移动 |
福建 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
8 |
2 |
170.609ms |
0ms |
165.768ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Request timed out.
Reply from 38.49.39.136: bytes=32 time=166ms TTL=47
Reply from 38.49.39.136: bytes=32 time=162ms TTL=47
Reply from 38.49.39.136: bytes=32 time=166ms TTL=47
Reply from 38.49.39.136: bytes=32 time=165ms TTL=47
Reply from 38.49.39.136: bytes=32 time=171ms TTL=47
Reply from 38.49.39.136: bytes=32 time=171ms TTL=47
Request timed out.
Reply from 38.49.39.136: bytes=32 time=163ms TTL=47
Reply from 38.49.39.136: bytes=32 time=163ms TTL=47
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 8, Lost = 2 (20% loss),
Approximate round trip times in milli-seconds:
Minimum <1ms , Maximum = 171ms, Average = 166ms查看 |
GET PING Trace Dig |
|
| 山西晋城市移动 |
移动 |
山西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
167.427ms |
162.495ms |
165.763ms |
32B |
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=47
Reply from 38.49.39.136: bytes=32 time=162ms 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=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=166ms TTL=47
Reply from 38.49.39.136: bytes=32 time=165ms 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 = 162ms, Maximum = 167ms, Average = 166ms查看 |
GET PING Trace Dig |
|
| 陕西安康市电信 |
电信 |
陕西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
165.962ms |
165.222ms |
165.448ms |
32B |
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=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=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=165ms 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
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 |
166.861ms |
163.741ms |
165.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=166ms TTL=46
Reply from 38.49.39.136: bytes=32 time=166ms TTL=46
Reply from 38.49.39.136: bytes=32 time=167ms TTL=46
Reply from 38.49.39.136: bytes=32 time=166ms TTL=46
Reply from 38.49.39.136: bytes=32 time=164ms TTL=46
Reply from 38.49.39.136: bytes=32 time=167ms TTL=46
Reply from 38.49.39.136: bytes=32 time=164ms TTL=46
Reply from 38.49.39.136: bytes=32 time=165ms TTL=46
Reply from 38.49.39.136: bytes=32 time=164ms TTL=46
Reply from 38.49.39.136: bytes=32 time=164ms TTL=46
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 = 167ms, Average = 165ms查看 |
GET PING Trace Dig |
|
| 江西赣州市联通 |
联通 |
江西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
167.421ms |
163.886ms |
165.251ms |
32B |
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=167ms 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=165ms TTL=41
Reply from 38.49.39.136: bytes=32 time=164ms TTL=41
Reply from 38.49.39.136: bytes=32 time=167ms TTL=41
Reply from 38.49.39.136: bytes=32 time=164ms 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 = 164ms, Maximum = 167ms, Average = 165ms查看 |
GET PING Trace Dig |
|
| 山东日照市电信 |
电信 |
山东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
168.168ms |
164.531ms |
165.036ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=165ms TTL=49
Reply from 38.49.39.136: bytes=32 time=165ms TTL=49
Reply from 38.49.39.136: bytes=32 time=165ms TTL=49
Reply from 38.49.39.136: bytes=32 time=165ms TTL=49
Reply from 38.49.39.136: bytes=32 time=165ms TTL=49
Reply from 38.49.39.136: bytes=32 time=165ms TTL=49
Reply from 38.49.39.136: bytes=32 time=168ms TTL=49
Reply from 38.49.39.136: bytes=32 time=165ms TTL=49
Reply from 38.49.39.136: bytes=32 time=165ms TTL=49
Reply from 38.49.39.136: bytes=32 time=165ms TTL=49
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 165ms, Maximum = 168ms, Average = 165ms查看 |
GET PING Trace Dig |
|
| 山西临汾市联通 |
联通 |
山西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
167.442ms |
163.661ms |
164.856ms |
32B |
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=50
Reply from 38.49.39.136: bytes=32 time=167ms TTL=50
Reply from 38.49.39.136: bytes=32 time=164ms TTL=50
Reply from 38.49.39.136: bytes=32 time=165ms TTL=50
Reply from 38.49.39.136: bytes=32 time=165ms TTL=50
Reply from 38.49.39.136: bytes=32 time=165ms TTL=50
Reply from 38.49.39.136: bytes=32 time=165ms TTL=50
Reply from 38.49.39.136: bytes=32 time=165ms TTL=50
Reply from 38.49.39.136: bytes=32 time=165ms TTL=50
Reply from 38.49.39.136: bytes=32 time=164ms TTL=50
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 = 167ms, Average = 165ms查看 |
GET PING Trace Dig |
|
| 山西朔州市电信 |
电信 |
山西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
164.783ms |
164.522ms |
164.64ms |
32B |
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=51
Reply from 38.49.39.136: bytes=32 time=165ms TTL=51
Reply from 38.49.39.136: bytes=32 time=165ms TTL=51
Reply from 38.49.39.136: bytes=32 time=165ms TTL=51
Reply from 38.49.39.136: bytes=32 time=165ms TTL=51
Reply from 38.49.39.136: bytes=32 time=165ms TTL=51
Reply from 38.49.39.136: bytes=32 time=165ms TTL=51
Reply from 38.49.39.136: bytes=32 time=165ms TTL=51
Reply from 38.49.39.136: bytes=32 time=165ms TTL=51
Reply from 38.49.39.136: bytes=32 time=165ms TTL=51
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 165ms, Maximum = 165ms, Average = 165ms查看 |
GET PING Trace Dig |
|
| 内蒙古呼和浩特市电信 |
电信 |
内蒙古 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
164.639ms |
163.4ms |
163.812ms |
32B |
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=46
Reply from 38.49.39.136: bytes=32 time=163ms TTL=46
Reply from 38.49.39.136: bytes=32 time=165ms TTL=46
Reply from 38.49.39.136: bytes=32 time=164ms TTL=46
Reply from 38.49.39.136: bytes=32 time=164ms TTL=46
Reply from 38.49.39.136: bytes=32 time=164ms TTL=46
Reply from 38.49.39.136: bytes=32 time=164ms TTL=46
Reply from 38.49.39.136: bytes=32 time=164ms TTL=46
Reply from 38.49.39.136: bytes=32 time=164ms TTL=46
Reply from 38.49.39.136: bytes=32 time=164ms TTL=46
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 163ms, Maximum = 165ms, Average = 164ms查看 |
GET PING Trace Dig |
|
| 重庆重庆市电信 |
电信 |
重庆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
164.498ms |
162.492ms |
162.914ms |
32B |
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=52
Reply from 38.49.39.136: bytes=32 time=163ms TTL=52
Reply from 38.49.39.136: bytes=32 time=162ms TTL=52
Reply from 38.49.39.136: bytes=32 time=163ms TTL=52
Reply from 38.49.39.136: bytes=32 time=163ms TTL=52
Reply from 38.49.39.136: bytes=32 time=163ms TTL=52
Reply from 38.49.39.136: bytes=32 time=163ms TTL=52
Reply from 38.49.39.136: bytes=32 time=163ms TTL=52
Reply from 38.49.39.136: bytes=32 time=164ms TTL=52
Reply from 38.49.39.136: bytes=32 time=163ms 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 = 162ms, Maximum = 164ms, Average = 163ms查看 |
GET PING Trace Dig |
|
| 陕西西安市联通 |
联通 |
陕西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
163.22ms |
162.596ms |
162.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=163ms TTL=48
Reply from 38.49.39.136: bytes=32 time=163ms TTL=48
Reply from 38.49.39.136: bytes=32 time=163ms TTL=48
Reply from 38.49.39.136: bytes=32 time=163ms TTL=48
Reply from 38.49.39.136: bytes=32 time=163ms TTL=48
Reply from 38.49.39.136: bytes=32 time=163ms TTL=48
Reply from 38.49.39.136: bytes=32 time=163ms TTL=48
Reply from 38.49.39.136: bytes=32 time=163ms TTL=48
Reply from 38.49.39.136: bytes=32 time=163ms TTL=48
Reply from 38.49.39.136: bytes=32 time=163ms TTL=48
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 163ms, Maximum = 163ms, Average = 163ms查看 |
GET PING Trace Dig |
|
| 湖南株洲市电信 |
电信 |
湖南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
164.146ms |
161.744ms |
162.519ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=162ms TTL=51
Reply from 38.49.39.136: bytes=32 time=162ms TTL=51
Reply from 38.49.39.136: bytes=32 time=162ms TTL=51
Reply from 38.49.39.136: bytes=32 time=163ms TTL=51
Reply from 38.49.39.136: bytes=32 time=162ms TTL=51
Reply from 38.49.39.136: bytes=32 time=162ms TTL=51
Reply from 38.49.39.136: bytes=32 time=162ms TTL=51
Reply from 38.49.39.136: bytes=32 time=164ms TTL=51
Reply from 38.49.39.136: bytes=32 time=163ms TTL=51
Reply from 38.49.39.136: bytes=32 time=163ms TTL=51
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 162ms, Maximum = 164ms, Average = 163ms查看 |
GET PING Trace Dig |
|
| 重庆重庆市联通 |
联通 |
重庆 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
163.279ms |
161.42ms |
162.378ms |
32B |
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=46
Reply from 38.49.39.136: bytes=32 time=162ms TTL=46
Reply from 38.49.39.136: bytes=32 time=163ms TTL=46
Reply from 38.49.39.136: bytes=32 time=162ms TTL=46
Reply from 38.49.39.136: bytes=32 time=163ms TTL=46
Reply from 38.49.39.136: bytes=32 time=162ms TTL=46
Reply from 38.49.39.136: bytes=32 time=162ms TTL=46
Reply from 38.49.39.136: bytes=32 time=163ms TTL=46
Reply from 38.49.39.136: bytes=32 time=163ms TTL=46
Reply from 38.49.39.136: bytes=32 time=162ms 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 = 161ms, Maximum = 163ms, Average = 162ms查看 |
GET PING Trace Dig |
|
| 湖北襄阳移动 |
移动 |
湖北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
181.776ms |
153.09ms |
161.794ms |
32B |
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=178ms TTL=49
Reply from 38.49.39.136: bytes=32 time=182ms TTL=49
Reply from 38.49.39.136: bytes=32 time=153ms TTL=49
Reply from 38.49.39.136: bytes=32 time=158ms TTL=49
Reply from 38.49.39.136: bytes=32 time=153ms TTL=49
Reply from 38.49.39.136: bytes=32 time=155ms 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 = 182ms, Average = 162ms查看 |
GET PING Trace Dig |
|
| 河南周口移动 |
移动 |
河南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
167.315ms |
159.962ms |
161.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=162ms TTL=49
Reply from 38.49.39.136: bytes=32 time=161ms TTL=49
Reply from 38.49.39.136: bytes=32 time=161ms TTL=49
Reply from 38.49.39.136: bytes=32 time=161ms TTL=49
Reply from 38.49.39.136: bytes=32 time=161ms TTL=49
Reply from 38.49.39.136: bytes=32 time=167ms TTL=49
Reply from 38.49.39.136: bytes=32 time=161ms TTL=49
Reply from 38.49.39.136: bytes=32 time=160ms TTL=49
Reply from 38.49.39.136: bytes=32 time=162ms TTL=49
Reply from 38.49.39.136: bytes=32 time=161ms 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 = 160ms, Maximum = 167ms, Average = 162ms查看 |
GET PING Trace Dig |
|
| 香港香港 |
香港 |
香港 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
164.699ms |
160.865ms |
161.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=163ms 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=161ms TTL=51
Reply from 38.49.39.136: bytes=32 time=162ms TTL=51
Reply from 38.49.39.136: bytes=32 time=161ms TTL=51
Reply from 38.49.39.136: bytes=32 time=165ms 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=161ms 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 = 161ms, Maximum = 165ms, Average = 162ms查看 |
GET PING Trace Dig |
|
| 江苏南京联通 |
联通 |
江苏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
170.76ms |
157.02ms |
161.498ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=160ms TTL=46
Reply from 38.49.39.136: bytes=32 time=163ms TTL=46
Reply from 38.49.39.136: bytes=32 time=157ms TTL=46
Reply from 38.49.39.136: bytes=32 time=160ms TTL=46
Reply from 38.49.39.136: bytes=32 time=164ms TTL=46
Reply from 38.49.39.136: bytes=32 time=159ms TTL=46
Reply from 38.49.39.136: bytes=32 time=158ms TTL=46
Reply from 38.49.39.136: bytes=32 time=171ms TTL=46
Reply from 38.49.39.136: bytes=32 time=162ms TTL=46
Reply from 38.49.39.136: bytes=32 time=160ms 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 = 157ms, Maximum = 171ms, Average = 161ms查看 |
GET PING Trace Dig |
|
| 福建莆田市移动 |
移动 |
福建 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
176.196ms |
157.46ms |
161.46ms |
32B |
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=45
Reply from 38.49.39.136: bytes=32 time=176ms TTL=45
Reply from 38.49.39.136: bytes=32 time=158ms TTL=45
Reply from 38.49.39.136: bytes=32 time=161ms TTL=45
Reply from 38.49.39.136: bytes=32 time=159ms TTL=45
Reply from 38.49.39.136: bytes=32 time=158ms TTL=45
Reply from 38.49.39.136: bytes=32 time=165ms TTL=45
Reply from 38.49.39.136: bytes=32 time=158ms TTL=45
Reply from 38.49.39.136: bytes=32 time=157ms TTL=45
Reply from 38.49.39.136: bytes=32 time=165ms 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 = 157ms, Maximum = 176ms, Average = 161ms查看 |
GET PING Trace Dig |
|
| 河南驻马店市电信 |
电信 |
河南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
161.062ms |
160.302ms |
160.711ms |
32B |
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=49
Reply from 38.49.39.136: bytes=32 time=160ms TTL=49
Reply from 38.49.39.136: bytes=32 time=161ms TTL=49
Reply from 38.49.39.136: bytes=32 time=161ms TTL=49
Reply from 38.49.39.136: bytes=32 time=161ms TTL=49
Reply from 38.49.39.136: bytes=32 time=161ms TTL=49
Reply from 38.49.39.136: bytes=32 time=161ms TTL=49
Reply from 38.49.39.136: bytes=32 time=161ms TTL=49
Reply from 38.49.39.136: bytes=32 time=161ms TTL=49
Reply from 38.49.39.136: bytes=32 time=161ms 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 = 160ms, Maximum = 161ms, Average = 161ms查看 |
GET PING Trace Dig |
|
| 安徽阜阳联通 |
联通 |
安徽 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
158.706ms |
158.244ms |
158.385ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=158ms TTL=51
Reply from 38.49.39.136: bytes=32 time=159ms TTL=51
Reply from 38.49.39.136: bytes=32 time=158ms TTL=51
Reply from 38.49.39.136: bytes=32 time=158ms TTL=51
Reply from 38.49.39.136: bytes=32 time=158ms TTL=51
Reply from 38.49.39.136: bytes=32 time=159ms TTL=51
Reply from 38.49.39.136: bytes=32 time=158ms TTL=51
Reply from 38.49.39.136: bytes=32 time=158ms TTL=51
Reply from 38.49.39.136: bytes=32 time=158ms TTL=51
Reply from 38.49.39.136: bytes=32 time=158ms TTL=51
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 158ms, Maximum = 159ms, Average = 158ms查看 |
GET PING Trace Dig |
|
| 浙江嘉兴市联通 |
联通 |
浙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
157.711ms |
157.431ms |
157.583ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=158ms TTL=51
Reply from 38.49.39.136: bytes=32 time=158ms TTL=51
Reply from 38.49.39.136: bytes=32 time=158ms TTL=51
Reply from 38.49.39.136: bytes=32 time=158ms TTL=51
Reply from 38.49.39.136: bytes=32 time=158ms TTL=51
Reply from 38.49.39.136: bytes=32 time=158ms TTL=51
Reply from 38.49.39.136: bytes=32 time=158ms TTL=51
Reply from 38.49.39.136: bytes=32 time=158ms TTL=51
Reply from 38.49.39.136: bytes=32 time=158ms TTL=51
Reply from 38.49.39.136: bytes=32 time=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 = 157ms, Maximum = 158ms, Average = 158ms查看 |
GET PING Trace Dig |
|
| 北京北京市移动 |
移动 |
北京 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
157.994ms |
156.976ms |
157.434ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=158ms TTL=51
Reply from 38.49.39.136: bytes=32 time=157ms 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
Reply from 38.49.39.136: bytes=32 time=157ms TTL=51
Reply from 38.49.39.136: bytes=32 time=158ms TTL=51
Reply from 38.49.39.136: bytes=32 time=157ms TTL=51
Reply from 38.49.39.136: bytes=32 time=158ms 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 = 157ms, Maximum = 158ms, Average = 157ms查看 |
GET PING Trace Dig |
|
| 香港香港 |
香港 |
香港 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
158.471ms |
157.225ms |
157.417ms |
32B |
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=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=157ms 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=157ms 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=157ms 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 = 158ms, Average = 157ms查看 |
GET PING Trace Dig |
|
| 河北沧州市电信 |
电信 |
河北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
160.704ms |
155.564ms |
156.947ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=157ms TTL=49
Reply from 38.49.39.136: bytes=32 time=157ms TTL=49
Reply from 38.49.39.136: bytes=32 time=159ms TTL=49
Reply from 38.49.39.136: bytes=32 time=156ms TTL=49
Reply from 38.49.39.136: bytes=32 time=156ms TTL=49
Reply from 38.49.39.136: bytes=32 time=156ms TTL=49
Reply from 38.49.39.136: bytes=32 time=161ms TTL=49
Reply from 38.49.39.136: bytes=32 time=156ms TTL=49
Reply from 38.49.39.136: bytes=32 time=156ms TTL=49
Reply from 38.49.39.136: bytes=32 time=156ms TTL=49
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 156ms, Maximum = 161ms, Average = 157ms查看 |
GET PING Trace Dig |
|
| 广东深圳电信 |
电信 |
广东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
155.785ms |
155.466ms |
155.572ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=156ms TTL=47
Reply from 38.49.39.136: bytes=32 time=156ms TTL=47
Reply from 38.49.39.136: bytes=32 time=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=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
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.888ms |
154.316ms |
155.304ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=159ms TTL=50
Reply from 38.49.39.136: bytes=32 time=154ms 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=154ms 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=154ms TTL=50
Reply from 38.49.39.136: bytes=32 time=156ms TTL=50
Reply from 38.49.39.136: bytes=32 time=154ms 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 = 154ms, Maximum = 159ms, Average = 155ms查看 |
GET PING Trace Dig |
|
| 河北保定市联通 |
联通 |
河北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
160.18ms |
152.6ms |
155.112ms |
32B |
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=43
Reply from 38.49.39.136: bytes=32 time=157ms TTL=43
Reply from 38.49.39.136: bytes=32 time=154ms TTL=43
Reply from 38.49.39.136: bytes=32 time=153ms TTL=43
Reply from 38.49.39.136: bytes=32 time=155ms TTL=43
Reply from 38.49.39.136: bytes=32 time=155ms TTL=43
Reply from 38.49.39.136: bytes=32 time=160ms TTL=43
Reply from 38.49.39.136: bytes=32 time=153ms TTL=43
Reply from 38.49.39.136: bytes=32 time=157ms TTL=43
Reply from 38.49.39.136: bytes=32 time=155ms 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 = 153ms, Maximum = 160ms, Average = 155ms查看 |
GET PING Trace Dig |
|
| 江西抚州市电信 |
电信 |
江西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
160.06ms |
153.19ms |
154.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=154ms TTL=50
Reply from 38.49.39.136: bytes=32 time=153ms TTL=50
Reply from 38.49.39.136: bytes=32 time=160ms TTL=50
Reply from 38.49.39.136: bytes=32 time=153ms TTL=50
Reply from 38.49.39.136: bytes=32 time=155ms TTL=50
Reply from 38.49.39.136: bytes=32 time=153ms TTL=50
Reply from 38.49.39.136: bytes=32 time=153ms TTL=50
Reply from 38.49.39.136: bytes=32 time=155ms TTL=50
Reply from 38.49.39.136: bytes=32 time=153ms TTL=50
Reply from 38.49.39.136: bytes=32 time=153ms TTL=50
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 = 160ms, Average = 154ms查看 |
GET PING Trace Dig |
|
| 浙江台州市电信 |
电信 |
浙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
171.667ms |
145.903ms |
153.351ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=160ms TTL=50
Reply from 38.49.39.136: bytes=32 time=151ms TTL=50
Reply from 38.49.39.136: bytes=32 time=156ms TTL=50
Reply from 38.49.39.136: bytes=32 time=150ms TTL=50
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=157ms TTL=50
Reply from 38.49.39.136: bytes=32 time=146ms TTL=50
Reply from 38.49.39.136: bytes=32 time=172ms 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 = 146ms, Maximum = 172ms, Average = 153ms查看 |
GET PING Trace Dig |
|
| 河南洛阳市电信 |
电信 |
河南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
153.357ms |
153.173ms |
153.255ms |
32B |
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 |
153.8ms |
152.86ms |
153.149ms |
32B |
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=153ms TTL=48
Reply from 38.49.39.136: bytes=32 time=153ms TTL=48
Reply from 38.49.39.136: bytes=32 time=153ms TTL=48
Reply from 38.49.39.136: bytes=32 time=153ms TTL=48
Reply from 38.49.39.136: bytes=32 time=153ms TTL=48
Reply from 38.49.39.136: bytes=32 time=153ms TTL=48
Reply from 38.49.39.136: bytes=32 time=153ms TTL=48
Reply from 38.49.39.136: bytes=32 time=153ms TTL=48
Reply from 38.49.39.136: bytes=32 time=153ms TTL=48
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 153ms, Maximum = 154ms, Average = 153ms查看 |
GET PING Trace Dig |
|
| 安徽阜阳市移动 |
移动 |
安徽 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
189.555ms |
147.017ms |
152.894ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=190ms TTL=49
Reply from 38.49.39.136: bytes=32 time=148ms TTL=49
Reply from 38.49.39.136: bytes=32 time=147ms TTL=49
Reply from 38.49.39.136: bytes=32 time=147ms TTL=49
Reply from 38.49.39.136: bytes=32 time=147ms TTL=49
Reply from 38.49.39.136: bytes=32 time=147ms TTL=49
Reply from 38.49.39.136: bytes=32 time=156ms TTL=49
Reply from 38.49.39.136: bytes=32 time=150ms TTL=49
Reply from 38.49.39.136: bytes=32 time=150ms TTL=49
Reply from 38.49.39.136: bytes=32 time=147ms 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 = 147ms, Maximum = 190ms, Average = 153ms查看 |
GET PING Trace Dig |
|
| 湖北鄂州市联通 |
联通 |
湖北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
156.691ms |
151.252ms |
152.507ms |
32B |
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=49
Reply from 38.49.39.136: bytes=32 time=157ms 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=153ms TTL=49
Reply from 38.49.39.136: bytes=32 time=152ms TTL=49
Reply from 38.49.39.136: bytes=32 time=151ms TTL=49
Reply from 38.49.39.136: bytes=32 time=154ms TTL=49
Reply from 38.49.39.136: bytes=32 time=152ms TTL=49
Reply from 38.49.39.136: bytes=32 time=152ms 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 = 151ms, Maximum = 157ms, Average = 153ms查看 |
GET PING Trace Dig |
|
| 天津天津市电信 |
电信 |
天津 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
154.947ms |
150.915ms |
152.084ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
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=152ms 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
Reply from 38.49.39.136: bytes=32 time=154ms 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
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.635ms |
150.649ms |
151.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=151ms TTL=50
Reply from 38.49.39.136: bytes=32 time=152ms TTL=50
Reply from 38.49.39.136: bytes=32 time=152ms TTL=50
Reply from 38.49.39.136: bytes=32 time=151ms TTL=50
Reply from 38.49.39.136: bytes=32 time=151ms TTL=50
Reply from 38.49.39.136: bytes=32 time=152ms TTL=50
Reply from 38.49.39.136: bytes=32 time=152ms TTL=50
Reply from 38.49.39.136: bytes=32 time=154ms TTL=50
Reply from 38.49.39.136: bytes=32 time=154ms TTL=50
Reply from 38.49.39.136: bytes=32 time=152ms TTL=50
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 151ms, Maximum = 154ms, Average = 152ms查看 |
GET PING Trace Dig |
|
| 湖南长沙移动 |
移动 |
湖南 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
156.887ms |
149.868ms |
151.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=151ms 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=150ms TTL=48
Reply from 38.49.39.136: bytes=32 time=151ms 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=157ms TTL=48
Reply from 38.49.39.136: bytes=32 time=154ms TTL=48
Reply from 38.49.39.136: bytes=32 time=151ms 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 = 150ms, Maximum = 157ms, Average = 152ms查看 |
GET PING Trace Dig |
|
| 河北保定市电信 |
电信 |
河北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
153.033ms |
150.004ms |
150.954ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=151ms TTL=51
Reply from 38.49.39.136: bytes=32 time=150ms TTL=51
Reply from 38.49.39.136: bytes=32 time=151ms TTL=51
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=150ms TTL=51
Reply from 38.49.39.136: bytes=32 time=152ms 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=152ms 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 = 150ms, Maximum = 153ms, Average = 151ms查看 |
GET PING Trace Dig |
|
| 福建福州市电信 |
电信 |
福建 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
153.821ms |
148.258ms |
149.861ms |
32B |
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=51
Reply from 38.49.39.136: bytes=32 time=149ms TTL=51
Reply from 38.49.39.136: bytes=32 time=149ms TTL=51
Reply from 38.49.39.136: bytes=32 time=149ms TTL=51
Reply from 38.49.39.136: bytes=32 time=149ms TTL=51
Reply from 38.49.39.136: bytes=32 time=150ms TTL=51
Reply from 38.49.39.136: bytes=32 time=154ms TTL=51
Reply from 38.49.39.136: bytes=32 time=150ms TTL=51
Reply from 38.49.39.136: bytes=32 time=151ms TTL=51
Reply from 38.49.39.136: bytes=32 time=149ms 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 = 154ms, Average = 150ms查看 |
GET PING Trace Dig |
|
| 安徽黄山市移动 |
移动 |
安徽 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
156.416ms |
145.816ms |
149.174ms |
32B |
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=146ms TTL=48
Reply from 38.49.39.136: bytes=32 time=148ms TTL=48
Reply from 38.49.39.136: bytes=32 time=149ms TTL=48
Reply from 38.49.39.136: bytes=32 time=148ms TTL=48
Reply from 38.49.39.136: bytes=32 time=146ms TTL=48
Reply from 38.49.39.136: bytes=32 time=146ms TTL=48
Reply from 38.49.39.136: bytes=32 time=156ms TTL=48
Reply from 38.49.39.136: bytes=32 time=151ms TTL=48
Reply from 38.49.39.136: bytes=32 time=154ms 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 = 146ms, Maximum = 156ms, Average = 149ms查看 |
GET PING Trace Dig |
|
| 江西赣州市移动 |
移动 |
江西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
149.54ms |
148.661ms |
148.958ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=150ms TTL=50
Reply from 38.49.39.136: bytes=32 time=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 = 150ms, Average = 149ms查看 |
GET PING Trace Dig |
|
| 浙江温州市移动 |
移动 |
浙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
157.202ms |
144.004ms |
148.535ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=144ms TTL=49
Reply from 38.49.39.136: bytes=32 time=144ms TTL=49
Reply from 38.49.39.136: bytes=32 time=151ms TTL=49
Reply from 38.49.39.136: bytes=32 time=149ms TTL=49
Reply from 38.49.39.136: bytes=32 time=153ms TTL=49
Reply from 38.49.39.136: bytes=32 time=146ms TTL=49
Reply from 38.49.39.136: bytes=32 time=148ms TTL=49
Reply from 38.49.39.136: bytes=32 time=148ms TTL=49
Reply from 38.49.39.136: bytes=32 time=157ms 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 = 144ms, Maximum = 157ms, Average = 149ms查看 |
GET PING Trace Dig |
|
| 福建泉州市联通 |
联通 |
福建 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
158.16ms |
145.68ms |
147.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=149ms 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
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
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=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 = 146ms, Maximum = 158ms, Average = 147ms查看 |
GET PING Trace Dig |
|
| 山东聊城市移动 |
移动 |
山东 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
147.561ms |
147.262ms |
147.397ms |
32B |
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=49
Reply from 38.49.39.136: bytes=32 time=147ms TTL=49
Reply from 38.49.39.136: bytes=32 time=148ms TTL=49
Reply from 38.49.39.136: bytes=32 time=147ms TTL=49
Reply from 38.49.39.136: bytes=32 time=147ms TTL=49
Reply from 38.49.39.136: bytes=32 time=147ms TTL=49
Reply from 38.49.39.136: bytes=32 time=147ms TTL=49
Reply from 38.49.39.136: bytes=32 time=147ms TTL=49
Reply from 38.49.39.136: bytes=32 time=148ms TTL=49
Reply from 38.49.39.136: bytes=32 time=147ms 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 = 147ms, Maximum = 148ms, Average = 147ms查看 |
GET PING Trace Dig |
|
| 江西抚州市移动 |
移动 |
江西 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
150.775ms |
146.425ms |
147.336ms |
32B |
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=147ms TTL=48
Reply from 38.49.39.136: bytes=32 time=147ms TTL=48
Reply from 38.49.39.136: bytes=32 time=146ms TTL=48
Reply from 38.49.39.136: bytes=32 time=151ms TTL=48
Reply from 38.49.39.136: bytes=32 time=147ms TTL=48
Reply from 38.49.39.136: bytes=32 time=147ms TTL=48
Reply from 38.49.39.136: bytes=32 time=147ms TTL=48
Reply from 38.49.39.136: bytes=32 time=147ms TTL=48
Reply from 38.49.39.136: bytes=32 time=148ms 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 = 146ms, Maximum = 151ms, Average = 147ms查看 |
GET PING Trace Dig |
|
| 湖北黄冈市电信 |
电信 |
湖北 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
147.84ms |
146.62ms |
147.178ms |
32B |
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=148ms TTL=51
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=147ms TTL=51
Reply from 38.49.39.136: bytes=32 time=148ms TTL=51
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=147ms 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 = 147ms, Maximum = 148ms, Average = 147ms查看 |
GET PING Trace Dig |
|
| 宁夏银川市联通 |
联通 |
宁夏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
151.055ms |
146.241ms |
147.176ms |
32B |
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=146ms TTL=52
Reply from 38.49.39.136: bytes=32 time=151ms 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=146ms 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 = 146ms, Maximum = 151ms, Average = 147ms查看 |
GET PING Trace Dig |
|
| 江苏扬州市移动 |
移动 |
江苏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
143.78ms |
143.26ms |
143.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=143ms TTL=49
Reply from 38.49.39.136: bytes=32 time=144ms 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=144ms TTL=49
Reply from 38.49.39.136: bytes=32 time=144ms TTL=49
Reply from 38.49.39.136: bytes=32 time=143ms TTL=49
Reply from 38.49.39.136: bytes=32 time=143ms 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
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 = 144ms, Average = 143ms查看 |
GET PING Trace Dig |
|
| 上海上海市电信 |
电信 |
上海 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
143.099ms |
142.439ms |
142.611ms |
32B |
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=46
Reply from 38.49.39.136: bytes=32 time=143ms TTL=46
Reply from 38.49.39.136: bytes=32 time=142ms TTL=46
Reply from 38.49.39.136: bytes=32 time=143ms TTL=46
Reply from 38.49.39.136: bytes=32 time=143ms TTL=46
Reply from 38.49.39.136: bytes=32 time=143ms TTL=46
Reply from 38.49.39.136: bytes=32 time=142ms TTL=46
Reply from 38.49.39.136: bytes=32 time=143ms TTL=46
Reply from 38.49.39.136: bytes=32 time=142ms TTL=46
Reply from 38.49.39.136: bytes=32 time=142ms 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 = 142ms, Maximum = 143ms, Average = 143ms查看 |
GET PING Trace Dig |
|
| 安徽合肥市电信 |
电信 |
安徽 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
145.991ms |
138.945ms |
142.595ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=142ms TTL=50
Reply from 38.49.39.136: bytes=32 time=142ms TTL=50
Reply from 38.49.39.136: bytes=32 time=145ms 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=141ms TTL=50
Reply from 38.49.39.136: bytes=32 time=146ms TTL=50
Reply from 38.49.39.136: bytes=32 time=142ms TTL=50
Reply from 38.49.39.136: bytes=32 time=139ms 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 = 139ms, Maximum = 146ms, Average = 143ms查看 |
GET PING Trace Dig |
|
| 江苏苏州市电信 |
电信 |
江苏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
142.794ms |
141.667ms |
142.296ms |
32B |
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=48
Reply from 38.49.39.136: bytes=32 time=142ms TTL=48
Reply from 38.49.39.136: bytes=32 time=142ms TTL=48
Reply from 38.49.39.136: bytes=32 time=143ms TTL=48
Reply from 38.49.39.136: bytes=32 time=142ms TTL=48
Reply from 38.49.39.136: bytes=32 time=143ms TTL=48
Reply from 38.49.39.136: bytes=32 time=142ms TTL=48
Reply from 38.49.39.136: bytes=32 time=143ms TTL=48
Reply from 38.49.39.136: bytes=32 time=143ms TTL=48
Reply from 38.49.39.136: bytes=32 time=142ms 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 = 142ms, Maximum = 143ms, Average = 142ms查看 |
GET PING Trace Dig |
|
| 江苏南通市移动 |
移动 |
江苏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
142.001ms |
141.661ms |
141.839ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=142ms TTL=51
Reply from 38.49.39.136: bytes=32 time=142ms TTL=51
Reply from 38.49.39.136: bytes=32 time=142ms TTL=51
Reply from 38.49.39.136: bytes=32 time=142ms TTL=51
Reply from 38.49.39.136: bytes=32 time=142ms TTL=51
Reply from 38.49.39.136: bytes=32 time=142ms TTL=51
Reply from 38.49.39.136: bytes=32 time=142ms TTL=51
Reply from 38.49.39.136: bytes=32 time=142ms TTL=51
Reply from 38.49.39.136: bytes=32 time=142ms TTL=51
Reply from 38.49.39.136: bytes=32 time=142ms TTL=51
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 = 142ms, Average = 142ms查看 |
GET PING Trace Dig |
|
| 安徽马鞍山市电信 |
电信 |
安徽 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
139.738ms |
138.874ms |
139.234ms |
32B |
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=139ms TTL=51
Reply from 38.49.39.136: bytes=32 time=140ms TTL=51
Reply from 38.49.39.136: bytes=32 time=139ms TTL=51
Reply from 38.49.39.136: bytes=32 time=139ms TTL=51
Reply from 38.49.39.136: bytes=32 time=139ms TTL=51
Reply from 38.49.39.136: bytes=32 time=139ms TTL=51
Reply from 38.49.39.136: bytes=32 time=139ms TTL=51
Reply from 38.49.39.136: bytes=32 time=139ms TTL=51
Reply from 38.49.39.136: bytes=32 time=139ms TTL=51
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 139ms, Maximum = 140ms, Average = 139ms查看 |
GET PING Trace Dig |
|
| 台湾台湾 |
台湾 |
台湾 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
148.662ms |
136.501ms |
138.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=137ms TTL=52
Reply from 38.49.39.136: bytes=32 time=138ms TTL=52
Reply from 38.49.39.136: bytes=32 time=137ms TTL=52
Reply from 38.49.39.136: bytes=32 time=138ms TTL=52
Reply from 38.49.39.136: bytes=32 time=138ms TTL=52
Reply from 38.49.39.136: bytes=32 time=138ms TTL=52
Reply from 38.49.39.136: bytes=32 time=137ms TTL=52
Reply from 38.49.39.136: bytes=32 time=139ms TTL=52
Reply from 38.49.39.136: bytes=32 time=149ms TTL=52
Reply from 38.49.39.136: bytes=32 time=138ms 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 = 137ms, Maximum = 149ms, Average = 139ms查看 |
GET PING Trace Dig |
|
| 上海上海市移动 |
移动 |
上海 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
148.881ms |
130.329ms |
136.901ms |
32B |
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=50
Reply from 38.49.39.136: bytes=32 time=132ms TTL=50
Reply from 38.49.39.136: bytes=32 time=149ms TTL=50
Reply from 38.49.39.136: bytes=32 time=138ms TTL=50
Reply from 38.49.39.136: bytes=32 time=145ms TTL=50
Reply from 38.49.39.136: bytes=32 time=131ms TTL=50
Reply from 38.49.39.136: bytes=32 time=134ms 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=140ms TTL=50
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 130ms, Maximum = 149ms, Average = 137ms查看 |
GET PING Trace Dig |
|
| 上海上海市移动 |
移动 |
上海 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
135.062ms |
133.601ms |
134.409ms |
32B |
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=134ms 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=134ms TTL=51
Reply from 38.49.39.136: bytes=32 time=135ms 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
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 = 135ms, Average = 134ms查看 |
GET PING Trace Dig |
|
| 浙江杭州市移动 |
移动 |
浙江 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
133.12ms |
131.201ms |
131.665ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=133ms TTL=44
Reply from 38.49.39.136: bytes=32 time=132ms TTL=44
Reply from 38.49.39.136: bytes=32 time=132ms TTL=44
Reply from 38.49.39.136: bytes=32 time=131ms TTL=44
Reply from 38.49.39.136: bytes=32 time=132ms TTL=44
Reply from 38.49.39.136: bytes=32 time=132ms TTL=44
Reply from 38.49.39.136: bytes=32 time=132ms TTL=44
Reply from 38.49.39.136: bytes=32 time=131ms TTL=44
Reply from 38.49.39.136: bytes=32 time=132ms TTL=44
Reply from 38.49.39.136: bytes=32 time=131ms 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 = 131ms, Maximum = 133ms, Average = 132ms查看 |
GET PING Trace Dig |
|
| 江苏常州市电信 |
电信 |
江苏 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
130.431ms |
130.248ms |
130.312ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=130ms TTL=52
Reply from 38.49.39.136: bytes=32 time=130ms TTL=52
Reply from 38.49.39.136: bytes=32 time=130ms TTL=52
Reply from 38.49.39.136: bytes=32 time=130ms TTL=52
Reply from 38.49.39.136: bytes=32 time=130ms TTL=52
Reply from 38.49.39.136: bytes=32 time=130ms TTL=52
Reply from 38.49.39.136: bytes=32 time=130ms TTL=52
Reply from 38.49.39.136: bytes=32 time=130ms TTL=52
Reply from 38.49.39.136: bytes=32 time=130ms TTL=52
Reply from 38.49.39.136: bytes=32 time=130ms TTL=52
Ping statistics for 38.49.39.136:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 130ms, Maximum = 130ms, Average = 130ms查看 |
GET PING Trace Dig |
|
| 浙江宁波市电信 |
电信 |
浙江 |
36.150.215.166 |
中国江苏南京移动 |
10 |
10 |
0 |
61.48ms |
34.52ms |
44.954ms |
32B |
PING hmshu.com
PING hmshu.com (36.150.215.166) with 32 bytes of data:
Reply from 36.150.215.166: bytes=32 time=40ms TTL=50
Reply from 36.150.215.166: bytes=32 time=45ms TTL=50
Reply from 36.150.215.166: bytes=32 time=43ms TTL=50
Reply from 36.150.215.166: bytes=32 time=35ms TTL=50
Reply from 36.150.215.166: bytes=32 time=38ms TTL=50
Reply from 36.150.215.166: bytes=32 time=45ms TTL=50
Reply from 36.150.215.166: bytes=32 time=42ms TTL=50
Reply from 36.150.215.166: bytes=32 time=42ms TTL=50
Reply from 36.150.215.166: bytes=32 time=59ms TTL=50
Reply from 36.150.215.166: bytes=32 time=61ms TTL=50
Ping statistics for 36.150.215.166:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 61ms, Average = 45ms查看 |
GET PING Trace Dig |
|
| 美国国外 |
国外 |
美国 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
1.082ms |
0.665ms |
0.839ms |
32B |
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 |
|
| 美国国外 |
国外 |
美国 |
38.49.39.136 |
美国加利福尼亚洛杉矶Cogent |
10 |
10 |
0 |
0.71ms |
0.493ms |
0.606ms |
32B |
PING hmshu.com
PING hmshu.com (38.49.39.136) with 32 bytes of data:
Reply from 38.49.39.136: bytes=32 time=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 |
|
| 广东中山市联通 |
联通 |
广东 |
127.0.0.1 |
Local Address |
10 |
10 |
0 |
0.051ms |
0.046ms |
0.047ms |
32B |
PING hmshu.com
PING hmshu.com (127.0.0.1) with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Reply from 127.0.0.1: bytes=32 time<1ms TTL=64
Ping statistics for 127.0.0.1:
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=175ms TTL=50
Reply from : bytes=0 time=184ms TTL=50
Reply from : bytes=0 time=187ms TTL=50
Reply from : bytes=0 time=190ms TTL=50
Reply from : bytes=0 time=193ms TTL=50
Reply from : bytes=0 time=190ms TTL=50
Reply from : bytes=0 time=186ms TTL=50
Reply from : bytes=0 time=186ms TTL=50
Reply from : bytes=0 time=189ms TTL=50
Reply from : bytes=0 time=191ms TTL=50
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=182ms TTL=50
Reply from : bytes=0 time=182ms TTL=50
Reply from : bytes=0 time=179ms TTL=50
Reply from : bytes=0 time=181ms TTL=50
Reply from : bytes=0 time=182ms TTL=50
Reply from : bytes=0 time=182ms TTL=50
Reply from : bytes=0 time=180ms TTL=50
Reply from : bytes=0 time=179ms TTL=50
Reply from : bytes=0 time=181ms TTL=50
Reply from : bytes=0 time=180ms TTL=50
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 |
|
