监测点 |
ISP |
省份 |
解析IP |
解析IP所在地 |
发送 |
接收 |
丢弃 |
最大时间 |
最小时间 |
平均时间 |
包大小 |
详细信息 |
操作 |
共179个点 |
8个 |
共38个 |
共7个独立IP |
共7个独立节点 |
10 |
9 |
1 |
80.81ms |
52.181ms |
62.832ms |
|
|
|
天津天津市联通 |
联通 |
天津 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
8 |
2 |
745.338ms |
97.405ms |
533.274ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=277ms TTL=50 Reply from 157.185.139.32: bytes=32 time=726ms TTL=50 Reply from 157.185.139.32: bytes=32 time=745ms TTL=50 Request timed out. Request timed out. Reply from 157.185.139.32: bytes=32 time=727ms TTL=50 Reply from 157.185.139.32: bytes=32 time=644ms TTL=50 Reply from 157.185.139.32: bytes=32 time=690ms TTL=50 Reply from 157.185.139.32: bytes=32 time=97ms TTL=50 Reply from 157.185.139.32: bytes=32 time=360ms TTL=50
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 8, Lost = 2 (20% loss), Approximate round trip times in milli-seconds: Minimum = 97ms, Maximum = 745ms, Average = 533ms查看 |
GET PING Trace Dig |
|
内蒙古兴安盟移动 |
移动 |
内蒙古 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
546.842ms |
110.304ms |
283.293ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=117ms TTL=46 Reply from 138.113.156.56: bytes=32 time=113ms TTL=46 Reply from 138.113.156.56: bytes=32 time=228ms TTL=46 Reply from 138.113.156.56: bytes=32 time=438ms TTL=46 Reply from 138.113.156.56: bytes=32 time=374ms TTL=46 Reply from 138.113.156.56: bytes=32 time=513ms TTL=46 Reply from 138.113.156.56: bytes=32 time=547ms TTL=46 Reply from 138.113.156.56: bytes=32 time=272ms TTL=46 Reply from 138.113.156.56: bytes=32 time=110ms TTL=46 Reply from 138.113.156.56: bytes=32 time=122ms TTL=46
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 110ms, Maximum = 547ms, Average = 283ms查看 |
GET PING Trace Dig |
|
云南西双版纳移动 |
移动 |
云南 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
502.109ms |
65.583ms |
216.919ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=73ms TTL=50 Reply from 138.113.156.56: bytes=32 time=502ms TTL=50 Reply from 138.113.156.56: bytes=32 time=280ms TTL=50 Reply from 138.113.156.56: bytes=32 time=80ms TTL=50 Reply from 138.113.156.56: bytes=32 time=428ms TTL=50 Reply from 138.113.156.56: bytes=32 time=230ms TTL=50 Reply from 138.113.156.56: bytes=32 time=100ms TTL=50 Reply from 138.113.156.56: bytes=32 time=66ms TTL=50 Reply from 138.113.156.56: bytes=32 time=157ms TTL=50 Reply from 138.113.156.56: bytes=32 time=253ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 66ms, Maximum = 502ms, Average = 217ms查看 |
GET PING Trace Dig |
|
辽宁锦州市联通 |
联通 |
辽宁 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
390.818ms |
88.42ms |
195.325ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=130ms TTL=50 Reply from 157.185.139.32: bytes=32 time=104ms TTL=50 Reply from 157.185.139.32: bytes=32 time=95ms TTL=50 Reply from 157.185.139.32: bytes=32 time=88ms TTL=50 Reply from 157.185.139.32: bytes=32 time=130ms TTL=50 Reply from 157.185.139.32: bytes=32 time=124ms TTL=50 Reply from 157.185.139.32: bytes=32 time=217ms TTL=50 Reply from 157.185.139.32: bytes=32 time=345ms TTL=50 Reply from 157.185.139.32: bytes=32 time=391ms TTL=50 Reply from 157.185.139.32: bytes=32 time=328ms TTL=50
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 88ms, Maximum = 391ms, Average = 195ms查看 |
GET PING Trace Dig |
|
河北沧州市联通 |
联通 |
河北 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
475.945ms |
51.823ms |
189.855ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=389ms TTL=49 Reply from 138.113.156.56: bytes=32 time=52ms TTL=49 Reply from 138.113.156.56: bytes=32 time=52ms TTL=49 Reply from 138.113.156.56: bytes=32 time=98ms TTL=49 Reply from 138.113.156.56: bytes=32 time=141ms TTL=49 Reply from 138.113.156.56: bytes=32 time=60ms TTL=49 Reply from 138.113.156.56: bytes=32 time=476ms TTL=49 Reply from 138.113.156.56: bytes=32 time=148ms TTL=49 Reply from 138.113.156.56: bytes=32 time=424ms TTL=49 Reply from 138.113.156.56: bytes=32 time=59ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 52ms, Maximum = 476ms, Average = 190ms查看 |
GET PING Trace Dig |
|
江苏南京市电信 |
电信 |
江苏 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
282.218ms |
103.18ms |
158.139ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=130ms TTL=49 Reply from 138.113.156.56: bytes=32 time=120ms TTL=49 Reply from 138.113.156.56: bytes=32 time=103ms TTL=49 Reply from 138.113.156.56: bytes=32 time=106ms TTL=49 Reply from 138.113.156.56: bytes=32 time=166ms TTL=49 Reply from 138.113.156.56: bytes=32 time=282ms TTL=49 Reply from 138.113.156.56: bytes=32 time=231ms TTL=49 Reply from 138.113.156.56: bytes=32 time=144ms TTL=49 Reply from 138.113.156.56: bytes=32 time=115ms TTL=49 Reply from 138.113.156.56: bytes=32 time=184ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 103ms, Maximum = 282ms, Average = 158ms查看 |
GET PING Trace Dig |
|
内蒙古呼和浩特市联通 |
联通 |
内蒙古 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
9 |
1 |
310.68ms |
110.324ms |
145.977ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=311ms TTL=48 Reply from 157.185.139.32: bytes=32 time=125ms TTL=48 Reply from 157.185.139.32: bytes=32 time=114ms TTL=48 Reply from 157.185.139.32: bytes=32 time=127ms TTL=48 Reply from 157.185.139.32: bytes=32 time=110ms TTL=48 Reply from 157.185.139.32: bytes=32 time=168ms TTL=48 Reply from 157.185.139.32: bytes=32 time=118ms TTL=48 Reply from 157.185.139.32: bytes=32 time=122ms TTL=48 Reply from 157.185.139.32: bytes=32 time=119ms TTL=48 Request timed out.
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 9, Lost = 1 (10% loss), Approximate round trip times in milli-seconds: Minimum = 110ms, Maximum = 311ms, Average = 146ms查看 |
GET PING Trace Dig |
|
湖北咸宁市联通 |
联通 |
湖北 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
339.844ms |
75.279ms |
142.446ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=96ms TTL=42 Reply from 157.185.139.32: bytes=32 time=79ms TTL=42 Reply from 157.185.139.32: bytes=32 time=77ms TTL=42 Reply from 157.185.139.32: bytes=32 time=165ms TTL=42 Reply from 157.185.139.32: bytes=32 time=340ms TTL=42 Reply from 157.185.139.32: bytes=32 time=78ms TTL=42 Reply from 157.185.139.32: bytes=32 time=75ms TTL=42 Reply from 157.185.139.32: bytes=32 time=83ms TTL=42 Reply from 157.185.139.32: bytes=32 time=245ms TTL=42 Reply from 157.185.139.32: bytes=32 time=186ms TTL=42
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 75ms, Maximum = 340ms, Average = 142ms查看 |
GET PING Trace Dig |
|
重庆重庆市电信 |
电信 |
重庆 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
213.745ms |
90.336ms |
139.753ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=214ms TTL=47 Reply from 157.185.139.32: bytes=32 time=90ms TTL=47 Reply from 157.185.139.32: bytes=32 time=121ms TTL=47 Reply from 157.185.139.32: bytes=32 time=182ms TTL=47 Reply from 157.185.139.32: bytes=32 time=135ms TTL=47 Reply from 157.185.139.32: bytes=32 time=112ms TTL=47 Reply from 157.185.139.32: bytes=32 time=176ms TTL=47 Reply from 157.185.139.32: bytes=32 time=171ms TTL=47 Reply from 157.185.139.32: bytes=32 time=96ms TTL=47 Reply from 157.185.139.32: bytes=32 time=102ms TTL=47
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 90ms, Maximum = 214ms, Average = 140ms查看 |
GET PING Trace Dig |
|
内蒙古兴安盟移动 |
移动 |
内蒙古 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
8 |
2 |
300.165ms |
92.6ms |
124.105ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=300ms TTL=48 Reply from 138.113.156.56: bytes=32 time=108ms TTL=48 Reply from 138.113.156.56: bytes=32 time=102ms TTL=48 Request timed out. Reply from 138.113.156.56: bytes=32 time=96ms TTL=48 Reply from 138.113.156.56: bytes=32 time=93ms TTL=48 Reply from 138.113.156.56: bytes=32 time=97ms TTL=48 Reply from 138.113.156.56: bytes=32 time=100ms TTL=48 Reply from 138.113.156.56: bytes=32 time=98ms TTL=48 Request timed out.
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 8, Lost = 2 (20% loss), Approximate round trip times in milli-seconds: Minimum = 93ms, Maximum = 300ms, Average = 124ms查看 |
GET PING Trace Dig |
|
新疆喀什地区移动 |
移动 |
新疆 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
135.15ms |
114.701ms |
120.125ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=119ms TTL=50 Reply from 138.113.156.56: bytes=32 time=122ms TTL=50 Reply from 138.113.156.56: bytes=32 time=116ms TTL=50 Reply from 138.113.156.56: bytes=32 time=115ms TTL=50 Reply from 138.113.156.56: bytes=32 time=135ms TTL=50 Reply from 138.113.156.56: bytes=32 time=121ms TTL=50 Reply from 138.113.156.56: bytes=32 time=116ms TTL=50 Reply from 138.113.156.56: bytes=32 time=119ms TTL=50 Reply from 138.113.156.56: bytes=32 time=115ms TTL=50 Reply from 138.113.156.56: bytes=32 time=124ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 115ms, Maximum = 135ms, Average = 120ms查看 |
GET PING Trace Dig |
|
新疆乌鲁木齐市电信 |
电信 |
新疆 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
112.341ms |
110.72ms |
111.406ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=112ms TTL=50 Reply from 138.113.156.56: bytes=32 time=111ms TTL=50 Reply from 138.113.156.56: bytes=32 time=111ms TTL=50 Reply from 138.113.156.56: bytes=32 time=111ms TTL=50 Reply from 138.113.156.56: bytes=32 time=112ms TTL=50 Reply from 138.113.156.56: bytes=32 time=111ms TTL=50 Reply from 138.113.156.56: bytes=32 time=112ms TTL=50 Reply from 138.113.156.56: bytes=32 time=111ms TTL=50 Reply from 138.113.156.56: bytes=32 time=112ms TTL=50 Reply from 138.113.156.56: bytes=32 time=112ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 111ms, Maximum = 112ms, Average = 111ms查看 |
GET PING Trace Dig |
|
北京北京市移动 |
移动 |
北京 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
119.44ms |
102.18ms |
110.648ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=119ms TTL=48 Reply from 138.113.156.56: bytes=32 time=109ms TTL=48 Reply from 138.113.156.56: bytes=32 time=111ms TTL=48 Reply from 138.113.156.56: bytes=32 time=102ms TTL=48 Reply from 138.113.156.56: bytes=32 time=107ms TTL=48 Reply from 138.113.156.56: bytes=32 time=119ms TTL=48 Reply from 138.113.156.56: bytes=32 time=110ms TTL=48 Reply from 138.113.156.56: bytes=32 time=107ms TTL=48 Reply from 138.113.156.56: bytes=32 time=111ms TTL=48 Reply from 138.113.156.56: bytes=32 time=111ms TTL=48
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 102ms, Maximum = 119ms, Average = 111ms查看 |
GET PING Trace Dig |
|
河北邯郸市移动 |
移动 |
河北 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
216.95ms |
68.493ms |
108.803ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=91ms TTL=50 Reply from 157.185.139.32: bytes=32 time=115ms TTL=50 Reply from 157.185.139.32: bytes=32 time=90ms TTL=50 Reply from 157.185.139.32: bytes=32 time=90ms TTL=50 Reply from 157.185.139.32: bytes=32 time=128ms TTL=50 Reply from 157.185.139.32: bytes=32 time=119ms TTL=50 Reply from 157.185.139.32: bytes=32 time=87ms TTL=50 Reply from 157.185.139.32: bytes=32 time=217ms TTL=50 Reply from 157.185.139.32: bytes=32 time=68ms TTL=50 Reply from 157.185.139.32: bytes=32 time=83ms TTL=50
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 68ms, Maximum = 217ms, Average = 109ms查看 |
GET PING Trace Dig |
|
新疆塔城地区联通 |
联通 |
新疆 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
127.696ms |
94.645ms |
108.233ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=100ms TTL=49 Reply from 157.185.139.32: bytes=32 time=95ms TTL=49 Reply from 157.185.139.32: bytes=32 time=128ms TTL=49 Reply from 157.185.139.32: bytes=32 time=96ms TTL=49 Reply from 157.185.139.32: bytes=32 time=107ms TTL=49 Reply from 157.185.139.32: bytes=32 time=111ms TTL=49 Reply from 157.185.139.32: bytes=32 time=107ms TTL=49 Reply from 157.185.139.32: bytes=32 time=111ms TTL=49 Reply from 157.185.139.32: bytes=32 time=108ms TTL=49 Reply from 157.185.139.32: bytes=32 time=120ms TTL=49
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 95ms, Maximum = 128ms, Average = 108ms查看 |
GET PING Trace Dig |
|
新疆克拉玛依市电信 |
电信 |
新疆 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
113.5ms |
103.54ms |
106.781ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=108ms TTL=48 Reply from 157.185.139.32: bytes=32 time=109ms TTL=48 Reply from 157.185.139.32: bytes=32 time=104ms TTL=48 Reply from 157.185.139.32: bytes=32 time=106ms TTL=48 Reply from 157.185.139.32: bytes=32 time=105ms TTL=48 Reply from 157.185.139.32: bytes=32 time=114ms TTL=48 Reply from 157.185.139.32: bytes=32 time=105ms TTL=48 Reply from 157.185.139.32: bytes=32 time=109ms TTL=48 Reply from 157.185.139.32: bytes=32 time=105ms TTL=48 Reply from 157.185.139.32: bytes=32 time=105ms TTL=48
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 104ms, Maximum = 114ms, Average = 107ms查看 |
GET PING Trace Dig |
|
西藏拉萨市移动 |
移动 |
西藏 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
103.14ms |
99.599ms |
101.384ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=102ms TTL=50 Reply from 138.113.156.56: bytes=32 time=102ms TTL=50 Reply from 138.113.156.56: bytes=32 time=103ms TTL=50 Reply from 138.113.156.56: bytes=32 time=101ms TTL=50 Reply from 138.113.156.56: bytes=32 time=101ms TTL=50 Reply from 138.113.156.56: bytes=32 time=100ms TTL=50 Reply from 138.113.156.56: bytes=32 time=100ms TTL=50 Reply from 138.113.156.56: bytes=32 time=103ms TTL=50 Reply from 138.113.156.56: bytes=32 time=102ms TTL=50 Reply from 138.113.156.56: bytes=32 time=102ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 100ms, Maximum = 103ms, Average = 101ms查看 |
GET PING Trace Dig |
|
新疆昌吉回族自治州移动 |
移动 |
新疆 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
100.59ms |
98.426ms |
99.166ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=99ms TTL=49 Reply from 138.113.156.56: bytes=32 time=101ms TTL=49 Reply from 138.113.156.56: bytes=32 time=99ms TTL=49 Reply from 138.113.156.56: bytes=32 time=100ms TTL=49 Reply from 138.113.156.56: bytes=32 time=101ms TTL=49 Reply from 138.113.156.56: bytes=32 time=99ms TTL=49 Reply from 138.113.156.56: bytes=32 time=98ms TTL=49 Reply from 138.113.156.56: bytes=32 time=99ms TTL=49 Reply from 138.113.156.56: bytes=32 time=99ms TTL=49 Reply from 138.113.156.56: bytes=32 time=99ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 98ms, Maximum = 101ms, Average = 99ms查看 |
GET PING Trace Dig |
|
西藏拉萨市电信 |
电信 |
西藏 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
102.78ms |
95.711ms |
97.256ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=103ms TTL=47 Reply from 138.113.156.56: bytes=32 time=96ms TTL=47 Reply from 138.113.156.56: bytes=32 time=96ms TTL=47 Reply from 138.113.156.56: bytes=32 time=98ms TTL=47 Reply from 138.113.156.56: bytes=32 time=97ms TTL=47 Reply from 138.113.156.56: bytes=32 time=96ms TTL=47 Reply from 138.113.156.56: bytes=32 time=96ms TTL=47 Reply from 138.113.156.56: bytes=32 time=97ms TTL=47 Reply from 138.113.156.56: bytes=32 time=96ms TTL=47 Reply from 138.113.156.56: bytes=32 time=97ms TTL=47
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 96ms, Maximum = 103ms, Average = 97ms查看 |
GET PING Trace Dig |
|
青海黄南电信 |
电信 |
青海 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
109.051ms |
84.155ms |
90.871ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=88ms TTL=49 Reply from 138.113.156.56: bytes=32 time=90ms TTL=49 Reply from 138.113.156.56: bytes=32 time=91ms TTL=49 Reply from 138.113.156.56: bytes=32 time=89ms TTL=49 Reply from 138.113.156.56: bytes=32 time=88ms TTL=49 Reply from 138.113.156.56: bytes=32 time=91ms TTL=49 Reply from 138.113.156.56: bytes=32 time=109ms TTL=49 Reply from 138.113.156.56: bytes=32 time=84ms TTL=49 Reply from 138.113.156.56: bytes=32 time=88ms TTL=49 Reply from 138.113.156.56: bytes=32 time=90ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 84ms, Maximum = 109ms, Average = 91ms查看 |
GET PING Trace Dig |
|
江西南昌市移动 |
移动 |
江西 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
109.224ms |
74.839ms |
88.531ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=103ms TTL=51 Reply from 138.113.156.56: bytes=32 time=88ms TTL=51 Reply from 138.113.156.56: bytes=32 time=109ms TTL=51 Reply from 138.113.156.56: bytes=32 time=79ms TTL=51 Reply from 138.113.156.56: bytes=32 time=98ms TTL=51 Reply from 138.113.156.56: bytes=32 time=86ms TTL=51 Reply from 138.113.156.56: bytes=32 time=90ms TTL=51 Reply from 138.113.156.56: bytes=32 time=80ms TTL=51 Reply from 138.113.156.56: bytes=32 time=75ms TTL=51 Reply from 138.113.156.56: bytes=32 time=78ms TTL=51
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 75ms, Maximum = 109ms, Average = 89ms查看 |
GET PING Trace Dig |
|
新疆克拉玛依市联通 |
联通 |
新疆 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
89.66ms |
85.58ms |
86.727ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=87ms TTL=49 Reply from 138.113.156.56: bytes=32 time=87ms TTL=49 Reply from 138.113.156.56: bytes=32 time=86ms TTL=49 Reply from 138.113.156.56: bytes=32 time=87ms TTL=49 Reply from 138.113.156.56: bytes=32 time=90ms TTL=49 Reply from 138.113.156.56: bytes=32 time=87ms TTL=49 Reply from 138.113.156.56: bytes=32 time=87ms TTL=49 Reply from 138.113.156.56: bytes=32 time=86ms TTL=49 Reply from 138.113.156.56: bytes=32 time=86ms TTL=49 Reply from 138.113.156.56: bytes=32 time=87ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 86ms, Maximum = 90ms, Average = 87ms查看 |
GET PING Trace Dig |
|
吉林松原市移动 |
移动 |
吉林 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
100.471ms |
78.284ms |
83.693ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=81ms TTL=50 Reply from 157.185.139.32: bytes=32 time=80ms TTL=50 Reply from 157.185.139.32: bytes=32 time=79ms TTL=50 Reply from 157.185.139.32: bytes=32 time=78ms TTL=50 Reply from 157.185.139.32: bytes=32 time=100ms TTL=50 Reply from 157.185.139.32: bytes=32 time=79ms TTL=50 Reply from 157.185.139.32: bytes=32 time=86ms TTL=50 Reply from 157.185.139.32: bytes=32 time=79ms TTL=50 Reply from 157.185.139.32: bytes=32 time=85ms TTL=50 Reply from 157.185.139.32: bytes=32 time=90ms TTL=50
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 78ms, Maximum = 100ms, Average = 84ms查看 |
GET PING Trace Dig |
|
台湾台湾 |
台湾 |
台湾 |
140.150.47.68 |
瑞典 |
10 |
10 |
0 |
85.001ms |
79.321ms |
81.95ms |
32B |
PING 9d9032.com PING 9d9032.com (140.150.47.68) with 32 bytes of data: Reply from 140.150.47.68: bytes=32 time=84ms TTL=51 Reply from 140.150.47.68: bytes=32 time=79ms TTL=51 Reply from 140.150.47.68: bytes=32 time=83ms TTL=51 Reply from 140.150.47.68: bytes=32 time=80ms TTL=51 Reply from 140.150.47.68: bytes=32 time=82ms TTL=51 Reply from 140.150.47.68: bytes=32 time=85ms TTL=51 Reply from 140.150.47.68: bytes=32 time=83ms TTL=51 Reply from 140.150.47.68: bytes=32 time=81ms TTL=51 Reply from 140.150.47.68: bytes=32 time=81ms TTL=51 Reply from 140.150.47.68: bytes=32 time=80ms TTL=51
Ping statistics for 140.150.47.68: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 79ms, Maximum = 85ms, Average = 82ms查看 |
GET PING Trace Dig |
|
吉林长春市铁通 |
铁通 |
吉林 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
82.921ms |
80.44ms |
81.453ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=82ms TTL=43 Reply from 157.185.139.32: bytes=32 time=81ms TTL=43 Reply from 157.185.139.32: bytes=32 time=81ms TTL=43 Reply from 157.185.139.32: bytes=32 time=80ms TTL=43 Reply from 157.185.139.32: bytes=32 time=82ms TTL=43 Reply from 157.185.139.32: bytes=32 time=82ms TTL=43 Reply from 157.185.139.32: bytes=32 time=81ms TTL=43 Reply from 157.185.139.32: bytes=32 time=81ms TTL=43 Reply from 157.185.139.32: bytes=32 time=83ms TTL=43 Reply from 157.185.139.32: bytes=32 time=81ms TTL=43
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 80ms, Maximum = 83ms, Average = 81ms查看 |
GET PING Trace Dig |
|
黑龙江牡丹江市联通 |
联通 |
黑龙江 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
118.87ms |
74.796ms |
80.713ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=119ms TTL=51 Reply from 157.185.139.32: bytes=32 time=77ms TTL=51 Reply from 157.185.139.32: bytes=32 time=78ms TTL=51 Reply from 157.185.139.32: bytes=32 time=75ms TTL=51 Reply from 157.185.139.32: bytes=32 time=75ms TTL=51 Reply from 157.185.139.32: bytes=32 time=79ms TTL=51 Reply from 157.185.139.32: bytes=32 time=77ms TTL=51 Reply from 157.185.139.32: bytes=32 time=76ms TTL=51 Reply from 157.185.139.32: bytes=32 time=75ms TTL=51 Reply from 157.185.139.32: bytes=32 time=76ms TTL=51
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 75ms, Maximum = 119ms, Average = 81ms查看 |
GET PING Trace Dig |
|
黑龙江齐齐哈尔市移动 |
移动 |
黑龙江 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
88.888ms |
75.451ms |
80.333ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=83ms TTL=51 Reply from 157.185.139.32: bytes=32 time=79ms TTL=51 Reply from 157.185.139.32: bytes=32 time=79ms TTL=51 Reply from 157.185.139.32: bytes=32 time=80ms TTL=51 Reply from 157.185.139.32: bytes=32 time=80ms TTL=51 Reply from 157.185.139.32: bytes=32 time=75ms TTL=51 Reply from 157.185.139.32: bytes=32 time=80ms TTL=51 Reply from 157.185.139.32: bytes=32 time=89ms TTL=51 Reply from 157.185.139.32: bytes=32 time=82ms TTL=51 Reply from 157.185.139.32: bytes=32 time=77ms TTL=51
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 75ms, Maximum = 89ms, Average = 80ms查看 |
GET PING Trace Dig |
|
辽宁鞍山市移动 |
移动 |
辽宁 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
85.381ms |
74.78ms |
79.024ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=81ms TTL=50 Reply from 157.185.139.32: bytes=32 time=77ms TTL=50 Reply from 157.185.139.32: bytes=32 time=81ms TTL=50 Reply from 157.185.139.32: bytes=32 time=81ms TTL=50 Reply from 157.185.139.32: bytes=32 time=82ms TTL=50 Reply from 157.185.139.32: bytes=32 time=76ms TTL=50 Reply from 157.185.139.32: bytes=32 time=76ms TTL=50 Reply from 157.185.139.32: bytes=32 time=77ms TTL=50 Reply from 157.185.139.32: bytes=32 time=75ms TTL=50 Reply from 157.185.139.32: bytes=32 time=85ms TTL=50
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 75ms, Maximum = 85ms, Average = 79ms查看 |
GET PING Trace Dig |
|
吉林长春市移动 |
移动 |
吉林 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
104.487ms |
74.497ms |
78.992ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=76ms TTL=51 Reply from 157.185.139.32: bytes=32 time=104ms TTL=51 Reply from 157.185.139.32: bytes=32 time=75ms TTL=51 Reply from 157.185.139.32: bytes=32 time=76ms TTL=51 Reply from 157.185.139.32: bytes=32 time=75ms TTL=51 Reply from 157.185.139.32: bytes=32 time=77ms TTL=51 Reply from 157.185.139.32: bytes=32 time=76ms TTL=51 Reply from 157.185.139.32: bytes=32 time=79ms TTL=51 Reply from 157.185.139.32: bytes=32 time=74ms TTL=51 Reply from 157.185.139.32: bytes=32 time=77ms TTL=51
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 74ms, Maximum = 104ms, Average = 79ms查看 |
GET PING Trace Dig |
|
甘肃武威市移动 |
移动 |
甘肃 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
81.581ms |
75.661ms |
77.172ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=77ms TTL=48 Reply from 157.185.139.32: bytes=32 time=78ms TTL=48 Reply from 157.185.139.32: bytes=32 time=77ms TTL=48 Reply from 157.185.139.32: bytes=32 time=82ms TTL=48 Reply from 157.185.139.32: bytes=32 time=77ms TTL=48 Reply from 157.185.139.32: bytes=32 time=76ms TTL=48 Reply from 157.185.139.32: bytes=32 time=77ms TTL=48 Reply from 157.185.139.32: bytes=32 time=77ms TTL=48 Reply from 157.185.139.32: bytes=32 time=77ms TTL=48 Reply from 157.185.139.32: bytes=32 time=76ms TTL=48
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 76ms, Maximum = 82ms, Average = 77ms查看 |
GET PING Trace Dig |
|
甘肃庆阳联通 |
联通 |
甘肃 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
81.113ms |
74.788ms |
76.839ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=78ms TTL=49 Reply from 157.185.139.32: bytes=32 time=76ms TTL=49 Reply from 157.185.139.32: bytes=32 time=75ms TTL=49 Reply from 157.185.139.32: bytes=32 time=77ms TTL=49 Reply from 157.185.139.32: bytes=32 time=81ms TTL=49 Reply from 157.185.139.32: bytes=32 time=77ms TTL=49 Reply from 157.185.139.32: bytes=32 time=76ms TTL=49 Reply from 157.185.139.32: bytes=32 time=76ms TTL=49 Reply from 157.185.139.32: bytes=32 time=77ms TTL=49 Reply from 157.185.139.32: bytes=32 time=77ms TTL=49
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 75ms, Maximum = 81ms, Average = 77ms查看 |
GET PING Trace Dig |
|
黑龙江牡丹江市电信 |
电信 |
黑龙江 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
82.122ms |
74.64ms |
76.683ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=76ms TTL=48 Reply from 138.113.156.56: bytes=32 time=76ms TTL=48 Reply from 138.113.156.56: bytes=32 time=76ms TTL=48 Reply from 138.113.156.56: bytes=32 time=76ms TTL=48 Reply from 138.113.156.56: bytes=32 time=75ms TTL=48 Reply from 138.113.156.56: bytes=32 time=77ms TTL=48 Reply from 138.113.156.56: bytes=32 time=77ms TTL=48 Reply from 138.113.156.56: bytes=32 time=82ms TTL=48 Reply from 138.113.156.56: bytes=32 time=78ms TTL=48 Reply from 138.113.156.56: bytes=32 time=75ms TTL=48
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 75ms, Maximum = 82ms, Average = 77ms查看 |
GET PING Trace Dig |
|
贵州贵阳市联通 |
联通 |
贵州 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
78.279ms |
74.299ms |
75.353ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=76ms TTL=48 Reply from 138.113.156.56: bytes=32 time=75ms TTL=48 Reply from 138.113.156.56: bytes=32 time=74ms TTL=48 Reply from 138.113.156.56: bytes=32 time=76ms TTL=48 Reply from 138.113.156.56: bytes=32 time=75ms TTL=48 Reply from 138.113.156.56: bytes=32 time=75ms TTL=48 Reply from 138.113.156.56: bytes=32 time=78ms TTL=48 Reply from 138.113.156.56: bytes=32 time=75ms TTL=48 Reply from 138.113.156.56: bytes=32 time=75ms TTL=48 Reply from 138.113.156.56: bytes=32 time=75ms TTL=48
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 74ms, Maximum = 78ms, Average = 75ms查看 |
GET PING Trace Dig |
|
甘肃平凉电信 |
电信 |
甘肃 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
80.293ms |
70.009ms |
74.484ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=70ms TTL=49 Reply from 157.185.139.32: bytes=32 time=74ms TTL=49 Reply from 157.185.139.32: bytes=32 time=78ms TTL=49 Reply from 157.185.139.32: bytes=32 time=73ms TTL=49 Reply from 157.185.139.32: bytes=32 time=79ms TTL=49 Reply from 157.185.139.32: bytes=32 time=73ms TTL=49 Reply from 157.185.139.32: bytes=32 time=71ms TTL=49 Reply from 157.185.139.32: bytes=32 time=76ms TTL=49 Reply from 157.185.139.32: bytes=32 time=72ms TTL=49 Reply from 157.185.139.32: bytes=32 time=80ms TTL=49
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 70ms, Maximum = 80ms, Average = 74ms查看 |
GET PING Trace Dig |
|
辽宁沈阳市移动 |
移动 |
辽宁 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
76.123ms |
71.555ms |
73.223ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=72ms TTL=51 Reply from 157.185.139.32: bytes=32 time=72ms TTL=51 Reply from 157.185.139.32: bytes=32 time=72ms TTL=51 Reply from 157.185.139.32: bytes=32 time=72ms TTL=51 Reply from 157.185.139.32: bytes=32 time=74ms TTL=51 Reply from 157.185.139.32: bytes=32 time=76ms TTL=51 Reply from 157.185.139.32: bytes=32 time=73ms TTL=51 Reply from 157.185.139.32: bytes=32 time=73ms TTL=51 Reply from 157.185.139.32: bytes=32 time=73ms TTL=51 Reply from 157.185.139.32: bytes=32 time=76ms TTL=51
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 72ms, Maximum = 76ms, Average = 73ms查看 |
GET PING Trace Dig |
|
山西运城市移动 |
移动 |
山西 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
75.481ms |
71.161ms |
72.757ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=74ms TTL=51 Reply from 138.113.156.56: bytes=32 time=75ms TTL=51 Reply from 138.113.156.56: bytes=32 time=71ms TTL=51 Reply from 138.113.156.56: bytes=32 time=73ms TTL=51 Reply from 138.113.156.56: bytes=32 time=74ms TTL=51 Reply from 138.113.156.56: bytes=32 time=72ms TTL=51 Reply from 138.113.156.56: bytes=32 time=71ms TTL=51 Reply from 138.113.156.56: bytes=32 time=72ms TTL=51 Reply from 138.113.156.56: bytes=32 time=73ms TTL=51 Reply from 138.113.156.56: bytes=32 time=73ms TTL=51
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 71ms, Maximum = 75ms, Average = 73ms查看 |
GET PING Trace Dig |
|
湖北黄石移动 |
移动 |
湖北 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
115.974ms |
51.965ms |
72.548ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=71ms TTL=48 Reply from 157.185.139.32: bytes=32 time=102ms TTL=48 Reply from 157.185.139.32: bytes=32 time=57ms TTL=48 Reply from 157.185.139.32: bytes=32 time=116ms TTL=48 Reply from 157.185.139.32: bytes=32 time=73ms TTL=48 Reply from 157.185.139.32: bytes=32 time=74ms TTL=48 Reply from 157.185.139.32: bytes=32 time=57ms TTL=48 Reply from 157.185.139.32: bytes=32 time=60ms TTL=48 Reply from 157.185.139.32: bytes=32 time=63ms TTL=48 Reply from 157.185.139.32: bytes=32 time=52ms TTL=48
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 52ms, Maximum = 116ms, Average = 73ms查看 |
GET PING Trace Dig |
|
云南普洱移动 |
移动 |
云南 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
73.43ms |
70.783ms |
72.215ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=73ms TTL=50 Reply from 157.185.139.32: bytes=32 time=73ms TTL=50 Reply from 157.185.139.32: bytes=32 time=72ms TTL=50 Reply from 157.185.139.32: bytes=32 time=73ms TTL=50 Reply from 157.185.139.32: bytes=32 time=72ms TTL=50 Reply from 157.185.139.32: bytes=32 time=73ms TTL=50 Reply from 157.185.139.32: bytes=32 time=72ms TTL=50 Reply from 157.185.139.32: bytes=32 time=71ms TTL=50 Reply from 157.185.139.32: bytes=32 time=71ms TTL=50 Reply from 157.185.139.32: bytes=32 time=72ms TTL=50
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 71ms, Maximum = 73ms, Average = 72ms查看 |
GET PING Trace Dig |
|
陕西安康市移动 |
移动 |
陕西 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
85.36ms |
66.72ms |
71.479ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=74ms TTL=51 Reply from 138.113.156.56: bytes=32 time=67ms TTL=51 Reply from 138.113.156.56: bytes=32 time=68ms TTL=51 Reply from 138.113.156.56: bytes=32 time=72ms TTL=51 Reply from 138.113.156.56: bytes=32 time=85ms TTL=51 Reply from 138.113.156.56: bytes=32 time=67ms TTL=51 Reply from 138.113.156.56: bytes=32 time=73ms TTL=51 Reply from 138.113.156.56: bytes=32 time=68ms TTL=51 Reply from 138.113.156.56: bytes=32 time=68ms TTL=51 Reply from 138.113.156.56: bytes=32 time=74ms TTL=51
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 67ms, Maximum = 85ms, Average = 71ms查看 |
GET PING Trace Dig |
|
重庆重庆市移动 |
移动 |
重庆 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
100.06ms |
55.56ms |
71.135ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=66ms TTL=49 Reply from 138.113.156.56: bytes=32 time=56ms TTL=49 Reply from 138.113.156.56: bytes=32 time=58ms TTL=49 Reply from 138.113.156.56: bytes=32 time=67ms TTL=49 Reply from 138.113.156.56: bytes=32 time=68ms TTL=49 Reply from 138.113.156.56: bytes=32 time=61ms TTL=49 Reply from 138.113.156.56: bytes=32 time=66ms TTL=49 Reply from 138.113.156.56: bytes=32 time=100ms TTL=49 Reply from 138.113.156.56: bytes=32 time=86ms TTL=49 Reply from 138.113.156.56: bytes=32 time=84ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 56ms, Maximum = 100ms, Average = 71ms查看 |
GET PING Trace Dig |
|
内蒙古巴彦淖尔市移动 |
移动 |
内蒙古 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
72.118ms |
69.978ms |
70.877ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=70ms TTL=51 Reply from 157.185.139.32: bytes=32 time=71ms TTL=51 Reply from 157.185.139.32: bytes=32 time=71ms TTL=51 Reply from 157.185.139.32: bytes=32 time=71ms TTL=51 Reply from 157.185.139.32: bytes=32 time=71ms TTL=51 Reply from 157.185.139.32: bytes=32 time=71ms TTL=51 Reply from 157.185.139.32: bytes=32 time=71ms TTL=51 Reply from 157.185.139.32: bytes=32 time=72ms TTL=51 Reply from 157.185.139.32: bytes=32 time=72ms TTL=51 Reply from 157.185.139.32: bytes=32 time=70ms TTL=51
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 70ms, Maximum = 72ms, Average = 71ms查看 |
GET PING Trace Dig |
|
山西吕梁市电信 |
电信 |
山西 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
73.034ms |
69.781ms |
70.856ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=73ms TTL=51 Reply from 138.113.156.56: bytes=32 time=70ms TTL=51 Reply from 138.113.156.56: bytes=32 time=72ms TTL=51 Reply from 138.113.156.56: bytes=32 time=71ms TTL=51 Reply from 138.113.156.56: bytes=32 time=70ms TTL=51 Reply from 138.113.156.56: bytes=32 time=71ms TTL=51 Reply from 138.113.156.56: bytes=32 time=71ms TTL=51 Reply from 138.113.156.56: bytes=32 time=71ms TTL=51 Reply from 138.113.156.56: bytes=32 time=71ms TTL=51 Reply from 138.113.156.56: bytes=32 time=70ms TTL=51
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 70ms, Maximum = 73ms, Average = 71ms查看 |
GET PING Trace Dig |
|
宁夏银川市联通 |
联通 |
宁夏 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
73.467ms |
68.47ms |
70.756ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=70ms TTL=48 Reply from 138.113.156.56: bytes=32 time=73ms TTL=48 Reply from 138.113.156.56: bytes=32 time=70ms TTL=48 Reply from 138.113.156.56: bytes=32 time=73ms TTL=48 Reply from 138.113.156.56: bytes=32 time=68ms TTL=48 Reply from 138.113.156.56: bytes=32 time=71ms TTL=48 Reply from 138.113.156.56: bytes=32 time=70ms TTL=48 Reply from 138.113.156.56: bytes=32 time=71ms TTL=48 Reply from 138.113.156.56: bytes=32 time=71ms TTL=48 Reply from 138.113.156.56: bytes=32 time=71ms TTL=48
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 68ms, Maximum = 73ms, Average = 71ms查看 |
GET PING Trace Dig |
|
内蒙古巴彦淖尔市电信 |
电信 |
内蒙古 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
73.08ms |
68.66ms |
70.304ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=70ms TTL=48 Reply from 138.113.156.56: bytes=32 time=69ms TTL=48 Reply from 138.113.156.56: bytes=32 time=73ms TTL=48 Reply from 138.113.156.56: bytes=32 time=70ms TTL=48 Reply from 138.113.156.56: bytes=32 time=71ms TTL=48 Reply from 138.113.156.56: bytes=32 time=69ms TTL=48 Reply from 138.113.156.56: bytes=32 time=69ms TTL=48 Reply from 138.113.156.56: bytes=32 time=71ms TTL=48 Reply from 138.113.156.56: bytes=32 time=71ms TTL=48 Reply from 138.113.156.56: bytes=32 time=71ms TTL=48
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 69ms, Maximum = 73ms, Average = 70ms查看 |
GET PING Trace Dig |
|
青海西宁市电信 |
电信 |
青海 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
92.633ms |
61.496ms |
69.749ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=62ms TTL=51 Reply from 138.113.156.56: bytes=32 time=65ms TTL=51 Reply from 138.113.156.56: bytes=32 time=73ms TTL=51 Reply from 138.113.156.56: bytes=32 time=74ms TTL=51 Reply from 138.113.156.56: bytes=32 time=63ms TTL=51 Reply from 138.113.156.56: bytes=32 time=93ms TTL=51 Reply from 138.113.156.56: bytes=32 time=78ms TTL=51 Reply from 138.113.156.56: bytes=32 time=65ms TTL=51 Reply from 138.113.156.56: bytes=32 time=63ms TTL=51 Reply from 138.113.156.56: bytes=32 time=61ms TTL=51
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 61ms, Maximum = 93ms, Average = 70ms查看 |
GET PING Trace Dig |
|
河北保定市移动 |
移动 |
河北 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
98.22ms |
61.204ms |
69.507ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=98ms TTL=49 Reply from 157.185.139.32: bytes=32 time=64ms TTL=49 Reply from 157.185.139.32: bytes=32 time=66ms TTL=49 Reply from 157.185.139.32: bytes=32 time=62ms TTL=49 Reply from 157.185.139.32: bytes=32 time=77ms TTL=49 Reply from 157.185.139.32: bytes=32 time=62ms TTL=49 Reply from 157.185.139.32: bytes=32 time=75ms TTL=49 Reply from 157.185.139.32: bytes=32 time=64ms TTL=49 Reply from 157.185.139.32: bytes=32 time=65ms TTL=49 Reply from 157.185.139.32: bytes=32 time=61ms TTL=49
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 61ms, Maximum = 98ms, Average = 70ms查看 |
GET PING Trace Dig |
|
吉林松原市电信 |
电信 |
吉林 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
95.437ms |
60.217ms |
69.33ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=66ms TTL=50 Reply from 138.113.156.56: bytes=32 time=95ms TTL=50 Reply from 138.113.156.56: bytes=32 time=61ms TTL=50 Reply from 138.113.156.56: bytes=32 time=65ms TTL=50 Reply from 138.113.156.56: bytes=32 time=69ms TTL=50 Reply from 138.113.156.56: bytes=32 time=65ms TTL=50 Reply from 138.113.156.56: bytes=32 time=63ms TTL=50 Reply from 138.113.156.56: bytes=32 time=86ms TTL=50 Reply from 138.113.156.56: bytes=32 time=63ms TTL=50 Reply from 138.113.156.56: bytes=32 time=60ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 60ms, Maximum = 95ms, Average = 69ms查看 |
GET PING Trace Dig |
|
黑龙江大庆市联通 |
联通 |
黑龙江 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
71.601ms |
66.841ms |
69.042ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=72ms TTL=48 Reply from 138.113.156.56: bytes=32 time=70ms TTL=48 Reply from 138.113.156.56: bytes=32 time=68ms TTL=48 Reply from 138.113.156.56: bytes=32 time=68ms TTL=48 Reply from 138.113.156.56: bytes=32 time=71ms TTL=48 Reply from 138.113.156.56: bytes=32 time=68ms TTL=48 Reply from 138.113.156.56: bytes=32 time=67ms TTL=48 Reply from 138.113.156.56: bytes=32 time=68ms TTL=48 Reply from 138.113.156.56: bytes=32 time=69ms TTL=48 Reply from 138.113.156.56: bytes=32 time=71ms TTL=48
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 67ms, Maximum = 72ms, Average = 69ms查看 |
GET PING Trace Dig |
|
黑龙江哈尔滨市电信 |
电信 |
黑龙江 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
69.681ms |
67.281ms |
68.386ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=68ms TTL=50 Reply from 138.113.156.56: bytes=32 time=69ms TTL=50 Reply from 138.113.156.56: bytes=32 time=68ms TTL=50 Reply from 138.113.156.56: bytes=32 time=68ms TTL=50 Reply from 138.113.156.56: bytes=32 time=68ms TTL=50 Reply from 138.113.156.56: bytes=32 time=68ms TTL=50 Reply from 138.113.156.56: bytes=32 time=70ms TTL=50 Reply from 138.113.156.56: bytes=32 time=70ms TTL=50 Reply from 138.113.156.56: bytes=32 time=67ms TTL=50 Reply from 138.113.156.56: bytes=32 time=68ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 67ms, Maximum = 70ms, Average = 68ms查看 |
GET PING Trace Dig |
|
黑龙江牡丹江市联通 |
联通 |
黑龙江 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
69.576ms |
66.026ms |
68.294ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=68ms TTL=49 Reply from 157.185.139.32: bytes=32 time=66ms TTL=49 Reply from 157.185.139.32: bytes=32 time=69ms TTL=49 Reply from 157.185.139.32: bytes=32 time=69ms TTL=49 Reply from 157.185.139.32: bytes=32 time=67ms TTL=49 Reply from 157.185.139.32: bytes=32 time=69ms TTL=49 Reply from 157.185.139.32: bytes=32 time=69ms TTL=49 Reply from 157.185.139.32: bytes=32 time=67ms TTL=49 Reply from 157.185.139.32: bytes=32 time=68ms TTL=49 Reply from 157.185.139.32: bytes=32 time=70ms TTL=49
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 66ms, Maximum = 70ms, Average = 68ms查看 |
GET PING Trace Dig |
|
宁夏银川市电信 |
电信 |
宁夏 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
69.54ms |
65.36ms |
67.964ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=69ms TTL=49 Reply from 138.113.156.56: bytes=32 time=70ms TTL=49 Reply from 138.113.156.56: bytes=32 time=67ms TTL=49 Reply from 138.113.156.56: bytes=32 time=65ms TTL=49 Reply from 138.113.156.56: bytes=32 time=69ms TTL=49 Reply from 138.113.156.56: bytes=32 time=69ms TTL=49 Reply from 138.113.156.56: bytes=32 time=68ms TTL=49 Reply from 138.113.156.56: bytes=32 time=68ms TTL=49 Reply from 138.113.156.56: bytes=32 time=68ms TTL=49 Reply from 138.113.156.56: bytes=32 time=68ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 65ms, Maximum = 70ms, Average = 68ms查看 |
GET PING Trace Dig |
|
山西吕梁市移动 |
移动 |
山西 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
70.94ms |
66.4ms |
67.706ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=67ms TTL=51 Reply from 138.113.156.56: bytes=32 time=68ms TTL=51 Reply from 138.113.156.56: bytes=32 time=68ms TTL=51 Reply from 138.113.156.56: bytes=32 time=68ms TTL=51 Reply from 138.113.156.56: bytes=32 time=71ms TTL=51 Reply from 138.113.156.56: bytes=32 time=66ms TTL=51 Reply from 138.113.156.56: bytes=32 time=67ms TTL=51 Reply from 138.113.156.56: bytes=32 time=67ms TTL=51 Reply from 138.113.156.56: bytes=32 time=68ms TTL=51 Reply from 138.113.156.56: bytes=32 time=68ms TTL=51
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 66ms, Maximum = 71ms, Average = 68ms查看 |
GET PING Trace Dig |
|
甘肃兰州市电信 |
电信 |
甘肃 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
73.815ms |
65.277ms |
67.383ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=72ms TTL=49 Reply from 157.185.139.32: bytes=32 time=65ms TTL=49 Reply from 157.185.139.32: bytes=32 time=66ms TTL=49 Reply from 157.185.139.32: bytes=32 time=65ms TTL=49 Reply from 157.185.139.32: bytes=32 time=74ms TTL=49 Reply from 157.185.139.32: bytes=32 time=68ms TTL=49 Reply from 157.185.139.32: bytes=32 time=67ms TTL=49 Reply from 157.185.139.32: bytes=32 time=66ms TTL=49 Reply from 157.185.139.32: bytes=32 time=66ms TTL=49 Reply from 157.185.139.32: bytes=32 time=66ms TTL=49
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 65ms, Maximum = 74ms, Average = 67ms查看 |
GET PING Trace Dig |
|
吉林通化市联通 |
联通 |
吉林 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
70.05ms |
65.81ms |
67.076ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=67ms TTL=50 Reply from 138.113.156.56: bytes=32 time=66ms TTL=50 Reply from 138.113.156.56: bytes=32 time=68ms TTL=50 Reply from 138.113.156.56: bytes=32 time=66ms TTL=50 Reply from 138.113.156.56: bytes=32 time=66ms TTL=50 Reply from 138.113.156.56: bytes=32 time=66ms TTL=50 Reply from 138.113.156.56: bytes=32 time=70ms TTL=50 Reply from 138.113.156.56: bytes=32 time=66ms TTL=50 Reply from 138.113.156.56: bytes=32 time=67ms TTL=50 Reply from 138.113.156.56: bytes=32 time=69ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 66ms, Maximum = 70ms, Average = 67ms查看 |
GET PING Trace Dig |
|
甘肃兰州市移动 |
移动 |
甘肃 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
70.121ms |
64.386ms |
66.653ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=67ms TTL=48 Reply from 157.185.139.32: bytes=32 time=66ms TTL=48 Reply from 157.185.139.32: bytes=32 time=65ms TTL=48 Reply from 157.185.139.32: bytes=32 time=66ms TTL=48 Reply from 157.185.139.32: bytes=32 time=65ms TTL=48 Reply from 157.185.139.32: bytes=32 time=66ms TTL=48 Reply from 157.185.139.32: bytes=32 time=70ms TTL=48 Reply from 157.185.139.32: bytes=32 time=70ms TTL=48 Reply from 157.185.139.32: bytes=32 time=67ms TTL=48 Reply from 157.185.139.32: bytes=32 time=64ms TTL=48
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 64ms, Maximum = 70ms, Average = 67ms查看 |
GET PING Trace Dig |
|
宁夏银川市移动 |
移动 |
宁夏 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
67.418ms |
65.627ms |
66.414ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=67ms TTL=50 Reply from 157.185.139.32: bytes=32 time=67ms TTL=50 Reply from 157.185.139.32: bytes=32 time=66ms TTL=50 Reply from 157.185.139.32: bytes=32 time=66ms TTL=50 Reply from 157.185.139.32: bytes=32 time=66ms TTL=50 Reply from 157.185.139.32: bytes=32 time=67ms TTL=50 Reply from 157.185.139.32: bytes=32 time=67ms TTL=50 Reply from 157.185.139.32: bytes=32 time=66ms TTL=50 Reply from 157.185.139.32: bytes=32 time=67ms TTL=50 Reply from 157.185.139.32: bytes=32 time=67ms TTL=50
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 66ms, Maximum = 67ms, Average = 66ms查看 |
GET PING Trace Dig |
|
陕西渭南市移动 |
移动 |
陕西 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
67.69ms |
63.308ms |
65.077ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=66ms TTL=51 Reply from 138.113.156.56: bytes=32 time=63ms TTL=51 Reply from 138.113.156.56: bytes=32 time=65ms TTL=51 Reply from 138.113.156.56: bytes=32 time=65ms TTL=51 Reply from 138.113.156.56: bytes=32 time=65ms TTL=51 Reply from 138.113.156.56: bytes=32 time=68ms TTL=51 Reply from 138.113.156.56: bytes=32 time=65ms TTL=51 Reply from 138.113.156.56: bytes=32 time=66ms TTL=51 Reply from 138.113.156.56: bytes=32 time=65ms TTL=51 Reply from 138.113.156.56: bytes=32 time=64ms TTL=51
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 63ms, Maximum = 68ms, Average = 65ms查看 |
GET PING Trace Dig |
|
陕西安康市电信 |
电信 |
陕西 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
70.32ms |
61.751ms |
64.732ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=62ms TTL=49 Reply from 138.113.156.56: bytes=32 time=62ms TTL=49 Reply from 138.113.156.56: bytes=32 time=62ms TTL=49 Reply from 138.113.156.56: bytes=32 time=64ms TTL=49 Reply from 138.113.156.56: bytes=32 time=63ms TTL=49 Reply from 138.113.156.56: bytes=32 time=65ms TTL=49 Reply from 138.113.156.56: bytes=32 time=67ms TTL=49 Reply from 138.113.156.56: bytes=32 time=70ms TTL=49 Reply from 138.113.156.56: bytes=32 time=66ms TTL=49 Reply from 138.113.156.56: bytes=32 time=66ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 62ms, Maximum = 70ms, Average = 65ms查看 |
GET PING Trace Dig |
|
吉林长春市联通 |
联通 |
吉林 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
67.737ms |
59.329ms |
63.786ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=62ms TTL=49 Reply from 138.113.156.56: bytes=32 time=66ms TTL=49 Reply from 138.113.156.56: bytes=32 time=66ms TTL=49 Reply from 138.113.156.56: bytes=32 time=64ms TTL=49 Reply from 138.113.156.56: bytes=32 time=59ms TTL=49 Reply from 138.113.156.56: bytes=32 time=67ms TTL=49 Reply from 138.113.156.56: bytes=32 time=68ms TTL=49 Reply from 138.113.156.56: bytes=32 time=62ms TTL=49 Reply from 138.113.156.56: bytes=32 time=64ms TTL=49 Reply from 138.113.156.56: bytes=32 time=59ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 59ms, Maximum = 68ms, Average = 64ms查看 |
GET PING Trace Dig |
|
海南海口联通 |
联通 |
海南 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
65.572ms |
60.288ms |
63.588ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=65ms TTL=47 Reply from 138.113.156.56: bytes=32 time=62ms TTL=47 Reply from 138.113.156.56: bytes=32 time=66ms TTL=47 Reply from 138.113.156.56: bytes=32 time=62ms TTL=47 Reply from 138.113.156.56: bytes=32 time=65ms TTL=47 Reply from 138.113.156.56: bytes=32 time=60ms TTL=47 Reply from 138.113.156.56: bytes=32 time=63ms TTL=47 Reply from 138.113.156.56: bytes=32 time=65ms TTL=47 Reply from 138.113.156.56: bytes=32 time=64ms TTL=47 Reply from 138.113.156.56: bytes=32 time=64ms TTL=47
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 60ms, Maximum = 66ms, Average = 64ms查看 |
GET PING Trace Dig |
|
河南开封市移动 |
移动 |
河南 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
115.121ms |
41.101ms |
62.96ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=50ms TTL=48 Reply from 138.113.156.56: bytes=32 time=59ms TTL=48 Reply from 138.113.156.56: bytes=32 time=74ms TTL=48 Reply from 138.113.156.56: bytes=32 time=50ms TTL=48 Reply from 138.113.156.56: bytes=32 time=62ms TTL=48 Reply from 138.113.156.56: bytes=32 time=57ms TTL=48 Reply from 138.113.156.56: bytes=32 time=115ms TTL=48 Reply from 138.113.156.56: bytes=32 time=41ms TTL=48 Reply from 138.113.156.56: bytes=32 time=74ms TTL=48 Reply from 138.113.156.56: bytes=32 time=48ms TTL=48
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 41ms, Maximum = 115ms, Average = 63ms查看 |
GET PING Trace Dig |
|
辽宁大连市电信 |
电信 |
辽宁 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
66.9ms |
61.38ms |
62.946ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=62ms TTL=49 Reply from 138.113.156.56: bytes=32 time=61ms TTL=49 Reply from 138.113.156.56: bytes=32 time=62ms TTL=49 Reply from 138.113.156.56: bytes=32 time=63ms TTL=49 Reply from 138.113.156.56: bytes=32 time=62ms TTL=49 Reply from 138.113.156.56: bytes=32 time=62ms TTL=49 Reply from 138.113.156.56: bytes=32 time=63ms TTL=49 Reply from 138.113.156.56: bytes=32 time=67ms TTL=49 Reply from 138.113.156.56: bytes=32 time=63ms TTL=49 Reply from 138.113.156.56: bytes=32 time=65ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 61ms, Maximum = 67ms, Average = 63ms查看 |
GET PING Trace Dig |
|
福建莆田市移动 |
移动 |
福建 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
91.055ms |
43.535ms |
62.561ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=82ms TTL=51 Reply from 138.113.156.56: bytes=32 time=61ms TTL=51 Reply from 138.113.156.56: bytes=32 time=75ms TTL=51 Reply from 138.113.156.56: bytes=32 time=60ms TTL=51 Reply from 138.113.156.56: bytes=32 time=69ms TTL=51 Reply from 138.113.156.56: bytes=32 time=91ms TTL=51 Reply from 138.113.156.56: bytes=32 time=45ms TTL=51 Reply from 138.113.156.56: bytes=32 time=54ms TTL=51 Reply from 138.113.156.56: bytes=32 time=45ms TTL=51 Reply from 138.113.156.56: bytes=32 time=44ms TTL=51
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 44ms, Maximum = 91ms, Average = 63ms查看 |
GET PING Trace Dig |
|
台湾台湾 |
台湾 |
台湾 |
140.150.47.68 |
瑞典 |
10 |
10 |
0 |
64.6ms |
61.201ms |
62.53ms |
32B |
PING 9d9032.com PING 9d9032.com (140.150.47.68) with 32 bytes of data: Reply from 140.150.47.68: bytes=32 time=61ms TTL=45 Reply from 140.150.47.68: bytes=32 time=63ms TTL=45 Reply from 140.150.47.68: bytes=32 time=63ms TTL=45 Reply from 140.150.47.68: bytes=32 time=64ms TTL=45 Reply from 140.150.47.68: bytes=32 time=62ms TTL=45 Reply from 140.150.47.68: bytes=32 time=62ms TTL=45 Reply from 140.150.47.68: bytes=32 time=62ms TTL=45 Reply from 140.150.47.68: bytes=32 time=62ms TTL=45 Reply from 140.150.47.68: bytes=32 time=65ms TTL=45 Reply from 140.150.47.68: bytes=32 time=63ms TTL=45
Ping statistics for 140.150.47.68: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 61ms, Maximum = 65ms, Average = 63ms查看 |
GET PING Trace Dig |
|
重庆重庆市移动 |
移动 |
重庆 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
86.953ms |
52.227ms |
62.513ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=55ms TTL=50 Reply from 138.113.156.56: bytes=32 time=62ms TTL=50 Reply from 138.113.156.56: bytes=32 time=57ms TTL=50 Reply from 138.113.156.56: bytes=32 time=85ms TTL=50 Reply from 138.113.156.56: bytes=32 time=54ms TTL=50 Reply from 138.113.156.56: bytes=32 time=52ms TTL=50 Reply from 138.113.156.56: bytes=32 time=56ms TTL=50 Reply from 138.113.156.56: bytes=32 time=54ms TTL=50 Reply from 138.113.156.56: bytes=32 time=87ms TTL=50 Reply from 138.113.156.56: bytes=32 time=63ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 52ms, Maximum = 87ms, Average = 63ms查看 |
GET PING Trace Dig |
|
陕西咸阳市电信 |
电信 |
陕西 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
63.077ms |
59.563ms |
61.298ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=60ms TTL=49 Reply from 138.113.156.56: bytes=32 time=62ms TTL=49 Reply from 138.113.156.56: bytes=32 time=61ms TTL=49 Reply from 138.113.156.56: bytes=32 time=63ms TTL=49 Reply from 138.113.156.56: bytes=32 time=60ms TTL=49 Reply from 138.113.156.56: bytes=32 time=60ms TTL=49 Reply from 138.113.156.56: bytes=32 time=63ms TTL=49 Reply from 138.113.156.56: bytes=32 time=60ms TTL=49 Reply from 138.113.156.56: bytes=32 time=62ms TTL=49 Reply from 138.113.156.56: bytes=32 time=63ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 60ms, Maximum = 63ms, Average = 61ms查看 |
GET PING Trace Dig |
|
上海上海市电信 |
电信 |
上海 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
66.66ms |
56.98ms |
60.246ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=57ms TTL=47 Reply from 138.113.156.56: bytes=32 time=61ms TTL=47 Reply from 138.113.156.56: bytes=32 time=60ms TTL=47 Reply from 138.113.156.56: bytes=32 time=65ms TTL=47 Reply from 138.113.156.56: bytes=32 time=59ms TTL=47 Reply from 138.113.156.56: bytes=32 time=58ms TTL=47 Reply from 138.113.156.56: bytes=32 time=60ms TTL=47 Reply from 138.113.156.56: bytes=32 time=59ms TTL=47 Reply from 138.113.156.56: bytes=32 time=67ms TTL=47 Reply from 138.113.156.56: bytes=32 time=59ms TTL=47
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 57ms, Maximum = 67ms, Average = 60ms查看 |
GET PING Trace Dig |
|
河北衡水电信 |
电信 |
河北 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
73.56ms |
56.58ms |
59.754ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=59ms TTL=49 Reply from 138.113.156.56: bytes=32 time=58ms TTL=49 Reply from 138.113.156.56: bytes=32 time=59ms TTL=49 Reply from 138.113.156.56: bytes=32 time=60ms TTL=49 Reply from 138.113.156.56: bytes=32 time=59ms TTL=49 Reply from 138.113.156.56: bytes=32 time=57ms TTL=49 Reply from 138.113.156.56: bytes=32 time=59ms TTL=49 Reply from 138.113.156.56: bytes=32 time=58ms TTL=49 Reply from 138.113.156.56: bytes=32 time=57ms TTL=49 Reply from 138.113.156.56: bytes=32 time=74ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 57ms, Maximum = 74ms, Average = 60ms查看 |
GET PING Trace Dig |
|
四川成都市移动 |
移动 |
四川 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
65.62ms |
57.6ms |
59.655ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=62ms TTL=48 Reply from 138.113.156.56: bytes=32 time=60ms TTL=48 Reply from 138.113.156.56: bytes=32 time=59ms TTL=48 Reply from 138.113.156.56: bytes=32 time=58ms TTL=48 Reply from 138.113.156.56: bytes=32 time=59ms TTL=48 Reply from 138.113.156.56: bytes=32 time=59ms TTL=48 Reply from 138.113.156.56: bytes=32 time=58ms TTL=48 Reply from 138.113.156.56: bytes=32 time=59ms TTL=48 Reply from 138.113.156.56: bytes=32 time=66ms TTL=48 Reply from 138.113.156.56: bytes=32 time=58ms TTL=48
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 58ms, Maximum = 66ms, Average = 60ms查看 |
GET PING Trace Dig |
|
天津天津市电信 |
电信 |
天津 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
67.924ms |
52.105ms |
59.482ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=67ms TTL=48 Reply from 157.185.139.32: bytes=32 time=60ms TTL=48 Reply from 157.185.139.32: bytes=32 time=57ms TTL=48 Reply from 157.185.139.32: bytes=32 time=60ms TTL=48 Reply from 157.185.139.32: bytes=32 time=55ms TTL=48 Reply from 157.185.139.32: bytes=32 time=58ms TTL=48 Reply from 157.185.139.32: bytes=32 time=61ms TTL=48 Reply from 157.185.139.32: bytes=32 time=57ms TTL=48 Reply from 157.185.139.32: bytes=32 time=52ms TTL=48 Reply from 157.185.139.32: bytes=32 time=68ms TTL=48
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 52ms, Maximum = 68ms, Average = 59ms查看 |
GET PING Trace Dig |
|
山东潍坊市联通 |
联通 |
山东 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
82.98ms |
47.341ms |
57.988ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=65ms TTL=49 Reply from 138.113.156.56: bytes=32 time=55ms TTL=49 Reply from 138.113.156.56: bytes=32 time=83ms TTL=49 Reply from 138.113.156.56: bytes=32 time=61ms TTL=49 Reply from 138.113.156.56: bytes=32 time=48ms TTL=49 Reply from 138.113.156.56: bytes=32 time=57ms TTL=49 Reply from 138.113.156.56: bytes=32 time=60ms TTL=49 Reply from 138.113.156.56: bytes=32 time=47ms TTL=49 Reply from 138.113.156.56: bytes=32 time=49ms TTL=49 Reply from 138.113.156.56: bytes=32 time=55ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 47ms, Maximum = 83ms, Average = 58ms查看 |
GET PING Trace Dig |
|
吉林长春市电信 |
电信 |
吉林 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
63.32ms |
56.001ms |
57.505ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=56ms TTL=49 Reply from 138.113.156.56: bytes=32 time=63ms TTL=49 Reply from 138.113.156.56: bytes=32 time=56ms TTL=49 Reply from 138.113.156.56: bytes=32 time=57ms TTL=49 Reply from 138.113.156.56: bytes=32 time=58ms TTL=49 Reply from 138.113.156.56: bytes=32 time=58ms TTL=49 Reply from 138.113.156.56: bytes=32 time=58ms TTL=49 Reply from 138.113.156.56: bytes=32 time=56ms TTL=49 Reply from 138.113.156.56: bytes=32 time=56ms TTL=49 Reply from 138.113.156.56: bytes=32 time=57ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 56ms, Maximum = 63ms, Average = 58ms查看 |
GET PING Trace Dig |
|
陕西西安市联通 |
联通 |
陕西 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
58.229ms |
55.776ms |
56.67ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=58ms TTL=48 Reply from 138.113.156.56: bytes=32 time=56ms TTL=48 Reply from 138.113.156.56: bytes=32 time=57ms TTL=48 Reply from 138.113.156.56: bytes=32 time=57ms TTL=48 Reply from 138.113.156.56: bytes=32 time=57ms TTL=48 Reply from 138.113.156.56: bytes=32 time=57ms TTL=48 Reply from 138.113.156.56: bytes=32 time=56ms TTL=48 Reply from 138.113.156.56: bytes=32 time=57ms TTL=48 Reply from 138.113.156.56: bytes=32 time=57ms TTL=48 Reply from 138.113.156.56: bytes=32 time=56ms TTL=48
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 56ms, Maximum = 58ms, Average = 57ms查看 |
GET PING Trace Dig |
|
山西朔州市电信 |
电信 |
山西 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
58.05ms |
55.462ms |
56.402ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=58ms TTL=49 Reply from 157.185.139.32: bytes=32 time=58ms TTL=49 Reply from 157.185.139.32: bytes=32 time=56ms TTL=49 Reply from 157.185.139.32: bytes=32 time=56ms TTL=49 Reply from 157.185.139.32: bytes=32 time=56ms TTL=49 Reply from 157.185.139.32: bytes=32 time=56ms TTL=49 Reply from 157.185.139.32: bytes=32 time=55ms TTL=49 Reply from 157.185.139.32: bytes=32 time=56ms TTL=49 Reply from 157.185.139.32: bytes=32 time=56ms TTL=49 Reply from 157.185.139.32: bytes=32 time=57ms TTL=49
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 55ms, Maximum = 58ms, Average = 56ms查看 |
GET PING Trace Dig |
|
山东日照市电信 |
电信 |
山东 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
9 |
1 |
58.891ms |
53.991ms |
56.242ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=55ms TTL=48 Reply from 138.113.156.56: bytes=32 time=59ms TTL=48 Reply from 138.113.156.56: bytes=32 time=58ms TTL=48 Reply from 138.113.156.56: bytes=32 time=54ms TTL=48 Reply from 138.113.156.56: bytes=32 time=58ms TTL=48 Reply from 138.113.156.56: bytes=32 time=56ms TTL=48 Reply from 138.113.156.56: bytes=32 time=54ms TTL=48 Reply from 138.113.156.56: bytes=32 time=56ms TTL=48 Reply from 138.113.156.56: bytes=32 time=56ms TTL=48 Request timed out.
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 9, Lost = 1 (10% loss), Approximate round trip times in milli-seconds: Minimum = 54ms, Maximum = 59ms, Average = 56ms查看 |
GET PING Trace Dig |
|
天津天津市电信 |
电信 |
天津 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
61.804ms |
48.173ms |
55.916ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=55ms TTL=48 Reply from 157.185.139.32: bytes=32 time=60ms TTL=48 Reply from 157.185.139.32: bytes=32 time=55ms TTL=48 Reply from 157.185.139.32: bytes=32 time=50ms TTL=48 Reply from 157.185.139.32: bytes=32 time=54ms TTL=48 Reply from 157.185.139.32: bytes=32 time=48ms TTL=48 Reply from 157.185.139.32: bytes=32 time=62ms TTL=48 Reply from 157.185.139.32: bytes=32 time=56ms TTL=48 Reply from 157.185.139.32: bytes=32 time=59ms TTL=48 Reply from 157.185.139.32: bytes=32 time=61ms TTL=48
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 48ms, Maximum = 62ms, Average = 56ms查看 |
GET PING Trace Dig |
|
北京北京市联通 |
联通 |
北京 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
60.5ms |
51.761ms |
55.601ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=54ms TTL=52 Reply from 138.113.156.56: bytes=32 time=61ms TTL=52 Reply from 138.113.156.56: bytes=32 time=53ms TTL=52 Reply from 138.113.156.56: bytes=32 time=60ms TTL=52 Reply from 138.113.156.56: bytes=32 time=58ms TTL=52 Reply from 138.113.156.56: bytes=32 time=52ms TTL=52 Reply from 138.113.156.56: bytes=32 time=52ms TTL=52 Reply from 138.113.156.56: bytes=32 time=60ms TTL=52 Reply from 138.113.156.56: bytes=32 time=52ms TTL=52 Reply from 138.113.156.56: bytes=32 time=54ms TTL=52
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 52ms, Maximum = 61ms, Average = 56ms查看 |
GET PING Trace Dig |
|
广东深圳市移动 |
移动 |
广东 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
69.66ms |
47.751ms |
54.639ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=50ms TTL=64 Reply from 157.185.139.32: bytes=32 time=50ms TTL=64 Reply from 157.185.139.32: bytes=32 time=70ms TTL=64 Reply from 157.185.139.32: bytes=32 time=60ms TTL=64 Reply from 157.185.139.32: bytes=32 time=48ms TTL=64 Reply from 157.185.139.32: bytes=32 time=54ms TTL=64 Reply from 157.185.139.32: bytes=32 time=50ms TTL=64 Reply from 157.185.139.32: bytes=32 time=57ms TTL=64 Reply from 157.185.139.32: bytes=32 time=58ms TTL=64 Reply from 157.185.139.32: bytes=32 time=50ms TTL=64
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 48ms, Maximum = 70ms, Average = 55ms查看 |
GET PING Trace Dig |
|
河北保定市电信 |
电信 |
河北 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
60.703ms |
52.051ms |
54.46ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=57ms TTL=49 Reply from 157.185.139.32: bytes=32 time=54ms TTL=49 Reply from 157.185.139.32: bytes=32 time=54ms TTL=49 Reply from 157.185.139.32: bytes=32 time=61ms TTL=49 Reply from 157.185.139.32: bytes=32 time=53ms TTL=49 Reply from 157.185.139.32: bytes=32 time=55ms TTL=49 Reply from 157.185.139.32: bytes=32 time=53ms TTL=49 Reply from 157.185.139.32: bytes=32 time=53ms TTL=49 Reply from 157.185.139.32: bytes=32 time=52ms TTL=49 Reply from 157.185.139.32: bytes=32 time=53ms TTL=49
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 52ms, Maximum = 61ms, Average = 54ms查看 |
GET PING Trace Dig |
|
天津天津市移动 |
移动 |
天津 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
64.997ms |
49.417ms |
54.059ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=51ms TTL=51 Reply from 157.185.139.32: bytes=32 time=50ms TTL=51 Reply from 157.185.139.32: bytes=32 time=50ms TTL=51 Reply from 157.185.139.32: bytes=32 time=52ms TTL=51 Reply from 157.185.139.32: bytes=32 time=62ms TTL=51 Reply from 157.185.139.32: bytes=32 time=65ms TTL=51 Reply from 157.185.139.32: bytes=32 time=58ms TTL=51 Reply from 157.185.139.32: bytes=32 time=51ms TTL=51 Reply from 157.185.139.32: bytes=32 time=49ms TTL=51 Reply from 157.185.139.32: bytes=32 time=51ms TTL=51
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 49ms, Maximum = 65ms, Average = 54ms查看 |
GET PING Trace Dig |
|
贵州遵义市电信 |
电信 |
贵州 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
57.53ms |
51.531ms |
53.475ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=53ms TTL=50 Reply from 138.113.156.56: bytes=32 time=52ms TTL=50 Reply from 138.113.156.56: bytes=32 time=53ms TTL=50 Reply from 138.113.156.56: bytes=32 time=52ms TTL=50 Reply from 138.113.156.56: bytes=32 time=58ms TTL=50 Reply from 138.113.156.56: bytes=32 time=54ms TTL=50 Reply from 138.113.156.56: bytes=32 time=52ms TTL=50 Reply from 138.113.156.56: bytes=32 time=53ms TTL=50 Reply from 138.113.156.56: bytes=32 time=54ms TTL=50 Reply from 138.113.156.56: bytes=32 time=56ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 52ms, Maximum = 58ms, Average = 53ms查看 |
GET PING Trace Dig |
|
北京北京市移动 |
移动 |
北京 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
54.652ms |
52.324ms |
53.143ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=52ms TTL=51 Reply from 138.113.156.56: bytes=32 time=54ms TTL=51 Reply from 138.113.156.56: bytes=32 time=52ms TTL=51 Reply from 138.113.156.56: bytes=32 time=53ms TTL=51 Reply from 138.113.156.56: bytes=32 time=53ms TTL=51 Reply from 138.113.156.56: bytes=32 time=54ms TTL=51 Reply from 138.113.156.56: bytes=32 time=53ms TTL=51 Reply from 138.113.156.56: bytes=32 time=53ms TTL=51 Reply from 138.113.156.56: bytes=32 time=55ms TTL=51 Reply from 138.113.156.56: bytes=32 time=53ms TTL=51
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 52ms, Maximum = 55ms, Average = 53ms查看 |
GET PING Trace Dig |
|
云南保山市电信 |
电信 |
云南 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
54.2ms |
52.22ms |
53.133ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=52ms TTL=51 Reply from 138.113.156.56: bytes=32 time=53ms TTL=51 Reply from 138.113.156.56: bytes=32 time=53ms TTL=51 Reply from 138.113.156.56: bytes=32 time=54ms TTL=51 Reply from 138.113.156.56: bytes=32 time=53ms TTL=51 Reply from 138.113.156.56: bytes=32 time=52ms TTL=51 Reply from 138.113.156.56: bytes=32 time=54ms TTL=51 Reply from 138.113.156.56: bytes=32 time=54ms TTL=51 Reply from 138.113.156.56: bytes=32 time=53ms TTL=51 Reply from 138.113.156.56: bytes=32 time=54ms TTL=51
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 52ms, Maximum = 54ms, Average = 53ms查看 |
GET PING Trace Dig |
|
山东济南市移动 |
移动 |
山东 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
53.676ms |
51.575ms |
52.767ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=53ms TTL=45 Reply from 138.113.156.56: bytes=32 time=52ms TTL=45 Reply from 138.113.156.56: bytes=32 time=53ms TTL=45 Reply from 138.113.156.56: bytes=32 time=54ms TTL=45 Reply from 138.113.156.56: bytes=32 time=54ms TTL=45 Reply from 138.113.156.56: bytes=32 time=53ms TTL=45 Reply from 138.113.156.56: bytes=32 time=54ms TTL=45 Reply from 138.113.156.56: bytes=32 time=52ms TTL=45 Reply from 138.113.156.56: bytes=32 time=54ms TTL=45 Reply from 138.113.156.56: bytes=32 time=52ms TTL=45
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 52ms, Maximum = 54ms, Average = 53ms查看 |
GET PING Trace Dig |
|
江西赣州市移动 |
移动 |
江西 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
64.64ms |
40.2ms |
52.244ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=51ms TTL=51 Reply from 138.113.156.56: bytes=32 time=61ms TTL=51 Reply from 138.113.156.56: bytes=32 time=65ms TTL=51 Reply from 138.113.156.56: bytes=32 time=51ms TTL=51 Reply from 138.113.156.56: bytes=32 time=51ms TTL=51 Reply from 138.113.156.56: bytes=32 time=51ms TTL=51 Reply from 138.113.156.56: bytes=32 time=40ms TTL=51 Reply from 138.113.156.56: bytes=32 time=53ms TTL=51 Reply from 138.113.156.56: bytes=32 time=51ms TTL=51 Reply from 138.113.156.56: bytes=32 time=50ms TTL=51
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 40ms, Maximum = 65ms, Average = 52ms查看 |
GET PING Trace Dig |
|
四川达州市电信 |
电信 |
四川 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
53.7ms |
50.781ms |
51.911ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=51ms TTL=49 Reply from 157.185.139.32: bytes=32 time=53ms TTL=49 Reply from 157.185.139.32: bytes=32 time=51ms TTL=49 Reply from 157.185.139.32: bytes=32 time=51ms TTL=49 Reply from 157.185.139.32: bytes=32 time=54ms TTL=49 Reply from 157.185.139.32: bytes=32 time=53ms TTL=49 Reply from 157.185.139.32: bytes=32 time=53ms TTL=49 Reply from 157.185.139.32: bytes=32 time=52ms TTL=49 Reply from 157.185.139.32: bytes=32 time=52ms TTL=49 Reply from 157.185.139.32: bytes=32 time=51ms TTL=49
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 51ms, Maximum = 54ms, Average = 52ms查看 |
GET PING Trace Dig |
|
山东滨州电信 |
电信 |
山东 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
52.908ms |
50.782ms |
51.707ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=51ms TTL=49 Reply from 138.113.156.56: bytes=32 time=51ms TTL=49 Reply from 138.113.156.56: bytes=32 time=53ms TTL=49 Reply from 138.113.156.56: bytes=32 time=52ms TTL=49 Reply from 138.113.156.56: bytes=32 time=51ms TTL=49 Reply from 138.113.156.56: bytes=32 time=51ms TTL=49 Reply from 138.113.156.56: bytes=32 time=53ms TTL=49 Reply from 138.113.156.56: bytes=32 time=51ms TTL=49 Reply from 138.113.156.56: bytes=32 time=52ms TTL=49 Reply from 138.113.156.56: bytes=32 time=52ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 51ms, Maximum = 53ms, Average = 52ms查看 |
GET PING Trace Dig |
|
河北沧州市联通 |
联通 |
河北 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
54.959ms |
48.42ms |
51.164ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=49ms TTL=49 Reply from 138.113.156.56: bytes=32 time=51ms TTL=49 Reply from 138.113.156.56: bytes=32 time=50ms TTL=49 Reply from 138.113.156.56: bytes=32 time=54ms TTL=49 Reply from 138.113.156.56: bytes=32 time=50ms TTL=49 Reply from 138.113.156.56: bytes=32 time=50ms TTL=49 Reply from 138.113.156.56: bytes=32 time=55ms TTL=49 Reply from 138.113.156.56: bytes=32 time=48ms TTL=49 Reply from 138.113.156.56: bytes=32 time=52ms TTL=49 Reply from 138.113.156.56: bytes=32 time=52ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 48ms, Maximum = 55ms, Average = 51ms查看 |
GET PING Trace Dig |
|
安徽亳州市联通 |
联通 |
安徽 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
58.221ms |
47.04ms |
51ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=47ms TTL=50 Reply from 157.185.139.32: bytes=32 time=49ms TTL=50 Reply from 157.185.139.32: bytes=32 time=56ms TTL=50 Reply from 157.185.139.32: bytes=32 time=48ms TTL=50 Reply from 157.185.139.32: bytes=32 time=58ms TTL=50 Reply from 157.185.139.32: bytes=32 time=52ms TTL=50 Reply from 157.185.139.32: bytes=32 time=50ms TTL=50 Reply from 157.185.139.32: bytes=32 time=55ms TTL=50 Reply from 157.185.139.32: bytes=32 time=47ms TTL=50 Reply from 157.185.139.32: bytes=32 time=48ms TTL=50
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 47ms, Maximum = 58ms, Average = 51ms查看 |
GET PING Trace Dig |
|
安徽芜湖市移动 |
移动 |
安徽 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
8 |
2 |
58.621ms |
48.661ms |
50.994ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=50ms TTL=51 Reply from 138.113.156.56: bytes=32 time=50ms TTL=51 Reply from 138.113.156.56: bytes=32 time=50ms TTL=51 Reply from 138.113.156.56: bytes=32 time=49ms TTL=51 Reply from 138.113.156.56: bytes=32 time=52ms TTL=51 Reply from 138.113.156.56: bytes=32 time=59ms TTL=51 Reply from 138.113.156.56: bytes=32 time=50ms TTL=51 Request timed out. Request timed out. Reply from 138.113.156.56: bytes=32 time=49ms TTL=51
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 8, Lost = 2 (20% loss), Approximate round trip times in milli-seconds: Minimum = 49ms, Maximum = 59ms, Average = 51ms查看 |
GET PING Trace Dig |
|
湖北孝感市电信 |
电信 |
湖北 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
55.48ms |
48.72ms |
50.911ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=55ms TTL=49 Reply from 157.185.139.32: bytes=32 time=50ms TTL=49 Reply from 157.185.139.32: bytes=32 time=50ms TTL=49 Reply from 157.185.139.32: bytes=32 time=50ms TTL=49 Reply from 157.185.139.32: bytes=32 time=51ms TTL=49 Reply from 157.185.139.32: bytes=32 time=55ms TTL=49 Reply from 157.185.139.32: bytes=32 time=49ms TTL=49 Reply from 157.185.139.32: bytes=32 time=49ms TTL=49 Reply from 157.185.139.32: bytes=32 time=50ms TTL=49 Reply from 157.185.139.32: bytes=32 time=50ms TTL=49
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 49ms, Maximum = 55ms, Average = 51ms查看 |
GET PING Trace Dig |
|
四川成都市联通 |
联通 |
四川 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
51.891ms |
49.787ms |
50.868ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=51ms TTL=47 Reply from 138.113.156.56: bytes=32 time=51ms TTL=47 Reply from 138.113.156.56: bytes=32 time=51ms TTL=47 Reply from 138.113.156.56: bytes=32 time=51ms TTL=47 Reply from 138.113.156.56: bytes=32 time=52ms TTL=47 Reply from 138.113.156.56: bytes=32 time=51ms TTL=47 Reply from 138.113.156.56: bytes=32 time=52ms TTL=47 Reply from 138.113.156.56: bytes=32 time=51ms TTL=47 Reply from 138.113.156.56: bytes=32 time=51ms TTL=47 Reply from 138.113.156.56: bytes=32 time=50ms TTL=47
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 50ms, Maximum = 52ms, Average = 51ms查看 |
GET PING Trace Dig |
|
山西长治市联通 |
联通 |
山西 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
52.78ms |
48.96ms |
50.746ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=50ms TTL=50 Reply from 138.113.156.56: bytes=32 time=50ms TTL=50 Reply from 138.113.156.56: bytes=32 time=49ms TTL=50 Reply from 138.113.156.56: bytes=32 time=50ms TTL=50 Reply from 138.113.156.56: bytes=32 time=51ms TTL=50 Reply from 138.113.156.56: bytes=32 time=53ms TTL=50 Reply from 138.113.156.56: bytes=32 time=50ms TTL=50 Reply from 138.113.156.56: bytes=32 time=51ms TTL=50 Reply from 138.113.156.56: bytes=32 time=52ms TTL=50 Reply from 138.113.156.56: bytes=32 time=52ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 49ms, Maximum = 53ms, Average = 51ms查看 |
GET PING Trace Dig |
|
香港香港 |
香港 |
香港 |
138.113.43.11 |
日本东京QuantilNetworks |
10 |
10 |
0 |
52.067ms |
49.579ms |
50.41ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.43.11) with 32 bytes of data: Reply from 138.113.43.11: bytes=32 time=51ms TTL=52 Reply from 138.113.43.11: bytes=32 time=51ms TTL=52 Reply from 138.113.43.11: bytes=32 time=50ms TTL=52 Reply from 138.113.43.11: bytes=32 time=51ms TTL=52 Reply from 138.113.43.11: bytes=32 time=50ms TTL=52 Reply from 138.113.43.11: bytes=32 time=50ms TTL=52 Reply from 138.113.43.11: bytes=32 time=52ms TTL=52 Reply from 138.113.43.11: bytes=32 time=50ms TTL=52 Reply from 138.113.43.11: bytes=32 time=51ms TTL=52 Reply from 138.113.43.11: bytes=32 time=50ms TTL=52
Ping statistics for 138.113.43.11: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 50ms, Maximum = 52ms, Average = 50ms查看 |
GET PING Trace Dig |
|
香港香港 |
香港 |
香港 |
138.113.43.11 |
日本东京QuantilNetworks |
10 |
10 |
0 |
50.843ms |
49.938ms |
50.388ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.43.11) with 32 bytes of data: Reply from 138.113.43.11: bytes=32 time=51ms TTL=50 Reply from 138.113.43.11: bytes=32 time=50ms TTL=50 Reply from 138.113.43.11: bytes=32 time=50ms TTL=50 Reply from 138.113.43.11: bytes=32 time=51ms TTL=50 Reply from 138.113.43.11: bytes=32 time=50ms TTL=50 Reply from 138.113.43.11: bytes=32 time=50ms TTL=50 Reply from 138.113.43.11: bytes=32 time=51ms TTL=50 Reply from 138.113.43.11: bytes=32 time=50ms TTL=50 Reply from 138.113.43.11: bytes=32 time=51ms TTL=50 Reply from 138.113.43.11: bytes=32 time=50ms TTL=50
Ping statistics for 138.113.43.11: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 50ms, Maximum = 51ms, Average = 50ms查看 |
GET PING Trace Dig |
|
甘肃兰州市联通 |
联通 |
甘肃 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
56.759ms |
48.539ms |
50.19ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=49ms TTL=43 Reply from 138.113.156.56: bytes=32 time=49ms TTL=43 Reply from 138.113.156.56: bytes=32 time=51ms TTL=43 Reply from 138.113.156.56: bytes=32 time=49ms TTL=43 Reply from 138.113.156.56: bytes=32 time=57ms TTL=43 Reply from 138.113.156.56: bytes=32 time=51ms TTL=43 Reply from 138.113.156.56: bytes=32 time=50ms TTL=43 Reply from 138.113.156.56: bytes=32 time=49ms TTL=43 Reply from 138.113.156.56: bytes=32 time=49ms TTL=43 Reply from 138.113.156.56: bytes=32 time=50ms TTL=43
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 49ms, Maximum = 57ms, Average = 50ms查看 |
GET PING Trace Dig |
|
安徽宣城市电信 |
电信 |
安徽 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
51.74ms |
48.64ms |
49.683ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=49ms TTL=47 Reply from 157.185.139.32: bytes=32 time=52ms TTL=47 Reply from 157.185.139.32: bytes=32 time=50ms TTL=47 Reply from 157.185.139.32: bytes=32 time=50ms TTL=47 Reply from 157.185.139.32: bytes=32 time=49ms TTL=47 Reply from 157.185.139.32: bytes=32 time=51ms TTL=47 Reply from 157.185.139.32: bytes=32 time=49ms TTL=47 Reply from 157.185.139.32: bytes=32 time=49ms TTL=47 Reply from 157.185.139.32: bytes=32 time=50ms TTL=47 Reply from 157.185.139.32: bytes=32 time=50ms TTL=47
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 49ms, Maximum = 52ms, Average = 50ms查看 |
GET PING Trace Dig |
|
河南洛阳市电信 |
电信 |
河南 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
50.629ms |
48.936ms |
49.631ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=49ms TTL=46 Reply from 138.113.156.56: bytes=32 time=50ms TTL=46 Reply from 138.113.156.56: bytes=32 time=49ms TTL=46 Reply from 138.113.156.56: bytes=32 time=51ms TTL=46 Reply from 138.113.156.56: bytes=32 time=49ms TTL=46 Reply from 138.113.156.56: bytes=32 time=49ms TTL=46 Reply from 138.113.156.56: bytes=32 time=49ms TTL=46 Reply from 138.113.156.56: bytes=32 time=50ms TTL=46 Reply from 138.113.156.56: bytes=32 time=50ms TTL=46 Reply from 138.113.156.56: bytes=32 time=50ms TTL=46
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 49ms, Maximum = 51ms, Average = 50ms查看 |
GET PING Trace Dig |
|
山东济南市移动 |
移动 |
山东 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
9 |
1 |
52.451ms |
0ms |
49.612ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Request timed out. Reply from 157.185.139.32: bytes=32 time=49ms TTL=50 Reply from 157.185.139.32: bytes=32 time=48ms TTL=50 Reply from 157.185.139.32: bytes=32 time=49ms TTL=50 Reply from 157.185.139.32: bytes=32 time=50ms TTL=50 Reply from 157.185.139.32: bytes=32 time=52ms TTL=50 Reply from 157.185.139.32: bytes=32 time=49ms TTL=50 Reply from 157.185.139.32: bytes=32 time=52ms TTL=50 Reply from 157.185.139.32: bytes=32 time=48ms TTL=50 Reply from 157.185.139.32: bytes=32 time=50ms TTL=50
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 9, Lost = 1 (10% loss), Approximate round trip times in milli-seconds: Minimum <1ms , Maximum = 52ms, Average = 50ms查看 |
GET PING Trace Dig |
|
浙江丽水市移动 |
移动 |
浙江 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
52.8ms |
45.761ms |
48.636ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=48ms TTL=52 Reply from 138.113.156.56: bytes=32 time=48ms TTL=52 Reply from 138.113.156.56: bytes=32 time=53ms TTL=52 Reply from 138.113.156.56: bytes=32 time=52ms TTL=52 Reply from 138.113.156.56: bytes=32 time=48ms TTL=52 Reply from 138.113.156.56: bytes=32 time=48ms TTL=52 Reply from 138.113.156.56: bytes=32 time=46ms TTL=52 Reply from 138.113.156.56: bytes=32 time=48ms TTL=52 Reply from 138.113.156.56: bytes=32 time=50ms TTL=52 Reply from 138.113.156.56: bytes=32 time=47ms TTL=52
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 46ms, Maximum = 53ms, Average = 49ms查看 |
GET PING Trace Dig |
|
云南昆明市联通 |
联通 |
云南 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
49.889ms |
47.709ms |
48.583ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=49ms TTL=51 Reply from 138.113.156.56: bytes=32 time=48ms TTL=51 Reply from 138.113.156.56: bytes=32 time=48ms TTL=51 Reply from 138.113.156.56: bytes=32 time=48ms TTL=51 Reply from 138.113.156.56: bytes=32 time=49ms TTL=51 Reply from 138.113.156.56: bytes=32 time=49ms TTL=51 Reply from 138.113.156.56: bytes=32 time=49ms TTL=51 Reply from 138.113.156.56: bytes=32 time=50ms TTL=51 Reply from 138.113.156.56: bytes=32 time=49ms TTL=51 Reply from 138.113.156.56: bytes=32 time=48ms TTL=51
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 48ms, Maximum = 50ms, Average = 49ms查看 |
GET PING Trace Dig |
|
湖南湘潭市电信 |
电信 |
湖南 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
55.44ms |
41.92ms |
48.572ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=43ms TTL=50 Reply from 157.185.139.32: bytes=32 time=45ms TTL=50 Reply from 157.185.139.32: bytes=32 time=52ms TTL=50 Reply from 157.185.139.32: bytes=32 time=54ms TTL=50 Reply from 157.185.139.32: bytes=32 time=45ms TTL=50 Reply from 157.185.139.32: bytes=32 time=50ms TTL=50 Reply from 157.185.139.32: bytes=32 time=55ms TTL=50 Reply from 157.185.139.32: bytes=32 time=51ms TTL=50 Reply from 157.185.139.32: bytes=32 time=47ms TTL=50 Reply from 157.185.139.32: bytes=32 time=42ms TTL=50
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 42ms, Maximum = 55ms, Average = 49ms查看 |
GET PING Trace Dig |
|
福建泉州市电信 |
电信 |
福建 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
52.168ms |
46.325ms |
47.839ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=47ms TTL=48 Reply from 157.185.139.32: bytes=32 time=47ms TTL=48 Reply from 157.185.139.32: bytes=32 time=48ms TTL=48 Reply from 157.185.139.32: bytes=32 time=47ms TTL=48 Reply from 157.185.139.32: bytes=32 time=48ms TTL=48 Reply from 157.185.139.32: bytes=32 time=47ms TTL=48 Reply from 157.185.139.32: bytes=32 time=46ms TTL=48 Reply from 157.185.139.32: bytes=32 time=47ms TTL=48 Reply from 157.185.139.32: bytes=32 time=48ms TTL=48 Reply from 157.185.139.32: bytes=32 time=52ms TTL=48
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 46ms, Maximum = 52ms, Average = 48ms查看 |
GET PING Trace Dig |
|
湖北黄冈市电信 |
电信 |
湖北 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
51.039ms |
45.54ms |
47.045ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=48ms TTL=49 Reply from 157.185.139.32: bytes=32 time=47ms TTL=49 Reply from 157.185.139.32: bytes=32 time=46ms TTL=49 Reply from 157.185.139.32: bytes=32 time=51ms TTL=49 Reply from 157.185.139.32: bytes=32 time=47ms TTL=49 Reply from 157.185.139.32: bytes=32 time=46ms TTL=49 Reply from 157.185.139.32: bytes=32 time=48ms TTL=49 Reply from 157.185.139.32: bytes=32 time=46ms TTL=49 Reply from 157.185.139.32: bytes=32 time=47ms TTL=49 Reply from 157.185.139.32: bytes=32 time=46ms TTL=49
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 46ms, Maximum = 51ms, Average = 47ms查看 |
GET PING Trace Dig |
|
安徽合肥市移动 |
移动 |
安徽 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
49.44ms |
45.34ms |
46.526ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=49ms TTL=50 Reply from 157.185.139.32: bytes=32 time=45ms TTL=50 Reply from 157.185.139.32: bytes=32 time=46ms TTL=50 Reply from 157.185.139.32: bytes=32 time=47ms TTL=50 Reply from 157.185.139.32: bytes=32 time=47ms TTL=50 Reply from 157.185.139.32: bytes=32 time=46ms TTL=50 Reply from 157.185.139.32: bytes=32 time=46ms TTL=50 Reply from 157.185.139.32: bytes=32 time=47ms TTL=50 Reply from 157.185.139.32: bytes=32 time=47ms TTL=50 Reply from 157.185.139.32: bytes=32 time=47ms TTL=50
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 45ms, Maximum = 49ms, Average = 47ms查看 |
GET PING Trace Dig |
|
贵州黔南布依族苗族自治州移动 |
移动 |
贵州 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
57.416ms |
42.43ms |
46.473ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=45ms TTL=51 Reply from 138.113.156.56: bytes=32 time=45ms TTL=51 Reply from 138.113.156.56: bytes=32 time=44ms TTL=51 Reply from 138.113.156.56: bytes=32 time=45ms TTL=51 Reply from 138.113.156.56: bytes=32 time=44ms TTL=51 Reply from 138.113.156.56: bytes=32 time=46ms TTL=51 Reply from 138.113.156.56: bytes=32 time=49ms TTL=51 Reply from 138.113.156.56: bytes=32 time=48ms TTL=51 Reply from 138.113.156.56: bytes=32 time=57ms TTL=51 Reply from 138.113.156.56: bytes=32 time=42ms TTL=51
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 42ms, Maximum = 57ms, Average = 46ms查看 |
GET PING Trace Dig |
|
天津天津市联通 |
联通 |
天津 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
48.648ms |
44.613ms |
46.271ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=46ms TTL=49 Reply from 157.185.139.32: bytes=32 time=49ms TTL=49 Reply from 157.185.139.32: bytes=32 time=46ms TTL=49 Reply from 157.185.139.32: bytes=32 time=45ms TTL=49 Reply from 157.185.139.32: bytes=32 time=47ms TTL=49 Reply from 157.185.139.32: bytes=32 time=45ms TTL=49 Reply from 157.185.139.32: bytes=32 time=48ms TTL=49 Reply from 157.185.139.32: bytes=32 time=46ms TTL=49 Reply from 157.185.139.32: bytes=32 time=46ms TTL=49 Reply from 157.185.139.32: bytes=32 time=45ms TTL=49
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 45ms, Maximum = 49ms, Average = 46ms查看 |
GET PING Trace Dig |
|
福建漳州市移动 |
移动 |
福建 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
53.34ms |
42.64ms |
46.052ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=46ms TTL=48 Reply from 138.113.156.56: bytes=32 time=53ms TTL=48 Reply from 138.113.156.56: bytes=32 time=53ms TTL=48 Reply from 138.113.156.56: bytes=32 time=44ms TTL=48 Reply from 138.113.156.56: bytes=32 time=45ms TTL=48 Reply from 138.113.156.56: bytes=32 time=43ms TTL=48 Reply from 138.113.156.56: bytes=32 time=45ms TTL=48 Reply from 138.113.156.56: bytes=32 time=44ms TTL=48 Reply from 138.113.156.56: bytes=32 time=43ms TTL=48 Reply from 138.113.156.56: bytes=32 time=46ms TTL=48
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 43ms, Maximum = 53ms, Average = 46ms查看 |
GET PING Trace Dig |
|
四川绵阳市电信 |
电信 |
四川 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
47.272ms |
44.75ms |
46.013ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=47ms TTL=44 Reply from 138.113.156.56: bytes=32 time=47ms TTL=44 Reply from 138.113.156.56: bytes=32 time=46ms TTL=44 Reply from 138.113.156.56: bytes=32 time=47ms TTL=44 Reply from 138.113.156.56: bytes=32 time=47ms TTL=44 Reply from 138.113.156.56: bytes=32 time=45ms TTL=44 Reply from 138.113.156.56: bytes=32 time=46ms TTL=44 Reply from 138.113.156.56: bytes=32 time=46ms TTL=44 Reply from 138.113.156.56: bytes=32 time=46ms TTL=44 Reply from 138.113.156.56: bytes=32 time=45ms TTL=44
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 45ms, Maximum = 47ms, Average = 46ms查看 |
GET PING Trace Dig |
|
陕西咸阳市联通 |
联通 |
陕西 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
48.4ms |
44.639ms |
45.995ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=47ms TTL=50 Reply from 138.113.156.56: bytes=32 time=46ms TTL=50 Reply from 138.113.156.56: bytes=32 time=47ms TTL=50 Reply from 138.113.156.56: bytes=32 time=48ms TTL=50 Reply from 138.113.156.56: bytes=32 time=47ms TTL=50 Reply from 138.113.156.56: bytes=32 time=45ms TTL=50 Reply from 138.113.156.56: bytes=32 time=45ms TTL=50 Reply from 138.113.156.56: bytes=32 time=47ms TTL=50 Reply from 138.113.156.56: bytes=32 time=45ms TTL=50 Reply from 138.113.156.56: bytes=32 time=45ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 45ms, Maximum = 48ms, Average = 46ms查看 |
GET PING Trace Dig |
|
福建福州市联通 |
联通 |
福建 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
48.696ms |
44.531ms |
45.956ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=46ms TTL=50 Reply from 138.113.156.56: bytes=32 time=45ms TTL=50 Reply from 138.113.156.56: bytes=32 time=46ms TTL=50 Reply from 138.113.156.56: bytes=32 time=49ms TTL=50 Reply from 138.113.156.56: bytes=32 time=46ms TTL=50 Reply from 138.113.156.56: bytes=32 time=45ms TTL=50 Reply from 138.113.156.56: bytes=32 time=45ms TTL=50 Reply from 138.113.156.56: bytes=32 time=47ms TTL=50 Reply from 138.113.156.56: bytes=32 time=46ms TTL=50 Reply from 138.113.156.56: bytes=32 time=45ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 45ms, Maximum = 49ms, Average = 46ms查看 |
GET PING Trace Dig |
|
江苏泰州市联通 |
联通 |
江苏 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
47.419ms |
44.668ms |
45.892ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=47ms TTL=48 Reply from 138.113.156.56: bytes=32 time=45ms TTL=48 Reply from 138.113.156.56: bytes=32 time=46ms TTL=48 Reply from 138.113.156.56: bytes=32 time=47ms TTL=48 Reply from 138.113.156.56: bytes=32 time=46ms TTL=48 Reply from 138.113.156.56: bytes=32 time=46ms TTL=48 Reply from 138.113.156.56: bytes=32 time=45ms TTL=48 Reply from 138.113.156.56: bytes=32 time=46ms TTL=48 Reply from 138.113.156.56: bytes=32 time=47ms TTL=48 Reply from 138.113.156.56: bytes=32 time=45ms TTL=48
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 45ms, Maximum = 47ms, Average = 46ms查看 |
GET PING Trace Dig |
|
江苏南京联通 |
联通 |
江苏 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
47.18ms |
44.325ms |
45.636ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=45ms TTL=47 Reply from 138.113.156.56: bytes=32 time=45ms TTL=47 Reply from 138.113.156.56: bytes=32 time=47ms TTL=47 Reply from 138.113.156.56: bytes=32 time=44ms TTL=47 Reply from 138.113.156.56: bytes=32 time=45ms TTL=47 Reply from 138.113.156.56: bytes=32 time=46ms TTL=47 Reply from 138.113.156.56: bytes=32 time=47ms TTL=47 Reply from 138.113.156.56: bytes=32 time=46ms TTL=47 Reply from 138.113.156.56: bytes=32 time=45ms TTL=47 Reply from 138.113.156.56: bytes=32 time=46ms TTL=47
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 44ms, Maximum = 47ms, Average = 46ms查看 |
GET PING Trace Dig |
|
浙江台州市电信 |
电信 |
浙江 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
51.896ms |
41.097ms |
45.364ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=49ms TTL=47 Reply from 157.185.139.32: bytes=32 time=43ms TTL=47 Reply from 157.185.139.32: bytes=32 time=43ms TTL=47 Reply from 157.185.139.32: bytes=32 time=43ms TTL=47 Reply from 157.185.139.32: bytes=32 time=41ms TTL=47 Reply from 157.185.139.32: bytes=32 time=45ms TTL=47 Reply from 157.185.139.32: bytes=32 time=52ms TTL=47 Reply from 157.185.139.32: bytes=32 time=43ms TTL=47 Reply from 157.185.139.32: bytes=32 time=46ms TTL=47 Reply from 157.185.139.32: bytes=32 time=49ms TTL=47
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 41ms, Maximum = 52ms, Average = 45ms查看 |
GET PING Trace Dig |
|
福建泉州联通 |
联通 |
福建 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
64.84ms |
37.38ms |
44.964ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=52ms TTL=47 Reply from 157.185.139.32: bytes=32 time=40ms TTL=47 Reply from 157.185.139.32: bytes=32 time=45ms TTL=47 Reply from 157.185.139.32: bytes=32 time=37ms TTL=47 Reply from 157.185.139.32: bytes=32 time=41ms TTL=47 Reply from 157.185.139.32: bytes=32 time=39ms TTL=47 Reply from 157.185.139.32: bytes=32 time=38ms TTL=47 Reply from 157.185.139.32: bytes=32 time=42ms TTL=47 Reply from 157.185.139.32: bytes=32 time=51ms TTL=47 Reply from 157.185.139.32: bytes=32 time=65ms TTL=47
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 37ms, Maximum = 65ms, Average = 45ms查看 |
GET PING Trace Dig |
|
江苏宿迁市移动 |
移动 |
江苏 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
45.338ms |
43.578ms |
44.517ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=44ms TTL=49 Reply from 138.113.156.56: bytes=32 time=44ms TTL=49 Reply from 138.113.156.56: bytes=32 time=45ms TTL=49 Reply from 138.113.156.56: bytes=32 time=44ms TTL=49 Reply from 138.113.156.56: bytes=32 time=45ms TTL=49 Reply from 138.113.156.56: bytes=32 time=44ms TTL=49 Reply from 138.113.156.56: bytes=32 time=45ms TTL=49 Reply from 138.113.156.56: bytes=32 time=45ms TTL=49 Reply from 138.113.156.56: bytes=32 time=44ms TTL=49 Reply from 138.113.156.56: bytes=32 time=45ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 44ms, Maximum = 45ms, Average = 45ms查看 |
GET PING Trace Dig |
|
河南洛阳市电信 |
电信 |
河南 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
45.221ms |
42.774ms |
43.918ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=43ms TTL=46 Reply from 138.113.156.56: bytes=32 time=44ms TTL=46 Reply from 138.113.156.56: bytes=32 time=44ms TTL=46 Reply from 138.113.156.56: bytes=32 time=43ms TTL=46 Reply from 138.113.156.56: bytes=32 time=44ms TTL=46 Reply from 138.113.156.56: bytes=32 time=44ms TTL=46 Reply from 138.113.156.56: bytes=32 time=44ms TTL=46 Reply from 138.113.156.56: bytes=32 time=44ms TTL=46 Reply from 138.113.156.56: bytes=32 time=45ms TTL=46 Reply from 138.113.156.56: bytes=32 time=45ms TTL=46
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 43ms, Maximum = 45ms, Average = 44ms查看 |
GET PING Trace Dig |
|
重庆重庆市联通 |
联通 |
重庆 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
46.58ms |
42.42ms |
43.707ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=43ms TTL=50 Reply from 138.113.156.56: bytes=32 time=44ms TTL=50 Reply from 138.113.156.56: bytes=32 time=43ms TTL=50 Reply from 138.113.156.56: bytes=32 time=47ms TTL=50 Reply from 138.113.156.56: bytes=32 time=43ms TTL=50 Reply from 138.113.156.56: bytes=32 time=44ms TTL=50 Reply from 138.113.156.56: bytes=32 time=42ms TTL=50 Reply from 138.113.156.56: bytes=32 time=43ms TTL=50 Reply from 138.113.156.56: bytes=32 time=45ms TTL=50 Reply from 138.113.156.56: bytes=32 time=43ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 42ms, Maximum = 47ms, Average = 44ms查看 |
GET PING Trace Dig |
|
江苏南京市移动 |
移动 |
江苏 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
52.14ms |
40.62ms |
43.509ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=43ms TTL=51 Reply from 138.113.156.56: bytes=32 time=44ms TTL=51 Reply from 138.113.156.56: bytes=32 time=43ms TTL=51 Reply from 138.113.156.56: bytes=32 time=43ms TTL=51 Reply from 138.113.156.56: bytes=32 time=41ms TTL=51 Reply from 138.113.156.56: bytes=32 time=42ms TTL=51 Reply from 138.113.156.56: bytes=32 time=43ms TTL=51 Reply from 138.113.156.56: bytes=32 time=43ms TTL=51 Reply from 138.113.156.56: bytes=32 time=42ms TTL=51 Reply from 138.113.156.56: bytes=32 time=52ms TTL=51
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 41ms, Maximum = 52ms, Average = 44ms查看 |
GET PING Trace Dig |
|
山东泰安联通 |
联通 |
山东 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
47.04ms |
41.561ms |
43.502ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=45ms TTL=49 Reply from 138.113.156.56: bytes=32 time=43ms TTL=49 Reply from 138.113.156.56: bytes=32 time=43ms TTL=49 Reply from 138.113.156.56: bytes=32 time=42ms TTL=49 Reply from 138.113.156.56: bytes=32 time=42ms TTL=49 Reply from 138.113.156.56: bytes=32 time=42ms TTL=49 Reply from 138.113.156.56: bytes=32 time=43ms TTL=49 Reply from 138.113.156.56: bytes=32 time=43ms TTL=49 Reply from 138.113.156.56: bytes=32 time=47ms TTL=49 Reply from 138.113.156.56: bytes=32 time=45ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 42ms, Maximum = 47ms, Average = 44ms查看 |
GET PING Trace Dig |
|
湖南湘潭电信 |
电信 |
湖南 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
52.941ms |
37.701ms |
43.134ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=53ms TTL=48 Reply from 138.113.156.56: bytes=32 time=38ms TTL=48 Reply from 138.113.156.56: bytes=32 time=50ms TTL=48 Reply from 138.113.156.56: bytes=32 time=41ms TTL=48 Reply from 138.113.156.56: bytes=32 time=38ms TTL=48 Reply from 138.113.156.56: bytes=32 time=44ms TTL=48 Reply from 138.113.156.56: bytes=32 time=41ms TTL=48 Reply from 138.113.156.56: bytes=32 time=41ms TTL=48 Reply from 138.113.156.56: bytes=32 time=44ms TTL=48 Reply from 138.113.156.56: bytes=32 time=42ms TTL=48
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 38ms, Maximum = 53ms, Average = 43ms查看 |
GET PING Trace Dig |
|
江西赣州市联通 |
联通 |
江西 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
43.786ms |
41.69ms |
42.518ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=44ms TTL=48 Reply from 157.185.139.32: bytes=32 time=43ms TTL=48 Reply from 157.185.139.32: bytes=32 time=42ms TTL=48 Reply from 157.185.139.32: bytes=32 time=43ms TTL=48 Reply from 157.185.139.32: bytes=32 time=43ms TTL=48 Reply from 157.185.139.32: bytes=32 time=44ms TTL=48 Reply from 157.185.139.32: bytes=32 time=42ms TTL=48 Reply from 157.185.139.32: bytes=32 time=42ms TTL=48 Reply from 157.185.139.32: bytes=32 time=42ms TTL=48 Reply from 157.185.139.32: bytes=32 time=43ms TTL=48
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 42ms, Maximum = 44ms, Average = 43ms查看 |
GET PING Trace Dig |
|
北京北京市联通 |
联通 |
北京 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
43.802ms |
41.613ms |
42.459ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=43ms TTL=49 Reply from 157.185.139.32: bytes=32 time=43ms TTL=49 Reply from 157.185.139.32: bytes=32 time=42ms TTL=49 Reply from 157.185.139.32: bytes=32 time=44ms TTL=49 Reply from 157.185.139.32: bytes=32 time=43ms TTL=49 Reply from 157.185.139.32: bytes=32 time=42ms TTL=49 Reply from 157.185.139.32: bytes=32 time=43ms TTL=49 Reply from 157.185.139.32: bytes=32 time=42ms TTL=49 Reply from 157.185.139.32: bytes=32 time=43ms TTL=49 Reply from 157.185.139.32: bytes=32 time=42ms TTL=49
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 42ms, Maximum = 44ms, Average = 42ms查看 |
GET PING Trace Dig |
|
上海上海市移动 |
移动 |
上海 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
60.213ms |
33.025ms |
42.369ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=36ms TTL=49 Reply from 138.113.156.56: bytes=32 time=50ms TTL=49 Reply from 138.113.156.56: bytes=32 time=33ms TTL=49 Reply from 138.113.156.56: bytes=32 time=40ms TTL=49 Reply from 138.113.156.56: bytes=32 time=60ms TTL=49 Reply from 138.113.156.56: bytes=32 time=41ms TTL=49 Reply from 138.113.156.56: bytes=32 time=39ms TTL=49 Reply from 138.113.156.56: bytes=32 time=46ms TTL=49 Reply from 138.113.156.56: bytes=32 time=43ms TTL=49 Reply from 138.113.156.56: bytes=32 time=35ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 33ms, Maximum = 60ms, Average = 42ms查看 |
GET PING Trace Dig |
|
贵州黔东南苗族侗族自治州移动 |
移动 |
贵州 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
42.983ms |
40.701ms |
41.72ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=43ms TTL=51 Reply from 138.113.156.56: bytes=32 time=42ms TTL=51 Reply from 138.113.156.56: bytes=32 time=42ms TTL=51 Reply from 138.113.156.56: bytes=32 time=41ms TTL=51 Reply from 138.113.156.56: bytes=32 time=41ms TTL=51 Reply from 138.113.156.56: bytes=32 time=42ms TTL=51 Reply from 138.113.156.56: bytes=32 time=43ms TTL=51 Reply from 138.113.156.56: bytes=32 time=42ms TTL=51 Reply from 138.113.156.56: bytes=32 time=41ms TTL=51 Reply from 138.113.156.56: bytes=32 time=42ms TTL=51
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 41ms, Maximum = 43ms, Average = 42ms查看 |
GET PING Trace Dig |
|
河南商丘市移动 |
移动 |
河南 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
43.4ms |
40.66ms |
41.714ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=42ms TTL=50 Reply from 138.113.156.56: bytes=32 time=41ms TTL=50 Reply from 138.113.156.56: bytes=32 time=41ms TTL=50 Reply from 138.113.156.56: bytes=32 time=42ms TTL=50 Reply from 138.113.156.56: bytes=32 time=41ms TTL=50 Reply from 138.113.156.56: bytes=32 time=41ms TTL=50 Reply from 138.113.156.56: bytes=32 time=42ms TTL=50 Reply from 138.113.156.56: bytes=32 time=43ms TTL=50 Reply from 138.113.156.56: bytes=32 time=41ms TTL=50 Reply from 138.113.156.56: bytes=32 time=42ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 41ms, Maximum = 43ms, Average = 42ms查看 |
GET PING Trace Dig |
|
湖南长沙市移动 |
移动 |
湖南 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
44.78ms |
40.58ms |
41.656ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=42ms TTL=50 Reply from 138.113.156.56: bytes=32 time=42ms TTL=50 Reply from 138.113.156.56: bytes=32 time=41ms TTL=50 Reply from 138.113.156.56: bytes=32 time=41ms TTL=50 Reply from 138.113.156.56: bytes=32 time=41ms TTL=50 Reply from 138.113.156.56: bytes=32 time=45ms TTL=50 Reply from 138.113.156.56: bytes=32 time=41ms TTL=50 Reply from 138.113.156.56: bytes=32 time=42ms TTL=50 Reply from 138.113.156.56: bytes=32 time=42ms TTL=50 Reply from 138.113.156.56: bytes=32 time=41ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 41ms, Maximum = 45ms, Average = 42ms查看 |
GET PING Trace Dig |
|
浙江台州市电信 |
电信 |
浙江 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
45.079ms |
35.44ms |
41.488ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=45ms TTL=43 Reply from 157.185.139.32: bytes=32 time=37ms TTL=43 Reply from 157.185.139.32: bytes=32 time=35ms TTL=43 Reply from 157.185.139.32: bytes=32 time=39ms TTL=43 Reply from 157.185.139.32: bytes=32 time=45ms TTL=43 Reply from 157.185.139.32: bytes=32 time=43ms TTL=43 Reply from 157.185.139.32: bytes=32 time=42ms TTL=43 Reply from 157.185.139.32: bytes=32 time=44ms TTL=43 Reply from 157.185.139.32: bytes=32 time=42ms TTL=43 Reply from 157.185.139.32: bytes=32 time=42ms TTL=43
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 35ms, Maximum = 45ms, Average = 41ms查看 |
GET PING Trace Dig |
|
江西南昌市联通 |
联通 |
江西 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
42.84ms |
39.82ms |
41.411ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=41ms TTL=49 Reply from 138.113.156.56: bytes=32 time=43ms TTL=49 Reply from 138.113.156.56: bytes=32 time=42ms TTL=49 Reply from 138.113.156.56: bytes=32 time=43ms TTL=49 Reply from 138.113.156.56: bytes=32 time=41ms TTL=49 Reply from 138.113.156.56: bytes=32 time=41ms TTL=49 Reply from 138.113.156.56: bytes=32 time=43ms TTL=49 Reply from 138.113.156.56: bytes=32 time=42ms TTL=49 Reply from 138.113.156.56: bytes=32 time=40ms TTL=49 Reply from 138.113.156.56: bytes=32 time=41ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 40ms, Maximum = 43ms, Average = 41ms查看 |
GET PING Trace Dig |
|
广西贵港市电信 |
电信 |
广西 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
50.92ms |
33.8ms |
41.18ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=35ms TTL=49 Reply from 157.185.139.32: bytes=32 time=46ms TTL=49 Reply from 157.185.139.32: bytes=32 time=34ms TTL=49 Reply from 157.185.139.32: bytes=32 time=51ms TTL=49 Reply from 157.185.139.32: bytes=32 time=34ms TTL=49 Reply from 157.185.139.32: bytes=32 time=44ms TTL=49 Reply from 157.185.139.32: bytes=32 time=35ms TTL=49 Reply from 157.185.139.32: bytes=32 time=48ms TTL=49 Reply from 157.185.139.32: bytes=32 time=34ms TTL=49 Reply from 157.185.139.32: bytes=32 time=51ms TTL=49
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 34ms, Maximum = 51ms, Average = 41ms查看 |
GET PING Trace Dig |
|
上海上海市电信 |
电信 |
上海 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
52.57ms |
35.46ms |
41.077ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=53ms TTL=45 Reply from 138.113.156.56: bytes=32 time=35ms TTL=45 Reply from 138.113.156.56: bytes=32 time=38ms TTL=45 Reply from 138.113.156.56: bytes=32 time=38ms TTL=45 Reply from 138.113.156.56: bytes=32 time=37ms TTL=45 Reply from 138.113.156.56: bytes=32 time=43ms TTL=45 Reply from 138.113.156.56: bytes=32 time=44ms TTL=45 Reply from 138.113.156.56: bytes=32 time=39ms TTL=45 Reply from 138.113.156.56: bytes=32 time=38ms TTL=45 Reply from 138.113.156.56: bytes=32 time=45ms TTL=45
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 35ms, Maximum = 53ms, Average = 41ms查看 |
GET PING Trace Dig |
|
湖南长沙市联通 |
联通 |
湖南 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
42.121ms |
39.78ms |
40.994ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=42ms TTL=49 Reply from 138.113.156.56: bytes=32 time=40ms TTL=49 Reply from 138.113.156.56: bytes=32 time=41ms TTL=49 Reply from 138.113.156.56: bytes=32 time=41ms TTL=49 Reply from 138.113.156.56: bytes=32 time=42ms TTL=49 Reply from 138.113.156.56: bytes=32 time=40ms TTL=49 Reply from 138.113.156.56: bytes=32 time=41ms TTL=49 Reply from 138.113.156.56: bytes=32 time=41ms TTL=49 Reply from 138.113.156.56: bytes=32 time=41ms TTL=49 Reply from 138.113.156.56: bytes=32 time=42ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 40ms, Maximum = 42ms, Average = 41ms查看 |
GET PING Trace Dig |
|
浙江台州市电信 |
电信 |
浙江 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
41.812ms |
39.285ms |
40.77ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=41ms TTL=48 Reply from 157.185.139.32: bytes=32 time=41ms TTL=48 Reply from 157.185.139.32: bytes=32 time=40ms TTL=48 Reply from 157.185.139.32: bytes=32 time=40ms TTL=48 Reply from 157.185.139.32: bytes=32 time=42ms TTL=48 Reply from 157.185.139.32: bytes=32 time=42ms TTL=48 Reply from 157.185.139.32: bytes=32 time=40ms TTL=48 Reply from 157.185.139.32: bytes=32 time=42ms TTL=48 Reply from 157.185.139.32: bytes=32 time=42ms TTL=48 Reply from 157.185.139.32: bytes=32 time=39ms TTL=48
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 39ms, Maximum = 42ms, Average = 41ms查看 |
GET PING Trace Dig |
|
四川眉山市联通 |
联通 |
四川 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
41.701ms |
39.7ms |
40.665ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=40ms TTL=49 Reply from 157.185.139.32: bytes=32 time=40ms TTL=49 Reply from 157.185.139.32: bytes=32 time=40ms TTL=49 Reply from 157.185.139.32: bytes=32 time=42ms TTL=49 Reply from 157.185.139.32: bytes=32 time=41ms TTL=49 Reply from 157.185.139.32: bytes=32 time=41ms TTL=49 Reply from 157.185.139.32: bytes=32 time=41ms TTL=49 Reply from 157.185.139.32: bytes=32 time=41ms TTL=49 Reply from 157.185.139.32: bytes=32 time=41ms TTL=49 Reply from 157.185.139.32: bytes=32 time=41ms TTL=49
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 40ms, Maximum = 42ms, Average = 41ms查看 |
GET PING Trace Dig |
|
安徽合肥市电信 |
电信 |
安徽 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
43.923ms |
38.071ms |
40.55ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=41ms TTL=47 Reply from 138.113.156.56: bytes=32 time=40ms TTL=47 Reply from 138.113.156.56: bytes=32 time=41ms TTL=47 Reply from 138.113.156.56: bytes=32 time=39ms TTL=47 Reply from 138.113.156.56: bytes=32 time=44ms TTL=47 Reply from 138.113.156.56: bytes=32 time=41ms TTL=47 Reply from 138.113.156.56: bytes=32 time=40ms TTL=47 Reply from 138.113.156.56: bytes=32 time=42ms TTL=47 Reply from 138.113.156.56: bytes=32 time=38ms TTL=47 Reply from 138.113.156.56: bytes=32 time=38ms TTL=47
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 38ms, Maximum = 44ms, Average = 41ms查看 |
GET PING Trace Dig |
|
湖南怀化市移动 |
移动 |
湖南 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
43.25ms |
38.714ms |
40.506ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=42ms TTL=49 Reply from 157.185.139.32: bytes=32 time=43ms TTL=49 Reply from 157.185.139.32: bytes=32 time=40ms TTL=49 Reply from 157.185.139.32: bytes=32 time=41ms TTL=49 Reply from 157.185.139.32: bytes=32 time=39ms TTL=49 Reply from 157.185.139.32: bytes=32 time=39ms TTL=49 Reply from 157.185.139.32: bytes=32 time=43ms TTL=49 Reply from 157.185.139.32: bytes=32 time=39ms TTL=49 Reply from 157.185.139.32: bytes=32 time=40ms TTL=49 Reply from 157.185.139.32: bytes=32 time=40ms TTL=49
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 39ms, Maximum = 43ms, Average = 41ms查看 |
GET PING Trace Dig |
|
上海上海市联通 |
联通 |
上海 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
41.036ms |
38.461ms |
39.662ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=40ms TTL=50 Reply from 138.113.156.56: bytes=32 time=38ms TTL=50 Reply from 138.113.156.56: bytes=32 time=41ms TTL=50 Reply from 138.113.156.56: bytes=32 time=39ms TTL=50 Reply from 138.113.156.56: bytes=32 time=40ms TTL=50 Reply from 138.113.156.56: bytes=32 time=39ms TTL=50 Reply from 138.113.156.56: bytes=32 time=41ms TTL=50 Reply from 138.113.156.56: bytes=32 time=39ms TTL=50 Reply from 138.113.156.56: bytes=32 time=40ms TTL=50 Reply from 138.113.156.56: bytes=32 time=41ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 38ms, Maximum = 41ms, Average = 40ms查看 |
GET PING Trace Dig |
|
重庆重庆市联通 |
联通 |
重庆 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
40.04ms |
37.82ms |
39.046ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=39ms TTL=49 Reply from 138.113.156.56: bytes=32 time=38ms TTL=49 Reply from 138.113.156.56: bytes=32 time=39ms TTL=49 Reply from 138.113.156.56: bytes=32 time=40ms TTL=49 Reply from 138.113.156.56: bytes=32 time=40ms TTL=49 Reply from 138.113.156.56: bytes=32 time=38ms TTL=49 Reply from 138.113.156.56: bytes=32 time=39ms TTL=49 Reply from 138.113.156.56: bytes=32 time=40ms TTL=49 Reply from 138.113.156.56: bytes=32 time=39ms TTL=49 Reply from 138.113.156.56: bytes=32 time=40ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 38ms, Maximum = 40ms, Average = 39ms查看 |
GET PING Trace Dig |
|
河南平顶山市联通 |
联通 |
河南 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
44.44ms |
36.219ms |
38.356ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=44ms TTL=50 Reply from 138.113.156.56: bytes=32 time=36ms TTL=50 Reply from 138.113.156.56: bytes=32 time=37ms TTL=50 Reply from 138.113.156.56: bytes=32 time=37ms TTL=50 Reply from 138.113.156.56: bytes=32 time=37ms TTL=50 Reply from 138.113.156.56: bytes=32 time=37ms TTL=50 Reply from 138.113.156.56: bytes=32 time=37ms TTL=50 Reply from 138.113.156.56: bytes=32 time=36ms TTL=50 Reply from 138.113.156.56: bytes=32 time=37ms TTL=50 Reply from 138.113.156.56: bytes=32 time=44ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 36ms, Maximum = 44ms, Average = 38ms查看 |
GET PING Trace Dig |
|
贵州毕节市联通 |
联通 |
贵州 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
41.562ms |
35.883ms |
37.963ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=39ms TTL=48 Reply from 157.185.139.32: bytes=32 time=36ms TTL=48 Reply from 157.185.139.32: bytes=32 time=37ms TTL=48 Reply from 157.185.139.32: bytes=32 time=42ms TTL=48 Reply from 157.185.139.32: bytes=32 time=38ms TTL=48 Reply from 157.185.139.32: bytes=32 time=37ms TTL=48 Reply from 157.185.139.32: bytes=32 time=40ms TTL=48 Reply from 157.185.139.32: bytes=32 time=38ms TTL=48 Reply from 157.185.139.32: bytes=32 time=37ms TTL=48 Reply from 157.185.139.32: bytes=32 time=37ms TTL=48
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 36ms, Maximum = 42ms, Average = 38ms查看 |
GET PING Trace Dig |
|
河南许昌市联通 |
联通 |
河南 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
39.26ms |
36.64ms |
37.819ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=38ms TTL=50 Reply from 138.113.156.56: bytes=32 time=39ms TTL=50 Reply from 138.113.156.56: bytes=32 time=39ms TTL=50 Reply from 138.113.156.56: bytes=32 time=37ms TTL=50 Reply from 138.113.156.56: bytes=32 time=38ms TTL=50 Reply from 138.113.156.56: bytes=32 time=38ms TTL=50 Reply from 138.113.156.56: bytes=32 time=37ms TTL=50 Reply from 138.113.156.56: bytes=32 time=37ms TTL=50 Reply from 138.113.156.56: bytes=32 time=38ms TTL=50 Reply from 138.113.156.56: bytes=32 time=38ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 37ms, Maximum = 39ms, Average = 38ms查看 |
GET PING Trace Dig |
|
浙江杭州市联通 |
联通 |
浙江 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
40.083ms |
36.683ms |
37.766ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=38ms TTL=52 Reply from 138.113.156.56: bytes=32 time=37ms TTL=52 Reply from 138.113.156.56: bytes=32 time=38ms TTL=52 Reply from 138.113.156.56: bytes=32 time=37ms TTL=52 Reply from 138.113.156.56: bytes=32 time=37ms TTL=52 Reply from 138.113.156.56: bytes=32 time=37ms TTL=52 Reply from 138.113.156.56: bytes=32 time=38ms TTL=52 Reply from 138.113.156.56: bytes=32 time=39ms TTL=52 Reply from 138.113.156.56: bytes=32 time=40ms TTL=52 Reply from 138.113.156.56: bytes=32 time=37ms TTL=52
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 37ms, Maximum = 40ms, Average = 38ms查看 |
GET PING Trace Dig |
|
澳门澳门 |
澳门 |
澳门 |
140.150.47.68 |
瑞典 |
10 |
10 |
0 |
43.879ms |
35.28ms |
37.172ms |
32B |
PING 9d9032.com PING 9d9032.com (140.150.47.68) with 32 bytes of data: Reply from 140.150.47.68: bytes=32 time=39ms TTL=55 Reply from 140.150.47.68: bytes=32 time=36ms TTL=55 Reply from 140.150.47.68: bytes=32 time=36ms TTL=55 Reply from 140.150.47.68: bytes=32 time=36ms TTL=55 Reply from 140.150.47.68: bytes=32 time=44ms TTL=55 Reply from 140.150.47.68: bytes=32 time=36ms TTL=55 Reply from 140.150.47.68: bytes=32 time=39ms TTL=55 Reply from 140.150.47.68: bytes=32 time=36ms TTL=55 Reply from 140.150.47.68: bytes=32 time=35ms TTL=55 Reply from 140.150.47.68: bytes=32 time=36ms TTL=55
Ping statistics for 140.150.47.68: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 35ms, Maximum = 44ms, Average = 37ms查看 |
GET PING Trace Dig |
|
安徽宿州市联通 |
联通 |
安徽 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
9 |
1 |
41.213ms |
34.576ms |
37.069ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=35ms TTL=49 Reply from 157.185.139.32: bytes=32 time=37ms TTL=49 Reply from 157.185.139.32: bytes=32 time=40ms TTL=49 Reply from 157.185.139.32: bytes=32 time=37ms TTL=49 Request timed out. Reply from 157.185.139.32: bytes=32 time=36ms TTL=49 Reply from 157.185.139.32: bytes=32 time=36ms TTL=49 Reply from 157.185.139.32: bytes=32 time=37ms TTL=49 Reply from 157.185.139.32: bytes=32 time=35ms TTL=49 Reply from 157.185.139.32: bytes=32 time=41ms TTL=49
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 9, Lost = 1 (10% loss), Approximate round trip times in milli-seconds: Minimum = 35ms, Maximum = 41ms, Average = 37ms查看 |
GET PING Trace Dig |
|
上海上海市联通 |
联通 |
上海 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
41.934ms |
33.464ms |
36.547ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=42ms TTL=50 Reply from 138.113.156.56: bytes=32 time=37ms TTL=50 Reply from 138.113.156.56: bytes=32 time=37ms TTL=50 Reply from 138.113.156.56: bytes=32 time=35ms TTL=50 Reply from 138.113.156.56: bytes=32 time=35ms TTL=50 Reply from 138.113.156.56: bytes=32 time=33ms TTL=50 Reply from 138.113.156.56: bytes=32 time=36ms TTL=50 Reply from 138.113.156.56: bytes=32 time=37ms TTL=50 Reply from 138.113.156.56: bytes=32 time=37ms TTL=50 Reply from 138.113.156.56: bytes=32 time=36ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 33ms, Maximum = 42ms, Average = 37ms查看 |
GET PING Trace Dig |
|
上海上海市移动 |
移动 |
上海 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
38.063ms |
34.372ms |
35.578ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=36ms TTL=50 Reply from 138.113.156.56: bytes=32 time=35ms TTL=50 Reply from 138.113.156.56: bytes=32 time=35ms TTL=50 Reply from 138.113.156.56: bytes=32 time=35ms TTL=50 Reply from 138.113.156.56: bytes=32 time=35ms TTL=50 Reply from 138.113.156.56: bytes=32 time=34ms TTL=50 Reply from 138.113.156.56: bytes=32 time=36ms TTL=50 Reply from 138.113.156.56: bytes=32 time=35ms TTL=50 Reply from 138.113.156.56: bytes=32 time=38ms TTL=50 Reply from 138.113.156.56: bytes=32 time=36ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 34ms, Maximum = 38ms, Average = 36ms查看 |
GET PING Trace Dig |
|
浙江嘉兴市联通 |
联通 |
浙江 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
36.603ms |
33.642ms |
34.929ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=35ms TTL=50 Reply from 138.113.156.56: bytes=32 time=34ms TTL=50 Reply from 138.113.156.56: bytes=32 time=34ms TTL=50 Reply from 138.113.156.56: bytes=32 time=35ms TTL=50 Reply from 138.113.156.56: bytes=32 time=35ms TTL=50 Reply from 138.113.156.56: bytes=32 time=36ms TTL=50 Reply from 138.113.156.56: bytes=32 time=36ms TTL=50 Reply from 138.113.156.56: bytes=32 time=34ms TTL=50 Reply from 138.113.156.56: bytes=32 time=37ms TTL=50 Reply from 138.113.156.56: bytes=32 time=36ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 34ms, Maximum = 37ms, Average = 35ms查看 |
GET PING Trace Dig |
|
重庆重庆市电信 |
电信 |
重庆 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
36.951ms |
33.007ms |
34.595ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=34ms TTL=47 Reply from 157.185.139.32: bytes=32 time=35ms TTL=47 Reply from 157.185.139.32: bytes=32 time=35ms TTL=47 Reply from 157.185.139.32: bytes=32 time=33ms TTL=47 Reply from 157.185.139.32: bytes=32 time=33ms TTL=47 Reply from 157.185.139.32: bytes=32 time=36ms TTL=47 Reply from 157.185.139.32: bytes=32 time=37ms TTL=47 Reply from 157.185.139.32: bytes=32 time=34ms TTL=47 Reply from 157.185.139.32: bytes=32 time=36ms TTL=47 Reply from 157.185.139.32: bytes=32 time=34ms TTL=47
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 33ms, Maximum = 37ms, Average = 35ms查看 |
GET PING Trace Dig |
|
广西南宁市移动 |
移动 |
广西 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
44.226ms |
30.645ms |
34.525ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=31ms TTL=49 Reply from 157.185.139.32: bytes=32 time=36ms TTL=49 Reply from 157.185.139.32: bytes=32 time=31ms TTL=49 Reply from 157.185.139.32: bytes=32 time=32ms TTL=49 Reply from 157.185.139.32: bytes=32 time=31ms TTL=49 Reply from 157.185.139.32: bytes=32 time=31ms TTL=49 Reply from 157.185.139.32: bytes=32 time=39ms TTL=49 Reply from 157.185.139.32: bytes=32 time=35ms TTL=49 Reply from 157.185.139.32: bytes=32 time=44ms TTL=49 Reply from 157.185.139.32: bytes=32 time=34ms TTL=49
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 31ms, Maximum = 44ms, Average = 35ms查看 |
GET PING Trace Dig |
|
福建福州市电信 |
电信 |
福建 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
42.08ms |
30.919ms |
33.814ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=37ms TTL=50 Reply from 138.113.156.56: bytes=32 time=31ms TTL=50 Reply from 138.113.156.56: bytes=32 time=42ms TTL=50 Reply from 138.113.156.56: bytes=32 time=34ms TTL=50 Reply from 138.113.156.56: bytes=32 time=31ms TTL=50 Reply from 138.113.156.56: bytes=32 time=32ms TTL=50 Reply from 138.113.156.56: bytes=32 time=31ms TTL=50 Reply from 138.113.156.56: bytes=32 time=35ms TTL=50 Reply from 138.113.156.56: bytes=32 time=34ms TTL=50 Reply from 138.113.156.56: bytes=32 time=32ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 31ms, Maximum = 42ms, Average = 34ms查看 |
GET PING Trace Dig |
|
湖北鄂州市移动 |
移动 |
湖北 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
34.78ms |
32.479ms |
33.515ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=34ms TTL=50 Reply from 138.113.156.56: bytes=32 time=34ms TTL=50 Reply from 138.113.156.56: bytes=32 time=33ms TTL=50 Reply from 138.113.156.56: bytes=32 time=34ms TTL=50 Reply from 138.113.156.56: bytes=32 time=32ms TTL=50 Reply from 138.113.156.56: bytes=32 time=34ms TTL=50 Reply from 138.113.156.56: bytes=32 time=34ms TTL=50 Reply from 138.113.156.56: bytes=32 time=34ms TTL=50 Reply from 138.113.156.56: bytes=32 time=35ms TTL=50 Reply from 138.113.156.56: bytes=32 time=33ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 32ms, Maximum = 35ms, Average = 34ms查看 |
GET PING Trace Dig |
|
湖北孝感市联通 |
联通 |
湖北 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
37.784ms |
30.665ms |
32.224ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=33ms TTL=50 Reply from 138.113.156.56: bytes=32 time=31ms TTL=50 Reply from 138.113.156.56: bytes=32 time=38ms TTL=50 Reply from 138.113.156.56: bytes=32 time=33ms TTL=50 Reply from 138.113.156.56: bytes=32 time=31ms TTL=50 Reply from 138.113.156.56: bytes=32 time=33ms TTL=50 Reply from 138.113.156.56: bytes=32 time=31ms TTL=50 Reply from 138.113.156.56: bytes=32 time=32ms TTL=50 Reply from 138.113.156.56: bytes=32 time=31ms TTL=50 Reply from 138.113.156.56: bytes=32 time=31ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 31ms, Maximum = 38ms, Average = 32ms查看 |
GET PING Trace Dig |
|
意大利国外 |
国外 |
意大利 |
138.113.100.30 |
法国法兰西岛巴黎QuantilNetworks |
10 |
10 |
0 |
40.82ms |
30.56ms |
32.222ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.100.30) with 32 bytes of data: Reply from 138.113.100.30: bytes=32 time=31ms TTL=53 Reply from 138.113.100.30: bytes=32 time=31ms TTL=53 Reply from 138.113.100.30: bytes=32 time=31ms TTL=53 Reply from 138.113.100.30: bytes=32 time=33ms TTL=53 Reply from 138.113.100.30: bytes=32 time=41ms TTL=53 Reply from 138.113.100.30: bytes=32 time=33ms TTL=53 Reply from 138.113.100.30: bytes=32 time=31ms TTL=53 Reply from 138.113.100.30: bytes=32 time=31ms TTL=53 Reply from 138.113.100.30: bytes=32 time=31ms TTL=53 Reply from 138.113.100.30: bytes=32 time=31ms TTL=53
Ping statistics for 138.113.100.30: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 31ms, Maximum = 41ms, Average = 32ms查看 |
GET PING Trace Dig |
|
海南海口移动 |
移动 |
海南 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
33.13ms |
30.371ms |
31.674ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=33ms TTL=50 Reply from 157.185.139.32: bytes=32 time=32ms TTL=50 Reply from 157.185.139.32: bytes=32 time=32ms TTL=50 Reply from 157.185.139.32: bytes=32 time=31ms TTL=50 Reply from 157.185.139.32: bytes=32 time=30ms TTL=50 Reply from 157.185.139.32: bytes=32 time=31ms TTL=50 Reply from 157.185.139.32: bytes=32 time=33ms TTL=50 Reply from 157.185.139.32: bytes=32 time=32ms TTL=50 Reply from 157.185.139.32: bytes=32 time=32ms TTL=50 Reply from 157.185.139.32: bytes=32 time=32ms TTL=50
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 30ms, Maximum = 33ms, Average = 32ms查看 |
GET PING Trace Dig |
|
海南陵水黎族自治县电信 |
电信 |
海南 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
37.924ms |
27.759ms |
31.563ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=29ms TTL=50 Reply from 157.185.139.32: bytes=32 time=29ms TTL=50 Reply from 157.185.139.32: bytes=32 time=37ms TTL=50 Reply from 157.185.139.32: bytes=32 time=38ms TTL=50 Reply from 157.185.139.32: bytes=32 time=30ms TTL=50 Reply from 157.185.139.32: bytes=32 time=29ms TTL=50 Reply from 157.185.139.32: bytes=32 time=28ms TTL=50 Reply from 157.185.139.32: bytes=32 time=32ms TTL=50 Reply from 157.185.139.32: bytes=32 time=28ms TTL=50 Reply from 157.185.139.32: bytes=32 time=36ms TTL=50
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 28ms, Maximum = 38ms, Average = 32ms查看 |
GET PING Trace Dig |
|
广西北海市联通 |
联通 |
广西 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
31.688ms |
28.79ms |
29.762ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=31ms TTL=49 Reply from 157.185.139.32: bytes=32 time=30ms TTL=49 Reply from 157.185.139.32: bytes=32 time=29ms TTL=49 Reply from 157.185.139.32: bytes=32 time=30ms TTL=49 Reply from 157.185.139.32: bytes=32 time=29ms TTL=49 Reply from 157.185.139.32: bytes=32 time=29ms TTL=49 Reply from 157.185.139.32: bytes=32 time=30ms TTL=49 Reply from 157.185.139.32: bytes=32 time=30ms TTL=49 Reply from 157.185.139.32: bytes=32 time=29ms TTL=49 Reply from 157.185.139.32: bytes=32 time=32ms TTL=49
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 29ms, Maximum = 32ms, Average = 30ms查看 |
GET PING Trace Dig |
|
广西南宁市联通 |
联通 |
广西 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
30.89ms |
28.454ms |
29.56ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=30ms TTL=45 Reply from 157.185.139.32: bytes=32 time=30ms TTL=45 Reply from 157.185.139.32: bytes=32 time=29ms TTL=45 Reply from 157.185.139.32: bytes=32 time=28ms TTL=45 Reply from 157.185.139.32: bytes=32 time=30ms TTL=45 Reply from 157.185.139.32: bytes=32 time=31ms TTL=45 Reply from 157.185.139.32: bytes=32 time=30ms TTL=45 Reply from 157.185.139.32: bytes=32 time=30ms TTL=45 Reply from 157.185.139.32: bytes=32 time=29ms TTL=45 Reply from 157.185.139.32: bytes=32 time=30ms TTL=45
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 28ms, Maximum = 31ms, Average = 30ms查看 |
GET PING Trace Dig |
|
贵州贵阳电信 |
电信 |
贵州 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
29.629ms |
26.733ms |
27.978ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=29ms TTL=48 Reply from 157.185.139.32: bytes=32 time=30ms TTL=48 Reply from 157.185.139.32: bytes=32 time=29ms TTL=48 Reply from 157.185.139.32: bytes=32 time=28ms TTL=48 Reply from 157.185.139.32: bytes=32 time=27ms TTL=48 Reply from 157.185.139.32: bytes=32 time=29ms TTL=48 Reply from 157.185.139.32: bytes=32 time=28ms TTL=48 Reply from 157.185.139.32: bytes=32 time=27ms TTL=48 Reply from 157.185.139.32: bytes=32 time=27ms TTL=48 Reply from 157.185.139.32: bytes=32 time=27ms TTL=48
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 27ms, Maximum = 30ms, Average = 28ms查看 |
GET PING Trace Dig |
|
湖南株洲市联通 |
联通 |
湖南 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
35.045ms |
25.201ms |
27.508ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=26ms TTL=48 Reply from 157.185.139.32: bytes=32 time=28ms TTL=48 Reply from 157.185.139.32: bytes=32 time=27ms TTL=48 Reply from 157.185.139.32: bytes=32 time=27ms TTL=48 Reply from 157.185.139.32: bytes=32 time=25ms TTL=48 Reply from 157.185.139.32: bytes=32 time=35ms TTL=48 Reply from 157.185.139.32: bytes=32 time=25ms TTL=48 Reply from 157.185.139.32: bytes=32 time=29ms TTL=48 Reply from 157.185.139.32: bytes=32 time=26ms TTL=48 Reply from 157.185.139.32: bytes=32 time=26ms TTL=48
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 25ms, Maximum = 35ms, Average = 28ms查看 |
GET PING Trace Dig |
|
广东云浮市联通 |
联通 |
广东 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
38.14ms |
24.08ms |
26.926ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=26ms TTL=51 Reply from 138.113.156.56: bytes=32 time=25ms TTL=51 Reply from 138.113.156.56: bytes=32 time=24ms TTL=51 Reply from 138.113.156.56: bytes=32 time=25ms TTL=51 Reply from 138.113.156.56: bytes=32 time=24ms TTL=51 Reply from 138.113.156.56: bytes=32 time=31ms TTL=51 Reply from 138.113.156.56: bytes=32 time=25ms TTL=51 Reply from 138.113.156.56: bytes=32 time=24ms TTL=51 Reply from 138.113.156.56: bytes=32 time=26ms TTL=51 Reply from 138.113.156.56: bytes=32 time=38ms TTL=51
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 24ms, Maximum = 38ms, Average = 27ms查看 |
GET PING Trace Dig |
|
江西新余市电信 |
电信 |
江西 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
28.6ms |
25.74ms |
26.268ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=29ms TTL=49 Reply from 157.185.139.32: bytes=32 time=27ms TTL=49 Reply from 157.185.139.32: bytes=32 time=26ms TTL=49 Reply from 157.185.139.32: bytes=32 time=26ms TTL=49 Reply from 157.185.139.32: bytes=32 time=26ms TTL=49 Reply from 157.185.139.32: bytes=32 time=26ms TTL=49 Reply from 157.185.139.32: bytes=32 time=26ms TTL=49 Reply from 157.185.139.32: bytes=32 time=26ms TTL=49 Reply from 157.185.139.32: bytes=32 time=26ms TTL=49 Reply from 157.185.139.32: bytes=32 time=26ms TTL=49
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 26ms, Maximum = 29ms, Average = 26ms查看 |
GET PING Trace Dig |
|
广西贵港市电信 |
电信 |
广西 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
27.7ms |
23.401ms |
24.512ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=24ms TTL=48 Reply from 138.113.156.56: bytes=32 time=23ms TTL=48 Reply from 138.113.156.56: bytes=32 time=24ms TTL=48 Reply from 138.113.156.56: bytes=32 time=24ms TTL=48 Reply from 138.113.156.56: bytes=32 time=28ms TTL=48 Reply from 138.113.156.56: bytes=32 time=25ms TTL=48 Reply from 138.113.156.56: bytes=32 time=24ms TTL=48 Reply from 138.113.156.56: bytes=32 time=25ms TTL=48 Reply from 138.113.156.56: bytes=32 time=25ms TTL=48 Reply from 138.113.156.56: bytes=32 time=25ms TTL=48
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 23ms, Maximum = 28ms, Average = 25ms查看 |
GET PING Trace Dig |
|
宁夏银川移动 |
移动 |
宁夏 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
28.196ms |
20.894ms |
24.11ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=28ms TTL=40 Reply from 157.185.139.32: bytes=32 time=25ms TTL=40 Reply from 157.185.139.32: bytes=32 time=21ms TTL=40 Reply from 157.185.139.32: bytes=32 time=25ms TTL=40 Reply from 157.185.139.32: bytes=32 time=27ms TTL=40 Reply from 157.185.139.32: bytes=32 time=21ms TTL=40 Reply from 157.185.139.32: bytes=32 time=23ms TTL=40 Reply from 157.185.139.32: bytes=32 time=24ms TTL=40 Reply from 157.185.139.32: bytes=32 time=24ms TTL=40 Reply from 157.185.139.32: bytes=32 time=23ms TTL=40
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 21ms, Maximum = 28ms, Average = 24ms查看 |
GET PING Trace Dig |
|
西藏拉萨市电信 |
电信 |
西藏 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
24.979ms |
21.611ms |
23.266ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=23ms TTL=52 Reply from 157.185.139.32: bytes=32 time=22ms TTL=52 Reply from 157.185.139.32: bytes=32 time=23ms TTL=52 Reply from 157.185.139.32: bytes=32 time=24ms TTL=52 Reply from 157.185.139.32: bytes=32 time=23ms TTL=52 Reply from 157.185.139.32: bytes=32 time=23ms TTL=52 Reply from 157.185.139.32: bytes=32 time=23ms TTL=52 Reply from 157.185.139.32: bytes=32 time=25ms TTL=52 Reply from 157.185.139.32: bytes=32 time=23ms TTL=52 Reply from 157.185.139.32: bytes=32 time=24ms TTL=52
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 22ms, Maximum = 25ms, Average = 23ms查看 |
GET PING Trace Dig |
|
海南儋州市电信 |
电信 |
海南 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
25.16ms |
21.48ms |
22.538ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=21ms TTL=50 Reply from 138.113.156.56: bytes=32 time=22ms TTL=50 Reply from 138.113.156.56: bytes=32 time=23ms TTL=50 Reply from 138.113.156.56: bytes=32 time=22ms TTL=50 Reply from 138.113.156.56: bytes=32 time=24ms TTL=50 Reply from 138.113.156.56: bytes=32 time=23ms TTL=50 Reply from 138.113.156.56: bytes=32 time=22ms TTL=50 Reply from 138.113.156.56: bytes=32 time=22ms TTL=50 Reply from 138.113.156.56: bytes=32 time=23ms TTL=50 Reply from 138.113.156.56: bytes=32 time=25ms TTL=50
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 21ms, Maximum = 25ms, Average = 23ms查看 |
GET PING Trace Dig |
|
海南文昌市移动 |
移动 |
海南 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
21.939ms |
19.639ms |
21.037ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=22ms TTL=49 Reply from 138.113.156.56: bytes=32 time=22ms TTL=49 Reply from 138.113.156.56: bytes=32 time=20ms TTL=49 Reply from 138.113.156.56: bytes=32 time=21ms TTL=49 Reply from 138.113.156.56: bytes=32 time=22ms TTL=49 Reply from 138.113.156.56: bytes=32 time=22ms TTL=49 Reply from 138.113.156.56: bytes=32 time=21ms TTL=49 Reply from 138.113.156.56: bytes=32 time=20ms TTL=49 Reply from 138.113.156.56: bytes=32 time=22ms TTL=49 Reply from 138.113.156.56: bytes=32 time=20ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 20ms, Maximum = 22ms, Average = 21ms查看 |
GET PING Trace Dig |
|
广东广州市联通 |
联通 |
广东 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
21.62ms |
18.78ms |
20.262ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=20ms TTL=52 Reply from 157.185.139.32: bytes=32 time=22ms TTL=52 Reply from 157.185.139.32: bytes=32 time=20ms TTL=52 Reply from 157.185.139.32: bytes=32 time=19ms TTL=52 Reply from 157.185.139.32: bytes=32 time=21ms TTL=52 Reply from 157.185.139.32: bytes=32 time=20ms TTL=52 Reply from 157.185.139.32: bytes=32 time=21ms TTL=52 Reply from 157.185.139.32: bytes=32 time=21ms TTL=52 Reply from 157.185.139.32: bytes=32 time=21ms TTL=52 Reply from 157.185.139.32: bytes=32 time=20ms TTL=52
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 19ms, Maximum = 22ms, Average = 20ms查看 |
GET PING Trace Dig |
|
马来西亚国外 |
国外 |
马来西亚 |
140.150.47.68 |
瑞典 |
10 |
10 |
0 |
23.34ms |
17.56ms |
19.78ms |
32B |
PING 9d9032.com PING 9d9032.com (140.150.47.68) with 32 bytes of data: Reply from 140.150.47.68: bytes=32 time=21ms TTL=50 Reply from 140.150.47.68: bytes=32 time=18ms TTL=50 Reply from 140.150.47.68: bytes=32 time=18ms TTL=50 Reply from 140.150.47.68: bytes=32 time=23ms TTL=50 Reply from 140.150.47.68: bytes=32 time=18ms TTL=50 Reply from 140.150.47.68: bytes=32 time=22ms TTL=50 Reply from 140.150.47.68: bytes=32 time=19ms TTL=50 Reply from 140.150.47.68: bytes=32 time=22ms TTL=50 Reply from 140.150.47.68: bytes=32 time=20ms TTL=50 Reply from 140.150.47.68: bytes=32 time=18ms TTL=50
Ping statistics for 140.150.47.68: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 18ms, Maximum = 23ms, Average = 20ms查看 |
GET PING Trace Dig |
|
广东惠州市电信 |
电信 |
广东 |
157.185.139.32 |
美国加利福尼亚圣何塞 |
10 |
10 |
0 |
23.82ms |
17.4ms |
19.773ms |
32B |
PING 9d9032.com PING 9d9032.com (157.185.139.32) with 32 bytes of data: Reply from 157.185.139.32: bytes=32 time=20ms TTL=47 Reply from 157.185.139.32: bytes=32 time=22ms TTL=47 Reply from 157.185.139.32: bytes=32 time=19ms TTL=47 Reply from 157.185.139.32: bytes=32 time=19ms TTL=47 Reply from 157.185.139.32: bytes=32 time=18ms TTL=47 Reply from 157.185.139.32: bytes=32 time=17ms TTL=47 Reply from 157.185.139.32: bytes=32 time=20ms TTL=47 Reply from 157.185.139.32: bytes=32 time=18ms TTL=47 Reply from 157.185.139.32: bytes=32 time=22ms TTL=47 Reply from 157.185.139.32: bytes=32 time=24ms TTL=47
Ping statistics for 157.185.139.32: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 17ms, Maximum = 24ms, Average = 20ms查看 |
GET PING Trace Dig |
|
云南昆明市电信 |
电信 |
云南 |
140.150.47.68 |
瑞典 |
10 |
10 |
0 |
17ms |
15.56ms |
16.354ms |
32B |
PING 9d9032.com PING 9d9032.com (140.150.47.68) with 32 bytes of data: Reply from 140.150.47.68: bytes=32 time=17ms TTL=51 Reply from 140.150.47.68: bytes=32 time=17ms TTL=51 Reply from 140.150.47.68: bytes=32 time=17ms TTL=51 Reply from 140.150.47.68: bytes=32 time=17ms TTL=51 Reply from 140.150.47.68: bytes=32 time=16ms TTL=51 Reply from 140.150.47.68: bytes=32 time=17ms TTL=51 Reply from 140.150.47.68: bytes=32 time=16ms TTL=51 Reply from 140.150.47.68: bytes=32 time=17ms TTL=51 Reply from 140.150.47.68: bytes=32 time=16ms TTL=51 Reply from 140.150.47.68: bytes=32 time=16ms TTL=51
Ping statistics for 140.150.47.68: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 16ms, Maximum = 17ms, Average = 16ms查看 |
GET PING Trace Dig |
|
浙江温州市移动 |
移动 |
浙江 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
10 |
0 |
17.079ms |
10.751ms |
13.621ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Reply from 138.113.156.56: bytes=32 time=12ms TTL=49 Reply from 138.113.156.56: bytes=32 time=12ms TTL=49 Reply from 138.113.156.56: bytes=32 time=15ms TTL=49 Reply from 138.113.156.56: bytes=32 time=17ms TTL=49 Reply from 138.113.156.56: bytes=32 time=15ms TTL=49 Reply from 138.113.156.56: bytes=32 time=15ms TTL=49 Reply from 138.113.156.56: bytes=32 time=14ms TTL=49 Reply from 138.113.156.56: bytes=32 time=13ms TTL=49 Reply from 138.113.156.56: bytes=32 time=11ms TTL=49 Reply from 138.113.156.56: bytes=32 time=14ms TTL=49
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 17ms, Average = 14ms查看 |
GET PING Trace Dig |
|
印度尼西亚国外 |
国外 |
印度尼西亚 |
138.113.250.183 |
中国香港QuantilNetworks |
10 |
10 |
0 |
6.44ms |
4.3ms |
5.15ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.250.183) with 32 bytes of data: Reply from 138.113.250.183: bytes=32 time=5ms TTL=55 Reply from 138.113.250.183: bytes=32 time=6ms TTL=55 Reply from 138.113.250.183: bytes=32 time=5ms TTL=55 Reply from 138.113.250.183: bytes=32 time=5ms TTL=55 Reply from 138.113.250.183: bytes=32 time=5ms TTL=55 Reply from 138.113.250.183: bytes=32 time=5ms TTL=55 Reply from 138.113.250.183: bytes=32 time=6ms TTL=55 Reply from 138.113.250.183: bytes=32 time=5ms TTL=55 Reply from 138.113.250.183: bytes=32 time=6ms TTL=55 Reply from 138.113.250.183: bytes=32 time=4ms TTL=55
Ping statistics for 138.113.250.183: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 4ms, Maximum = 6ms, Average = 5ms查看 |
GET PING Trace Dig |
|
美国国外 |
国外 |
美国 |
140.150.47.68 |
瑞典 |
10 |
10 |
0 |
10.856ms |
1.862ms |
4.268ms |
32B |
PING 9d9032.com PING 9d9032.com (140.150.47.68) with 32 bytes of data: Reply from 140.150.47.68: bytes=32 time=2ms TTL=51 Reply from 140.150.47.68: bytes=32 time=11ms TTL=51 Reply from 140.150.47.68: bytes=32 time=2ms TTL=51 Reply from 140.150.47.68: bytes=32 time=8ms TTL=51 Reply from 140.150.47.68: bytes=32 time=4ms TTL=51 Reply from 140.150.47.68: bytes=32 time=2ms TTL=51 Reply from 140.150.47.68: bytes=32 time=6ms TTL=51 Reply from 140.150.47.68: bytes=32 time=3ms TTL=51 Reply from 140.150.47.68: bytes=32 time=3ms TTL=51 Reply from 140.150.47.68: bytes=32 time=2ms TTL=51
Ping statistics for 140.150.47.68: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 2ms, Maximum = 11ms, Average = 4ms查看 |
GET PING Trace Dig |
|
美国国外 |
国外 |
美国 |
146.103.66.58 |
比利时法兰德斯 |
10 |
10 |
0 |
1.283ms |
0.446ms |
0.898ms |
32B |
PING 9d9032.com PING 9d9032.com (146.103.66.58) with 32 bytes of data: Reply from 146.103.66.58: bytes=32 time=1ms TTL=58 Reply from 146.103.66.58: bytes=32 time=1ms TTL=58 Reply from 146.103.66.58: bytes=32 time=1ms TTL=58 Reply from 146.103.66.58: bytes=32 time=1ms TTL=58 Reply from 146.103.66.58: bytes=32 time=1ms TTL=58 Reply from 146.103.66.58: bytes=32 time<1ms TTL=58 Reply from 146.103.66.58: bytes=32 time=1ms TTL=58 Reply from 146.103.66.58: bytes=32 time=1ms TTL=58 Reply from 146.103.66.58: bytes=32 time=1ms TTL=58 Reply from 146.103.66.58: bytes=32 time=1ms TTL=58
Ping statistics for 146.103.66.58: 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 9d9032.com PING 9d9032.com () with 0 bytes of data: Reply from : bytes=0 time=51ms TTL=52 Reply from : bytes=0 time=51ms TTL=52 Reply from : bytes=0 time=50ms TTL=52 Reply from : bytes=0 time=51ms TTL=52 Reply from : bytes=0 time=50ms TTL=52 Reply from : bytes=0 time=50ms TTL=52 Reply from : bytes=0 time=52ms TTL=52 Reply from : bytes=0 time=50ms TTL=52 Reply from : bytes=0 time=51ms TTL=52 Reply from : bytes=0 time=50ms TTL=52
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 9d9032.com PING 9d9032.com () with 0 bytes of data: Reply from : bytes=0 time=59ms TTL=49 Reply from : bytes=0 time=58ms TTL=49 Reply from : bytes=0 time=59ms TTL=49 Reply from : bytes=0 time=60ms TTL=49 Reply from : bytes=0 time=59ms TTL=49 Reply from : bytes=0 time=57ms TTL=49 Reply from : bytes=0 time=59ms TTL=49 Reply from : bytes=0 time=58ms TTL=49 Reply from : bytes=0 time=57ms TTL=49 Reply from : bytes=0 time=74ms TTL=49
Ping statistics for : Packets: Sent = 0, Received = 0, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum <1ms , Maximum <1ms , Average <1ms 查看 |
GET PING Trace Dig |
|
云南楚雄彝族自治州联通 |
联通 |
云南 |
|
* |
0 |
0 |
0 |
0ms |
0ms |
0ms |
|
PING 9d9032.com PING 9d9032.com () with 0 bytes of data: Reply from : bytes=0 time=44ms TTL=50 Reply from : bytes=0 time=36ms TTL=50 Reply from : bytes=0 time=37ms TTL=50 Reply from : bytes=0 time=37ms TTL=50 Reply from : bytes=0 time=37ms TTL=50 Reply from : bytes=0 time=37ms TTL=50 Reply from : bytes=0 time=37ms TTL=50 Reply from : bytes=0 time=36ms TTL=50 Reply from : bytes=0 time=37ms TTL=50 Reply from : bytes=0 time=44ms 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 9d9032.com PING 9d9032.com () with 0 bytes of data: Reply from : bytes=0 time=50ms TTL=50 Reply from : bytes=0 time=50ms TTL=50 Reply from : bytes=0 time=49ms TTL=50 Reply from : bytes=0 time=50ms TTL=50 Reply from : bytes=0 time=51ms TTL=50 Reply from : bytes=0 time=53ms TTL=50 Reply from : bytes=0 time=50ms TTL=50 Reply from : bytes=0 time=51ms TTL=50 Reply from : bytes=0 time=52ms TTL=50 Reply from : bytes=0 time=52ms 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 |
|
四川成都移动 |
移动 |
四川 |
138.113.156.56 |
日本大阪QuantilNetworks |
10 |
0 |
10 |
0ms |
0ms |
0ms |
32B |
PING 9d9032.com PING 9d9032.com (138.113.156.56) with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Request timed out.
Ping statistics for 138.113.156.56: Packets: Sent = 10, Received = 0, Lost = 10 (100% loss), Approximate round trip times in milli-seconds: Minimum <1ms , Maximum <1ms , Average <1ms 查看 |
GET PING Trace Dig |
|