监测点 |
ISP |
省份 |
解析IP |
解析IP所在地 |
发送 |
接收 |
丢弃 |
最大时间 |
最小时间 |
平均时间 |
包大小 |
详细信息 |
操作 |
共171个点 |
7个 |
共37个 |
共155个独立IP |
共89个独立节点 |
10 |
9 |
1 |
41.391ms |
18.767ms |
27.465ms |
|
|
|
内蒙古通辽移动 |
移动 |
内蒙古 |
116.136.134.236 |
中国内蒙古呼和浩特联通 |
10 |
10 |
0 |
970.894ms |
10.673ms |
362.707ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (116.136.134.236) with 32 bytes of data: Reply from 116.136.134.236: bytes=32 time=916ms TTL=52 Reply from 116.136.134.236: bytes=32 time=34ms TTL=52 Reply from 116.136.134.236: bytes=32 time=971ms TTL=52 Reply from 116.136.134.236: bytes=32 time=777ms TTL=52 Reply from 116.136.134.236: bytes=32 time=11ms TTL=52 Reply from 116.136.134.236: bytes=32 time=181ms TTL=52 Reply from 116.136.134.236: bytes=32 time=229ms TTL=52 Reply from 116.136.134.236: bytes=32 time=27ms TTL=52 Reply from 116.136.134.236: bytes=32 time=156ms TTL=52 Reply from 116.136.134.236: bytes=32 time=324ms TTL=52
Ping statistics for 116.136.134.236: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 971ms, Average = 363ms查看 |
GET PING Trace Dig |
|
黑龙江哈尔滨市联通 |
联通 |
黑龙江 |
1.189.232.66 |
中国黑龙江哈尔滨联通 |
10 |
8 |
2 |
646.901ms |
7.249ms |
260.23ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (1.189.232.66) with 32 bytes of data: Reply from 1.189.232.66: bytes=32 time=9ms TTL=58 Reply from 1.189.232.66: bytes=32 time=7ms TTL=58 Reply from 1.189.232.66: bytes=32 time=253ms TTL=58 Request timed out. Reply from 1.189.232.66: bytes=32 time=647ms TTL=58 Request timed out. Reply from 1.189.232.66: bytes=32 time=360ms TTL=58 Reply from 1.189.232.66: bytes=32 time=249ms TTL=58 Reply from 1.189.232.66: bytes=32 time=178ms TTL=58 Reply from 1.189.232.66: bytes=32 time=379ms TTL=58
Ping statistics for 1.189.232.66: Packets: Sent = 10, Received = 8, Lost = 2 (20% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 647ms, Average = 260ms查看 |
GET PING Trace Dig |
|
台湾台湾 |
台湾 |
台湾 |
114.80.179.167 |
中国上海电信 |
10 |
5 |
5 |
263.63ms |
234.026ms |
250.64ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (114.80.179.167) with 32 bytes of data: Reply from 114.80.179.167: bytes=32 time=250ms TTL=41 Reply from 114.80.179.167: bytes=32 time=246ms TTL=41 Reply from 114.80.179.167: bytes=32 time=259ms TTL=41 Request timed out. Request timed out. Request timed out. Request timed out. Reply from 114.80.179.167: bytes=32 time=264ms TTL=41 Request timed out. Reply from 114.80.179.167: bytes=32 time=234ms TTL=41
Ping statistics for 114.80.179.167: Packets: Sent = 10, Received = 5, Lost = 5 (50% loss), Approximate round trip times in milli-seconds: Minimum = 234ms, Maximum = 264ms, Average = 251ms查看 |
GET PING Trace Dig |
|
香港香港 |
香港 |
香港 |
61.170.77.82 |
中国上海电信 |
10 |
7 |
3 |
249.01ms |
244.166ms |
245.516ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (61.170.77.82) with 32 bytes of data: Reply from 61.170.77.82: bytes=32 time=244ms TTL=48 Reply from 61.170.77.82: bytes=32 time=245ms TTL=48 Reply from 61.170.77.82: bytes=32 time=246ms TTL=48 Request timed out. Reply from 61.170.77.82: bytes=32 time=249ms TTL=48 Reply from 61.170.77.82: bytes=32 time=244ms TTL=48 Request timed out. Request timed out. Reply from 61.170.77.82: bytes=32 time=245ms TTL=48 Reply from 61.170.77.82: bytes=32 time=245ms TTL=48
Ping statistics for 61.170.77.82: Packets: Sent = 10, Received = 7, Lost = 3 (30% loss), Approximate round trip times in milli-seconds: Minimum = 244ms, Maximum = 249ms, Average = 246ms查看 |
GET PING Trace Dig |
|
香港香港 |
香港 |
香港 |
180.163.145.53 |
中国上海电信 |
10 |
7 |
3 |
247.622ms |
0ms |
243.959ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (180.163.145.53) with 32 bytes of data: Request timed out. Reply from 180.163.145.53: bytes=32 time=247ms TTL=49 Reply from 180.163.145.53: bytes=32 time=236ms TTL=49 Reply from 180.163.145.53: bytes=32 time=248ms TTL=49 Reply from 180.163.145.53: bytes=32 time=241ms TTL=49 Reply from 180.163.145.53: bytes=32 time=242ms TTL=49 Reply from 180.163.145.53: bytes=32 time=248ms TTL=49 Request timed out. Request timed out. Reply from 180.163.145.53: bytes=32 time=247ms TTL=49
Ping statistics for 180.163.145.53: Packets: Sent = 10, Received = 7, Lost = 3 (30% loss), Approximate round trip times in milli-seconds: Minimum <1ms , Maximum = 248ms, Average = 244ms查看 |
GET PING Trace Dig |
|
美国国外 |
国外 |
美国 |
61.170.77.82 |
中国上海电信 |
10 |
10 |
0 |
229.127ms |
221.239ms |
226.882ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (61.170.77.82) with 32 bytes of data: Reply from 61.170.77.82: bytes=32 time=229ms TTL=48 Reply from 61.170.77.82: bytes=32 time=227ms TTL=48 Reply from 61.170.77.82: bytes=32 time=227ms TTL=48 Reply from 61.170.77.82: bytes=32 time=228ms TTL=48 Reply from 61.170.77.82: bytes=32 time=224ms TTL=48 Reply from 61.170.77.82: bytes=32 time=227ms TTL=48 Reply from 61.170.77.82: bytes=32 time=228ms TTL=48 Reply from 61.170.77.82: bytes=32 time=221ms TTL=48 Reply from 61.170.77.82: bytes=32 time=228ms TTL=48 Reply from 61.170.77.82: bytes=32 time=229ms TTL=48
Ping statistics for 61.170.77.82: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 221ms, Maximum = 229ms, Average = 227ms查看 |
GET PING Trace Dig |
|
马来西亚国外 |
国外 |
马来西亚 |
180.163.145.51 |
中国上海电信 |
10 |
10 |
0 |
226.82ms |
169.92ms |
191.252ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (180.163.145.51) with 32 bytes of data: Reply from 180.163.145.51: bytes=32 time=181ms TTL=40 Reply from 180.163.145.51: bytes=32 time=171ms TTL=40 Reply from 180.163.145.51: bytes=32 time=198ms TTL=40 Reply from 180.163.145.51: bytes=32 time=210ms TTL=40 Reply from 180.163.145.51: bytes=32 time=198ms TTL=40 Reply from 180.163.145.51: bytes=32 time=176ms TTL=40 Reply from 180.163.145.51: bytes=32 time=198ms TTL=40 Reply from 180.163.145.51: bytes=32 time=184ms TTL=40 Reply from 180.163.145.51: bytes=32 time=227ms TTL=40 Reply from 180.163.145.51: bytes=32 time=170ms TTL=40
Ping statistics for 180.163.145.51: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 170ms, Maximum = 227ms, Average = 191ms查看 |
GET PING Trace Dig |
|
青海西宁市电信 |
电信 |
青海 |
112.45.115.16 |
中国四川成都移动 |
10 |
10 |
0 |
346.365ms |
22.755ms |
161.028ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (112.45.115.16) with 32 bytes of data: Reply from 112.45.115.16: bytes=32 time=346ms TTL=55 Reply from 112.45.115.16: bytes=32 time=126ms TTL=55 Reply from 112.45.115.16: bytes=32 time=101ms TTL=55 Reply from 112.45.115.16: bytes=32 time=97ms TTL=55 Reply from 112.45.115.16: bytes=32 time=29ms TTL=55 Reply from 112.45.115.16: bytes=32 time=23ms TTL=55 Reply from 112.45.115.16: bytes=32 time=62ms TTL=55 Reply from 112.45.115.16: bytes=32 time=255ms TTL=55 Reply from 112.45.115.16: bytes=32 time=334ms TTL=55 Reply from 112.45.115.16: bytes=32 time=237ms TTL=55
Ping statistics for 112.45.115.16: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 23ms, Maximum = 346ms, Average = 161ms查看 |
GET PING Trace Dig |
|
美国国外 |
国外 |
美国 |
114.80.179.170 |
中国上海电信 |
10 |
10 |
0 |
131.347ms |
130.811ms |
130.987ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (114.80.179.170) with 32 bytes of data: Reply from 114.80.179.170: bytes=32 time=131ms TTL=53 Reply from 114.80.179.170: bytes=32 time=131ms TTL=53 Reply from 114.80.179.170: bytes=32 time=131ms TTL=53 Reply from 114.80.179.170: bytes=32 time=131ms TTL=53 Reply from 114.80.179.170: bytes=32 time=131ms TTL=53 Reply from 114.80.179.170: bytes=32 time=131ms TTL=53 Reply from 114.80.179.170: bytes=32 time=131ms TTL=53 Reply from 114.80.179.170: bytes=32 time=131ms TTL=53 Reply from 114.80.179.170: bytes=32 time=131ms TTL=53 Reply from 114.80.179.170: bytes=32 time=131ms TTL=53
Ping statistics for 114.80.179.170: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 131ms, Maximum = 131ms, Average = 131ms查看 |
GET PING Trace Dig |
|
印度尼西亚国外 |
国外 |
印度尼西亚 |
180.163.145.51 |
中国上海电信 |
10 |
10 |
0 |
137.998ms |
119.458ms |
128.415ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (180.163.145.51) with 32 bytes of data: Reply from 180.163.145.51: bytes=32 time=129ms TTL=44 Reply from 180.163.145.51: bytes=32 time=126ms TTL=44 Reply from 180.163.145.51: bytes=32 time=119ms TTL=44 Reply from 180.163.145.51: bytes=32 time=136ms TTL=44 Reply from 180.163.145.51: bytes=32 time=130ms TTL=44 Reply from 180.163.145.51: bytes=32 time=138ms TTL=44 Reply from 180.163.145.51: bytes=32 time=127ms TTL=44 Reply from 180.163.145.51: bytes=32 time=124ms TTL=44 Reply from 180.163.145.51: bytes=32 time=128ms TTL=44 Reply from 180.163.145.51: bytes=32 time=125ms TTL=44
Ping statistics for 180.163.145.51: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 119ms, Maximum = 138ms, Average = 128ms查看 |
GET PING Trace Dig |
|
江苏南京市电信 |
电信 |
江苏 |
222.211.13.100 |
中国四川绵阳电信 |
10 |
10 |
0 |
88.42ms |
79.32ms |
80.808ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (222.211.13.100) with 32 bytes of data: Reply from 222.211.13.100: bytes=32 time=81ms TTL=53 Reply from 222.211.13.100: bytes=32 time=79ms TTL=53 Reply from 222.211.13.100: bytes=32 time=80ms TTL=53 Reply from 222.211.13.100: bytes=32 time=80ms TTL=53 Reply from 222.211.13.100: bytes=32 time=80ms TTL=53 Reply from 222.211.13.100: bytes=32 time=79ms TTL=53 Reply from 222.211.13.100: bytes=32 time=88ms TTL=53 Reply from 222.211.13.100: bytes=32 time=81ms TTL=53 Reply from 222.211.13.100: bytes=32 time=79ms TTL=53 Reply from 222.211.13.100: bytes=32 time=80ms TTL=53
Ping statistics for 222.211.13.100: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 79ms, Maximum = 88ms, Average = 81ms查看 |
GET PING Trace Dig |
|
广东广州市联通 |
联通 |
广东 |
117.161.47.98 |
中国内蒙古呼和浩特移动 |
10 |
10 |
0 |
63.74ms |
51.02ms |
55.973ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (117.161.47.98) with 32 bytes of data: Reply from 117.161.47.98: bytes=32 time=55ms TTL=52 Reply from 117.161.47.98: bytes=32 time=56ms TTL=52 Reply from 117.161.47.98: bytes=32 time=54ms TTL=52 Reply from 117.161.47.98: bytes=32 time=55ms TTL=52 Reply from 117.161.47.98: bytes=32 time=55ms TTL=52 Reply from 117.161.47.98: bytes=32 time=54ms TTL=52 Reply from 117.161.47.98: bytes=32 time=64ms TTL=52 Reply from 117.161.47.98: bytes=32 time=51ms TTL=52 Reply from 117.161.47.98: bytes=32 time=59ms TTL=52 Reply from 117.161.47.98: bytes=32 time=57ms TTL=52
Ping statistics for 117.161.47.98: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 51ms, Maximum = 64ms, Average = 56ms查看 |
GET PING Trace Dig |
|
四川广元市联通 |
联通 |
四川 |
60.255.158.117 |
中国四川成都广电 |
10 |
10 |
0 |
102.62ms |
29.66ms |
54.471ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (60.255.158.117) with 32 bytes of data: Reply from 60.255.158.117: bytes=32 time=92ms TTL=57 Reply from 60.255.158.117: bytes=32 time=101ms TTL=57 Reply from 60.255.158.117: bytes=32 time=103ms TTL=57 Reply from 60.255.158.117: bytes=32 time=30ms TTL=57 Reply from 60.255.158.117: bytes=32 time=32ms TTL=57 Reply from 60.255.158.117: bytes=32 time=67ms TTL=57 Reply from 60.255.158.117: bytes=32 time=30ms TTL=57 Reply from 60.255.158.117: bytes=32 time=31ms TTL=57 Reply from 60.255.158.117: bytes=32 time=30ms TTL=57 Reply from 60.255.158.117: bytes=32 time=30ms TTL=57
Ping statistics for 60.255.158.117: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 30ms, Maximum = 103ms, Average = 54ms查看 |
GET PING Trace Dig |
|
北京北京市移动 |
移动 |
北京 |
171.43.165.236 |
中国湖北武汉电信 |
10 |
10 |
0 |
125.601ms |
22.68ms |
50.958ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (171.43.165.236) with 32 bytes of data: Reply from 171.43.165.236: bytes=32 time=70ms TTL=53 Reply from 171.43.165.236: bytes=32 time=29ms TTL=53 Reply from 171.43.165.236: bytes=32 time=44ms TTL=53 Reply from 171.43.165.236: bytes=32 time=31ms TTL=53 Reply from 171.43.165.236: bytes=32 time=59ms TTL=53 Reply from 171.43.165.236: bytes=32 time=126ms TTL=53 Reply from 171.43.165.236: bytes=32 time=56ms TTL=53 Reply from 171.43.165.236: bytes=32 time=27ms TTL=53 Reply from 171.43.165.236: bytes=32 time=46ms TTL=53 Reply from 171.43.165.236: bytes=32 time=23ms TTL=53
Ping statistics for 171.43.165.236: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 23ms, Maximum = 126ms, Average = 51ms查看 |
GET PING Trace Dig |
|
西藏拉萨市电信 |
电信 |
西藏 |
60.165.66.78 |
中国甘肃天水电信 |
10 |
10 |
0 |
51.667ms |
47.109ms |
48.923ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (60.165.66.78) with 32 bytes of data: Reply from 60.165.66.78: bytes=32 time=52ms TTL=53 Reply from 60.165.66.78: bytes=32 time=48ms TTL=53 Reply from 60.165.66.78: bytes=32 time=51ms TTL=53 Reply from 60.165.66.78: bytes=32 time=50ms TTL=53 Reply from 60.165.66.78: bytes=32 time=47ms TTL=53 Reply from 60.165.66.78: bytes=32 time=51ms TTL=53 Reply from 60.165.66.78: bytes=32 time=48ms TTL=53 Reply from 60.165.66.78: bytes=32 time=47ms TTL=53 Reply from 60.165.66.78: bytes=32 time=50ms TTL=53 Reply from 60.165.66.78: bytes=32 time=47ms TTL=53
Ping statistics for 60.165.66.78: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 47ms, Maximum = 52ms, Average = 49ms查看 |
GET PING Trace Dig |
|
内蒙古呼伦贝尔电信 |
电信 |
内蒙古 |
36.102.211.19 |
中国内蒙古呼和浩特电信 |
10 |
10 |
0 |
43.86ms |
38.82ms |
40.839ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (36.102.211.19) with 32 bytes of data: Reply from 36.102.211.19: bytes=32 time=40ms TTL=56 Reply from 36.102.211.19: bytes=32 time=42ms TTL=56 Reply from 36.102.211.19: bytes=32 time=41ms TTL=56 Reply from 36.102.211.19: bytes=32 time=39ms TTL=56 Reply from 36.102.211.19: bytes=32 time=40ms TTL=56 Reply from 36.102.211.19: bytes=32 time=44ms TTL=56 Reply from 36.102.211.19: bytes=32 time=41ms TTL=56 Reply from 36.102.211.19: bytes=32 time=41ms TTL=56 Reply from 36.102.211.19: bytes=32 time=40ms TTL=56 Reply from 36.102.211.19: bytes=32 time=41ms TTL=56
Ping statistics for 36.102.211.19: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 39ms, Maximum = 44ms, Average = 41ms查看 |
GET PING Trace Dig |
|
福建漳州市电信 |
电信 |
福建 |
220.160.45.46 |
中国福建厦门电信 |
10 |
10 |
0 |
78.215ms |
10.282ms |
40.692ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (220.160.45.46) with 32 bytes of data: Reply from 220.160.45.46: bytes=32 time=21ms TTL=56 Reply from 220.160.45.46: bytes=32 time=10ms TTL=56 Reply from 220.160.45.46: bytes=32 time=78ms TTL=56 Reply from 220.160.45.46: bytes=32 time=30ms TTL=56 Reply from 220.160.45.46: bytes=32 time=55ms TTL=56 Reply from 220.160.45.46: bytes=32 time=52ms TTL=56 Reply from 220.160.45.46: bytes=32 time=29ms TTL=56 Reply from 220.160.45.46: bytes=32 time=20ms TTL=56 Reply from 220.160.45.46: bytes=32 time=64ms TTL=56 Reply from 220.160.45.46: bytes=32 time=50ms TTL=56
Ping statistics for 220.160.45.46: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 78ms, Average = 41ms查看 |
GET PING Trace Dig |
|
台湾台湾 |
台湾 |
台湾 |
61.170.79.108 |
中国上海电信 |
10 |
10 |
0 |
45.8ms |
37.421ms |
40.02ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (61.170.79.108) with 32 bytes of data: Reply from 61.170.79.108: bytes=32 time=37ms TTL=51 Reply from 61.170.79.108: bytes=32 time=38ms TTL=51 Reply from 61.170.79.108: bytes=32 time=38ms TTL=51 Reply from 61.170.79.108: bytes=32 time=43ms TTL=51 Reply from 61.170.79.108: bytes=32 time=41ms TTL=51 Reply from 61.170.79.108: bytes=32 time=42ms TTL=51 Reply from 61.170.79.108: bytes=32 time=38ms TTL=51 Reply from 61.170.79.108: bytes=32 time=46ms TTL=51 Reply from 61.170.79.108: bytes=32 time=38ms TTL=51 Reply from 61.170.79.108: bytes=32 time=41ms TTL=51
Ping statistics for 61.170.79.108: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 37ms, Maximum = 46ms, Average = 40ms查看 |
GET PING Trace Dig |
|
新疆克拉玛依市联通 |
联通 |
新疆 |
60.13.234.83 |
中国新疆伊犁联通 |
10 |
10 |
0 |
43.36ms |
35.1ms |
36.09ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (60.13.234.83) with 32 bytes of data: Reply from 60.13.234.83: bytes=32 time=35ms TTL=57 Reply from 60.13.234.83: bytes=32 time=35ms TTL=57 Reply from 60.13.234.83: bytes=32 time=35ms TTL=57 Reply from 60.13.234.83: bytes=32 time=36ms TTL=57 Reply from 60.13.234.83: bytes=32 time=43ms TTL=57 Reply from 60.13.234.83: bytes=32 time=35ms TTL=57 Reply from 60.13.234.83: bytes=32 time=35ms TTL=57 Reply from 60.13.234.83: bytes=32 time=35ms TTL=57 Reply from 60.13.234.83: bytes=32 time=35ms TTL=57 Reply from 60.13.234.83: bytes=32 time=35ms TTL=57
Ping statistics for 60.13.234.83: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 35ms, Maximum = 43ms, Average = 36ms查看 |
GET PING Trace Dig |
|
内蒙古呼伦贝尔市联通 |
联通 |
内蒙古 |
116.136.134.234 |
中国内蒙古呼和浩特联通 |
10 |
10 |
0 |
39.02ms |
32.5ms |
35.539ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (116.136.134.234) with 32 bytes of data: Reply from 116.136.134.234: bytes=32 time=38ms TTL=56 Reply from 116.136.134.234: bytes=32 time=33ms TTL=56 Reply from 116.136.134.234: bytes=32 time=33ms TTL=56 Reply from 116.136.134.234: bytes=32 time=39ms TTL=56 Reply from 116.136.134.234: bytes=32 time=34ms TTL=56 Reply from 116.136.134.234: bytes=32 time=34ms TTL=56 Reply from 116.136.134.234: bytes=32 time=37ms TTL=56 Reply from 116.136.134.234: bytes=32 time=36ms TTL=56 Reply from 116.136.134.234: bytes=32 time=39ms TTL=56 Reply from 116.136.134.234: bytes=32 time=33ms TTL=56
Ping statistics for 116.136.134.234: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 33ms, Maximum = 39ms, Average = 36ms查看 |
GET PING Trace Dig |
|
澳门澳门 |
澳门 |
澳门 |
61.170.77.87 |
中国上海电信 |
10 |
10 |
0 |
37.42ms |
26.92ms |
34.915ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (61.170.77.87) with 32 bytes of data: Reply from 61.170.77.87: bytes=32 time=34ms TTL=51 Reply from 61.170.77.87: bytes=32 time=37ms TTL=51 Reply from 61.170.77.87: bytes=32 time=37ms TTL=51 Reply from 61.170.77.87: bytes=32 time=37ms TTL=51 Reply from 61.170.77.87: bytes=32 time=37ms TTL=51 Reply from 61.170.77.87: bytes=32 time=37ms TTL=51 Reply from 61.170.77.87: bytes=32 time=36ms TTL=51 Reply from 61.170.77.87: bytes=32 time=35ms TTL=51 Reply from 61.170.77.87: bytes=32 time=32ms TTL=51 Reply from 61.170.77.87: bytes=32 time=27ms TTL=51
Ping statistics for 61.170.77.87: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 27ms, Maximum = 37ms, Average = 35ms查看 |
GET PING Trace Dig |
|
湖北咸宁市电信 |
电信 |
湖北 |
119.36.63.227 |
中国湖北武汉联通 |
10 |
10 |
0 |
50.68ms |
28.66ms |
33.902ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (119.36.63.227) with 32 bytes of data: Reply from 119.36.63.227: bytes=32 time=32ms TTL=56 Reply from 119.36.63.227: bytes=32 time=29ms TTL=56 Reply from 119.36.63.227: bytes=32 time=36ms TTL=56 Reply from 119.36.63.227: bytes=32 time=29ms TTL=56 Reply from 119.36.63.227: bytes=32 time=30ms TTL=56 Reply from 119.36.63.227: bytes=32 time=30ms TTL=56 Reply from 119.36.63.227: bytes=32 time=30ms TTL=56 Reply from 119.36.63.227: bytes=32 time=45ms TTL=56 Reply from 119.36.63.227: bytes=32 time=30ms TTL=56 Reply from 119.36.63.227: bytes=32 time=51ms TTL=56
Ping statistics for 119.36.63.227: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 29ms, Maximum = 51ms, Average = 34ms查看 |
GET PING Trace Dig |
|
四川凉山彝族自治州电信 |
电信 |
四川 |
222.211.13.98 |
中国四川绵阳电信 |
10 |
10 |
0 |
57.701ms |
18.341ms |
31.526ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (222.211.13.98) with 32 bytes of data: Reply from 222.211.13.98: bytes=32 time=18ms TTL=55 Reply from 222.211.13.98: bytes=32 time=32ms TTL=55 Reply from 222.211.13.98: bytes=32 time=37ms TTL=55 Reply from 222.211.13.98: bytes=32 time=30ms TTL=55 Reply from 222.211.13.98: bytes=32 time=22ms TTL=55 Reply from 222.211.13.98: bytes=32 time=30ms TTL=55 Reply from 222.211.13.98: bytes=32 time=58ms TTL=55 Reply from 222.211.13.98: bytes=32 time=27ms TTL=55 Reply from 222.211.13.98: bytes=32 time=33ms TTL=55 Reply from 222.211.13.98: bytes=32 time=31ms TTL=55
Ping statistics for 222.211.13.98: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 18ms, Maximum = 58ms, Average = 32ms查看 |
GET PING Trace Dig |
|
新疆克拉玛依市电信 |
电信 |
新疆 |
110.157.250.204 |
中国新疆乌鲁木齐电信 |
10 |
10 |
0 |
53ms |
15.68ms |
30.249ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (110.157.250.204) with 32 bytes of data: Reply from 110.157.250.204: bytes=32 time=23ms TTL=57 Reply from 110.157.250.204: bytes=32 time=24ms TTL=57 Reply from 110.157.250.204: bytes=32 time=36ms TTL=57 Reply from 110.157.250.204: bytes=32 time=16ms TTL=57 Reply from 110.157.250.204: bytes=32 time=52ms TTL=57 Reply from 110.157.250.204: bytes=32 time=25ms TTL=57 Reply from 110.157.250.204: bytes=32 time=24ms TTL=57 Reply from 110.157.250.204: bytes=32 time=32ms TTL=57 Reply from 110.157.250.204: bytes=32 time=17ms TTL=57 Reply from 110.157.250.204: bytes=32 time=53ms TTL=57
Ping statistics for 110.157.250.204: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 16ms, Maximum = 53ms, Average = 30ms查看 |
GET PING Trace Dig |
|
河北沧州市移动 |
移动 |
河北 |
36.144.23.234 |
中国河北移动 |
10 |
10 |
0 |
33.794ms |
26.336ms |
29.056ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (36.144.23.234) with 32 bytes of data: Reply from 36.144.23.234: bytes=32 time=30ms TTL=56 Reply from 36.144.23.234: bytes=32 time=29ms TTL=56 Reply from 36.144.23.234: bytes=32 time=28ms TTL=56 Reply from 36.144.23.234: bytes=32 time=29ms TTL=56 Reply from 36.144.23.234: bytes=32 time=28ms TTL=56 Reply from 36.144.23.234: bytes=32 time=34ms TTL=56 Reply from 36.144.23.234: bytes=32 time=33ms TTL=56 Reply from 36.144.23.234: bytes=32 time=26ms TTL=56 Reply from 36.144.23.234: bytes=32 time=27ms TTL=56 Reply from 36.144.23.234: bytes=32 time=27ms TTL=56
Ping statistics for 36.144.23.234: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 26ms, Maximum = 34ms, Average = 29ms查看 |
GET PING Trace Dig |
|
贵州安顺市移动 |
移动 |
贵州 |
117.187.205.53 |
中国贵州贵阳移动 |
10 |
10 |
0 |
35.041ms |
21.9ms |
28.811ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (117.187.205.53) with 32 bytes of data: Reply from 117.187.205.53: bytes=32 time=26ms TTL=53 Reply from 117.187.205.53: bytes=32 time=31ms TTL=53 Reply from 117.187.205.53: bytes=32 time=22ms TTL=53 Reply from 117.187.205.53: bytes=32 time=28ms TTL=53 Reply from 117.187.205.53: bytes=32 time=32ms TTL=53 Reply from 117.187.205.53: bytes=32 time=28ms TTL=53 Reply from 117.187.205.53: bytes=32 time=35ms TTL=53 Reply from 117.187.205.53: bytes=32 time=25ms TTL=53 Reply from 117.187.205.53: bytes=32 time=30ms TTL=53 Reply from 117.187.205.53: bytes=32 time=31ms TTL=53
Ping statistics for 117.187.205.53: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 22ms, Maximum = 35ms, Average = 29ms查看 |
GET PING Trace Dig |
|
北京北京市移动 |
移动 |
北京 |
116.136.134.235 |
中国内蒙古呼和浩特联通 |
10 |
10 |
0 |
33.159ms |
24.7ms |
28.746ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (116.136.134.235) with 32 bytes of data: Reply from 116.136.134.235: bytes=32 time=27ms TTL=56 Reply from 116.136.134.235: bytes=32 time=31ms TTL=56 Reply from 116.136.134.235: bytes=32 time=32ms TTL=56 Reply from 116.136.134.235: bytes=32 time=27ms TTL=56 Reply from 116.136.134.235: bytes=32 time=29ms TTL=56 Reply from 116.136.134.235: bytes=32 time=33ms TTL=56 Reply from 116.136.134.235: bytes=32 time=28ms TTL=56 Reply from 116.136.134.235: bytes=32 time=25ms TTL=56 Reply from 116.136.134.235: bytes=32 time=26ms TTL=56 Reply from 116.136.134.235: bytes=32 time=30ms TTL=56
Ping statistics for 116.136.134.235: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 25ms, Maximum = 33ms, Average = 29ms查看 |
GET PING Trace Dig |
|
河北秦皇岛市联通 |
联通 |
河北 |
36.144.23.229 |
中国河北移动 |
10 |
10 |
0 |
40.941ms |
25.36ms |
28.642ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (36.144.23.229) with 32 bytes of data: Reply from 36.144.23.229: bytes=32 time=27ms TTL=56 Reply from 36.144.23.229: bytes=32 time=26ms TTL=56 Reply from 36.144.23.229: bytes=32 time=29ms TTL=56 Reply from 36.144.23.229: bytes=32 time=29ms TTL=56 Reply from 36.144.23.229: bytes=32 time=27ms TTL=56 Reply from 36.144.23.229: bytes=32 time=41ms TTL=56 Reply from 36.144.23.229: bytes=32 time=28ms TTL=56 Reply from 36.144.23.229: bytes=32 time=27ms TTL=56 Reply from 36.144.23.229: bytes=32 time=25ms TTL=56 Reply from 36.144.23.229: bytes=32 time=28ms TTL=56
Ping statistics for 36.144.23.229: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 25ms, Maximum = 41ms, Average = 29ms查看 |
GET PING Trace Dig |
|
青海西宁市电信 |
电信 |
青海 |
125.72.124.81 |
中国青海西宁电信 |
10 |
10 |
0 |
70.83ms |
17.136ms |
27.971ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (125.72.124.81) with 32 bytes of data: Reply from 125.72.124.81: bytes=32 time=34ms TTL=56 Reply from 125.72.124.81: bytes=32 time=18ms TTL=56 Reply from 125.72.124.81: bytes=32 time=18ms TTL=56 Reply from 125.72.124.81: bytes=32 time=71ms TTL=56 Reply from 125.72.124.81: bytes=32 time=17ms TTL=56 Reply from 125.72.124.81: bytes=32 time=34ms TTL=56 Reply from 125.72.124.81: bytes=32 time=18ms TTL=56 Reply from 125.72.124.81: bytes=32 time=18ms TTL=56 Reply from 125.72.124.81: bytes=32 time=20ms TTL=56 Reply from 125.72.124.81: bytes=32 time=31ms TTL=56
Ping statistics for 125.72.124.81: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 17ms, Maximum = 71ms, Average = 28ms查看 |
GET PING Trace Dig |
|
湖南长沙移动 |
移动 |
湖南 |
118.253.170.228 |
中国湖南怀化电信 |
10 |
10 |
0 |
33.427ms |
24.169ms |
26.521ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (118.253.170.228) with 32 bytes of data: Reply from 118.253.170.228: bytes=32 time=33ms TTL=54 Reply from 118.253.170.228: bytes=32 time=26ms TTL=54 Reply from 118.253.170.228: bytes=32 time=26ms TTL=54 Reply from 118.253.170.228: bytes=32 time=25ms TTL=54 Reply from 118.253.170.228: bytes=32 time=26ms TTL=54 Reply from 118.253.170.228: bytes=32 time=26ms TTL=54 Reply from 118.253.170.228: bytes=32 time=26ms TTL=54 Reply from 118.253.170.228: bytes=32 time=24ms TTL=54 Reply from 118.253.170.228: bytes=32 time=27ms TTL=54 Reply from 118.253.170.228: bytes=32 time=26ms TTL=54
Ping statistics for 118.253.170.228: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 24ms, Maximum = 33ms, Average = 27ms查看 |
GET PING Trace Dig |
|
甘肃平凉移动 |
移动 |
甘肃 |
117.157.133.27 |
中国甘肃酒泉移动 |
10 |
10 |
0 |
32.581ms |
22.326ms |
25.55ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (117.157.133.27) with 32 bytes of data: Reply from 117.157.133.27: bytes=32 time=24ms TTL=55 Reply from 117.157.133.27: bytes=32 time=33ms TTL=55 Reply from 117.157.133.27: bytes=32 time=28ms TTL=55 Reply from 117.157.133.27: bytes=32 time=23ms TTL=55 Reply from 117.157.133.27: bytes=32 time=26ms TTL=55 Reply from 117.157.133.27: bytes=32 time=22ms TTL=55 Reply from 117.157.133.27: bytes=32 time=30ms TTL=55 Reply from 117.157.133.27: bytes=32 time=24ms TTL=55 Reply from 117.157.133.27: bytes=32 time=23ms TTL=55 Reply from 117.157.133.27: bytes=32 time=22ms TTL=55
Ping statistics for 117.157.133.27: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 22ms, Maximum = 33ms, Average = 26ms查看 |
GET PING Trace Dig |
|
上海上海市联通 |
联通 |
上海 |
140.207.63.155 |
中国上海联通 |
10 |
10 |
0 |
98.069ms |
4.561ms |
25.417ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (140.207.63.155) with 32 bytes of data: Reply from 140.207.63.155: bytes=32 time=5ms TTL=58 Reply from 140.207.63.155: bytes=32 time=9ms TTL=58 Reply from 140.207.63.155: bytes=32 time=9ms TTL=58 Reply from 140.207.63.155: bytes=32 time=16ms TTL=58 Reply from 140.207.63.155: bytes=32 time=19ms TTL=58 Reply from 140.207.63.155: bytes=32 time=59ms TTL=58 Reply from 140.207.63.155: bytes=32 time=21ms TTL=58 Reply from 140.207.63.155: bytes=32 time=98ms TTL=58 Reply from 140.207.63.155: bytes=32 time=7ms TTL=58 Reply from 140.207.63.155: bytes=32 time=10ms TTL=58
Ping statistics for 140.207.63.155: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 5ms, Maximum = 98ms, Average = 25ms查看 |
GET PING Trace Dig |
|
重庆重庆市电信 |
电信 |
重庆 |
219.153.157.103 |
中国重庆电信 |
10 |
10 |
0 |
30.903ms |
18.69ms |
24.92ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (219.153.157.103) with 32 bytes of data: Reply from 219.153.157.103: bytes=32 time=26ms TTL=55 Reply from 219.153.157.103: bytes=32 time=21ms TTL=55 Reply from 219.153.157.103: bytes=32 time=19ms TTL=55 Reply from 219.153.157.103: bytes=32 time=22ms TTL=55 Reply from 219.153.157.103: bytes=32 time=28ms TTL=55 Reply from 219.153.157.103: bytes=32 time=24ms TTL=55 Reply from 219.153.157.103: bytes=32 time=26ms TTL=55 Reply from 219.153.157.103: bytes=32 time=27ms TTL=55 Reply from 219.153.157.103: bytes=32 time=31ms TTL=55 Reply from 219.153.157.103: bytes=32 time=28ms TTL=55
Ping statistics for 219.153.157.103: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 19ms, Maximum = 31ms, Average = 25ms查看 |
GET PING Trace Dig |
|
新疆阿拉尔市电信 |
电信 |
新疆 |
110.157.250.210 |
中国新疆乌鲁木齐电信 |
10 |
10 |
0 |
25.063ms |
24.513ms |
24.721ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (110.157.250.210) with 32 bytes of data: Reply from 110.157.250.210: bytes=32 time=25ms TTL=56 Reply from 110.157.250.210: bytes=32 time=25ms TTL=56 Reply from 110.157.250.210: bytes=32 time=25ms TTL=56 Reply from 110.157.250.210: bytes=32 time=25ms TTL=56 Reply from 110.157.250.210: bytes=32 time=25ms TTL=56 Reply from 110.157.250.210: bytes=32 time=25ms TTL=56 Reply from 110.157.250.210: bytes=32 time=25ms TTL=56 Reply from 110.157.250.210: bytes=32 time=25ms TTL=56 Reply from 110.157.250.210: bytes=32 time=25ms TTL=56 Reply from 110.157.250.210: bytes=32 time=25ms TTL=56
Ping statistics for 110.157.250.210: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 25ms, Maximum = 25ms, Average = 25ms查看 |
GET PING Trace Dig |
|
江苏南京市移动 |
移动 |
江苏 |
223.109.63.220 |
中国江苏扬州移动 |
10 |
10 |
0 |
64.144ms |
7.545ms |
22.431ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (223.109.63.220) with 32 bytes of data: Reply from 223.109.63.220: bytes=32 time=22ms TTL=55 Reply from 223.109.63.220: bytes=32 time=47ms TTL=55 Reply from 223.109.63.220: bytes=32 time=10ms TTL=55 Reply from 223.109.63.220: bytes=32 time=18ms TTL=55 Reply from 223.109.63.220: bytes=32 time=64ms TTL=55 Reply from 223.109.63.220: bytes=32 time=8ms TTL=55 Reply from 223.109.63.220: bytes=32 time=25ms TTL=55 Reply from 223.109.63.220: bytes=32 time=12ms TTL=55 Reply from 223.109.63.220: bytes=32 time=12ms TTL=55 Reply from 223.109.63.220: bytes=32 time=8ms TTL=55
Ping statistics for 223.109.63.220: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 8ms, Maximum = 64ms, Average = 22ms查看 |
GET PING Trace Dig |
|
河南开封市联通 |
联通 |
河南 |
219.154.251.9 |
中国河南许昌联通 |
10 |
10 |
0 |
39.205ms |
10.575ms |
21.632ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (219.154.251.9) with 32 bytes of data: Reply from 219.154.251.9: bytes=32 time=14ms TTL=54 Reply from 219.154.251.9: bytes=32 time=22ms TTL=54 Reply from 219.154.251.9: bytes=32 time=23ms TTL=54 Reply from 219.154.251.9: bytes=32 time=11ms TTL=54 Reply from 219.154.251.9: bytes=32 time=39ms TTL=54 Reply from 219.154.251.9: bytes=32 time=25ms TTL=54 Reply from 219.154.251.9: bytes=32 time=32ms TTL=54 Reply from 219.154.251.9: bytes=32 time=14ms TTL=54 Reply from 219.154.251.9: bytes=32 time=25ms TTL=54 Reply from 219.154.251.9: bytes=32 time=11ms TTL=54
Ping statistics for 219.154.251.9: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 39ms, Average = 22ms查看 |
GET PING Trace Dig |
|
内蒙古呼和浩特移动 |
移动 |
内蒙古 |
45.115.202.45 |
中国北京联通 |
10 |
10 |
0 |
26.44ms |
19.08ms |
21.267ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (45.115.202.45) with 32 bytes of data: Reply from 45.115.202.45: bytes=32 time=20ms TTL=58 Reply from 45.115.202.45: bytes=32 time=20ms TTL=58 Reply from 45.115.202.45: bytes=32 time=26ms TTL=58 Reply from 45.115.202.45: bytes=32 time=24ms TTL=58 Reply from 45.115.202.45: bytes=32 time=21ms TTL=58 Reply from 45.115.202.45: bytes=32 time=21ms TTL=58 Reply from 45.115.202.45: bytes=32 time=19ms TTL=58 Reply from 45.115.202.45: bytes=32 time=20ms TTL=58 Reply from 45.115.202.45: bytes=32 time=21ms TTL=58 Reply from 45.115.202.45: bytes=32 time=20ms TTL=58
Ping statistics for 45.115.202.45: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 19ms, Maximum = 26ms, Average = 21ms查看 |
GET PING Trace Dig |
|
四川达州市电信 |
电信 |
四川 |
222.211.13.95 |
中国四川绵阳电信 |
10 |
10 |
0 |
24.72ms |
19.68ms |
20.989ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (222.211.13.95) with 32 bytes of data: Reply from 222.211.13.95: bytes=32 time=25ms TTL=55 Reply from 222.211.13.95: bytes=32 time=20ms TTL=55 Reply from 222.211.13.95: bytes=32 time=20ms TTL=55 Reply from 222.211.13.95: bytes=32 time=22ms TTL=55 Reply from 222.211.13.95: bytes=32 time=20ms TTL=55 Reply from 222.211.13.95: bytes=32 time=20ms TTL=55 Reply from 222.211.13.95: bytes=32 time=20ms TTL=55 Reply from 222.211.13.95: bytes=32 time=20ms TTL=55 Reply from 222.211.13.95: bytes=32 time=21ms TTL=55 Reply from 222.211.13.95: bytes=32 time=23ms TTL=55
Ping statistics for 222.211.13.95: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 20ms, Maximum = 25ms, Average = 21ms查看 |
GET PING Trace Dig |
|
安徽蚌埠市联通 |
联通 |
安徽 |
119.188.217.66 |
中国山东济南联通 |
10 |
10 |
0 |
21.26ms |
19.18ms |
19.704ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (119.188.217.66) with 32 bytes of data: Reply from 119.188.217.66: bytes=32 time=21ms TTL=54 Reply from 119.188.217.66: bytes=32 time=19ms TTL=54 Reply from 119.188.217.66: bytes=32 time=20ms TTL=54 Reply from 119.188.217.66: bytes=32 time=20ms TTL=54 Reply from 119.188.217.66: bytes=32 time=19ms TTL=54 Reply from 119.188.217.66: bytes=32 time=19ms TTL=54 Reply from 119.188.217.66: bytes=32 time=20ms TTL=54 Reply from 119.188.217.66: bytes=32 time=20ms TTL=54 Reply from 119.188.217.66: bytes=32 time=20ms TTL=54 Reply from 119.188.217.66: bytes=32 time=19ms TTL=54
Ping statistics for 119.188.217.66: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 19ms, Maximum = 21ms, Average = 20ms查看 |
GET PING Trace Dig |
|
山东潍坊市电信 |
电信 |
山东 |
120.220.78.231 |
中国山东济南移动 |
10 |
10 |
0 |
19.998ms |
18.538ms |
18.945ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (120.220.78.231) with 32 bytes of data: Reply from 120.220.78.231: bytes=32 time=19ms TTL=54 Reply from 120.220.78.231: bytes=32 time=19ms TTL=54 Reply from 120.220.78.231: bytes=32 time=19ms TTL=54 Reply from 120.220.78.231: bytes=32 time=19ms TTL=54 Reply from 120.220.78.231: bytes=32 time=19ms TTL=54 Reply from 120.220.78.231: bytes=32 time=19ms TTL=54 Reply from 120.220.78.231: bytes=32 time=19ms TTL=54 Reply from 120.220.78.231: bytes=32 time=19ms TTL=54 Reply from 120.220.78.231: bytes=32 time=20ms TTL=54 Reply from 120.220.78.231: bytes=32 time=19ms TTL=54
Ping statistics for 120.220.78.231: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 19ms, Maximum = 20ms, Average = 19ms查看 |
GET PING Trace Dig |
|
广东东莞市联通 |
联通 |
广东 |
36.147.34.24 |
中国云南昆明移动 |
10 |
10 |
0 |
26.98ms |
14ms |
18.944ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (36.147.34.24) with 32 bytes of data: Reply from 36.147.34.24: bytes=32 time=27ms TTL=57 Reply from 36.147.34.24: bytes=32 time=21ms TTL=57 Reply from 36.147.34.24: bytes=32 time=14ms TTL=57 Reply from 36.147.34.24: bytes=32 time=15ms TTL=57 Reply from 36.147.34.24: bytes=32 time=24ms TTL=57 Reply from 36.147.34.24: bytes=32 time=21ms TTL=57 Reply from 36.147.34.24: bytes=32 time=14ms TTL=57 Reply from 36.147.34.24: bytes=32 time=23ms TTL=57 Reply from 36.147.34.24: bytes=32 time=14ms TTL=57 Reply from 36.147.34.24: bytes=32 time=16ms TTL=57
Ping statistics for 36.147.34.24: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 14ms, Maximum = 27ms, Average = 19ms查看 |
GET PING Trace Dig |
|
浙江台州市移动 |
移动 |
浙江 |
39.183.48.102 |
中国浙江杭州移动 |
10 |
10 |
0 |
30.439ms |
15.62ms |
18.891ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (39.183.48.102) with 32 bytes of data: Reply from 39.183.48.102: bytes=32 time=16ms TTL=56 Reply from 39.183.48.102: bytes=32 time=17ms TTL=56 Reply from 39.183.48.102: bytes=32 time=20ms TTL=56 Reply from 39.183.48.102: bytes=32 time=19ms TTL=56 Reply from 39.183.48.102: bytes=32 time=16ms TTL=56 Reply from 39.183.48.102: bytes=32 time=16ms TTL=56 Reply from 39.183.48.102: bytes=32 time=30ms TTL=56 Reply from 39.183.48.102: bytes=32 time=20ms TTL=56 Reply from 39.183.48.102: bytes=32 time=16ms TTL=56 Reply from 39.183.48.102: bytes=32 time=20ms TTL=56
Ping statistics for 39.183.48.102: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 16ms, Maximum = 30ms, Average = 19ms查看 |
GET PING Trace Dig |
|
河南驻马店市移动 |
移动 |
河南 |
183.204.37.210 |
中国河南郑州移动 |
10 |
10 |
0 |
41.88ms |
13.44ms |
18.691ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (183.204.37.210) with 32 bytes of data: Reply from 183.204.37.210: bytes=32 time=24ms TTL=55 Reply from 183.204.37.210: bytes=32 time=13ms TTL=55 Reply from 183.204.37.210: bytes=32 time=14ms TTL=55 Reply from 183.204.37.210: bytes=32 time=14ms TTL=55 Reply from 183.204.37.210: bytes=32 time=18ms TTL=55 Reply from 183.204.37.210: bytes=32 time=18ms TTL=55 Reply from 183.204.37.210: bytes=32 time=14ms TTL=55 Reply from 183.204.37.210: bytes=32 time=42ms TTL=55 Reply from 183.204.37.210: bytes=32 time=18ms TTL=55 Reply from 183.204.37.210: bytes=32 time=14ms TTL=55
Ping statistics for 183.204.37.210: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 42ms, Average = 19ms查看 |
GET PING Trace Dig |
|
重庆梁平电信 |
电信 |
重庆 |
183.231.33.83 |
中国重庆移动 |
10 |
10 |
0 |
21.142ms |
16.939ms |
18.598ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (183.231.33.83) with 32 bytes of data: Reply from 183.231.33.83: bytes=32 time=17ms TTL=55 Reply from 183.231.33.83: bytes=32 time=20ms TTL=55 Reply from 183.231.33.83: bytes=32 time=19ms TTL=55 Reply from 183.231.33.83: bytes=32 time=18ms TTL=55 Reply from 183.231.33.83: bytes=32 time=17ms TTL=55 Reply from 183.231.33.83: bytes=32 time=18ms TTL=55 Reply from 183.231.33.83: bytes=32 time=18ms TTL=55 Reply from 183.231.33.83: bytes=32 time=21ms TTL=55 Reply from 183.231.33.83: bytes=32 time=21ms TTL=55 Reply from 183.231.33.83: bytes=32 time=17ms TTL=55
Ping statistics for 183.231.33.83: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 17ms, Maximum = 21ms, Average = 19ms查看 |
GET PING Trace Dig |
|
天津天津市电信 |
电信 |
天津 |
125.39.43.8 |
中国天津联通 |
10 |
10 |
0 |
29.951ms |
12.653ms |
18.456ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (125.39.43.8) with 32 bytes of data: Reply from 125.39.43.8: bytes=32 time=25ms TTL=56 Reply from 125.39.43.8: bytes=32 time=14ms TTL=56 Reply from 125.39.43.8: bytes=32 time=30ms TTL=56 Reply from 125.39.43.8: bytes=32 time=27ms TTL=56 Reply from 125.39.43.8: bytes=32 time=15ms TTL=56 Reply from 125.39.43.8: bytes=32 time=13ms TTL=56 Reply from 125.39.43.8: bytes=32 time=15ms TTL=56 Reply from 125.39.43.8: bytes=32 time=18ms TTL=56 Reply from 125.39.43.8: bytes=32 time=13ms TTL=56 Reply from 125.39.43.8: bytes=32 time=15ms TTL=56
Ping statistics for 125.39.43.8: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 30ms, Average = 18ms查看 |
GET PING Trace Dig |
|
浙江宁波市电信 |
电信 |
浙江 |
61.164.147.229 |
中国浙江温州电信 |
10 |
10 |
0 |
28.008ms |
14.672ms |
18.125ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (61.164.147.229) with 32 bytes of data: Reply from 61.164.147.229: bytes=32 time=17ms TTL=54 Reply from 61.164.147.229: bytes=32 time=22ms TTL=54 Reply from 61.164.147.229: bytes=32 time=15ms TTL=54 Reply from 61.164.147.229: bytes=32 time=17ms TTL=54 Reply from 61.164.147.229: bytes=32 time=28ms TTL=54 Reply from 61.164.147.229: bytes=32 time=22ms TTL=54 Reply from 61.164.147.229: bytes=32 time=15ms TTL=54 Reply from 61.164.147.229: bytes=32 time=17ms TTL=54 Reply from 61.164.147.229: bytes=32 time=15ms TTL=54 Reply from 61.164.147.229: bytes=32 time=15ms TTL=54
Ping statistics for 61.164.147.229: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 15ms, Maximum = 28ms, Average = 18ms查看 |
GET PING Trace Dig |
|
四川成都市电信 |
电信 |
四川 |
60.255.158.117 |
中国四川成都广电 |
10 |
10 |
0 |
63.14ms |
5.381ms |
17.854ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (60.255.158.117) with 32 bytes of data: Reply from 60.255.158.117: bytes=32 time=11ms TTL=55 Reply from 60.255.158.117: bytes=32 time=63ms TTL=55 Reply from 60.255.158.117: bytes=32 time=9ms TTL=55 Reply from 60.255.158.117: bytes=32 time=7ms TTL=55 Reply from 60.255.158.117: bytes=32 time=8ms TTL=55 Reply from 60.255.158.117: bytes=32 time=11ms TTL=55 Reply from 60.255.158.117: bytes=32 time=5ms TTL=55 Reply from 60.255.158.117: bytes=32 time=11ms TTL=55 Reply from 60.255.158.117: bytes=32 time=14ms TTL=55 Reply from 60.255.158.117: bytes=32 time=39ms TTL=55
Ping statistics for 60.255.158.117: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 5ms, Maximum = 63ms, Average = 18ms查看 |
GET PING Trace Dig |
|
福建福州市联通 |
联通 |
福建 |
36.251.253.95 |
中国福建厦门联通 |
10 |
10 |
0 |
41.1ms |
13.34ms |
17.556ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (36.251.253.95) with 32 bytes of data: Reply from 36.251.253.95: bytes=32 time=16ms TTL=54 Reply from 36.251.253.95: bytes=32 time=18ms TTL=54 Reply from 36.251.253.95: bytes=32 time=13ms TTL=54 Reply from 36.251.253.95: bytes=32 time=14ms TTL=54 Reply from 36.251.253.95: bytes=32 time=16ms TTL=54 Reply from 36.251.253.95: bytes=32 time=13ms TTL=54 Reply from 36.251.253.95: bytes=32 time=16ms TTL=54 Reply from 36.251.253.95: bytes=32 time=15ms TTL=54 Reply from 36.251.253.95: bytes=32 time=14ms TTL=54 Reply from 36.251.253.95: bytes=32 time=41ms TTL=54
Ping statistics for 36.251.253.95: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 41ms, Average = 18ms查看 |
GET PING Trace Dig |
|
河北沧州市电信 |
电信 |
河北 |
221.192.166.216 |
中国河北石家庄联通 |
10 |
10 |
0 |
18.72ms |
16.961ms |
17.515ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (221.192.166.216) with 32 bytes of data: Reply from 221.192.166.216: bytes=32 time=17ms TTL=56 Reply from 221.192.166.216: bytes=32 time=17ms TTL=56 Reply from 221.192.166.216: bytes=32 time=19ms TTL=56 Reply from 221.192.166.216: bytes=32 time=17ms TTL=56 Reply from 221.192.166.216: bytes=32 time=18ms TTL=56 Reply from 221.192.166.216: bytes=32 time=18ms TTL=56 Reply from 221.192.166.216: bytes=32 time=17ms TTL=56 Reply from 221.192.166.216: bytes=32 time=17ms TTL=56 Reply from 221.192.166.216: bytes=32 time=17ms TTL=56 Reply from 221.192.166.216: bytes=32 time=18ms TTL=56
Ping statistics for 221.192.166.216: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 17ms, Maximum = 19ms, Average = 18ms查看 |
GET PING Trace Dig |
|
湖南永州市电信 |
电信 |
湖南 |
113.219.201.207 |
中国湖南长沙电信 |
10 |
10 |
0 |
32.54ms |
13.18ms |
17.377ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (113.219.201.207) with 32 bytes of data: Reply from 113.219.201.207: bytes=32 time=14ms TTL=56 Reply from 113.219.201.207: bytes=32 time=33ms TTL=56 Reply from 113.219.201.207: bytes=32 time=13ms TTL=56 Reply from 113.219.201.207: bytes=32 time=24ms TTL=56 Reply from 113.219.201.207: bytes=32 time=16ms TTL=56 Reply from 113.219.201.207: bytes=32 time=14ms TTL=56 Reply from 113.219.201.207: bytes=32 time=13ms TTL=56 Reply from 113.219.201.207: bytes=32 time=19ms TTL=56 Reply from 113.219.201.207: bytes=32 time=15ms TTL=56 Reply from 113.219.201.207: bytes=32 time=13ms TTL=56
Ping statistics for 113.219.201.207: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 33ms, Average = 17ms查看 |
GET PING Trace Dig |
|
广东广州市移动 |
移动 |
广东 |
120.233.45.178 |
中国广东深圳移动 |
10 |
10 |
0 |
18.17ms |
16.269ms |
17.312ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (120.233.45.178) with 32 bytes of data: Reply from 120.233.45.178: bytes=32 time=17ms TTL=54 Reply from 120.233.45.178: bytes=32 time=17ms TTL=54 Reply from 120.233.45.178: bytes=32 time=18ms TTL=54 Reply from 120.233.45.178: bytes=32 time=17ms TTL=54 Reply from 120.233.45.178: bytes=32 time=17ms TTL=54 Reply from 120.233.45.178: bytes=32 time=18ms TTL=54 Reply from 120.233.45.178: bytes=32 time=18ms TTL=54 Reply from 120.233.45.178: bytes=32 time=16ms TTL=54 Reply from 120.233.45.178: bytes=32 time=17ms TTL=54 Reply from 120.233.45.178: bytes=32 time=17ms TTL=54
Ping statistics for 120.233.45.178: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 16ms, Maximum = 18ms, Average = 17ms查看 |
GET PING Trace Dig |
|
广西南宁市联通 |
联通 |
广西 |
111.12.62.218 |
中国广西南宁移动 |
10 |
10 |
0 |
18.14ms |
16.56ms |
17.173ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (111.12.62.218) with 32 bytes of data: Reply from 111.12.62.218: bytes=32 time=18ms TTL=55 Reply from 111.12.62.218: bytes=32 time=17ms TTL=55 Reply from 111.12.62.218: bytes=32 time=17ms TTL=55 Reply from 111.12.62.218: bytes=32 time=17ms TTL=55 Reply from 111.12.62.218: bytes=32 time=17ms TTL=55 Reply from 111.12.62.218: bytes=32 time=17ms TTL=55 Reply from 111.12.62.218: bytes=32 time=17ms TTL=55 Reply from 111.12.62.218: bytes=32 time=17ms TTL=55 Reply from 111.12.62.218: bytes=32 time=17ms TTL=55 Reply from 111.12.62.218: bytes=32 time=17ms TTL=55
Ping statistics for 111.12.62.218: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 17ms, Maximum = 18ms, Average = 17ms查看 |
GET PING Trace Dig |
|
山西吕梁市联通 |
联通 |
山西 |
60.222.11.135 |
中国山西运城联通 |
10 |
10 |
0 |
20.274ms |
16.094ms |
17.137ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (60.222.11.135) with 32 bytes of data: Reply from 60.222.11.135: bytes=32 time=16ms TTL=56 Reply from 60.222.11.135: bytes=32 time=16ms TTL=56 Reply from 60.222.11.135: bytes=32 time=19ms TTL=56 Reply from 60.222.11.135: bytes=32 time=17ms TTL=56 Reply from 60.222.11.135: bytes=32 time=18ms TTL=56 Reply from 60.222.11.135: bytes=32 time=20ms TTL=56 Reply from 60.222.11.135: bytes=32 time=17ms TTL=56 Reply from 60.222.11.135: bytes=32 time=16ms TTL=56 Reply from 60.222.11.135: bytes=32 time=16ms TTL=56 Reply from 60.222.11.135: bytes=32 time=16ms TTL=56
Ping statistics for 60.222.11.135: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 16ms, Maximum = 20ms, Average = 17ms查看 |
GET PING Trace Dig |
|
江西赣州市联通 |
联通 |
江西 |
60.200.32.49 |
中国江西南昌广电 |
10 |
10 |
0 |
31.429ms |
13.612ms |
17.049ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (60.200.32.49) with 32 bytes of data: Reply from 60.200.32.49: bytes=32 time=15ms TTL=54 Reply from 60.200.32.49: bytes=32 time=14ms TTL=54 Reply from 60.200.32.49: bytes=32 time=31ms TTL=54 Reply from 60.200.32.49: bytes=32 time=16ms TTL=54 Reply from 60.200.32.49: bytes=32 time=14ms TTL=54 Reply from 60.200.32.49: bytes=32 time=23ms TTL=54 Reply from 60.200.32.49: bytes=32 time=15ms TTL=54 Reply from 60.200.32.49: bytes=32 time=14ms TTL=54 Reply from 60.200.32.49: bytes=32 time=14ms TTL=54 Reply from 60.200.32.49: bytes=32 time=14ms TTL=54
Ping statistics for 60.200.32.49: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 14ms, Maximum = 31ms, Average = 17ms查看 |
GET PING Trace Dig |
|
河南洛阳市电信 |
电信 |
河南 |
121.228.130.219 |
中国江苏苏州电信 |
10 |
10 |
0 |
17.108ms |
16.991ms |
17.022ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (121.228.130.219) with 32 bytes of data: Reply from 121.228.130.219: bytes=32 time=17ms TTL=54 Reply from 121.228.130.219: bytes=32 time=17ms TTL=54 Reply from 121.228.130.219: bytes=32 time=17ms TTL=54 Reply from 121.228.130.219: bytes=32 time=17ms TTL=54 Reply from 121.228.130.219: bytes=32 time=17ms TTL=54 Reply from 121.228.130.219: bytes=32 time=17ms TTL=54 Reply from 121.228.130.219: bytes=32 time=17ms TTL=54 Reply from 121.228.130.219: bytes=32 time=17ms TTL=54 Reply from 121.228.130.219: bytes=32 time=17ms TTL=54 Reply from 121.228.130.219: bytes=32 time=17ms TTL=54
Ping statistics for 121.228.130.219: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 17ms, Maximum = 17ms, Average = 17ms查看 |
GET PING Trace Dig |
|
湖北武汉市联通 |
联通 |
湖北 |
119.36.63.228 |
中国湖北武汉联通 |
10 |
10 |
0 |
17.06ms |
16.58ms |
16.808ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (119.36.63.228) with 32 bytes of data: Reply from 119.36.63.228: bytes=32 time=17ms TTL=56 Reply from 119.36.63.228: bytes=32 time=17ms TTL=56 Reply from 119.36.63.228: bytes=32 time=17ms TTL=56 Reply from 119.36.63.228: bytes=32 time=17ms TTL=56 Reply from 119.36.63.228: bytes=32 time=17ms TTL=56 Reply from 119.36.63.228: bytes=32 time=17ms TTL=56 Reply from 119.36.63.228: bytes=32 time=17ms TTL=56 Reply from 119.36.63.228: bytes=32 time=17ms TTL=56 Reply from 119.36.63.228: bytes=32 time=17ms TTL=56 Reply from 119.36.63.228: bytes=32 time=17ms TTL=56
Ping statistics for 119.36.63.228: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 17ms, Maximum = 17ms, Average = 17ms查看 |
GET PING Trace Dig |
|
西藏拉萨市电信 |
电信 |
西藏 |
183.240.239.240 |
中国广东广州移动 |
10 |
9 |
1 |
18.846ms |
15.363ms |
16.626ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (183.240.239.240) with 32 bytes of data: Reply from 183.240.239.240: bytes=32 time=16ms TTL=57 Reply from 183.240.239.240: bytes=32 time=15ms TTL=57 Reply from 183.240.239.240: bytes=32 time=19ms TTL=57 Reply from 183.240.239.240: bytes=32 time=15ms TTL=57 Reply from 183.240.239.240: bytes=32 time=15ms TTL=57 Reply from 183.240.239.240: bytes=32 time=15ms TTL=57 Reply from 183.240.239.240: bytes=32 time=19ms TTL=57 Request timed out. Reply from 183.240.239.240: bytes=32 time=18ms TTL=57 Reply from 183.240.239.240: bytes=32 time=16ms TTL=57
Ping statistics for 183.240.239.240: Packets: Sent = 10, Received = 9, Lost = 1 (10% loss), Approximate round trip times in milli-seconds: Minimum = 15ms, Maximum = 19ms, Average = 17ms查看 |
GET PING Trace Dig |
|
四川攀枝花市移动 |
移动 |
四川 |
112.45.115.19 |
中国四川成都移动 |
10 |
10 |
0 |
17.24ms |
16.4ms |
16.564ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (112.45.115.19) with 32 bytes of data: Reply from 112.45.115.19: bytes=32 time=17ms TTL=55 Reply from 112.45.115.19: bytes=32 time=16ms TTL=55 Reply from 112.45.115.19: bytes=32 time=16ms TTL=55 Reply from 112.45.115.19: bytes=32 time=16ms TTL=55 Reply from 112.45.115.19: bytes=32 time=16ms TTL=55 Reply from 112.45.115.19: bytes=32 time=17ms TTL=55 Reply from 112.45.115.19: bytes=32 time=17ms TTL=55 Reply from 112.45.115.19: bytes=32 time=17ms TTL=55 Reply from 112.45.115.19: bytes=32 time=16ms TTL=55 Reply from 112.45.115.19: bytes=32 time=17ms TTL=55
Ping statistics for 112.45.115.19: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 16ms, Maximum = 17ms, Average = 17ms查看 |
GET PING Trace Dig |
|
湖南常德市电信 |
电信 |
湖南 |
118.253.170.226 |
中国湖南怀化电信 |
10 |
10 |
0 |
20.169ms |
12.558ms |
16.155ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (118.253.170.226) with 32 bytes of data: Reply from 118.253.170.226: bytes=32 time=13ms TTL=56 Reply from 118.253.170.226: bytes=32 time=13ms TTL=56 Reply from 118.253.170.226: bytes=32 time=20ms TTL=56 Reply from 118.253.170.226: bytes=32 time=19ms TTL=56 Reply from 118.253.170.226: bytes=32 time=13ms TTL=56 Reply from 118.253.170.226: bytes=32 time=17ms TTL=56 Reply from 118.253.170.226: bytes=32 time=20ms TTL=56 Reply from 118.253.170.226: bytes=32 time=16ms TTL=56 Reply from 118.253.170.226: bytes=32 time=13ms TTL=56 Reply from 118.253.170.226: bytes=32 time=19ms TTL=56
Ping statistics for 118.253.170.226: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 20ms, Average = 16ms查看 |
GET PING Trace Dig |
|
山东济南市电信 |
电信 |
山东 |
116.196.134.207 |
中国上海 |
10 |
10 |
0 |
16.5ms |
15.3ms |
16.133ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (116.196.134.207) with 32 bytes of data: Reply from 116.196.134.207: bytes=32 time=17ms TTL=54 Reply from 116.196.134.207: bytes=32 time=16ms TTL=54 Reply from 116.196.134.207: bytes=32 time=15ms TTL=54 Reply from 116.196.134.207: bytes=32 time=16ms TTL=54 Reply from 116.196.134.207: bytes=32 time=16ms TTL=54 Reply from 116.196.134.207: bytes=32 time=16ms TTL=54 Reply from 116.196.134.207: bytes=32 time=16ms TTL=54 Reply from 116.196.134.207: bytes=32 time=16ms TTL=54 Reply from 116.196.134.207: bytes=32 time=16ms TTL=54 Reply from 116.196.134.207: bytes=32 time=16ms TTL=54
Ping statistics for 116.196.134.207: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 15ms, Maximum = 17ms, Average = 16ms查看 |
GET PING Trace Dig |
|
上海上海市移动 |
移动 |
上海 |
61.170.79.110 |
中国上海电信 |
10 |
10 |
0 |
50.754ms |
6.921ms |
15.534ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (61.170.79.110) with 32 bytes of data: Reply from 61.170.79.110: bytes=32 time=51ms TTL=56 Reply from 61.170.79.110: bytes=32 time=16ms TTL=56 Reply from 61.170.79.110: bytes=32 time=10ms TTL=56 Reply from 61.170.79.110: bytes=32 time=7ms TTL=56 Reply from 61.170.79.110: bytes=32 time=28ms TTL=56 Reply from 61.170.79.110: bytes=32 time=10ms TTL=56 Reply from 61.170.79.110: bytes=32 time=9ms TTL=56 Reply from 61.170.79.110: bytes=32 time=7ms TTL=56 Reply from 61.170.79.110: bytes=32 time=9ms TTL=56 Reply from 61.170.79.110: bytes=32 time=9ms TTL=56
Ping statistics for 61.170.79.110: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 51ms, Average = 16ms查看 |
GET PING Trace Dig |
|
甘肃兰州市联通 |
联通 |
甘肃 |
117.157.133.27 |
中国甘肃酒泉移动 |
10 |
10 |
0 |
16.4ms |
14.901ms |
15.442ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (117.157.133.27) with 32 bytes of data: Reply from 117.157.133.27: bytes=32 time=15ms TTL=55 Reply from 117.157.133.27: bytes=32 time=15ms TTL=55 Reply from 117.157.133.27: bytes=32 time=15ms TTL=55 Reply from 117.157.133.27: bytes=32 time=15ms TTL=55 Reply from 117.157.133.27: bytes=32 time=15ms TTL=55 Reply from 117.157.133.27: bytes=32 time=16ms TTL=55 Reply from 117.157.133.27: bytes=32 time=15ms TTL=55 Reply from 117.157.133.27: bytes=32 time=16ms TTL=55 Reply from 117.157.133.27: bytes=32 time=16ms TTL=55 Reply from 117.157.133.27: bytes=32 time=16ms TTL=55
Ping statistics for 117.157.133.27: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 15ms, Maximum = 16ms, Average = 15ms查看 |
GET PING Trace Dig |
|
安徽六安市电信 |
电信 |
安徽 |
112.29.220.125 |
中国安徽合肥移动 |
10 |
10 |
0 |
32.99ms |
9.318ms |
15.272ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (112.29.220.125) with 32 bytes of data: Reply from 112.29.220.125: bytes=32 time=26ms TTL=57 Reply from 112.29.220.125: bytes=32 time=11ms TTL=57 Reply from 112.29.220.125: bytes=32 time=10ms TTL=57 Reply from 112.29.220.125: bytes=32 time=17ms TTL=57 Reply from 112.29.220.125: bytes=32 time=12ms TTL=57 Reply from 112.29.220.125: bytes=32 time=9ms TTL=57 Reply from 112.29.220.125: bytes=32 time=10ms TTL=57 Reply from 112.29.220.125: bytes=32 time=33ms TTL=57 Reply from 112.29.220.125: bytes=32 time=10ms TTL=57 Reply from 112.29.220.125: bytes=32 time=14ms TTL=57
Ping statistics for 112.29.220.125: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 9ms, Maximum = 33ms, Average = 15ms查看 |
GET PING Trace Dig |
|
辽宁沈阳市电信 |
电信 |
辽宁 |
36.131.139.244 |
中国辽宁丹东移动 |
10 |
10 |
0 |
45.8ms |
11.46ms |
15.174ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (36.131.139.244) with 32 bytes of data: Reply from 36.131.139.244: bytes=32 time=12ms TTL=55 Reply from 36.131.139.244: bytes=32 time=11ms TTL=55 Reply from 36.131.139.244: bytes=32 time=46ms TTL=55 Reply from 36.131.139.244: bytes=32 time=12ms TTL=55 Reply from 36.131.139.244: bytes=32 time=12ms TTL=55 Reply from 36.131.139.244: bytes=32 time=12ms TTL=55 Reply from 36.131.139.244: bytes=32 time=12ms TTL=55 Reply from 36.131.139.244: bytes=32 time=12ms TTL=55 Reply from 36.131.139.244: bytes=32 time=12ms TTL=55 Reply from 36.131.139.244: bytes=32 time=12ms TTL=55
Ping statistics for 36.131.139.244: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 46ms, Average = 15ms查看 |
GET PING Trace Dig |
|
山西吕梁市电信 |
电信 |
山西 |
1.71.81.78 |
中国山西太原电信 |
10 |
10 |
0 |
45.1ms |
9.48ms |
15.135ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (1.71.81.78) with 32 bytes of data: Reply from 1.71.81.78: bytes=32 time=16ms TTL=53 Reply from 1.71.81.78: bytes=32 time=10ms TTL=53 Reply from 1.71.81.78: bytes=32 time=11ms TTL=53 Reply from 1.71.81.78: bytes=32 time=45ms TTL=53 Reply from 1.71.81.78: bytes=32 time=10ms TTL=53 Reply from 1.71.81.78: bytes=32 time=9ms TTL=53 Reply from 1.71.81.78: bytes=32 time=12ms TTL=53 Reply from 1.71.81.78: bytes=32 time=13ms TTL=53 Reply from 1.71.81.78: bytes=32 time=16ms TTL=53 Reply from 1.71.81.78: bytes=32 time=10ms TTL=53
Ping statistics for 1.71.81.78: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 9ms, Maximum = 45ms, Average = 15ms查看 |
GET PING Trace Dig |
|
陕西榆林市联通 |
联通 |
陕西 |
124.89.110.212 |
中国陕西安康联通 |
10 |
10 |
0 |
16.053ms |
14.424ms |
15.1ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (124.89.110.212) with 32 bytes of data: Reply from 124.89.110.212: bytes=32 time=15ms TTL=51 Reply from 124.89.110.212: bytes=32 time=15ms TTL=51 Reply from 124.89.110.212: bytes=32 time=15ms TTL=51 Reply from 124.89.110.212: bytes=32 time=15ms TTL=51 Reply from 124.89.110.212: bytes=32 time=16ms TTL=51 Reply from 124.89.110.212: bytes=32 time=16ms TTL=51 Reply from 124.89.110.212: bytes=32 time=14ms TTL=51 Reply from 124.89.110.212: bytes=32 time=14ms TTL=51 Reply from 124.89.110.212: bytes=32 time=15ms TTL=51 Reply from 124.89.110.212: bytes=32 time=15ms TTL=51
Ping statistics for 124.89.110.212: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 14ms, Maximum = 16ms, Average = 15ms查看 |
GET PING Trace Dig |
|
山东济宁市移动 |
移动 |
山东 |
120.220.78.233 |
中国山东济南移动 |
10 |
10 |
0 |
18.22ms |
13.68ms |
15.025ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (120.220.78.233) with 32 bytes of data: Reply from 120.220.78.233: bytes=32 time=14ms TTL=55 Reply from 120.220.78.233: bytes=32 time=14ms TTL=55 Reply from 120.220.78.233: bytes=32 time=14ms TTL=55 Reply from 120.220.78.233: bytes=32 time=14ms TTL=55 Reply from 120.220.78.233: bytes=32 time=18ms TTL=55 Reply from 120.220.78.233: bytes=32 time=18ms TTL=55 Reply from 120.220.78.233: bytes=32 time=14ms TTL=55 Reply from 120.220.78.233: bytes=32 time=14ms TTL=55 Reply from 120.220.78.233: bytes=32 time=15ms TTL=55 Reply from 120.220.78.233: bytes=32 time=16ms TTL=55
Ping statistics for 120.220.78.233: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 14ms, Maximum = 18ms, Average = 15ms查看 |
GET PING Trace Dig |
|
黑龙江佳木斯市移动 |
移动 |
黑龙江 |
111.42.186.75 |
中国黑龙江哈尔滨移动 |
10 |
10 |
0 |
15.439ms |
14.68ms |
14.851ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (111.42.186.75) with 32 bytes of data: Reply from 111.42.186.75: bytes=32 time=15ms TTL=56 Reply from 111.42.186.75: bytes=32 time=15ms TTL=56 Reply from 111.42.186.75: bytes=32 time=15ms TTL=56 Reply from 111.42.186.75: bytes=32 time=15ms TTL=56 Reply from 111.42.186.75: bytes=32 time=15ms TTL=56 Reply from 111.42.186.75: bytes=32 time=15ms TTL=56 Reply from 111.42.186.75: bytes=32 time=15ms TTL=56 Reply from 111.42.186.75: bytes=32 time=15ms TTL=56 Reply from 111.42.186.75: bytes=32 time=15ms TTL=56 Reply from 111.42.186.75: bytes=32 time=15ms TTL=56
Ping statistics for 111.42.186.75: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 15ms, Maximum = 15ms, Average = 15ms查看 |
GET PING Trace Dig |
|
重庆重庆市移动 |
移动 |
重庆 |
183.231.33.83 |
中国重庆移动 |
10 |
10 |
0 |
15.12ms |
14.68ms |
14.835ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (183.231.33.83) with 32 bytes of data: Reply from 183.231.33.83: bytes=32 time=15ms TTL=54 Reply from 183.231.33.83: bytes=32 time=15ms TTL=54 Reply from 183.231.33.83: bytes=32 time=15ms TTL=54 Reply from 183.231.33.83: bytes=32 time=15ms TTL=54 Reply from 183.231.33.83: bytes=32 time=15ms TTL=54 Reply from 183.231.33.83: bytes=32 time=15ms TTL=54 Reply from 183.231.33.83: bytes=32 time=15ms TTL=54 Reply from 183.231.33.83: bytes=32 time=15ms TTL=54 Reply from 183.231.33.83: bytes=32 time=15ms TTL=54 Reply from 183.231.33.83: bytes=32 time=15ms TTL=54
Ping statistics for 183.231.33.83: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 15ms, Maximum = 15ms, Average = 15ms查看 |
GET PING Trace Dig |
|
山西忻州市联通 |
联通 |
山西 |
60.222.200.223 |
中国山西运城联通 |
10 |
10 |
0 |
17.356ms |
13.814ms |
14.818ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (60.222.200.223) with 32 bytes of data: Reply from 60.222.200.223: bytes=32 time=14ms TTL=57 Reply from 60.222.200.223: bytes=32 time=14ms TTL=57 Reply from 60.222.200.223: bytes=32 time=14ms TTL=57 Reply from 60.222.200.223: bytes=32 time=15ms TTL=57 Reply from 60.222.200.223: bytes=32 time=15ms TTL=57 Reply from 60.222.200.223: bytes=32 time=15ms TTL=57 Reply from 60.222.200.223: bytes=32 time=14ms TTL=57 Reply from 60.222.200.223: bytes=32 time=14ms TTL=57 Reply from 60.222.200.223: bytes=32 time=17ms TTL=57 Reply from 60.222.200.223: bytes=32 time=16ms TTL=57
Ping statistics for 60.222.200.223: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 14ms, Maximum = 17ms, Average = 15ms查看 |
GET PING Trace Dig |
|
辽宁营口市移动 |
移动 |
辽宁 |
36.131.139.243 |
中国辽宁丹东移动 |
10 |
10 |
0 |
15.256ms |
14.477ms |
14.739ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (36.131.139.243) with 32 bytes of data: Reply from 36.131.139.243: bytes=32 time=15ms TTL=55 Reply from 36.131.139.243: bytes=32 time=15ms TTL=55 Reply from 36.131.139.243: bytes=32 time=14ms TTL=55 Reply from 36.131.139.243: bytes=32 time=15ms TTL=55 Reply from 36.131.139.243: bytes=32 time=15ms TTL=55 Reply from 36.131.139.243: bytes=32 time=15ms TTL=55 Reply from 36.131.139.243: bytes=32 time=15ms TTL=55 Reply from 36.131.139.243: bytes=32 time=15ms TTL=55 Reply from 36.131.139.243: bytes=32 time=15ms TTL=55 Reply from 36.131.139.243: bytes=32 time=15ms TTL=55
Ping statistics for 36.131.139.243: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 14ms, Maximum = 15ms, Average = 15ms查看 |
GET PING Trace Dig |
|
河北廊坊市联通 |
联通 |
河北 |
221.192.166.214 |
中国河北石家庄联通 |
10 |
10 |
0 |
33.9ms |
11.12ms |
14.564ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (221.192.166.214) with 32 bytes of data: Reply from 221.192.166.214: bytes=32 time=12ms TTL=56 Reply from 221.192.166.214: bytes=32 time=17ms TTL=56 Reply from 221.192.166.214: bytes=32 time=12ms TTL=56 Reply from 221.192.166.214: bytes=32 time=12ms TTL=56 Reply from 221.192.166.214: bytes=32 time=11ms TTL=56 Reply from 221.192.166.214: bytes=32 time=34ms TTL=56 Reply from 221.192.166.214: bytes=32 time=12ms TTL=56 Reply from 221.192.166.214: bytes=32 time=11ms TTL=56 Reply from 221.192.166.214: bytes=32 time=14ms TTL=56 Reply from 221.192.166.214: bytes=32 time=12ms TTL=56
Ping statistics for 221.192.166.214: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 34ms, Average = 15ms查看 |
GET PING Trace Dig |
|
吉林白山市联通 |
联通 |
吉林 |
122.141.229.16 |
中国吉林长春联通 |
10 |
8 |
2 |
15.606ms |
13.549ms |
14.441ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (122.141.229.16) with 32 bytes of data: Reply from 122.141.229.16: bytes=32 time=14ms TTL=57 Reply from 122.141.229.16: bytes=32 time=14ms TTL=57 Reply from 122.141.229.16: bytes=32 time=14ms TTL=57 Reply from 122.141.229.16: bytes=32 time=16ms TTL=57 Reply from 122.141.229.16: bytes=32 time=15ms TTL=57 Reply from 122.141.229.16: bytes=32 time=14ms TTL=57 Reply from 122.141.229.16: bytes=32 time=14ms TTL=57 Request timed out. Request timed out. Reply from 122.141.229.16: bytes=32 time=15ms TTL=57
Ping statistics for 122.141.229.16: Packets: Sent = 10, Received = 8, Lost = 2 (20% loss), Approximate round trip times in milli-seconds: Minimum = 14ms, Maximum = 16ms, Average = 14ms查看 |
GET PING Trace Dig |
|
浙江嘉兴电信 |
电信 |
浙江 |
122.225.209.185 |
中国浙江杭州电信 |
10 |
10 |
0 |
18.9ms |
13.02ms |
14.388ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (122.225.209.185) with 32 bytes of data: Reply from 122.225.209.185: bytes=32 time=15ms TTL=54 Reply from 122.225.209.185: bytes=32 time=16ms TTL=54 Reply from 122.225.209.185: bytes=32 time=13ms TTL=54 Reply from 122.225.209.185: bytes=32 time=14ms TTL=54 Reply from 122.225.209.185: bytes=32 time=14ms TTL=54 Reply from 122.225.209.185: bytes=32 time=13ms TTL=54 Reply from 122.225.209.185: bytes=32 time=13ms TTL=54 Reply from 122.225.209.185: bytes=32 time=13ms TTL=54 Reply from 122.225.209.185: bytes=32 time=14ms TTL=54 Reply from 122.225.209.185: bytes=32 time=19ms TTL=54
Ping statistics for 122.225.209.185: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 19ms, Average = 14ms查看 |
GET PING Trace Dig |
|
江西赣州市移动 |
移动 |
江西 |
117.167.114.21 |
中国江西南昌移动 |
10 |
10 |
0 |
15.88ms |
13.779ms |
14.203ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (117.167.114.21) with 32 bytes of data: Reply from 117.167.114.21: bytes=32 time=14ms TTL=56 Reply from 117.167.114.21: bytes=32 time=14ms TTL=56 Reply from 117.167.114.21: bytes=32 time=14ms TTL=56 Reply from 117.167.114.21: bytes=32 time=16ms TTL=56 Reply from 117.167.114.21: bytes=32 time=14ms TTL=56 Reply from 117.167.114.21: bytes=32 time=14ms TTL=56 Reply from 117.167.114.21: bytes=32 time=14ms TTL=56 Reply from 117.167.114.21: bytes=32 time=14ms TTL=56 Reply from 117.167.114.21: bytes=32 time=14ms TTL=56 Reply from 117.167.114.21: bytes=32 time=14ms TTL=56
Ping statistics for 117.167.114.21: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 14ms, Maximum = 16ms, Average = 14ms查看 |
GET PING Trace Dig |
|
江西新余市电信 |
电信 |
江西 |
182.87.105.54 |
中国江西赣州电信 |
10 |
10 |
0 |
14.4ms |
13.7ms |
14.012ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (182.87.105.54) with 32 bytes of data: Reply from 182.87.105.54: bytes=32 time=14ms TTL=53 Reply from 182.87.105.54: bytes=32 time=14ms TTL=53 Reply from 182.87.105.54: bytes=32 time=14ms TTL=53 Reply from 182.87.105.54: bytes=32 time=14ms TTL=53 Reply from 182.87.105.54: bytes=32 time=14ms TTL=53 Reply from 182.87.105.54: bytes=32 time=14ms TTL=53 Reply from 182.87.105.54: bytes=32 time=14ms TTL=53 Reply from 182.87.105.54: bytes=32 time=14ms TTL=53 Reply from 182.87.105.54: bytes=32 time=14ms TTL=53 Reply from 182.87.105.54: bytes=32 time=14ms TTL=53
Ping statistics for 182.87.105.54: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 14ms, Maximum = 14ms, Average = 14ms查看 |
GET PING Trace Dig |
|
河南洛阳市电信 |
电信 |
河南 |
58.215.155.8 |
中国江苏无锡电信 |
10 |
10 |
0 |
14.143ms |
13.822ms |
13.978ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (58.215.155.8) with 32 bytes of data: Reply from 58.215.155.8: bytes=32 time=14ms TTL=54 Reply from 58.215.155.8: bytes=32 time=14ms TTL=54 Reply from 58.215.155.8: bytes=32 time=14ms TTL=54 Reply from 58.215.155.8: bytes=32 time=14ms TTL=54 Reply from 58.215.155.8: bytes=32 time=14ms TTL=54 Reply from 58.215.155.8: bytes=32 time=14ms TTL=54 Reply from 58.215.155.8: bytes=32 time=14ms TTL=54 Reply from 58.215.155.8: bytes=32 time=14ms TTL=54 Reply from 58.215.155.8: bytes=32 time=14ms TTL=54 Reply from 58.215.155.8: bytes=32 time=14ms TTL=54
Ping statistics for 58.215.155.8: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 14ms, Maximum = 14ms, Average = 14ms查看 |
GET PING Trace Dig |
|
甘肃陇南市电信 |
电信 |
甘肃 |
60.165.64.82 |
中国甘肃天水电信 |
10 |
10 |
0 |
15.075ms |
13.442ms |
13.975ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (60.165.64.82) with 32 bytes of data: Reply from 60.165.64.82: bytes=32 time=14ms TTL=54 Reply from 60.165.64.82: bytes=32 time=15ms TTL=52 Reply from 60.165.64.82: bytes=32 time=14ms TTL=52 Reply from 60.165.64.82: bytes=32 time=15ms TTL=52 Reply from 60.165.64.82: bytes=32 time=13ms TTL=54 Reply from 60.165.64.82: bytes=32 time=13ms TTL=52 Reply from 60.165.64.82: bytes=32 time=13ms TTL=54 Reply from 60.165.64.82: bytes=32 time=14ms TTL=54 Reply from 60.165.64.82: bytes=32 time=14ms TTL=54 Reply from 60.165.64.82: bytes=32 time=13ms TTL=54
Ping statistics for 60.165.64.82: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 15ms, Average = 14ms查看 |
GET PING Trace Dig |
|
吉林松原联通 |
联通 |
吉林 |
122.141.229.18 |
中国吉林长春联通 |
10 |
10 |
0 |
22.131ms |
11.869ms |
13.754ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (122.141.229.18) with 32 bytes of data: Reply from 122.141.229.18: bytes=32 time=22ms TTL=57 Reply from 122.141.229.18: bytes=32 time=12ms TTL=57 Reply from 122.141.229.18: bytes=32 time=12ms TTL=57 Reply from 122.141.229.18: bytes=32 time=13ms TTL=57 Reply from 122.141.229.18: bytes=32 time=12ms TTL=57 Reply from 122.141.229.18: bytes=32 time=13ms TTL=57 Reply from 122.141.229.18: bytes=32 time=12ms TTL=57 Reply from 122.141.229.18: bytes=32 time=13ms TTL=57 Reply from 122.141.229.18: bytes=32 time=16ms TTL=57 Reply from 122.141.229.18: bytes=32 time=12ms TTL=57
Ping statistics for 122.141.229.18: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 12ms, Maximum = 22ms, Average = 14ms查看 |
GET PING Trace Dig |
|
湖南长沙联通 |
联通 |
湖南 |
36.158.219.34 |
中国湖南长沙移动 |
10 |
10 |
0 |
35.237ms |
9.715ms |
13.723ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (36.158.219.34) with 32 bytes of data: Reply from 36.158.219.34: bytes=32 time=12ms TTL=52 Reply from 36.158.219.34: bytes=32 time=11ms TTL=52 Reply from 36.158.219.34: bytes=32 time=10ms TTL=52 Reply from 36.158.219.34: bytes=32 time=15ms TTL=52 Reply from 36.158.219.34: bytes=32 time=11ms TTL=52 Reply from 36.158.219.34: bytes=32 time=10ms TTL=52 Reply from 36.158.219.34: bytes=32 time=10ms TTL=52 Reply from 36.158.219.34: bytes=32 time=35ms TTL=52 Reply from 36.158.219.34: bytes=32 time=10ms TTL=52 Reply from 36.158.219.34: bytes=32 time=13ms TTL=52
Ping statistics for 36.158.219.34: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 35ms, Average = 14ms查看 |
GET PING Trace Dig |
|
河北邯郸市移动 |
移动 |
河北 |
221.192.166.213 |
中国河北石家庄联通 |
10 |
10 |
0 |
14.04ms |
13.3ms |
13.668ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (221.192.166.213) with 32 bytes of data: Reply from 221.192.166.213: bytes=32 time=14ms TTL=56 Reply from 221.192.166.213: bytes=32 time=14ms TTL=56 Reply from 221.192.166.213: bytes=32 time=14ms TTL=56 Reply from 221.192.166.213: bytes=32 time=14ms TTL=56 Reply from 221.192.166.213: bytes=32 time=13ms TTL=56 Reply from 221.192.166.213: bytes=32 time=14ms TTL=56 Reply from 221.192.166.213: bytes=32 time=14ms TTL=56 Reply from 221.192.166.213: bytes=32 time=14ms TTL=56 Reply from 221.192.166.213: bytes=32 time=13ms TTL=56 Reply from 221.192.166.213: bytes=32 time=13ms TTL=56
Ping statistics for 221.192.166.213: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 14ms, Average = 14ms查看 |
GET PING Trace Dig |
|
湖北武汉移动 |
移动 |
湖北 |
120.202.140.230 |
中国湖北荆门移动 |
10 |
9 |
1 |
22.755ms |
10.68ms |
13.627ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (120.202.140.230) with 32 bytes of data: Reply from 120.202.140.230: bytes=32 time=12ms TTL=57 Reply from 120.202.140.230: bytes=32 time=23ms TTL=57 Request timed out. Reply from 120.202.140.230: bytes=32 time=12ms TTL=57 Reply from 120.202.140.230: bytes=32 time=14ms TTL=57 Reply from 120.202.140.230: bytes=32 time=11ms TTL=57 Reply from 120.202.140.230: bytes=32 time=13ms TTL=57 Reply from 120.202.140.230: bytes=32 time=12ms TTL=57 Reply from 120.202.140.230: bytes=32 time=11ms TTL=57 Reply from 120.202.140.230: bytes=32 time=16ms TTL=57
Ping statistics for 120.202.140.230: Packets: Sent = 10, Received = 9, Lost = 1 (10% loss), Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 23ms, Average = 14ms查看 |
GET PING Trace Dig |
|
云南楚雄彝族自治州联通 |
联通 |
云南 |
182.243.27.218 |
中国云南昭通电信 |
10 |
10 |
0 |
21.974ms |
8.66ms |
13.606ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (182.243.27.218) with 32 bytes of data: Reply from 182.243.27.218: bytes=32 time=9ms TTL=56 Reply from 182.243.27.218: bytes=32 time=9ms TTL=56 Reply from 182.243.27.218: bytes=32 time=19ms TTL=56 Reply from 182.243.27.218: bytes=32 time=15ms TTL=56 Reply from 182.243.27.218: bytes=32 time=20ms TTL=56 Reply from 182.243.27.218: bytes=32 time=9ms TTL=56 Reply from 182.243.27.218: bytes=32 time=9ms TTL=56 Reply from 182.243.27.218: bytes=32 time=15ms TTL=56 Reply from 182.243.27.218: bytes=32 time=10ms TTL=56 Reply from 182.243.27.218: bytes=32 time=22ms TTL=56
Ping statistics for 182.243.27.218: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 9ms, Maximum = 22ms, Average = 14ms查看 |
GET PING Trace Dig |
|
重庆重庆市电信 |
电信 |
重庆 |
219.153.157.104 |
中国重庆电信 |
10 |
10 |
0 |
15.299ms |
13.161ms |
13.459ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (219.153.157.104) with 32 bytes of data: Reply from 219.153.157.104: bytes=32 time=15ms TTL=56 Reply from 219.153.157.104: bytes=32 time=13ms TTL=56 Reply from 219.153.157.104: bytes=32 time=13ms TTL=56 Reply from 219.153.157.104: bytes=32 time=13ms TTL=56 Reply from 219.153.157.104: bytes=32 time=13ms TTL=56 Reply from 219.153.157.104: bytes=32 time=13ms TTL=56 Reply from 219.153.157.104: bytes=32 time=13ms TTL=56 Reply from 219.153.157.104: bytes=32 time=13ms TTL=56 Reply from 219.153.157.104: bytes=32 time=13ms TTL=56 Reply from 219.153.157.104: bytes=32 time=13ms TTL=56
Ping statistics for 219.153.157.104: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 15ms, Average = 13ms查看 |
GET PING Trace Dig |
|
云南保山市电信 |
电信 |
云南 |
36.147.34.24 |
中国云南昆明移动 |
10 |
10 |
0 |
14.06ms |
12.58ms |
13.192ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (36.147.34.24) with 32 bytes of data: Reply from 36.147.34.24: bytes=32 time=14ms TTL=57 Reply from 36.147.34.24: bytes=32 time=13ms TTL=57 Reply from 36.147.34.24: bytes=32 time=13ms TTL=57 Reply from 36.147.34.24: bytes=32 time=14ms TTL=57 Reply from 36.147.34.24: bytes=32 time=13ms TTL=57 Reply from 36.147.34.24: bytes=32 time=13ms TTL=57 Reply from 36.147.34.24: bytes=32 time=13ms TTL=57 Reply from 36.147.34.24: bytes=32 time=13ms TTL=57 Reply from 36.147.34.24: bytes=32 time=13ms TTL=57 Reply from 36.147.34.24: bytes=32 time=13ms TTL=57
Ping statistics for 36.147.34.24: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 14ms, Average = 13ms查看 |
GET PING Trace Dig |
|
辽宁锦州市联通 |
联通 |
辽宁 |
124.95.157.87 |
中国辽宁沈阳联通 |
10 |
10 |
0 |
16.222ms |
11.574ms |
13.139ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (124.95.157.87) with 32 bytes of data: Reply from 124.95.157.87: bytes=32 time=12ms TTL=55 Reply from 124.95.157.87: bytes=32 time=12ms TTL=55 Reply from 124.95.157.87: bytes=32 time=12ms TTL=55 Reply from 124.95.157.87: bytes=32 time=16ms TTL=55 Reply from 124.95.157.87: bytes=32 time=12ms TTL=55 Reply from 124.95.157.87: bytes=32 time=15ms TTL=55 Reply from 124.95.157.87: bytes=32 time=12ms TTL=55 Reply from 124.95.157.87: bytes=32 time=12ms TTL=55 Reply from 124.95.157.87: bytes=32 time=14ms TTL=55 Reply from 124.95.157.87: bytes=32 time=15ms TTL=55
Ping statistics for 124.95.157.87: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 12ms, Maximum = 16ms, Average = 13ms查看 |
GET PING Trace Dig |
|
黑龙江鸡西市联通 |
联通 |
黑龙江 |
1.189.232.71 |
中国黑龙江哈尔滨联通 |
10 |
10 |
0 |
14.48ms |
10.7ms |
13.064ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (1.189.232.71) with 32 bytes of data: Reply from 1.189.232.71: bytes=32 time=14ms TTL=56 Reply from 1.189.232.71: bytes=32 time=14ms TTL=56 Reply from 1.189.232.71: bytes=32 time=11ms TTL=56 Reply from 1.189.232.71: bytes=32 time=14ms TTL=56 Reply from 1.189.232.71: bytes=32 time=13ms TTL=56 Reply from 1.189.232.71: bytes=32 time=13ms TTL=56 Reply from 1.189.232.71: bytes=32 time=14ms TTL=56 Reply from 1.189.232.71: bytes=32 time=12ms TTL=56 Reply from 1.189.232.71: bytes=32 time=14ms TTL=56 Reply from 1.189.232.71: bytes=32 time=11ms TTL=56
Ping statistics for 1.189.232.71: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 14ms, Average = 13ms查看 |
GET PING Trace Dig |
|
吉林松原市电信 |
电信 |
吉林 |
122.141.229.19 |
中国吉林长春联通 |
10 |
10 |
0 |
24.001ms |
9.734ms |
12.864ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (122.141.229.19) with 32 bytes of data: Reply from 122.141.229.19: bytes=32 time=24ms TTL=57 Reply from 122.141.229.19: bytes=32 time=14ms TTL=57 Reply from 122.141.229.19: bytes=32 time=12ms TTL=57 Reply from 122.141.229.19: bytes=32 time=15ms TTL=57 Reply from 122.141.229.19: bytes=32 time=11ms TTL=57 Reply from 122.141.229.19: bytes=32 time=10ms TTL=57 Reply from 122.141.229.19: bytes=32 time=10ms TTL=57 Reply from 122.141.229.19: bytes=32 time=12ms TTL=57 Reply from 122.141.229.19: bytes=32 time=11ms TTL=57 Reply from 122.141.229.19: bytes=32 time=11ms TTL=57
Ping statistics for 122.141.229.19: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 24ms, Average = 13ms查看 |
GET PING Trace Dig |
|
福建泉州市电信 |
电信 |
福建 |
220.160.45.39 |
中国福建厦门电信 |
10 |
10 |
0 |
32.785ms |
6.58ms |
12.595ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (220.160.45.39) with 32 bytes of data: Reply from 220.160.45.39: bytes=32 time=10ms TTL=56 Reply from 220.160.45.39: bytes=32 time=7ms TTL=56 Reply from 220.160.45.39: bytes=32 time=11ms TTL=56 Reply from 220.160.45.39: bytes=32 time=7ms TTL=56 Reply from 220.160.45.39: bytes=32 time=7ms TTL=56 Reply from 220.160.45.39: bytes=32 time=7ms TTL=56 Reply from 220.160.45.39: bytes=32 time=15ms TTL=56 Reply from 220.160.45.39: bytes=32 time=33ms TTL=56 Reply from 220.160.45.39: bytes=32 time=7ms TTL=56 Reply from 220.160.45.39: bytes=32 time=23ms TTL=56
Ping statistics for 220.160.45.39: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 33ms, Average = 13ms查看 |
GET PING Trace Dig |
|
云南昭通市联通 |
联通 |
云南 |
36.147.34.26 |
中国云南昆明移动 |
10 |
10 |
0 |
13.36ms |
12.08ms |
12.551ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (36.147.34.26) with 32 bytes of data: Reply from 36.147.34.26: bytes=32 time=13ms TTL=56 Reply from 36.147.34.26: bytes=32 time=12ms TTL=56 Reply from 36.147.34.26: bytes=32 time=13ms TTL=56 Reply from 36.147.34.26: bytes=32 time=13ms TTL=56 Reply from 36.147.34.26: bytes=32 time=12ms TTL=56 Reply from 36.147.34.26: bytes=32 time=13ms TTL=56 Reply from 36.147.34.26: bytes=32 time=12ms TTL=56 Reply from 36.147.34.26: bytes=32 time=12ms TTL=56 Reply from 36.147.34.26: bytes=32 time=12ms TTL=56 Reply from 36.147.34.26: bytes=32 time=13ms TTL=56
Ping statistics for 36.147.34.26: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 12ms, Maximum = 13ms, Average = 13ms查看 |
GET PING Trace Dig |
|
天津天津市移动 |
移动 |
天津 |
120.255.47.47 |
中国天津移动 |
10 |
10 |
0 |
14.54ms |
10.82ms |
12.358ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (120.255.47.47) with 32 bytes of data: Reply from 120.255.47.47: bytes=32 time=13ms TTL=58 Reply from 120.255.47.47: bytes=32 time=11ms TTL=58 Reply from 120.255.47.47: bytes=32 time=14ms TTL=58 Reply from 120.255.47.47: bytes=32 time=11ms TTL=58 Reply from 120.255.47.47: bytes=32 time=13ms TTL=58 Reply from 120.255.47.47: bytes=32 time=11ms TTL=58 Reply from 120.255.47.47: bytes=32 time=11ms TTL=58 Reply from 120.255.47.47: bytes=32 time=11ms TTL=58 Reply from 120.255.47.47: bytes=32 time=15ms TTL=58 Reply from 120.255.47.47: bytes=32 time=12ms TTL=58
Ping statistics for 120.255.47.47: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 15ms, Average = 12ms查看 |
GET PING Trace Dig |
|
河南驻马店移动 |
移动 |
河南 |
183.204.37.210 |
中国河南郑州移动 |
10 |
10 |
0 |
14.68ms |
11.42ms |
12.316ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (183.204.37.210) with 32 bytes of data: Reply from 183.204.37.210: bytes=32 time=12ms TTL=56 Reply from 183.204.37.210: bytes=32 time=12ms TTL=56 Reply from 183.204.37.210: bytes=32 time=12ms TTL=56 Reply from 183.204.37.210: bytes=32 time=12ms TTL=56 Reply from 183.204.37.210: bytes=32 time=11ms TTL=56 Reply from 183.204.37.210: bytes=32 time=14ms TTL=56 Reply from 183.204.37.210: bytes=32 time=12ms TTL=56 Reply from 183.204.37.210: bytes=32 time=12ms TTL=56 Reply from 183.204.37.210: bytes=32 time=12ms TTL=56 Reply from 183.204.37.210: bytes=32 time=15ms TTL=56
Ping statistics for 183.204.37.210: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 15ms, Average = 12ms查看 |
GET PING Trace Dig |
|
广东肇庆市移动 |
移动 |
广东 |
202.168.162.29 |
中国广东东莞广电 |
10 |
10 |
0 |
14.071ms |
11.238ms |
12.194ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (202.168.162.29) with 32 bytes of data: Reply from 202.168.162.29: bytes=32 time=12ms TTL=56 Reply from 202.168.162.29: bytes=32 time=12ms TTL=56 Reply from 202.168.162.29: bytes=32 time=14ms TTL=56 Reply from 202.168.162.29: bytes=32 time=12ms TTL=56 Reply from 202.168.162.29: bytes=32 time=12ms TTL=56 Reply from 202.168.162.29: bytes=32 time=14ms TTL=56 Reply from 202.168.162.29: bytes=32 time=12ms TTL=56 Reply from 202.168.162.29: bytes=32 time=12ms TTL=56 Reply from 202.168.162.29: bytes=32 time=11ms TTL=56 Reply from 202.168.162.29: bytes=32 time=12ms TTL=56
Ping statistics for 202.168.162.29: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 14ms, Average = 12ms查看 |
GET PING Trace Dig |
|
广西玉林市联通 |
联通 |
广西 |
113.16.214.89 |
中国广西南宁电信 |
10 |
10 |
0 |
36.976ms |
7.086ms |
12.163ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (113.16.214.89) with 32 bytes of data: Reply from 113.16.214.89: bytes=32 time=9ms TTL=57 Reply from 113.16.214.89: bytes=32 time=14ms TTL=57 Reply from 113.16.214.89: bytes=32 time=10ms TTL=57 Reply from 113.16.214.89: bytes=32 time=7ms TTL=57 Reply from 113.16.214.89: bytes=32 time=8ms TTL=57 Reply from 113.16.214.89: bytes=32 time=11ms TTL=57 Reply from 113.16.214.89: bytes=32 time=7ms TTL=57 Reply from 113.16.214.89: bytes=32 time=10ms TTL=57 Reply from 113.16.214.89: bytes=32 time=37ms TTL=57 Reply from 113.16.214.89: bytes=32 time=8ms TTL=57
Ping statistics for 113.16.214.89: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 37ms, Average = 12ms查看 |
GET PING Trace Dig |
|
安徽阜阳联通 |
联通 |
安徽 |
112.29.208.16 |
中国安徽合肥移动 |
10 |
10 |
0 |
17.182ms |
10.181ms |
12.093ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (112.29.208.16) with 32 bytes of data: Reply from 112.29.208.16: bytes=32 time=12ms TTL=56 Reply from 112.29.208.16: bytes=32 time=10ms TTL=56 Reply from 112.29.208.16: bytes=32 time=13ms TTL=56 Reply from 112.29.208.16: bytes=32 time=10ms TTL=56 Reply from 112.29.208.16: bytes=32 time=11ms TTL=56 Reply from 112.29.208.16: bytes=32 time=10ms TTL=56 Reply from 112.29.208.16: bytes=32 time=10ms TTL=56 Reply from 112.29.208.16: bytes=32 time=10ms TTL=56 Reply from 112.29.208.16: bytes=32 time=17ms TTL=56 Reply from 112.29.208.16: bytes=32 time=17ms TTL=56
Ping statistics for 112.29.208.16: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 17ms, Average = 12ms查看 |
GET PING Trace Dig |
|
江苏徐州市联通 |
联通 |
江苏 |
218.98.46.65 |
中国江苏常州联通 |
10 |
10 |
0 |
12.256ms |
11.598ms |
12.044ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (218.98.46.65) with 32 bytes of data: Reply from 218.98.46.65: bytes=32 time=12ms TTL=57 Reply from 218.98.46.65: bytes=32 time=12ms TTL=57 Reply from 218.98.46.65: bytes=32 time=12ms TTL=57 Reply from 218.98.46.65: bytes=32 time=12ms TTL=57 Reply from 218.98.46.65: bytes=32 time=12ms TTL=57 Reply from 218.98.46.65: bytes=32 time=12ms TTL=57 Reply from 218.98.46.65: bytes=32 time=12ms TTL=57 Reply from 218.98.46.65: bytes=32 time=12ms TTL=57 Reply from 218.98.46.65: bytes=32 time=12ms TTL=57 Reply from 218.98.46.65: bytes=32 time=12ms TTL=57
Ping statistics for 218.98.46.65: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 12ms, Maximum = 12ms, Average = 12ms查看 |
GET PING Trace Dig |
|
宁夏银川市联通 |
联通 |
宁夏 |
171.43.165.236 |
中国湖北武汉电信 |
10 |
10 |
0 |
15.088ms |
10.043ms |
11.91ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (171.43.165.236) with 32 bytes of data: Reply from 171.43.165.236: bytes=32 time=11ms TTL=54 Reply from 171.43.165.236: bytes=32 time=15ms TTL=54 Reply from 171.43.165.236: bytes=32 time=11ms TTL=54 Reply from 171.43.165.236: bytes=32 time=12ms TTL=54 Reply from 171.43.165.236: bytes=32 time=11ms TTL=54 Reply from 171.43.165.236: bytes=32 time=15ms TTL=54 Reply from 171.43.165.236: bytes=32 time=10ms TTL=54 Reply from 171.43.165.236: bytes=32 time=12ms TTL=54 Reply from 171.43.165.236: bytes=32 time=11ms TTL=54 Reply from 171.43.165.236: bytes=32 time=11ms TTL=54
Ping statistics for 171.43.165.236: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 15ms, Average = 12ms查看 |
GET PING Trace Dig |
|
新疆昌吉回族自治州移动 |
移动 |
新疆 |
221.181.55.59 |
中国新疆阿克苏移动 |
10 |
10 |
0 |
15.158ms |
10.638ms |
11.854ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (221.181.55.59) with 32 bytes of data: Reply from 221.181.55.59: bytes=32 time=11ms TTL=56 Reply from 221.181.55.59: bytes=32 time=12ms TTL=56 Reply from 221.181.55.59: bytes=32 time=11ms TTL=56 Reply from 221.181.55.59: bytes=32 time=11ms TTL=56 Reply from 221.181.55.59: bytes=32 time=15ms TTL=56 Reply from 221.181.55.59: bytes=32 time=11ms TTL=56 Reply from 221.181.55.59: bytes=32 time=11ms TTL=56 Reply from 221.181.55.59: bytes=32 time=15ms TTL=56 Reply from 221.181.55.59: bytes=32 time=12ms TTL=56 Reply from 221.181.55.59: bytes=32 time=11ms TTL=56
Ping statistics for 221.181.55.59: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 15ms, Average = 12ms查看 |
GET PING Trace Dig |
|
黑龙江齐齐哈尔移动 |
移动 |
黑龙江 |
111.42.186.77 |
中国黑龙江哈尔滨移动 |
10 |
10 |
0 |
14.439ms |
11.161ms |
11.796ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (111.42.186.77) with 32 bytes of data: Reply from 111.42.186.77: bytes=32 time=12ms TTL=55 Reply from 111.42.186.77: bytes=32 time=11ms TTL=55 Reply from 111.42.186.77: bytes=32 time=11ms TTL=55 Reply from 111.42.186.77: bytes=32 time=14ms TTL=55 Reply from 111.42.186.77: bytes=32 time=11ms TTL=55 Reply from 111.42.186.77: bytes=32 time=11ms TTL=55 Reply from 111.42.186.77: bytes=32 time=12ms TTL=55 Reply from 111.42.186.77: bytes=32 time=12ms TTL=55 Reply from 111.42.186.77: bytes=32 time=12ms TTL=55 Reply from 111.42.186.77: bytes=32 time=12ms TTL=55
Ping statistics for 111.42.186.77: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 14ms, Average = 12ms查看 |
GET PING Trace Dig |
|
贵州遵义市联通 |
联通 |
贵州 |
111.124.208.60 |
中国贵州贵阳电信 |
10 |
10 |
0 |
12.76ms |
10.32ms |
11.642ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (111.124.208.60) with 32 bytes of data: Reply from 111.124.208.60: bytes=32 time=11ms TTL=53 Reply from 111.124.208.60: bytes=32 time=12ms TTL=53 Reply from 111.124.208.60: bytes=32 time=10ms TTL=53 Reply from 111.124.208.60: bytes=32 time=11ms TTL=53 Reply from 111.124.208.60: bytes=32 time=13ms TTL=53 Reply from 111.124.208.60: bytes=32 time=13ms TTL=53 Reply from 111.124.208.60: bytes=32 time=11ms TTL=53 Reply from 111.124.208.60: bytes=32 time=12ms TTL=53 Reply from 111.124.208.60: bytes=32 time=12ms TTL=53 Reply from 111.124.208.60: bytes=32 time=12ms TTL=53
Ping statistics for 111.124.208.60: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 13ms, Average = 12ms查看 |
GET PING Trace Dig |
|
吉林松原移动 |
移动 |
吉林 |
122.141.229.18 |
中国吉林长春联通 |
10 |
10 |
0 |
12.891ms |
10.848ms |
11.435ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (122.141.229.18) with 32 bytes of data: Reply from 122.141.229.18: bytes=32 time=11ms TTL=57 Reply from 122.141.229.18: bytes=32 time=11ms TTL=57 Reply from 122.141.229.18: bytes=32 time=13ms TTL=57 Reply from 122.141.229.18: bytes=32 time=11ms TTL=57 Reply from 122.141.229.18: bytes=32 time=11ms TTL=57 Reply from 122.141.229.18: bytes=32 time=11ms TTL=57 Reply from 122.141.229.18: bytes=32 time=13ms TTL=57 Reply from 122.141.229.18: bytes=32 time=11ms TTL=57 Reply from 122.141.229.18: bytes=32 time=11ms TTL=57 Reply from 122.141.229.18: bytes=32 time=11ms TTL=57
Ping statistics for 122.141.229.18: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 11ms, Maximum = 13ms, Average = 11ms查看 |
GET PING Trace Dig |
|
四川南充市移动 |
移动 |
四川 |
112.45.115.22 |
中国四川成都移动 |
10 |
10 |
0 |
14.36ms |
10.38ms |
11.425ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (112.45.115.22) with 32 bytes of data: Reply from 112.45.115.22: bytes=32 time=14ms TTL=55 Reply from 112.45.115.22: bytes=32 time=12ms TTL=55 Reply from 112.45.115.22: bytes=32 time=11ms TTL=55 Reply from 112.45.115.22: bytes=32 time=10ms TTL=55 Reply from 112.45.115.22: bytes=32 time=11ms TTL=55 Reply from 112.45.115.22: bytes=32 time=11ms TTL=55 Reply from 112.45.115.22: bytes=32 time=11ms TTL=55 Reply from 112.45.115.22: bytes=32 time=11ms TTL=55 Reply from 112.45.115.22: bytes=32 time=11ms TTL=55 Reply from 112.45.115.22: bytes=32 time=11ms TTL=55
Ping statistics for 112.45.115.22: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 14ms, Average = 11ms查看 |
GET PING Trace Dig |
|
内蒙古呼和浩特电信 |
电信 |
内蒙古 |
45.115.202.20 |
中国北京联通 |
10 |
10 |
0 |
16.04ms |
9.66ms |
11.158ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (45.115.202.20) with 32 bytes of data: Reply from 45.115.202.20: bytes=32 time=11ms TTL=58 Reply from 45.115.202.20: bytes=32 time=10ms TTL=58 Reply from 45.115.202.20: bytes=32 time=11ms TTL=58 Reply from 45.115.202.20: bytes=32 time=10ms TTL=58 Reply from 45.115.202.20: bytes=32 time=16ms TTL=58 Reply from 45.115.202.20: bytes=32 time=11ms TTL=58 Reply from 45.115.202.20: bytes=32 time=10ms TTL=58 Reply from 45.115.202.20: bytes=32 time=13ms TTL=58 Reply from 45.115.202.20: bytes=32 time=10ms TTL=58 Reply from 45.115.202.20: bytes=32 time=11ms TTL=58
Ping statistics for 45.115.202.20: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 16ms, Average = 11ms查看 |
GET PING Trace Dig |
|
陕西西安市电信 |
电信 |
陕西 |
113.142.71.14 |
中国陕西西安电信 |
10 |
10 |
0 |
29.98ms |
4.66ms |
11.13ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (113.142.71.14) with 32 bytes of data: Reply from 113.142.71.14: bytes=32 time=30ms TTL=53 Reply from 113.142.71.14: bytes=32 time=5ms TTL=53 Reply from 113.142.71.14: bytes=32 time=5ms TTL=53 Reply from 113.142.71.14: bytes=32 time=7ms TTL=53 Reply from 113.142.71.14: bytes=32 time=10ms TTL=53 Reply from 113.142.71.14: bytes=32 time=22ms TTL=53 Reply from 113.142.71.14: bytes=32 time=10ms TTL=53 Reply from 113.142.71.14: bytes=32 time=10ms TTL=53 Reply from 113.142.71.14: bytes=32 time=7ms TTL=53 Reply from 113.142.71.14: bytes=32 time=6ms TTL=53
Ping statistics for 113.142.71.14: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 5ms, Maximum = 30ms, Average = 11ms查看 |
GET PING Trace Dig |
|
宁夏银川市移动 |
移动 |
宁夏 |
111.51.89.205 |
中国宁夏银川移动 |
10 |
10 |
0 |
13.08ms |
10.38ms |
11.044ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (111.51.89.205) with 32 bytes of data: Reply from 111.51.89.205: bytes=32 time=11ms TTL=56 Reply from 111.51.89.205: bytes=32 time=12ms TTL=56 Reply from 111.51.89.205: bytes=32 time=13ms TTL=56 Reply from 111.51.89.205: bytes=32 time=11ms TTL=56 Reply from 111.51.89.205: bytes=32 time=11ms TTL=56 Reply from 111.51.89.205: bytes=32 time=10ms TTL=56 Reply from 111.51.89.205: bytes=32 time=11ms TTL=56 Reply from 111.51.89.205: bytes=32 time=11ms TTL=56 Reply from 111.51.89.205: bytes=32 time=11ms TTL=56 Reply from 111.51.89.205: bytes=32 time=11ms TTL=56
Ping statistics for 111.51.89.205: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 13ms, Average = 11ms查看 |
GET PING Trace Dig |
|
山西太原市移动 |
移动 |
山西 |
60.222.11.128 |
中国山西运城联通 |
10 |
10 |
0 |
11.342ms |
10.287ms |
10.747ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (60.222.11.128) with 32 bytes of data: Reply from 60.222.11.128: bytes=32 time=11ms TTL=56 Reply from 60.222.11.128: bytes=32 time=11ms TTL=56 Reply from 60.222.11.128: bytes=32 time=11ms TTL=56 Reply from 60.222.11.128: bytes=32 time=11ms TTL=56 Reply from 60.222.11.128: bytes=32 time=11ms TTL=56 Reply from 60.222.11.128: bytes=32 time=10ms TTL=56 Reply from 60.222.11.128: bytes=32 time=11ms TTL=56 Reply from 60.222.11.128: bytes=32 time=11ms TTL=56 Reply from 60.222.11.128: bytes=32 time=11ms TTL=56 Reply from 60.222.11.128: bytes=32 time=10ms TTL=56
Ping statistics for 60.222.11.128: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 11ms, Average = 11ms查看 |
GET PING Trace Dig |
|
江苏南京市移动 |
移动 |
江苏 |
36.150.50.96 |
中国移动 |
10 |
10 |
0 |
12.661ms |
9.28ms |
10.687ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (36.150.50.96) with 32 bytes of data: Reply from 36.150.50.96: bytes=32 time=13ms TTL=54 Reply from 36.150.50.96: bytes=32 time=11ms TTL=54 Reply from 36.150.50.96: bytes=32 time=10ms TTL=54 Reply from 36.150.50.96: bytes=32 time=9ms TTL=54 Reply from 36.150.50.96: bytes=32 time=12ms TTL=54 Reply from 36.150.50.96: bytes=32 time=11ms TTL=54 Reply from 36.150.50.96: bytes=32 time=11ms TTL=54 Reply from 36.150.50.96: bytes=32 time=11ms TTL=54 Reply from 36.150.50.96: bytes=32 time=11ms TTL=54 Reply from 36.150.50.96: bytes=32 time=11ms TTL=54
Ping statistics for 36.150.50.96: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 9ms, Maximum = 13ms, Average = 11ms查看 |
GET PING Trace Dig |
|
上海上海市电信 |
电信 |
上海 |
180.101.199.192 |
中国江苏无锡电信 |
10 |
10 |
0 |
12.7ms |
10.12ms |
10.588ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (180.101.199.192) with 32 bytes of data: Reply from 180.101.199.192: bytes=32 time=10ms TTL=56 Reply from 180.101.199.192: bytes=32 time=10ms TTL=56 Reply from 180.101.199.192: bytes=32 time=10ms TTL=56 Reply from 180.101.199.192: bytes=32 time=13ms TTL=56 Reply from 180.101.199.192: bytes=32 time=10ms TTL=56 Reply from 180.101.199.192: bytes=32 time=10ms TTL=56 Reply from 180.101.199.192: bytes=32 time=10ms TTL=56 Reply from 180.101.199.192: bytes=32 time=11ms TTL=56 Reply from 180.101.199.192: bytes=32 time=10ms TTL=56 Reply from 180.101.199.192: bytes=32 time=10ms TTL=56
Ping statistics for 180.101.199.192: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 13ms, Average = 11ms查看 |
GET PING Trace Dig |
|
安徽合肥移动 |
移动 |
安徽 |
60.170.11.87 |
中国安徽蚌埠电信 |
10 |
10 |
0 |
24.34ms |
7.472ms |
10.451ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (60.170.11.87) with 32 bytes of data: Reply from 60.170.11.87: bytes=32 time=10ms TTL=56 Reply from 60.170.11.87: bytes=32 time=24ms TTL=56 Reply from 60.170.11.87: bytes=32 time=8ms TTL=56 Reply from 60.170.11.87: bytes=32 time=9ms TTL=56 Reply from 60.170.11.87: bytes=32 time=9ms TTL=56 Reply from 60.170.11.87: bytes=32 time=8ms TTL=56 Reply from 60.170.11.87: bytes=32 time=8ms TTL=56 Reply from 60.170.11.87: bytes=32 time=7ms TTL=56 Reply from 60.170.11.87: bytes=32 time=10ms TTL=56 Reply from 60.170.11.87: bytes=32 time=11ms TTL=56
Ping statistics for 60.170.11.87: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 24ms, Average = 10ms查看 |
GET PING Trace Dig |
|
云南楚雄彝族自治州移动 |
移动 |
云南 |
36.147.19.141 |
中国云南昆明移动 |
10 |
10 |
0 |
11.279ms |
10.086ms |
10.364ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (36.147.19.141) with 32 bytes of data: Reply from 36.147.19.141: bytes=32 time=11ms TTL=56 Reply from 36.147.19.141: bytes=32 time=10ms TTL=56 Reply from 36.147.19.141: bytes=32 time=10ms TTL=56 Reply from 36.147.19.141: bytes=32 time=10ms TTL=56 Reply from 36.147.19.141: bytes=32 time=10ms TTL=56 Reply from 36.147.19.141: bytes=32 time=11ms TTL=56 Reply from 36.147.19.141: bytes=32 time=10ms TTL=56 Reply from 36.147.19.141: bytes=32 time=10ms TTL=56 Reply from 36.147.19.141: bytes=32 time=10ms TTL=56 Reply from 36.147.19.141: bytes=32 time=10ms TTL=56
Ping statistics for 36.147.19.141: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 11ms, Average = 10ms查看 |
GET PING Trace Dig |
|
宁夏银川移动 |
移动 |
宁夏 |
183.201.234.240 |
中国山西太原移动 |
10 |
10 |
0 |
15.114ms |
8.064ms |
10.324ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (183.201.234.240) with 32 bytes of data: Reply from 183.201.234.240: bytes=32 time=9ms TTL=55 Reply from 183.201.234.240: bytes=32 time=15ms TTL=55 Reply from 183.201.234.240: bytes=32 time=15ms TTL=55 Reply from 183.201.234.240: bytes=32 time=8ms TTL=55 Reply from 183.201.234.240: bytes=32 time=9ms TTL=55 Reply from 183.201.234.240: bytes=32 time=10ms TTL=55 Reply from 183.201.234.240: bytes=32 time=9ms TTL=55 Reply from 183.201.234.240: bytes=32 time=8ms TTL=55 Reply from 183.201.234.240: bytes=32 time=11ms TTL=55 Reply from 183.201.234.240: bytes=32 time=9ms TTL=55
Ping statistics for 183.201.234.240: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 8ms, Maximum = 15ms, Average = 10ms查看 |
GET PING Trace Dig |
|
江西赣州市移动 |
移动 |
江西 |
117.167.114.21 |
中国江西南昌移动 |
10 |
10 |
0 |
10.5ms |
9.96ms |
10.23ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (117.167.114.21) with 32 bytes of data: Reply from 117.167.114.21: bytes=32 time=11ms TTL=57 Reply from 117.167.114.21: bytes=32 time=10ms TTL=57 Reply from 117.167.114.21: bytes=32 time=10ms TTL=57 Reply from 117.167.114.21: bytes=32 time=10ms TTL=57 Reply from 117.167.114.21: bytes=32 time=10ms TTL=57 Reply from 117.167.114.21: bytes=32 time=10ms TTL=57 Reply from 117.167.114.21: bytes=32 time=10ms TTL=57 Reply from 117.167.114.21: bytes=32 time=10ms TTL=57 Reply from 117.167.114.21: bytes=32 time=10ms TTL=57 Reply from 117.167.114.21: bytes=32 time=10ms TTL=57
Ping statistics for 117.167.114.21: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 11ms, Average = 10ms查看 |
GET PING Trace Dig |
|
广西贵港市移动 |
移动 |
广西 |
111.12.62.223 |
中国广西南宁移动 |
10 |
10 |
0 |
12.976ms |
9.598ms |
10.228ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (111.12.62.223) with 32 bytes of data: Reply from 111.12.62.223: bytes=32 time=13ms TTL=55 Reply from 111.12.62.223: bytes=32 time=10ms TTL=55 Reply from 111.12.62.223: bytes=32 time=10ms TTL=55 Reply from 111.12.62.223: bytes=32 time=10ms TTL=55 Reply from 111.12.62.223: bytes=32 time=10ms TTL=55 Reply from 111.12.62.223: bytes=32 time=10ms TTL=55 Reply from 111.12.62.223: bytes=32 time=10ms TTL=55 Reply from 111.12.62.223: bytes=32 time=10ms TTL=55 Reply from 111.12.62.223: bytes=32 time=10ms TTL=55 Reply from 111.12.62.223: bytes=32 time=10ms TTL=55
Ping statistics for 111.12.62.223: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 13ms, Average = 10ms查看 |
GET PING Trace Dig |
|
山西吕梁市移动 |
移动 |
山西 |
183.201.234.240 |
中国山西太原移动 |
10 |
10 |
0 |
10.76ms |
9.74ms |
10.214ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (183.201.234.240) with 32 bytes of data: Reply from 183.201.234.240: bytes=32 time=11ms TTL=54 Reply from 183.201.234.240: bytes=32 time=10ms TTL=54 Reply from 183.201.234.240: bytes=32 time=10ms TTL=54 Reply from 183.201.234.240: bytes=32 time=10ms TTL=54 Reply from 183.201.234.240: bytes=32 time=10ms TTL=54 Reply from 183.201.234.240: bytes=32 time=10ms TTL=54 Reply from 183.201.234.240: bytes=32 time=10ms TTL=54 Reply from 183.201.234.240: bytes=32 time=10ms TTL=54 Reply from 183.201.234.240: bytes=32 time=10ms TTL=54 Reply from 183.201.234.240: bytes=32 time=10ms TTL=54
Ping statistics for 183.201.234.240: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 11ms, Average = 10ms查看 |
GET PING Trace Dig |
|
浙江温州市联通 |
联通 |
浙江 |
124.160.144.210 |
中国浙江杭州联通 |
10 |
10 |
0 |
10.183ms |
9.832ms |
10.013ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (124.160.144.210) with 32 bytes of data: Reply from 124.160.144.210: bytes=32 time=10ms TTL=57 Reply from 124.160.144.210: bytes=32 time=10ms TTL=57 Reply from 124.160.144.210: bytes=32 time=10ms TTL=57 Reply from 124.160.144.210: bytes=32 time=10ms TTL=57 Reply from 124.160.144.210: bytes=32 time=10ms TTL=57 Reply from 124.160.144.210: bytes=32 time=10ms TTL=57 Reply from 124.160.144.210: bytes=32 time=10ms TTL=57 Reply from 124.160.144.210: bytes=32 time=10ms TTL=57 Reply from 124.160.144.210: bytes=32 time=10ms TTL=57 Reply from 124.160.144.210: bytes=32 time=10ms TTL=57
Ping statistics for 124.160.144.210: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 10ms, Average = 10ms查看 |
GET PING Trace Dig |
|
江苏泰州市联通 |
联通 |
江苏 |
103.239.45.236 |
中国江苏南京广电 |
10 |
10 |
0 |
10.407ms |
9.649ms |
10.004ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (103.239.45.236) with 32 bytes of data: Reply from 103.239.45.236: bytes=32 time=10ms TTL=57 Reply from 103.239.45.236: bytes=32 time=10ms TTL=57 Reply from 103.239.45.236: bytes=32 time=10ms TTL=57 Reply from 103.239.45.236: bytes=32 time=10ms TTL=57 Reply from 103.239.45.236: bytes=32 time=10ms TTL=57 Reply from 103.239.45.236: bytes=32 time=10ms TTL=57 Reply from 103.239.45.236: bytes=32 time=10ms TTL=57 Reply from 103.239.45.236: bytes=32 time=10ms TTL=57 Reply from 103.239.45.236: bytes=32 time=10ms TTL=57 Reply from 103.239.45.236: bytes=32 time=10ms TTL=57
Ping statistics for 103.239.45.236: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 10ms, Average = 10ms查看 |
GET PING Trace Dig |
|
湖南邵阳市联通 |
联通 |
湖南 |
42.48.120.16 |
中国湖南长沙联通 |
10 |
10 |
0 |
10.261ms |
9.86ms |
9.978ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (42.48.120.16) with 32 bytes of data: Reply from 42.48.120.16: bytes=32 time=10ms TTL=56 Reply from 42.48.120.16: bytes=32 time=10ms TTL=56 Reply from 42.48.120.16: bytes=32 time=10ms TTL=56 Reply from 42.48.120.16: bytes=32 time=10ms TTL=56 Reply from 42.48.120.16: bytes=32 time=10ms TTL=56 Reply from 42.48.120.16: bytes=32 time=10ms TTL=56 Reply from 42.48.120.16: bytes=32 time=10ms TTL=56 Reply from 42.48.120.16: bytes=32 time=10ms TTL=56 Reply from 42.48.120.16: bytes=32 time=10ms TTL=56 Reply from 42.48.120.16: bytes=32 time=10ms TTL=56
Ping statistics for 42.48.120.16: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 10ms, Average = 10ms查看 |
GET PING Trace Dig |
|
贵州黔南布依族苗族自治州电信 |
电信 |
贵州 |
111.124.208.62 |
中国贵州贵阳电信 |
10 |
10 |
0 |
10.393ms |
9.413ms |
9.961ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (111.124.208.62) with 32 bytes of data: Reply from 111.124.208.62: bytes=32 time=10ms TTL=53 Reply from 111.124.208.62: bytes=32 time=10ms TTL=53 Reply from 111.124.208.62: bytes=32 time=10ms TTL=53 Reply from 111.124.208.62: bytes=32 time=10ms TTL=53 Reply from 111.124.208.62: bytes=32 time=10ms TTL=53 Reply from 111.124.208.62: bytes=32 time=10ms TTL=53 Reply from 111.124.208.62: bytes=32 time=10ms TTL=53 Reply from 111.124.208.62: bytes=32 time=9ms TTL=53 Reply from 111.124.208.62: bytes=32 time=10ms TTL=53 Reply from 111.124.208.62: bytes=32 time=10ms TTL=53
Ping statistics for 111.124.208.62: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 9ms, Maximum = 10ms, Average = 10ms查看 |
GET PING Trace Dig |
|
甘肃兰州市联通 |
联通 |
甘肃 |
180.95.230.74 |
中国甘肃兰州联通 |
10 |
10 |
0 |
19.18ms |
8.38ms |
9.856ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (180.95.230.74) with 32 bytes of data: Reply from 180.95.230.74: bytes=32 time=9ms TTL=49 Reply from 180.95.230.74: bytes=32 time=9ms TTL=49 Reply from 180.95.230.74: bytes=32 time=9ms TTL=49 Reply from 180.95.230.74: bytes=32 time=9ms TTL=49 Reply from 180.95.230.74: bytes=32 time=9ms TTL=49 Reply from 180.95.230.74: bytes=32 time=8ms TTL=49 Reply from 180.95.230.74: bytes=32 time=19ms TTL=49 Reply from 180.95.230.74: bytes=32 time=9ms TTL=49 Reply from 180.95.230.74: bytes=32 time=8ms TTL=49 Reply from 180.95.230.74: bytes=32 time=9ms TTL=49
Ping statistics for 180.95.230.74: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 8ms, Maximum = 19ms, Average = 10ms查看 |
GET PING Trace Dig |
|
宁夏银川电信 |
电信 |
宁夏 |
222.75.63.76 |
中国宁夏银川电信 |
10 |
10 |
0 |
12.653ms |
8.7ms |
9.77ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (222.75.63.76) with 32 bytes of data: Reply from 222.75.63.76: bytes=32 time=9ms TTL=58 Reply from 222.75.63.76: bytes=32 time=9ms TTL=58 Reply from 222.75.63.76: bytes=32 time=9ms TTL=58 Reply from 222.75.63.76: bytes=32 time=9ms TTL=58 Reply from 222.75.63.76: bytes=32 time=12ms TTL=58 Reply from 222.75.63.76: bytes=32 time=9ms TTL=58 Reply from 222.75.63.76: bytes=32 time=13ms TTL=58 Reply from 222.75.63.76: bytes=32 time=9ms TTL=58 Reply from 222.75.63.76: bytes=32 time=9ms TTL=58 Reply from 222.75.63.76: bytes=32 time=11ms TTL=58
Ping statistics for 222.75.63.76: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 9ms, Maximum = 13ms, Average = 10ms查看 |
GET PING Trace Dig |
|
河北石家庄市电信 |
电信 |
河北 |
27.128.221.230 |
中国河北廊坊电信 |
10 |
10 |
0 |
11.689ms |
8.804ms |
9.674ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (27.128.221.230) with 32 bytes of data: Reply from 27.128.221.230: bytes=32 time=9ms TTL=56 Reply from 27.128.221.230: bytes=32 time=12ms TTL=56 Reply from 27.128.221.230: bytes=32 time=9ms TTL=56 Reply from 27.128.221.230: bytes=32 time=9ms TTL=56 Reply from 27.128.221.230: bytes=32 time=9ms TTL=56 Reply from 27.128.221.230: bytes=32 time=10ms TTL=56 Reply from 27.128.221.230: bytes=32 time=10ms TTL=56 Reply from 27.128.221.230: bytes=32 time=9ms TTL=56 Reply from 27.128.221.230: bytes=32 time=10ms TTL=56 Reply from 27.128.221.230: bytes=32 time=9ms TTL=56
Ping statistics for 27.128.221.230: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 9ms, Maximum = 12ms, Average = 10ms查看 |
GET PING Trace Dig |
|
海南临高县移动 |
移动 |
海南 |
111.29.1.200 |
中国海南海口移动 |
10 |
10 |
0 |
11.709ms |
7.67ms |
9.561ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (111.29.1.200) with 32 bytes of data: Reply from 111.29.1.200: bytes=32 time=9ms TTL=57 Reply from 111.29.1.200: bytes=32 time=12ms TTL=57 Reply from 111.29.1.200: bytes=32 time=8ms TTL=57 Reply from 111.29.1.200: bytes=32 time=10ms TTL=57 Reply from 111.29.1.200: bytes=32 time=8ms TTL=57 Reply from 111.29.1.200: bytes=32 time=10ms TTL=57 Reply from 111.29.1.200: bytes=32 time=9ms TTL=57 Reply from 111.29.1.200: bytes=32 time=12ms TTL=57 Reply from 111.29.1.200: bytes=32 time=8ms TTL=57 Reply from 111.29.1.200: bytes=32 time=10ms TTL=57
Ping statistics for 111.29.1.200: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 8ms, Maximum = 12ms, Average = 10ms查看 |
GET PING Trace Dig |
|
福建泉州市联通 |
联通 |
福建 |
220.160.45.41 |
中国福建厦门电信 |
10 |
10 |
0 |
15.44ms |
6.56ms |
9.5ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (220.160.45.41) with 32 bytes of data: Reply from 220.160.45.41: bytes=32 time=11ms TTL=56 Reply from 220.160.45.41: bytes=32 time=13ms TTL=56 Reply from 220.160.45.41: bytes=32 time=7ms TTL=56 Reply from 220.160.45.41: bytes=32 time=9ms TTL=56 Reply from 220.160.45.41: bytes=32 time=7ms TTL=56 Reply from 220.160.45.41: bytes=32 time=8ms TTL=56 Reply from 220.160.45.41: bytes=32 time=7ms TTL=56 Reply from 220.160.45.41: bytes=32 time=15ms TTL=56 Reply from 220.160.45.41: bytes=32 time=8ms TTL=56 Reply from 220.160.45.41: bytes=32 time=11ms TTL=56
Ping statistics for 220.160.45.41: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 15ms, Average = 10ms查看 |
GET PING Trace Dig |
|
湖北鄂州市联通 |
联通 |
湖北 |
120.202.140.225 |
中国湖北荆门移动 |
10 |
10 |
0 |
17.199ms |
6.18ms |
9.321ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (120.202.140.225) with 32 bytes of data: Reply from 120.202.140.225: bytes=32 time=17ms TTL=56 Reply from 120.202.140.225: bytes=32 time=6ms TTL=56 Reply from 120.202.140.225: bytes=32 time=6ms TTL=56 Reply from 120.202.140.225: bytes=32 time=11ms TTL=56 Reply from 120.202.140.225: bytes=32 time=9ms TTL=56 Reply from 120.202.140.225: bytes=32 time=11ms TTL=56 Reply from 120.202.140.225: bytes=32 time=6ms TTL=56 Reply from 120.202.140.225: bytes=32 time=6ms TTL=56 Reply from 120.202.140.225: bytes=32 time=7ms TTL=56 Reply from 120.202.140.225: bytes=32 time=13ms TTL=56
Ping statistics for 120.202.140.225: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 6ms, Maximum = 17ms, Average = 9ms查看 |
GET PING Trace Dig |
|
辽宁朝阳市联通 |
联通 |
辽宁 |
124.95.157.80 |
中国辽宁沈阳联通 |
10 |
10 |
0 |
10.194ms |
8.766ms |
9.166ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (124.95.157.80) with 32 bytes of data: Reply from 124.95.157.80: bytes=32 time=10ms TTL=56 Reply from 124.95.157.80: bytes=32 time=9ms TTL=56 Reply from 124.95.157.80: bytes=32 time=9ms TTL=56 Reply from 124.95.157.80: bytes=32 time=10ms TTL=56 Reply from 124.95.157.80: bytes=32 time=9ms TTL=56 Reply from 124.95.157.80: bytes=32 time=9ms TTL=56 Reply from 124.95.157.80: bytes=32 time=9ms TTL=56 Reply from 124.95.157.80: bytes=32 time=9ms TTL=56 Reply from 124.95.157.80: bytes=32 time=9ms TTL=56 Reply from 124.95.157.80: bytes=32 time=9ms TTL=56
Ping statistics for 124.95.157.80: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 9ms, Maximum = 10ms, Average = 9ms查看 |
GET PING Trace Dig |
|
贵州六盘水市联通 |
联通 |
贵州 |
61.243.15.200 |
中国贵州贵阳联通 |
10 |
10 |
0 |
9.22ms |
8.6ms |
9.034ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (61.243.15.200) with 32 bytes of data: Reply from 61.243.15.200: bytes=32 time=9ms TTL=57 Reply from 61.243.15.200: bytes=32 time=9ms TTL=57 Reply from 61.243.15.200: bytes=32 time=9ms TTL=57 Reply from 61.243.15.200: bytes=32 time=9ms TTL=57 Reply from 61.243.15.200: bytes=32 time=9ms TTL=57 Reply from 61.243.15.200: bytes=32 time=9ms TTL=57 Reply from 61.243.15.200: bytes=32 time=9ms TTL=57 Reply from 61.243.15.200: bytes=32 time=9ms TTL=57 Reply from 61.243.15.200: bytes=32 time=9ms TTL=57 Reply from 61.243.15.200: bytes=32 time=9ms TTL=57
Ping statistics for 61.243.15.200: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 9ms, Maximum = 9ms, Average = 9ms查看 |
GET PING Trace Dig |
|
浙江湖州市联通 |
联通 |
浙江 |
124.160.144.216 |
中国浙江杭州联通 |
10 |
10 |
0 |
9.287ms |
8.86ms |
9.032ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (124.160.144.216) with 32 bytes of data: Reply from 124.160.144.216: bytes=32 time=9ms TTL=57 Reply from 124.160.144.216: bytes=32 time=9ms TTL=57 Reply from 124.160.144.216: bytes=32 time=9ms TTL=57 Reply from 124.160.144.216: bytes=32 time=9ms TTL=57 Reply from 124.160.144.216: bytes=32 time=9ms TTL=57 Reply from 124.160.144.216: bytes=32 time=9ms TTL=57 Reply from 124.160.144.216: bytes=32 time=9ms TTL=57 Reply from 124.160.144.216: bytes=32 time=9ms TTL=57 Reply from 124.160.144.216: bytes=32 time=9ms TTL=57 Reply from 124.160.144.216: bytes=32 time=9ms TTL=57
Ping statistics for 124.160.144.216: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 9ms, Maximum = 9ms, Average = 9ms查看 |
GET PING Trace Dig |
|
山东青岛市联通 |
联通 |
山东 |
120.220.218.225 |
中国山东移动 |
10 |
10 |
0 |
11.32ms |
7.92ms |
8.966ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (120.220.218.225) with 32 bytes of data: Reply from 120.220.218.225: bytes=32 time=11ms TTL=54 Reply from 120.220.218.225: bytes=32 time=8ms TTL=54 Reply from 120.220.218.225: bytes=32 time=10ms TTL=54 Reply from 120.220.218.225: bytes=32 time=8ms TTL=54 Reply from 120.220.218.225: bytes=32 time=11ms TTL=54 Reply from 120.220.218.225: bytes=32 time=8ms TTL=54 Reply from 120.220.218.225: bytes=32 time=8ms TTL=54 Reply from 120.220.218.225: bytes=32 time=8ms TTL=54 Reply from 120.220.218.225: bytes=32 time=8ms TTL=54 Reply from 120.220.218.225: bytes=32 time=9ms TTL=54
Ping statistics for 120.220.218.225: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 8ms, Maximum = 11ms, Average = 9ms查看 |
GET PING Trace Dig |
|
辽宁沈阳市移动 |
移动 |
辽宁 |
124.95.157.84 |
中国辽宁沈阳联通 |
10 |
10 |
0 |
13.677ms |
6.796ms |
8.745ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (124.95.157.84) with 32 bytes of data: Reply from 124.95.157.84: bytes=32 time=14ms TTL=57 Reply from 124.95.157.84: bytes=32 time=7ms TTL=57 Reply from 124.95.157.84: bytes=32 time=8ms TTL=57 Reply from 124.95.157.84: bytes=32 time=7ms TTL=57 Reply from 124.95.157.84: bytes=32 time=7ms TTL=57 Reply from 124.95.157.84: bytes=32 time=11ms TTL=57 Reply from 124.95.157.84: bytes=32 time=7ms TTL=57 Reply from 124.95.157.84: bytes=32 time=14ms TTL=57 Reply from 124.95.157.84: bytes=32 time=7ms TTL=57 Reply from 124.95.157.84: bytes=32 time=7ms TTL=57
Ping statistics for 124.95.157.84: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 14ms, Average = 9ms查看 |
GET PING Trace Dig |
|
浙江宁波市移动 |
移动 |
浙江 |
111.3.79.198 |
中国浙江杭州移动 |
10 |
10 |
0 |
9.143ms |
8.526ms |
8.735ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (111.3.79.198) with 32 bytes of data: Reply from 111.3.79.198: bytes=32 time=9ms TTL=56 Reply from 111.3.79.198: bytes=32 time=9ms TTL=56 Reply from 111.3.79.198: bytes=32 time=9ms TTL=56 Reply from 111.3.79.198: bytes=32 time=9ms TTL=56 Reply from 111.3.79.198: bytes=32 time=9ms TTL=56 Reply from 111.3.79.198: bytes=32 time=9ms TTL=56 Reply from 111.3.79.198: bytes=32 time=9ms TTL=56 Reply from 111.3.79.198: bytes=32 time=9ms TTL=56 Reply from 111.3.79.198: bytes=32 time=9ms TTL=56 Reply from 111.3.79.198: bytes=32 time=9ms TTL=56
Ping statistics for 111.3.79.198: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 9ms, Maximum = 9ms, Average = 9ms查看 |
GET PING Trace Dig |
|
黑龙江哈尔滨市电信 |
电信 |
黑龙江 |
1.189.232.66 |
中国黑龙江哈尔滨联通 |
10 |
10 |
0 |
8.88ms |
8.54ms |
8.716ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (1.189.232.66) with 32 bytes of data: Reply from 1.189.232.66: bytes=32 time=9ms TTL=57 Reply from 1.189.232.66: bytes=32 time=9ms TTL=57 Reply from 1.189.232.66: bytes=32 time=9ms TTL=57 Reply from 1.189.232.66: bytes=32 time=9ms TTL=57 Reply from 1.189.232.66: bytes=32 time=9ms TTL=57 Reply from 1.189.232.66: bytes=32 time=9ms TTL=57 Reply from 1.189.232.66: bytes=32 time=9ms TTL=57 Reply from 1.189.232.66: bytes=32 time=9ms TTL=57 Reply from 1.189.232.66: bytes=32 time=9ms TTL=57 Reply from 1.189.232.66: bytes=32 time=9ms TTL=57
Ping statistics for 1.189.232.66: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 9ms, Maximum = 9ms, Average = 9ms查看 |
GET PING Trace Dig |
|
重庆重庆市联通 |
联通 |
重庆 |
183.231.33.82 |
中国重庆移动 |
10 |
10 |
0 |
8.84ms |
8.44ms |
8.582ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (183.231.33.82) with 32 bytes of data: Reply from 183.231.33.82: bytes=32 time=9ms TTL=55 Reply from 183.231.33.82: bytes=32 time=9ms TTL=55 Reply from 183.231.33.82: bytes=32 time=9ms TTL=55 Reply from 183.231.33.82: bytes=32 time=9ms TTL=55 Reply from 183.231.33.82: bytes=32 time=9ms TTL=55 Reply from 183.231.33.82: bytes=32 time=9ms TTL=55 Reply from 183.231.33.82: bytes=32 time=9ms TTL=55 Reply from 183.231.33.82: bytes=32 time=8ms TTL=55 Reply from 183.231.33.82: bytes=32 time=9ms TTL=55 Reply from 183.231.33.82: bytes=32 time=8ms TTL=55
Ping statistics for 183.231.33.82: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 8ms, Maximum = 9ms, Average = 9ms查看 |
GET PING Trace Dig |
|
安徽蚌埠移动 |
移动 |
安徽 |
112.132.36.41 |
中国安徽合肥联通 |
10 |
10 |
0 |
11.304ms |
7.162ms |
8.181ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (112.132.36.41) with 32 bytes of data: Reply from 112.132.36.41: bytes=32 time=11ms TTL=56 Reply from 112.132.36.41: bytes=32 time=9ms TTL=56 Reply from 112.132.36.41: bytes=32 time=10ms TTL=56 Reply from 112.132.36.41: bytes=32 time=7ms TTL=56 Reply from 112.132.36.41: bytes=32 time=7ms TTL=56 Reply from 112.132.36.41: bytes=32 time=7ms TTL=56 Reply from 112.132.36.41: bytes=32 time=7ms TTL=56 Reply from 112.132.36.41: bytes=32 time=7ms TTL=56 Reply from 112.132.36.41: bytes=32 time=7ms TTL=56 Reply from 112.132.36.41: bytes=32 time=7ms TTL=56
Ping statistics for 112.132.36.41: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 11ms, Average = 8ms查看 |
GET PING Trace Dig |
|
辽宁锦州市电信 |
电信 |
辽宁 |
42.202.222.33 |
中国辽宁朝阳电信 |
10 |
10 |
0 |
8.26ms |
7.686ms |
8.031ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (42.202.222.33) with 32 bytes of data: Reply from 42.202.222.33: bytes=32 time=8ms TTL=54 Reply from 42.202.222.33: bytes=32 time=8ms TTL=54 Reply from 42.202.222.33: bytes=32 time=8ms TTL=54 Reply from 42.202.222.33: bytes=32 time=8ms TTL=54 Reply from 42.202.222.33: bytes=32 time=8ms TTL=54 Reply from 42.202.222.33: bytes=32 time=8ms TTL=54 Reply from 42.202.222.33: bytes=32 time=8ms TTL=54 Reply from 42.202.222.33: bytes=32 time=8ms TTL=54 Reply from 42.202.222.33: bytes=32 time=8ms TTL=54 Reply from 42.202.222.33: bytes=32 time=8ms TTL=54
Ping statistics for 42.202.222.33: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 8ms, Maximum = 8ms, Average = 8ms查看 |
GET PING Trace Dig |
|
福建漳州市移动 |
移动 |
福建 |
112.48.183.213 |
中国福建厦门移动 |
10 |
10 |
0 |
9.493ms |
7.512ms |
7.964ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (112.48.183.213) with 32 bytes of data: Reply from 112.48.183.213: bytes=32 time=8ms TTL=50 Reply from 112.48.183.213: bytes=32 time=8ms TTL=50 Reply from 112.48.183.213: bytes=32 time=8ms TTL=50 Reply from 112.48.183.213: bytes=32 time=8ms TTL=50 Reply from 112.48.183.213: bytes=32 time=8ms TTL=50 Reply from 112.48.183.213: bytes=32 time=8ms TTL=50 Reply from 112.48.183.213: bytes=32 time=8ms TTL=50 Reply from 112.48.183.213: bytes=32 time=9ms TTL=50 Reply from 112.48.183.213: bytes=32 time=8ms TTL=50 Reply from 112.48.183.213: bytes=32 time=8ms TTL=50
Ping statistics for 112.48.183.213: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 8ms, Maximum = 9ms, Average = 8ms查看 |
GET PING Trace Dig |
|
广西钦州市电信 |
电信 |
广西 |
113.16.214.87 |
中国广西南宁电信 |
10 |
10 |
0 |
9.34ms |
7.2ms |
7.816ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (113.16.214.87) with 32 bytes of data: Reply from 113.16.214.87: bytes=32 time=9ms TTL=58 Reply from 113.16.214.87: bytes=32 time=8ms TTL=58 Reply from 113.16.214.87: bytes=32 time=8ms TTL=58 Reply from 113.16.214.87: bytes=32 time=8ms TTL=58 Reply from 113.16.214.87: bytes=32 time=8ms TTL=58 Reply from 113.16.214.87: bytes=32 time=8ms TTL=58 Reply from 113.16.214.87: bytes=32 time=8ms TTL=58 Reply from 113.16.214.87: bytes=32 time=7ms TTL=58 Reply from 113.16.214.87: bytes=32 time=8ms TTL=58 Reply from 113.16.214.87: bytes=32 time=8ms TTL=58
Ping statistics for 113.16.214.87: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 9ms, Average = 8ms查看 |
GET PING Trace Dig |
|
黑龙江绥化市电信 |
电信 |
黑龙江 |
42.101.76.81 |
中国黑龙江哈尔滨电信 |
10 |
10 |
0 |
10.28ms |
6.64ms |
7.79ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (42.101.76.81) with 32 bytes of data: Reply from 42.101.76.81: bytes=32 time=7ms TTL=55 Reply from 42.101.76.81: bytes=32 time=7ms TTL=55 Reply from 42.101.76.81: bytes=32 time=7ms TTL=55 Reply from 42.101.76.81: bytes=32 time=7ms TTL=55 Reply from 42.101.76.81: bytes=32 time=8ms TTL=55 Reply from 42.101.76.81: bytes=32 time=9ms TTL=55 Reply from 42.101.76.81: bytes=32 time=7ms TTL=55 Reply from 42.101.76.81: bytes=32 time=10ms TTL=55 Reply from 42.101.76.81: bytes=32 time=8ms TTL=55 Reply from 42.101.76.81: bytes=32 time=7ms TTL=55
Ping statistics for 42.101.76.81: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 10ms, Average = 8ms查看 |
GET PING Trace Dig |
|
广西柳州市电信 |
电信 |
广西 |
113.16.214.85 |
中国广西南宁电信 |
10 |
10 |
0 |
8.423ms |
6.64ms |
7.653ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (113.16.214.85) with 32 bytes of data: Reply from 113.16.214.85: bytes=32 time=8ms TTL=58 Reply from 113.16.214.85: bytes=32 time=7ms TTL=58 Reply from 113.16.214.85: bytes=32 time=8ms TTL=58 Reply from 113.16.214.85: bytes=32 time=8ms TTL=58 Reply from 113.16.214.85: bytes=32 time=8ms TTL=58 Reply from 113.16.214.85: bytes=32 time=8ms TTL=58 Reply from 113.16.214.85: bytes=32 time=8ms TTL=58 Reply from 113.16.214.85: bytes=32 time=8ms TTL=58 Reply from 113.16.214.85: bytes=32 time=7ms TTL=58 Reply from 113.16.214.85: bytes=32 time=7ms TTL=58
Ping statistics for 113.16.214.85: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 8ms, Average = 8ms查看 |
GET PING Trace Dig |
|
上海上海市电信 |
电信 |
上海 |
61.170.79.113 |
中国上海电信 |
10 |
10 |
0 |
8.657ms |
6.404ms |
7.611ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (61.170.79.113) with 32 bytes of data: Reply from 61.170.79.113: bytes=32 time=8ms TTL=58 Reply from 61.170.79.113: bytes=32 time=7ms TTL=58 Reply from 61.170.79.113: bytes=32 time=8ms TTL=58 Reply from 61.170.79.113: bytes=32 time=6ms TTL=58 Reply from 61.170.79.113: bytes=32 time=8ms TTL=58 Reply from 61.170.79.113: bytes=32 time=6ms TTL=58 Reply from 61.170.79.113: bytes=32 time=8ms TTL=58 Reply from 61.170.79.113: bytes=32 time=8ms TTL=58 Reply from 61.170.79.113: bytes=32 time=9ms TTL=58 Reply from 61.170.79.113: bytes=32 time=8ms TTL=58
Ping statistics for 61.170.79.113: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 6ms, Maximum = 9ms, Average = 8ms查看 |
GET PING Trace Dig |
|
重庆重庆市联通 |
联通 |
重庆 |
183.231.33.85 |
中国重庆移动 |
10 |
10 |
0 |
8.19ms |
7.098ms |
7.53ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (183.231.33.85) with 32 bytes of data: Reply from 183.231.33.85: bytes=32 time=8ms TTL=54 Reply from 183.231.33.85: bytes=32 time=8ms TTL=54 Reply from 183.231.33.85: bytes=32 time=8ms TTL=54 Reply from 183.231.33.85: bytes=32 time=8ms TTL=54 Reply from 183.231.33.85: bytes=32 time=7ms TTL=54 Reply from 183.231.33.85: bytes=32 time=7ms TTL=54 Reply from 183.231.33.85: bytes=32 time=7ms TTL=54 Reply from 183.231.33.85: bytes=32 time=7ms TTL=54 Reply from 183.231.33.85: bytes=32 time=7ms TTL=54 Reply from 183.231.33.85: bytes=32 time=7ms TTL=54
Ping statistics for 183.231.33.85: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 8ms, Average = 8ms查看 |
GET PING Trace Dig |
|
江西九江市电信 |
电信 |
江西 |
117.45.3.17 |
中国江西南昌电信 |
10 |
10 |
0 |
7.902ms |
7.443ms |
7.524ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (117.45.3.17) with 32 bytes of data: Reply from 117.45.3.17: bytes=32 time=8ms TTL=56 Reply from 117.45.3.17: bytes=32 time=7ms TTL=56 Reply from 117.45.3.17: bytes=32 time=8ms TTL=56 Reply from 117.45.3.17: bytes=32 time=7ms TTL=56 Reply from 117.45.3.17: bytes=32 time=7ms TTL=56 Reply from 117.45.3.17: bytes=32 time=7ms TTL=56 Reply from 117.45.3.17: bytes=32 time=7ms TTL=56 Reply from 117.45.3.17: bytes=32 time=8ms TTL=56 Reply from 117.45.3.17: bytes=32 time=7ms TTL=56 Reply from 117.45.3.17: bytes=32 time=7ms TTL=56
Ping statistics for 117.45.3.17: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 8ms, Average = 8ms查看 |
GET PING Trace Dig |
|
云南昆明市移动 |
移动 |
云南 |
36.147.19.143 |
中国云南昆明移动 |
10 |
10 |
0 |
12.72ms |
5.56ms |
7.497ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (36.147.19.143) with 32 bytes of data: Reply from 36.147.19.143: bytes=32 time=7ms TTL=57 Reply from 36.147.19.143: bytes=32 time=6ms TTL=57 Reply from 36.147.19.143: bytes=32 time=6ms TTL=57 Reply from 36.147.19.143: bytes=32 time=12ms TTL=57 Reply from 36.147.19.143: bytes=32 time=13ms TTL=57 Reply from 36.147.19.143: bytes=32 time=6ms TTL=57 Reply from 36.147.19.143: bytes=32 time=6ms TTL=57 Reply from 36.147.19.143: bytes=32 time=7ms TTL=57 Reply from 36.147.19.143: bytes=32 time=6ms TTL=57 Reply from 36.147.19.143: bytes=32 time=9ms TTL=57
Ping statistics for 36.147.19.143: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 6ms, Maximum = 13ms, Average = 7ms查看 |
GET PING Trace Dig |
|
青海西宁市联通 |
联通 |
青海 |
139.170.154.36 |
中国青海西宁联通 |
10 |
10 |
0 |
9.1ms |
6.667ms |
7.462ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (139.170.154.36) with 32 bytes of data: Reply from 139.170.154.36: bytes=32 time=7ms TTL=56 Reply from 139.170.154.36: bytes=32 time=7ms TTL=56 Reply from 139.170.154.36: bytes=32 time=8ms TTL=56 Reply from 139.170.154.36: bytes=32 time=9ms TTL=56 Reply from 139.170.154.36: bytes=32 time=7ms TTL=56 Reply from 139.170.154.36: bytes=32 time=8ms TTL=56 Reply from 139.170.154.36: bytes=32 time=7ms TTL=56 Reply from 139.170.154.36: bytes=32 time=7ms TTL=56 Reply from 139.170.154.36: bytes=32 time=8ms TTL=56 Reply from 139.170.154.36: bytes=32 time=7ms TTL=56
Ping statistics for 139.170.154.36: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 9ms, Average = 7ms查看 |
GET PING Trace Dig |
|
湖南长沙市移动 |
移动 |
湖南 |
36.158.219.31 |
中国湖南长沙移动 |
10 |
10 |
0 |
8.68ms |
7.165ms |
7.412ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (36.158.219.31) with 32 bytes of data: Reply from 36.158.219.31: bytes=32 time=9ms TTL=51 Reply from 36.158.219.31: bytes=32 time=7ms TTL=51 Reply from 36.158.219.31: bytes=32 time=7ms TTL=51 Reply from 36.158.219.31: bytes=32 time=7ms TTL=51 Reply from 36.158.219.31: bytes=32 time=7ms TTL=51 Reply from 36.158.219.31: bytes=32 time=7ms TTL=51 Reply from 36.158.219.31: bytes=32 time=7ms TTL=51 Reply from 36.158.219.31: bytes=32 time=7ms TTL=51 Reply from 36.158.219.31: bytes=32 time=7ms TTL=51 Reply from 36.158.219.31: bytes=32 time=7ms TTL=51
Ping statistics for 36.158.219.31: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 9ms, Average = 7ms查看 |
GET PING Trace Dig |
|
海南东方市电信 |
电信 |
海南 |
111.29.1.196 |
中国海南海口移动 |
10 |
10 |
0 |
8.16ms |
6.32ms |
7.303ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (111.29.1.196) with 32 bytes of data: Reply from 111.29.1.196: bytes=32 time=7ms TTL=55 Reply from 111.29.1.196: bytes=32 time=8ms TTL=55 Reply from 111.29.1.196: bytes=32 time=7ms TTL=55 Reply from 111.29.1.196: bytes=32 time=8ms TTL=55 Reply from 111.29.1.196: bytes=32 time=7ms TTL=55 Reply from 111.29.1.196: bytes=32 time=8ms TTL=55 Reply from 111.29.1.196: bytes=32 time=6ms TTL=55 Reply from 111.29.1.196: bytes=32 time=8ms TTL=55 Reply from 111.29.1.196: bytes=32 time=6ms TTL=55 Reply from 111.29.1.196: bytes=32 time=8ms TTL=55
Ping statistics for 111.29.1.196: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 6ms, Maximum = 8ms, Average = 7ms查看 |
GET PING Trace Dig |
|
江西赣州市联通 |
联通 |
江西 |
182.87.105.50 |
中国江西赣州电信 |
10 |
10 |
0 |
7.314ms |
7.023ms |
7.191ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (182.87.105.50) with 32 bytes of data: Reply from 182.87.105.50: bytes=32 time=7ms TTL=53 Reply from 182.87.105.50: bytes=32 time=7ms TTL=53 Reply from 182.87.105.50: bytes=32 time=7ms TTL=53 Reply from 182.87.105.50: bytes=32 time=7ms TTL=53 Reply from 182.87.105.50: bytes=32 time=7ms TTL=53 Reply from 182.87.105.50: bytes=32 time=7ms TTL=53 Reply from 182.87.105.50: bytes=32 time=7ms TTL=53 Reply from 182.87.105.50: bytes=32 time=7ms TTL=53 Reply from 182.87.105.50: bytes=32 time=7ms TTL=53 Reply from 182.87.105.50: bytes=32 time=7ms TTL=53
Ping statistics for 182.87.105.50: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 7ms, Maximum = 7ms, Average = 7ms查看 |
GET PING Trace Dig |
|
甘肃兰州市移动 |
移动 |
甘肃 |
60.165.64.86 |
中国甘肃天水电信 |
10 |
10 |
0 |
9.541ms |
5.932ms |
7.064ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (60.165.64.86) with 32 bytes of data: Reply from 60.165.64.86: bytes=32 time=6ms TTL=53 Reply from 60.165.64.86: bytes=32 time=6ms TTL=53 Reply from 60.165.64.86: bytes=32 time=8ms TTL=51 Reply from 60.165.64.86: bytes=32 time=6ms TTL=53 Reply from 60.165.64.86: bytes=32 time=9ms TTL=53 Reply from 60.165.64.86: bytes=32 time=10ms TTL=53 Reply from 60.165.64.86: bytes=32 time=8ms TTL=53 Reply from 60.165.64.86: bytes=32 time=6ms TTL=53 Reply from 60.165.64.86: bytes=32 time=6ms TTL=53 Reply from 60.165.64.86: bytes=32 time=6ms TTL=53
Ping statistics for 60.165.64.86: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 6ms, Maximum = 10ms, Average = 7ms查看 |
GET PING Trace Dig |
|
天津天津市电信 |
电信 |
天津 |
60.222.11.134 |
中国山西运城联通 |
10 |
10 |
0 |
7.48ms |
6.42ms |
6.85ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (60.222.11.134) with 32 bytes of data: Reply from 60.222.11.134: bytes=32 time=7ms TTL=56 Reply from 60.222.11.134: bytes=32 time=7ms TTL=56 Reply from 60.222.11.134: bytes=32 time=6ms TTL=56 Reply from 60.222.11.134: bytes=32 time=7ms TTL=56 Reply from 60.222.11.134: bytes=32 time=7ms TTL=56 Reply from 60.222.11.134: bytes=32 time=7ms TTL=56 Reply from 60.222.11.134: bytes=32 time=7ms TTL=56 Reply from 60.222.11.134: bytes=32 time=7ms TTL=56 Reply from 60.222.11.134: bytes=32 time=7ms TTL=56 Reply from 60.222.11.134: bytes=32 time=6ms TTL=56
Ping statistics for 60.222.11.134: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 6ms, Maximum = 7ms, Average = 7ms查看 |
GET PING Trace Dig |
|
陕西咸阳市电信 |
电信 |
陕西 |
111.20.23.68 |
中国陕西咸阳移动 |
10 |
10 |
0 |
7.14ms |
6.28ms |
6.689ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (111.20.23.68) with 32 bytes of data: Reply from 111.20.23.68: bytes=32 time=7ms TTL=56 Reply from 111.20.23.68: bytes=32 time=7ms TTL=56 Reply from 111.20.23.68: bytes=32 time=6ms TTL=56 Reply from 111.20.23.68: bytes=32 time=6ms TTL=56 Reply from 111.20.23.68: bytes=32 time=7ms TTL=56 Reply from 111.20.23.68: bytes=32 time=7ms TTL=56 Reply from 111.20.23.68: bytes=32 time=7ms TTL=56 Reply from 111.20.23.68: bytes=32 time=6ms TTL=56 Reply from 111.20.23.68: bytes=32 time=7ms TTL=56 Reply from 111.20.23.68: bytes=32 time=7ms TTL=56
Ping statistics for 111.20.23.68: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 6ms, Maximum = 7ms, Average = 7ms查看 |
GET PING Trace Dig |
|
北京北京市联通 |
联通 |
北京 |
125.39.43.12 |
中国天津联通 |
10 |
10 |
0 |
6.66ms |
6.4ms |
6.569ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (125.39.43.12) with 32 bytes of data: Reply from 125.39.43.12: bytes=32 time=7ms TTL=56 Reply from 125.39.43.12: bytes=32 time=6ms TTL=56 Reply from 125.39.43.12: bytes=32 time=7ms TTL=56 Reply from 125.39.43.12: bytes=32 time=7ms TTL=56 Reply from 125.39.43.12: bytes=32 time=6ms TTL=56 Reply from 125.39.43.12: bytes=32 time=7ms TTL=56 Reply from 125.39.43.12: bytes=32 time=7ms TTL=56 Reply from 125.39.43.12: bytes=32 time=7ms TTL=56 Reply from 125.39.43.12: bytes=32 time=7ms TTL=56 Reply from 125.39.43.12: bytes=32 time=7ms TTL=56
Ping statistics for 125.39.43.12: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 6ms, Maximum = 7ms, Average = 7ms查看 |
GET PING Trace Dig |
|
海南澄迈市电信 |
电信 |
海南 |
124.225.166.65 |
中国海南海口电信 |
10 |
10 |
0 |
9.88ms |
4.64ms |
6.474ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (124.225.166.65) with 32 bytes of data: Reply from 124.225.166.65: bytes=32 time=10ms TTL=58 Reply from 124.225.166.65: bytes=32 time=8ms TTL=58 Reply from 124.225.166.65: bytes=32 time=5ms TTL=58 Reply from 124.225.166.65: bytes=32 time=8ms TTL=58 Reply from 124.225.166.65: bytes=32 time=5ms TTL=58 Reply from 124.225.166.65: bytes=32 time=5ms TTL=58 Reply from 124.225.166.65: bytes=32 time=8ms TTL=58 Reply from 124.225.166.65: bytes=32 time=6ms TTL=58 Reply from 124.225.166.65: bytes=32 time=5ms TTL=58 Reply from 124.225.166.65: bytes=32 time=6ms TTL=58
Ping statistics for 124.225.166.65: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 5ms, Maximum = 10ms, Average = 6ms查看 |
GET PING Trace Dig |
|
云南昆明市电信 |
电信 |
云南 |
36.147.34.22 |
中国云南昆明移动 |
10 |
10 |
0 |
7.198ms |
5.881ms |
6.301ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (36.147.34.22) with 32 bytes of data: Reply from 36.147.34.22: bytes=32 time=7ms TTL=56 Reply from 36.147.34.22: bytes=32 time=6ms TTL=56 Reply from 36.147.34.22: bytes=32 time=6ms TTL=56 Reply from 36.147.34.22: bytes=32 time=6ms TTL=56 Reply from 36.147.34.22: bytes=32 time=7ms TTL=56 Reply from 36.147.34.22: bytes=32 time=7ms TTL=56 Reply from 36.147.34.22: bytes=32 time=6ms TTL=56 Reply from 36.147.34.22: bytes=32 time=6ms TTL=56 Reply from 36.147.34.22: bytes=32 time=6ms TTL=56 Reply from 36.147.34.22: bytes=32 time=6ms TTL=56
Ping statistics for 36.147.34.22: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 6ms, Maximum = 7ms, Average = 6ms查看 |
GET PING Trace Dig |
|
福建厦门市移动 |
移动 |
福建 |
112.48.183.213 |
中国福建厦门移动 |
10 |
10 |
0 |
8.164ms |
5.385ms |
6.082ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (112.48.183.213) with 32 bytes of data: Reply from 112.48.183.213: bytes=32 time=6ms TTL=50 Reply from 112.48.183.213: bytes=32 time=6ms TTL=50 Reply from 112.48.183.213: bytes=32 time=6ms TTL=50 Reply from 112.48.183.213: bytes=32 time=6ms TTL=50 Reply from 112.48.183.213: bytes=32 time=5ms TTL=50 Reply from 112.48.183.213: bytes=32 time=6ms TTL=50 Reply from 112.48.183.213: bytes=32 time=8ms TTL=50 Reply from 112.48.183.213: bytes=32 time=5ms TTL=50 Reply from 112.48.183.213: bytes=32 time=6ms TTL=50 Reply from 112.48.183.213: bytes=32 time=6ms TTL=50
Ping statistics for 112.48.183.213: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 5ms, Maximum = 8ms, Average = 6ms查看 |
GET PING Trace Dig |
|
陕西宝鸡市移动 |
移动 |
陕西 |
111.20.23.64 |
中国陕西咸阳移动 |
10 |
10 |
0 |
6.02ms |
4.86ms |
5.666ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (111.20.23.64) with 32 bytes of data: Reply from 111.20.23.64: bytes=32 time=6ms TTL=56 Reply from 111.20.23.64: bytes=32 time=6ms TTL=56 Reply from 111.20.23.64: bytes=32 time=6ms TTL=56 Reply from 111.20.23.64: bytes=32 time=6ms TTL=56 Reply from 111.20.23.64: bytes=32 time=6ms TTL=56 Reply from 111.20.23.64: bytes=32 time=6ms TTL=56 Reply from 111.20.23.64: bytes=32 time=5ms TTL=56 Reply from 111.20.23.64: bytes=32 time=6ms TTL=56 Reply from 111.20.23.64: bytes=32 time=6ms TTL=56 Reply from 111.20.23.64: bytes=32 time=6ms TTL=56
Ping statistics for 111.20.23.64: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 5ms, Maximum = 6ms, Average = 6ms查看 |
GET PING Trace Dig |
|
天津天津市联通 |
联通 |
天津 |
125.39.43.7 |
中国天津联通 |
10 |
10 |
0 |
8.2ms |
4.54ms |
5.532ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (125.39.43.7) with 32 bytes of data: Reply from 125.39.43.7: bytes=32 time=5ms TTL=57 Reply from 125.39.43.7: bytes=32 time=5ms TTL=57 Reply from 125.39.43.7: bytes=32 time=7ms TTL=57 Reply from 125.39.43.7: bytes=32 time=8ms TTL=57 Reply from 125.39.43.7: bytes=32 time=5ms TTL=57 Reply from 125.39.43.7: bytes=32 time=5ms TTL=57 Reply from 125.39.43.7: bytes=32 time=5ms TTL=57 Reply from 125.39.43.7: bytes=32 time=5ms TTL=57 Reply from 125.39.43.7: bytes=32 time=5ms TTL=57 Reply from 125.39.43.7: bytes=32 time=5ms TTL=57
Ping statistics for 125.39.43.7: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 5ms, Maximum = 8ms, Average = 6ms查看 |
GET PING Trace Dig |
|
山西太原市电信 |
电信 |
山西 |
1.71.81.85 |
中国山西太原电信 |
10 |
10 |
0 |
5.964ms |
5.229ms |
5.42ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (1.71.81.85) with 32 bytes of data: Reply from 1.71.81.85: bytes=32 time=6ms TTL=53 Reply from 1.71.81.85: bytes=32 time=5ms TTL=53 Reply from 1.71.81.85: bytes=32 time=5ms TTL=53 Reply from 1.71.81.85: bytes=32 time=5ms TTL=53 Reply from 1.71.81.85: bytes=32 time=5ms TTL=53 Reply from 1.71.81.85: bytes=32 time=6ms TTL=53 Reply from 1.71.81.85: bytes=32 time=5ms TTL=53 Reply from 1.71.81.85: bytes=32 time=5ms TTL=53 Reply from 1.71.81.85: bytes=32 time=5ms TTL=53 Reply from 1.71.81.85: bytes=32 time=5ms TTL=53
Ping statistics for 1.71.81.85: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 5ms, Maximum = 6ms, Average = 5ms查看 |
GET PING Trace Dig |
|
新疆伊犁哈萨克自治州联通 |
联通 |
新疆 |
60.13.234.79 |
中国新疆伊犁联通 |
10 |
10 |
0 |
5.78ms |
5.2ms |
5.412ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (60.13.234.79) with 32 bytes of data: Reply from 60.13.234.79: bytes=32 time=6ms TTL=60 Reply from 60.13.234.79: bytes=32 time=5ms TTL=60 Reply from 60.13.234.79: bytes=32 time=5ms TTL=60 Reply from 60.13.234.79: bytes=32 time=6ms TTL=60 Reply from 60.13.234.79: bytes=32 time=5ms TTL=60 Reply from 60.13.234.79: bytes=32 time=6ms TTL=60 Reply from 60.13.234.79: bytes=32 time=6ms TTL=60 Reply from 60.13.234.79: bytes=32 time=5ms TTL=60 Reply from 60.13.234.79: bytes=32 time=5ms TTL=60 Reply from 60.13.234.79: bytes=32 time=5ms TTL=60
Ping statistics for 60.13.234.79: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 5ms, Maximum = 6ms, Average = 5ms查看 |
GET PING Trace Dig |
|
北京北京市联通 |
联通 |
北京 |
202.143.102.251 |
中国河北石家庄广电 |
10 |
10 |
0 |
6.86ms |
4.86ms |
5.194ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (202.143.102.251) with 32 bytes of data: Reply from 202.143.102.251: bytes=32 time=5ms TTL=58 Reply from 202.143.102.251: bytes=32 time=5ms TTL=58 Reply from 202.143.102.251: bytes=32 time=5ms TTL=58 Reply from 202.143.102.251: bytes=32 time=5ms TTL=58 Reply from 202.143.102.251: bytes=32 time=5ms TTL=58 Reply from 202.143.102.251: bytes=32 time=5ms TTL=58 Reply from 202.143.102.251: bytes=32 time=7ms TTL=58 Reply from 202.143.102.251: bytes=32 time=5ms TTL=58 Reply from 202.143.102.251: bytes=32 time=5ms TTL=58 Reply from 202.143.102.251: bytes=32 time=5ms TTL=58
Ping statistics for 202.143.102.251: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 5ms, Maximum = 7ms, Average = 5ms查看 |
GET PING Trace Dig |
|
上海上海市移动 |
移动 |
上海 |
140.207.63.162 |
中国上海联通 |
10 |
10 |
0 |
5.942ms |
4.031ms |
4.924ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (140.207.63.162) with 32 bytes of data: Reply from 140.207.63.162: bytes=32 time=5ms TTL=58 Reply from 140.207.63.162: bytes=32 time=5ms TTL=58 Reply from 140.207.63.162: bytes=32 time=5ms TTL=58 Reply from 140.207.63.162: bytes=32 time=6ms TTL=58 Reply from 140.207.63.162: bytes=32 time=5ms TTL=58 Reply from 140.207.63.162: bytes=32 time=5ms TTL=58 Reply from 140.207.63.162: bytes=32 time=4ms TTL=58 Reply from 140.207.63.162: bytes=32 time=4ms TTL=58 Reply from 140.207.63.162: bytes=32 time=5ms TTL=58 Reply from 140.207.63.162: bytes=32 time=5ms TTL=58
Ping statistics for 140.207.63.162: 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 |
|
新疆乌鲁木齐市移动 |
移动 |
新疆 |
221.181.55.57 |
中国新疆阿克苏移动 |
10 |
10 |
0 |
5.7ms |
4.032ms |
4.476ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (221.181.55.57) with 32 bytes of data: Reply from 221.181.55.57: bytes=32 time=5ms TTL=56 Reply from 221.181.55.57: bytes=32 time=4ms TTL=56 Reply from 221.181.55.57: bytes=32 time=4ms TTL=56 Reply from 221.181.55.57: bytes=32 time=4ms TTL=56 Reply from 221.181.55.57: bytes=32 time=4ms TTL=56 Reply from 221.181.55.57: bytes=32 time=4ms TTL=56 Reply from 221.181.55.57: bytes=32 time=5ms TTL=56 Reply from 221.181.55.57: bytes=32 time=4ms TTL=56 Reply from 221.181.55.57: bytes=32 time=4ms TTL=56 Reply from 221.181.55.57: bytes=32 time=6ms TTL=56
Ping statistics for 221.181.55.57: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 4ms, Maximum = 6ms, Average = 4ms查看 |
GET PING Trace Dig |
|
海南文昌市移动 |
移动 |
海南 |
153.0.232.50 |
中国海南海口联通 |
10 |
10 |
0 |
4.7ms |
4.24ms |
4.446ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (153.0.232.50) with 32 bytes of data: Reply from 153.0.232.50: bytes=32 time=5ms TTL=57 Reply from 153.0.232.50: bytes=32 time=4ms TTL=57 Reply from 153.0.232.50: bytes=32 time=4ms TTL=57 Reply from 153.0.232.50: bytes=32 time=4ms TTL=57 Reply from 153.0.232.50: bytes=32 time=4ms TTL=57 Reply from 153.0.232.50: bytes=32 time=5ms TTL=57 Reply from 153.0.232.50: bytes=32 time=4ms TTL=57 Reply from 153.0.232.50: bytes=32 time=4ms TTL=57 Reply from 153.0.232.50: bytes=32 time=4ms TTL=57 Reply from 153.0.232.50: bytes=32 time=4ms TTL=57
Ping statistics for 153.0.232.50: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 4ms, Maximum = 5ms, Average = 4ms查看 |
GET PING Trace Dig |
|
贵州贵阳市电信 |
电信 |
贵州 |
111.124.208.19 |
中国贵州贵阳电信 |
10 |
10 |
0 |
4.656ms |
4.031ms |
4.238ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (111.124.208.19) with 32 bytes of data: Reply from 111.124.208.19: bytes=32 time=5ms TTL=53 Reply from 111.124.208.19: bytes=32 time=4ms TTL=53 Reply from 111.124.208.19: bytes=32 time=4ms TTL=53 Reply from 111.124.208.19: bytes=32 time=4ms TTL=53 Reply from 111.124.208.19: bytes=32 time=4ms TTL=53 Reply from 111.124.208.19: bytes=32 time=4ms TTL=53 Reply from 111.124.208.19: bytes=32 time=4ms TTL=53 Reply from 111.124.208.19: bytes=32 time=4ms TTL=53 Reply from 111.124.208.19: bytes=32 time=4ms TTL=53 Reply from 111.124.208.19: bytes=32 time=4ms TTL=53
Ping statistics for 111.124.208.19: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 4ms, Maximum = 5ms, Average = 4ms查看 |
GET PING Trace Dig |
|
吉林长春市移动 |
移动 |
吉林 |
36.135.15.29 |
中国吉林移动 |
10 |
10 |
0 |
4.12ms |
3.4ms |
3.526ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (36.135.15.29) with 32 bytes of data: Reply from 36.135.15.29: bytes=32 time=4ms TTL=57 Reply from 36.135.15.29: bytes=32 time=3ms TTL=57 Reply from 36.135.15.29: bytes=32 time=3ms TTL=57 Reply from 36.135.15.29: bytes=32 time=3ms TTL=57 Reply from 36.135.15.29: bytes=32 time=4ms TTL=57 Reply from 36.135.15.29: bytes=32 time=3ms TTL=57 Reply from 36.135.15.29: bytes=32 time=3ms TTL=57 Reply from 36.135.15.29: bytes=32 time=3ms TTL=57 Reply from 36.135.15.29: bytes=32 time=3ms TTL=57 Reply from 36.135.15.29: bytes=32 time=4ms TTL=57
Ping statistics for 36.135.15.29: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 3ms, Maximum = 4ms, Average = 4ms查看 |
GET PING Trace Dig |
|
上海上海市联通 |
联通 |
上海 |
140.207.63.162 |
中国上海联通 |
10 |
10 |
0 |
3.408ms |
2.488ms |
3.069ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (140.207.63.162) with 32 bytes of data: Reply from 140.207.63.162: bytes=32 time=3ms TTL=58 Reply from 140.207.63.162: bytes=32 time=3ms TTL=58 Reply from 140.207.63.162: bytes=32 time=3ms TTL=58 Reply from 140.207.63.162: bytes=32 time=3ms TTL=58 Reply from 140.207.63.162: bytes=32 time=3ms TTL=58 Reply from 140.207.63.162: bytes=32 time=3ms TTL=58 Reply from 140.207.63.162: bytes=32 time=3ms TTL=58 Reply from 140.207.63.162: bytes=32 time=2ms TTL=58 Reply from 140.207.63.162: bytes=32 time=3ms TTL=58 Reply from 140.207.63.162: bytes=32 time=3ms TTL=58
Ping statistics for 140.207.63.162: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 2ms, Maximum = 3ms, Average = 3ms查看 |
GET PING Trace Dig |
|
天津天津市联通 |
联通 |
天津 |
125.39.43.14 |
中国天津联通 |
10 |
10 |
0 |
3.27ms |
2.803ms |
3.023ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (125.39.43.14) with 32 bytes of data: Reply from 125.39.43.14: bytes=32 time=3ms TTL=58 Reply from 125.39.43.14: bytes=32 time=3ms TTL=58 Reply from 125.39.43.14: bytes=32 time=3ms TTL=58 Reply from 125.39.43.14: bytes=32 time=3ms TTL=58 Reply from 125.39.43.14: bytes=32 time=3ms TTL=58 Reply from 125.39.43.14: bytes=32 time=3ms TTL=58 Reply from 125.39.43.14: bytes=32 time=3ms TTL=58 Reply from 125.39.43.14: bytes=32 time=3ms TTL=58 Reply from 125.39.43.14: bytes=32 time=3ms TTL=58 Reply from 125.39.43.14: bytes=32 time=3ms TTL=58
Ping statistics for 125.39.43.14: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 3ms, Maximum = 3ms, Average = 3ms查看 |
GET PING Trace Dig |
|
陕西西安市联通 |
联通 |
陕西 |
111.20.23.70 |
中国陕西咸阳移动 |
10 |
10 |
0 |
3.905ms |
2.412ms |
2.828ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (111.20.23.70) with 32 bytes of data: Reply from 111.20.23.70: bytes=32 time=4ms TTL=54 Reply from 111.20.23.70: bytes=32 time=3ms TTL=54 Reply from 111.20.23.70: bytes=32 time=3ms TTL=54 Reply from 111.20.23.70: bytes=32 time=3ms TTL=54 Reply from 111.20.23.70: bytes=32 time=3ms TTL=54 Reply from 111.20.23.70: bytes=32 time=3ms TTL=54 Reply from 111.20.23.70: bytes=32 time=2ms TTL=54 Reply from 111.20.23.70: bytes=32 time=3ms TTL=54 Reply from 111.20.23.70: bytes=32 time=3ms TTL=54 Reply from 111.20.23.70: bytes=32 time=3ms TTL=54
Ping statistics for 111.20.23.70: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 2ms, Maximum = 4ms, Average = 3ms查看 |
GET PING Trace Dig |
|
甘肃兰州市电信 |
电信 |
甘肃 |
60.165.64.81 |
中国甘肃天水电信 |
10 |
10 |
0 |
2.838ms |
2.285ms |
2.641ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (60.165.64.81) with 32 bytes of data: Reply from 60.165.64.81: bytes=32 time=3ms TTL=54 Reply from 60.165.64.81: bytes=32 time=3ms TTL=54 Reply from 60.165.64.81: bytes=32 time=3ms TTL=52 Reply from 60.165.64.81: bytes=32 time=2ms TTL=54 Reply from 60.165.64.81: bytes=32 time=3ms TTL=54 Reply from 60.165.64.81: bytes=32 time=3ms TTL=54 Reply from 60.165.64.81: bytes=32 time=2ms TTL=54 Reply from 60.165.64.81: bytes=32 time=3ms TTL=54 Reply from 60.165.64.81: bytes=32 time=3ms TTL=54 Reply from 60.165.64.81: bytes=32 time=3ms TTL=54
Ping statistics for 60.165.64.81: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 2ms, Maximum = 3ms, Average = 3ms查看 |
GET PING Trace Dig |
|
西藏拉萨市移动 |
移动 |
西藏 |
117.180.227.228 |
中国西藏拉萨移动 |
10 |
10 |
0 |
1.859ms |
1.38ms |
1.515ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (117.180.227.228) with 32 bytes of data: Reply from 117.180.227.228: bytes=32 time=2ms TTL=58 Reply from 117.180.227.228: bytes=32 time=1ms TTL=58 Reply from 117.180.227.228: bytes=32 time=1ms TTL=58 Reply from 117.180.227.228: bytes=32 time=1ms TTL=58 Reply from 117.180.227.228: bytes=32 time=1ms TTL=58 Reply from 117.180.227.228: bytes=32 time=2ms TTL=58 Reply from 117.180.227.228: bytes=32 time=2ms TTL=58 Reply from 117.180.227.228: bytes=32 time=2ms TTL=58 Reply from 117.180.227.228: bytes=32 time=1ms TTL=58 Reply from 117.180.227.228: bytes=32 time=2ms TTL=58
Ping statistics for 117.180.227.228: Packets: Sent = 10, Received = 10, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 2ms, Average = 2ms查看 |
GET PING Trace Dig |
|
吉林长春市电信 |
电信 |
吉林 |
36.104.139.33 |
中国吉林长春电信 |
10 |
10 |
0 |
1.14ms |
0.98ms |
1.03ms |
32B |
PING sdk.mihoyo.com PING sdk.mihoyo.com (36.104.139.33) with 32 bytes of data: Reply from 36.104.139.33: bytes=32 time=1ms TTL=56 Reply from 36.104.139.33: bytes=32 time=1ms TTL=56 Reply from 36.104.139.33: bytes=32 time=1ms TTL=56 Reply from 36.104.139.33: bytes=32 time=1ms TTL=56 Reply from 36.104.139.33: bytes=32 time=1ms TTL=56 Reply from 36.104.139.33: bytes=32 time=1ms TTL=56 Reply from 36.104.139.33: bytes=32 time=1ms TTL=56 Reply from 36.104.139.33: bytes=32 time=1ms TTL=56 Reply from 36.104.139.33: bytes=32 time=1ms TTL=56 Reply from 36.104.139.33: bytes=32 time=1ms TTL=56
Ping statistics for 36.104.139.33: 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 sdk.mihoyo.com PING sdk.mihoyo.com () with 0 bytes of data: Reply from : bytes=0 time=244ms TTL=48 Reply from : bytes=0 time=245ms TTL=48 Reply from : bytes=0 time=246ms TTL=48 Request timed out. Reply from : bytes=0 time=249ms TTL=48 Reply from : bytes=0 time=244ms TTL=48 Request timed out. Request timed out. Reply from : bytes=0 time=245ms TTL=48 Reply from : bytes=0 time=245ms TTL=48
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 sdk.mihoyo.com PING sdk.mihoyo.com () with 0 bytes of data: Reply from : bytes=0 time=5ms TTL=57 Reply from : bytes=0 time=5ms TTL=57 Reply from : bytes=0 time=7ms TTL=57 Reply from : bytes=0 time=8ms TTL=57 Reply from : bytes=0 time=5ms TTL=57 Reply from : bytes=0 time=5ms TTL=57 Reply from : bytes=0 time=5ms TTL=57 Reply from : bytes=0 time=5ms TTL=57 Reply from : bytes=0 time=5ms TTL=57 Reply from : bytes=0 time=5ms TTL=57
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 |
|