| 监测点 |
ISP |
省份 |
解析IP |
解析IP所在地 |
发送 |
接收 |
丢弃 |
最大时间 |
最小时间 |
平均时间 |
包大小 |
详细信息 |
操作 |
| 共179个点 |
8个 |
共37个 |
共6个独立IP |
共4个独立节点 |
10 |
9 |
1 |
59.681ms |
38.576ms |
45.515ms |
|
|
|
| 江西赣州市移动 |
移动 |
江西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
3 |
7 |
636.497ms |
0ms |
411.55ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Reply from 101.37.42.196: bytes=32 time=49ms TTL=52
Reply from 101.37.42.196: bytes=32 time=549ms TTL=52
Reply from 101.37.42.196: bytes=32 time=636ms TTL=52
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 3, Lost = 7 (70% loss),
Approximate round trip times in milli-seconds:
Minimum <1ms , Maximum = 636ms, Average = 412ms查看 |
GET PING Trace Dig |
|
| 广西南宁市其他 |
其他 |
广西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
429.201ms |
266.781ms |
320.981ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=338ms TTL=53
Reply from 101.37.42.196: bytes=32 time=293ms TTL=53
Reply from 101.37.42.196: bytes=32 time=285ms TTL=53
Reply from 101.37.42.196: bytes=32 time=316ms TTL=53
Reply from 101.37.42.196: bytes=32 time=302ms TTL=53
Reply from 101.37.42.196: bytes=32 time=295ms TTL=53
Reply from 101.37.42.196: bytes=32 time=429ms TTL=53
Reply from 101.37.42.196: bytes=32 time=346ms TTL=53
Reply from 101.37.42.196: bytes=32 time=339ms TTL=53
Reply from 101.37.42.196: bytes=32 time=267ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 267ms, Maximum = 429ms, Average = 321ms查看 |
GET PING Trace Dig |
|
| 广东茂名市电信 |
电信 |
广东 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
560.364ms |
35.025ms |
151.425ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=35ms TTL=52
Reply from 101.37.42.196: bytes=32 time=560ms TTL=52
Reply from 101.37.42.196: bytes=32 time=257ms TTL=52
Reply from 101.37.42.196: bytes=32 time=43ms TTL=52
Reply from 101.37.42.196: bytes=32 time=289ms TTL=52
Reply from 101.37.42.196: bytes=32 time=128ms TTL=52
Reply from 101.37.42.196: bytes=32 time=91ms TTL=52
Reply from 101.37.42.196: bytes=32 time=38ms TTL=52
Reply from 101.37.42.196: bytes=32 time=37ms TTL=52
Reply from 101.37.42.196: bytes=32 time=36ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 560ms, Average = 151ms查看 |
GET PING Trace Dig |
|
| 西藏拉萨市移动 |
移动 |
西藏 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
202.326ms |
109.567ms |
149.419ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=202ms TTL=50
Reply from 101.37.42.196: bytes=32 time=135ms TTL=50
Reply from 101.37.42.196: bytes=32 time=110ms TTL=50
Reply from 101.37.42.196: bytes=32 time=170ms TTL=50
Reply from 101.37.42.196: bytes=32 time=129ms TTL=50
Reply from 101.37.42.196: bytes=32 time=148ms TTL=50
Reply from 101.37.42.196: bytes=32 time=152ms TTL=50
Reply from 101.37.42.196: bytes=32 time=150ms TTL=50
Reply from 101.37.42.196: bytes=32 time=161ms TTL=50
Reply from 101.37.42.196: bytes=32 time=139ms TTL=50
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 110ms, Maximum = 202ms, Average = 149ms查看 |
GET PING Trace Dig |
|
| 北京北京市移动 |
移动 |
北京 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
118.18ms |
103.74ms |
110.526ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=118ms TTL=50
Reply from 101.37.42.196: bytes=32 time=110ms TTL=50
Reply from 101.37.42.196: bytes=32 time=110ms TTL=50
Reply from 101.37.42.196: bytes=32 time=110ms TTL=50
Reply from 101.37.42.196: bytes=32 time=110ms TTL=50
Reply from 101.37.42.196: bytes=32 time=116ms TTL=50
Reply from 101.37.42.196: bytes=32 time=104ms TTL=50
Reply from 101.37.42.196: bytes=32 time=110ms TTL=50
Reply from 101.37.42.196: bytes=32 time=110ms TTL=50
Reply from 101.37.42.196: bytes=32 time=110ms TTL=50
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 104ms, Maximum = 118ms, Average = 111ms查看 |
GET PING Trace Dig |
|
| 海南海口联通 |
联通 |
海南 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
159.512ms |
65.949ms |
100.475ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=67ms TTL=64
Reply from 101.37.42.196: bytes=32 time=76ms TTL=64
Reply from 101.37.42.196: bytes=32 time=66ms TTL=64
Reply from 101.37.42.196: bytes=32 time=105ms TTL=64
Reply from 101.37.42.196: bytes=32 time=126ms TTL=64
Reply from 101.37.42.196: bytes=32 time=131ms TTL=64
Reply from 101.37.42.196: bytes=32 time=74ms TTL=64
Reply from 101.37.42.196: bytes=32 time=93ms TTL=64
Reply from 101.37.42.196: bytes=32 time=160ms TTL=64
Reply from 101.37.42.196: bytes=32 time=109ms TTL=64
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 66ms, Maximum = 160ms, Average = 100ms查看 |
GET PING Trace Dig |
|
| 新疆喀什地区移动 |
移动 |
新疆 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
96.09ms |
89.526ms |
92.602ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=94ms TTL=52
Reply from 101.37.42.196: bytes=32 time=91ms TTL=52
Reply from 101.37.42.196: bytes=32 time=93ms TTL=52
Reply from 101.37.42.196: bytes=32 time=92ms TTL=52
Reply from 101.37.42.196: bytes=32 time=93ms TTL=52
Reply from 101.37.42.196: bytes=32 time=95ms TTL=52
Reply from 101.37.42.196: bytes=32 time=93ms TTL=52
Reply from 101.37.42.196: bytes=32 time=96ms TTL=52
Reply from 101.37.42.196: bytes=32 time=90ms TTL=52
Reply from 101.37.42.196: bytes=32 time=91ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 96ms, Average = 93ms查看 |
GET PING Trace Dig |
|
| 新疆喀什地区电信 |
电信 |
新疆 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
97.407ms |
90.493ms |
92.489ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=92ms TTL=51
Reply from 101.37.42.196: bytes=32 time=91ms TTL=51
Reply from 101.37.42.196: bytes=32 time=94ms TTL=51
Reply from 101.37.42.196: bytes=32 time=90ms TTL=51
Reply from 101.37.42.196: bytes=32 time=92ms TTL=51
Reply from 101.37.42.196: bytes=32 time=92ms TTL=51
Reply from 101.37.42.196: bytes=32 time=92ms TTL=51
Reply from 101.37.42.196: bytes=32 time=92ms TTL=51
Reply from 101.37.42.196: bytes=32 time=92ms TTL=51
Reply from 101.37.42.196: bytes=32 time=97ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 97ms, Average = 92ms查看 |
GET PING Trace Dig |
|
| 新疆克拉玛依市联通 |
联通 |
新疆 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
89.06ms |
88.76ms |
88.872ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=89ms TTL=51
Reply from 101.37.42.196: bytes=32 time=89ms TTL=51
Reply from 101.37.42.196: bytes=32 time=89ms TTL=51
Reply from 101.37.42.196: bytes=32 time=89ms TTL=51
Reply from 101.37.42.196: bytes=32 time=89ms TTL=51
Reply from 101.37.42.196: bytes=32 time=89ms TTL=51
Reply from 101.37.42.196: bytes=32 time=89ms TTL=51
Reply from 101.37.42.196: bytes=32 time=89ms TTL=51
Reply from 101.37.42.196: bytes=32 time=89ms TTL=51
Reply from 101.37.42.196: bytes=32 time=89ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 89ms, Maximum = 89ms, Average = 89ms查看 |
GET PING Trace Dig |
|
| 北京北京市移动 |
移动 |
北京 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
99.68ms |
79.72ms |
88.556ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=98ms TTL=50
Reply from 101.37.42.196: bytes=32 time=80ms TTL=50
Reply from 101.37.42.196: bytes=32 time=90ms TTL=50
Reply from 101.37.42.196: bytes=32 time=80ms TTL=50
Reply from 101.37.42.196: bytes=32 time=90ms TTL=50
Reply from 101.37.42.196: bytes=32 time=90ms TTL=50
Reply from 101.37.42.196: bytes=32 time=80ms TTL=50
Reply from 101.37.42.196: bytes=32 time=90ms TTL=50
Reply from 101.37.42.196: bytes=32 time=90ms TTL=50
Reply from 101.37.42.196: bytes=32 time=100ms TTL=50
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 100ms, Average = 89ms查看 |
GET PING Trace Dig |
|
| 青海西宁市联通 |
联通 |
青海 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
357.703ms |
52.157ms |
87.543ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=52ms TTL=52
Reply from 101.37.42.196: bytes=32 time=55ms TTL=52
Reply from 101.37.42.196: bytes=32 time=52ms TTL=52
Reply from 101.37.42.196: bytes=32 time=54ms TTL=52
Reply from 101.37.42.196: bytes=32 time=82ms TTL=52
Reply from 101.37.42.196: bytes=32 time=358ms TTL=52
Reply from 101.37.42.196: bytes=32 time=55ms TTL=52
Reply from 101.37.42.196: bytes=32 time=56ms TTL=52
Reply from 101.37.42.196: bytes=32 time=58ms TTL=52
Reply from 101.37.42.196: bytes=32 time=54ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 358ms, Average = 88ms查看 |
GET PING Trace Dig |
|
| 海南海口联通 |
联通 |
海南 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
95.344ms |
80.261ms |
85.93ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=82ms TTL=49
Reply from 101.37.42.196: bytes=32 time=95ms TTL=49
Reply from 101.37.42.196: bytes=32 time=85ms TTL=49
Reply from 101.37.42.196: bytes=32 time=81ms TTL=49
Reply from 101.37.42.196: bytes=32 time=93ms TTL=49
Reply from 101.37.42.196: bytes=32 time=83ms TTL=49
Reply from 101.37.42.196: bytes=32 time=83ms TTL=49
Reply from 101.37.42.196: bytes=32 time=94ms TTL=49
Reply from 101.37.42.196: bytes=32 time=84ms TTL=49
Reply from 101.37.42.196: bytes=32 time=80ms TTL=49
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 95ms, Average = 86ms查看 |
GET PING Trace Dig |
|
| 安徽马鞍山移动 |
移动 |
安徽 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
282.963ms |
21.28ms |
85.03ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=134ms TTL=52
Reply from 101.37.42.196: bytes=32 time=136ms TTL=52
Reply from 101.37.42.196: bytes=32 time=51ms TTL=52
Reply from 101.37.42.196: bytes=32 time=283ms TTL=52
Reply from 101.37.42.196: bytes=32 time=26ms TTL=52
Reply from 101.37.42.196: bytes=32 time=51ms TTL=52
Reply from 101.37.42.196: bytes=32 time=57ms TTL=52
Reply from 101.37.42.196: bytes=32 time=60ms TTL=52
Reply from 101.37.42.196: bytes=32 time=21ms TTL=52
Reply from 101.37.42.196: bytes=32 time=32ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 283ms, Average = 85ms查看 |
GET PING Trace Dig |
|
| 新疆伊犁哈萨克自治州移动 |
移动 |
新疆 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
85.508ms |
84.494ms |
84.958ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=85ms TTL=52
Reply from 101.37.42.196: bytes=32 time=85ms TTL=52
Reply from 101.37.42.196: bytes=32 time=85ms TTL=52
Reply from 101.37.42.196: bytes=32 time=85ms TTL=52
Reply from 101.37.42.196: bytes=32 time=85ms TTL=52
Reply from 101.37.42.196: bytes=32 time=84ms TTL=52
Reply from 101.37.42.196: bytes=32 time=86ms TTL=52
Reply from 101.37.42.196: bytes=32 time=85ms TTL=52
Reply from 101.37.42.196: bytes=32 time=85ms TTL=52
Reply from 101.37.42.196: bytes=32 time=85ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 84ms, Maximum = 86ms, Average = 85ms查看 |
GET PING Trace Dig |
|
| 新疆伊犁哈萨克自治州联通 |
联通 |
新疆 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
84.778ms |
84.218ms |
84.616ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=84ms TTL=51
Reply from 101.37.42.196: bytes=32 time=85ms TTL=51
Reply from 101.37.42.196: bytes=32 time=85ms TTL=51
Reply from 101.37.42.196: bytes=32 time=85ms TTL=51
Reply from 101.37.42.196: bytes=32 time=85ms TTL=51
Reply from 101.37.42.196: bytes=32 time=85ms TTL=51
Reply from 101.37.42.196: bytes=32 time=85ms TTL=51
Reply from 101.37.42.196: bytes=32 time=84ms TTL=51
Reply from 101.37.42.196: bytes=32 time=84ms TTL=51
Reply from 101.37.42.196: bytes=32 time=85ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 84ms, Maximum = 85ms, Average = 85ms查看 |
GET PING Trace Dig |
|
| 甘肃定西市电信 |
电信 |
甘肃 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
138.701ms |
52.706ms |
80.127ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=123ms TTL=49
Reply from 101.37.42.196: bytes=32 time=61ms TTL=49
Reply from 101.37.42.196: bytes=32 time=139ms TTL=49
Reply from 101.37.42.196: bytes=32 time=84ms TTL=49
Reply from 101.37.42.196: bytes=32 time=53ms TTL=49
Reply from 101.37.42.196: bytes=32 time=70ms TTL=49
Reply from 101.37.42.196: bytes=32 time=59ms TTL=49
Reply from 101.37.42.196: bytes=32 time=81ms TTL=49
Reply from 101.37.42.196: bytes=32 time=56ms TTL=49
Reply from 101.37.42.196: bytes=32 time=78ms TTL=49
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 53ms, Maximum = 139ms, Average = 80ms查看 |
GET PING Trace Dig |
|
| 美国国外 |
国外 |
美国 |
47.254.74.24 |
美国加利福尼亚圣克拉拉阿里云 |
10 |
10 |
0 |
80.075ms |
75.527ms |
76.901ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (47.254.74.24) with 32 bytes of data:
Reply from 47.254.74.24: bytes=32 time=77ms TTL=87
Reply from 47.254.74.24: bytes=32 time=76ms TTL=87
Reply from 47.254.74.24: bytes=32 time=77ms TTL=87
Reply from 47.254.74.24: bytes=32 time=77ms TTL=87
Reply from 47.254.74.24: bytes=32 time=80ms TTL=87
Reply from 47.254.74.24: bytes=32 time=76ms TTL=87
Reply from 47.254.74.24: bytes=32 time=76ms TTL=87
Reply from 47.254.74.24: bytes=32 time=76ms TTL=87
Reply from 47.254.74.24: bytes=32 time=77ms TTL=87
Reply from 47.254.74.24: bytes=32 time=77ms TTL=87
Ping statistics for 47.254.74.24:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 76ms, Maximum = 80ms, Average = 77ms查看 |
GET PING Trace Dig |
|
| 新疆阿拉尔市电信 |
电信 |
新疆 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
75.815ms |
75.317ms |
75.578ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=76ms TTL=50
Reply from 101.37.42.196: bytes=32 time=76ms TTL=50
Reply from 101.37.42.196: bytes=32 time=75ms TTL=50
Reply from 101.37.42.196: bytes=32 time=76ms TTL=50
Reply from 101.37.42.196: bytes=32 time=75ms TTL=50
Reply from 101.37.42.196: bytes=32 time=75ms TTL=50
Reply from 101.37.42.196: bytes=32 time=76ms TTL=50
Reply from 101.37.42.196: bytes=32 time=76ms TTL=50
Reply from 101.37.42.196: bytes=32 time=76ms TTL=50
Reply from 101.37.42.196: bytes=32 time=75ms TTL=50
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 75ms, Maximum = 76ms, Average = 76ms查看 |
GET PING Trace Dig |
|
| 重庆重庆市移动 |
移动 |
重庆 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
81.57ms |
63.895ms |
71.751ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=66ms TTL=47
Reply from 101.37.42.196: bytes=32 time=64ms TTL=47
Reply from 101.37.42.196: bytes=32 time=66ms TTL=47
Reply from 101.37.42.196: bytes=32 time=65ms TTL=47
Reply from 101.37.42.196: bytes=32 time=80ms TTL=47
Reply from 101.37.42.196: bytes=32 time=69ms TTL=47
Reply from 101.37.42.196: bytes=32 time=80ms TTL=47
Reply from 101.37.42.196: bytes=32 time=69ms TTL=47
Reply from 101.37.42.196: bytes=32 time=82ms TTL=47
Reply from 101.37.42.196: bytes=32 time=79ms TTL=47
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 82ms, Average = 72ms查看 |
GET PING Trace Dig |
|
| 宁夏银川市联通 |
联通 |
宁夏 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
76.371ms |
63.74ms |
70.121ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=74ms TTL=50
Reply from 101.37.42.196: bytes=32 time=76ms TTL=50
Reply from 101.37.42.196: bytes=32 time=69ms TTL=50
Reply from 101.37.42.196: bytes=32 time=64ms TTL=50
Reply from 101.37.42.196: bytes=32 time=70ms TTL=50
Reply from 101.37.42.196: bytes=32 time=70ms TTL=50
Reply from 101.37.42.196: bytes=32 time=70ms TTL=50
Reply from 101.37.42.196: bytes=32 time=70ms TTL=50
Reply from 101.37.42.196: bytes=32 time=70ms TTL=50
Reply from 101.37.42.196: bytes=32 time=70ms TTL=50
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 76ms, Average = 70ms查看 |
GET PING Trace Dig |
|
| 黑龙江绥化市电信 |
电信 |
黑龙江 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
69.581ms |
62.501ms |
64.803ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=68ms TTL=51
Reply from 101.37.42.196: bytes=32 time=70ms TTL=51
Reply from 101.37.42.196: bytes=32 time=64ms TTL=51
Reply from 101.37.42.196: bytes=32 time=63ms TTL=51
Reply from 101.37.42.196: bytes=32 time=64ms TTL=51
Reply from 101.37.42.196: bytes=32 time=63ms TTL=51
Reply from 101.37.42.196: bytes=32 time=67ms TTL=51
Reply from 101.37.42.196: bytes=32 time=63ms TTL=51
Reply from 101.37.42.196: bytes=32 time=63ms TTL=51
Reply from 101.37.42.196: bytes=32 time=64ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 70ms, Average = 65ms查看 |
GET PING Trace Dig |
|
| 西藏拉萨市电信 |
电信 |
西藏 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
68.078ms |
62.125ms |
64.287ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=66ms TTL=50
Reply from 101.37.42.196: bytes=32 time=62ms TTL=50
Reply from 101.37.42.196: bytes=32 time=65ms TTL=50
Reply from 101.37.42.196: bytes=32 time=68ms TTL=50
Reply from 101.37.42.196: bytes=32 time=62ms TTL=50
Reply from 101.37.42.196: bytes=32 time=63ms TTL=50
Reply from 101.37.42.196: bytes=32 time=64ms TTL=50
Reply from 101.37.42.196: bytes=32 time=63ms TTL=50
Reply from 101.37.42.196: bytes=32 time=64ms TTL=50
Reply from 101.37.42.196: bytes=32 time=66ms TTL=50
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 68ms, Average = 64ms查看 |
GET PING Trace Dig |
|
| 西藏拉萨市移动 |
移动 |
西藏 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
62.979ms |
62.52ms |
62.715ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=63ms TTL=52
Reply from 101.37.42.196: bytes=32 time=63ms TTL=52
Reply from 101.37.42.196: bytes=32 time=63ms TTL=52
Reply from 101.37.42.196: bytes=32 time=63ms TTL=52
Reply from 101.37.42.196: bytes=32 time=63ms TTL=52
Reply from 101.37.42.196: bytes=32 time=63ms TTL=52
Reply from 101.37.42.196: bytes=32 time=63ms TTL=52
Reply from 101.37.42.196: bytes=32 time=63ms TTL=52
Reply from 101.37.42.196: bytes=32 time=63ms TTL=52
Reply from 101.37.42.196: bytes=32 time=63ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 63ms, Maximum = 63ms, Average = 63ms查看 |
GET PING Trace Dig |
|
| 广东佛山联通 |
联通 |
广东 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
69.952ms |
51.689ms |
62.383ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=52ms TTL=49
Reply from 101.37.42.196: bytes=32 time=63ms TTL=49
Reply from 101.37.42.196: bytes=32 time=62ms TTL=49
Reply from 101.37.42.196: bytes=32 time=61ms TTL=49
Reply from 101.37.42.196: bytes=32 time=69ms TTL=49
Reply from 101.37.42.196: bytes=32 time=55ms TTL=49
Reply from 101.37.42.196: bytes=32 time=56ms TTL=49
Reply from 101.37.42.196: bytes=32 time=70ms TTL=49
Reply from 101.37.42.196: bytes=32 time=68ms TTL=49
Reply from 101.37.42.196: bytes=32 time=68ms TTL=49
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 70ms, Average = 62ms查看 |
GET PING Trace Dig |
|
| 甘肃定西市移动 |
移动 |
甘肃 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
9 |
1 |
84.84ms |
49.58ms |
62.38ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=54ms TTL=50
Reply from 101.37.42.196: bytes=32 time=70ms TTL=50
Reply from 101.37.42.196: bytes=32 time=85ms TTL=50
Reply from 101.37.42.196: bytes=32 time=85ms TTL=50
Reply from 101.37.42.196: bytes=32 time=50ms TTL=50
Reply from 101.37.42.196: bytes=32 time=52ms TTL=50
Reply from 101.37.42.196: bytes=32 time=50ms TTL=50
Request timed out.
Reply from 101.37.42.196: bytes=32 time=64ms TTL=50
Reply from 101.37.42.196: bytes=32 time=51ms TTL=50
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 9, Lost = 1 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 85ms, Average = 62ms查看 |
GET PING Trace Dig |
|
| 甘肃陇南市移动 |
移动 |
甘肃 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
68.117ms |
57.068ms |
61.172ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=60ms TTL=50
Reply from 101.37.42.196: bytes=32 time=60ms TTL=50
Reply from 101.37.42.196: bytes=32 time=60ms TTL=50
Reply from 101.37.42.196: bytes=32 time=68ms TTL=50
Reply from 101.37.42.196: bytes=32 time=59ms TTL=50
Reply from 101.37.42.196: bytes=32 time=68ms TTL=50
Reply from 101.37.42.196: bytes=32 time=57ms TTL=50
Reply from 101.37.42.196: bytes=32 time=60ms TTL=50
Reply from 101.37.42.196: bytes=32 time=60ms TTL=50
Reply from 101.37.42.196: bytes=32 time=60ms TTL=50
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 68ms, Average = 61ms查看 |
GET PING Trace Dig |
|
| 海南海口移动 |
移动 |
海南 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
75.532ms |
52.628ms |
60.758ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=73ms TTL=52
Reply from 101.37.42.196: bytes=32 time=68ms TTL=52
Reply from 101.37.42.196: bytes=32 time=60ms TTL=52
Reply from 101.37.42.196: bytes=32 time=62ms TTL=52
Reply from 101.37.42.196: bytes=32 time=53ms TTL=52
Reply from 101.37.42.196: bytes=32 time=54ms TTL=52
Reply from 101.37.42.196: bytes=32 time=76ms TTL=52
Reply from 101.37.42.196: bytes=32 time=53ms TTL=52
Reply from 101.37.42.196: bytes=32 time=56ms TTL=52
Reply from 101.37.42.196: bytes=32 time=54ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 53ms, Maximum = 76ms, Average = 61ms查看 |
GET PING Trace Dig |
|
| 青海西宁市电信 |
电信 |
青海 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
60.268ms |
58.424ms |
58.874ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=59ms TTL=51
Reply from 101.37.42.196: bytes=32 time=59ms TTL=51
Reply from 101.37.42.196: bytes=32 time=59ms TTL=51
Reply from 101.37.42.196: bytes=32 time=59ms TTL=51
Reply from 101.37.42.196: bytes=32 time=59ms TTL=51
Reply from 101.37.42.196: bytes=32 time=59ms TTL=51
Reply from 101.37.42.196: bytes=32 time=60ms TTL=51
Reply from 101.37.42.196: bytes=32 time=59ms TTL=51
Reply from 101.37.42.196: bytes=32 time=59ms TTL=51
Reply from 101.37.42.196: bytes=32 time=58ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 58ms, Maximum = 60ms, Average = 59ms查看 |
GET PING Trace Dig |
|
| 黑龙江双鸭山市移动 |
移动 |
黑龙江 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
59.3ms |
56.8ms |
57.861ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=59ms TTL=52
Reply from 101.37.42.196: bytes=32 time=58ms TTL=52
Reply from 101.37.42.196: bytes=32 time=57ms TTL=52
Reply from 101.37.42.196: bytes=32 time=58ms TTL=52
Reply from 101.37.42.196: bytes=32 time=58ms TTL=52
Reply from 101.37.42.196: bytes=32 time=57ms TTL=52
Reply from 101.37.42.196: bytes=32 time=57ms TTL=52
Reply from 101.37.42.196: bytes=32 time=57ms TTL=52
Reply from 101.37.42.196: bytes=32 time=57ms TTL=52
Reply from 101.37.42.196: bytes=32 time=58ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 59ms, Average = 58ms查看 |
GET PING Trace Dig |
|
| 黑龙江伊春市移动 |
移动 |
黑龙江 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
72.68ms |
54.84ms |
57.739ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=56ms TTL=51
Reply from 101.37.42.196: bytes=32 time=55ms TTL=51
Reply from 101.37.42.196: bytes=32 time=56ms TTL=51
Reply from 101.37.42.196: bytes=32 time=55ms TTL=51
Reply from 101.37.42.196: bytes=32 time=73ms TTL=51
Reply from 101.37.42.196: bytes=32 time=55ms TTL=51
Reply from 101.37.42.196: bytes=32 time=55ms TTL=51
Reply from 101.37.42.196: bytes=32 time=55ms TTL=51
Reply from 101.37.42.196: bytes=32 time=62ms TTL=51
Reply from 101.37.42.196: bytes=32 time=56ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 73ms, Average = 58ms查看 |
GET PING Trace Dig |
|
| 吉林松原市移动 |
移动 |
吉林 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
58.64ms |
56.02ms |
57.337ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=57ms TTL=53
Reply from 101.37.42.196: bytes=32 time=57ms TTL=53
Reply from 101.37.42.196: bytes=32 time=58ms TTL=53
Reply from 101.37.42.196: bytes=32 time=58ms TTL=53
Reply from 101.37.42.196: bytes=32 time=57ms TTL=53
Reply from 101.37.42.196: bytes=32 time=57ms TTL=53
Reply from 101.37.42.196: bytes=32 time=57ms TTL=53
Reply from 101.37.42.196: bytes=32 time=57ms TTL=53
Reply from 101.37.42.196: bytes=32 time=56ms TTL=53
Reply from 101.37.42.196: bytes=32 time=59ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 59ms, Average = 57ms查看 |
GET PING Trace Dig |
|
| 辽宁葫芦岛市联通 |
联通 |
辽宁 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
86.84ms |
47.36ms |
56.612ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=55ms TTL=53
Reply from 101.37.42.196: bytes=32 time=62ms TTL=53
Reply from 101.37.42.196: bytes=32 time=56ms TTL=53
Reply from 101.37.42.196: bytes=32 time=87ms TTL=53
Reply from 101.37.42.196: bytes=32 time=51ms TTL=53
Reply from 101.37.42.196: bytes=32 time=58ms TTL=53
Reply from 101.37.42.196: bytes=32 time=53ms TTL=53
Reply from 101.37.42.196: bytes=32 time=47ms TTL=53
Reply from 101.37.42.196: bytes=32 time=48ms TTL=53
Reply from 101.37.42.196: bytes=32 time=48ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 87ms, Average = 57ms查看 |
GET PING Trace Dig |
|
| 海南东方市电信 |
电信 |
海南 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
56.461ms |
55.881ms |
56.199ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=56ms TTL=51
Reply from 101.37.42.196: bytes=32 time=56ms TTL=51
Reply from 101.37.42.196: bytes=32 time=56ms TTL=51
Reply from 101.37.42.196: bytes=32 time=56ms TTL=51
Reply from 101.37.42.196: bytes=32 time=56ms TTL=51
Reply from 101.37.42.196: bytes=32 time=56ms TTL=51
Reply from 101.37.42.196: bytes=32 time=56ms TTL=51
Reply from 101.37.42.196: bytes=32 time=56ms TTL=51
Reply from 101.37.42.196: bytes=32 time=56ms TTL=51
Reply from 101.37.42.196: bytes=32 time=56ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 56ms, Average = 56ms查看 |
GET PING Trace Dig |
|
| 广西河池移动 |
移动 |
广西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
56.92ms |
55.1ms |
55.745ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=56ms TTL=53
Reply from 101.37.42.196: bytes=32 time=57ms TTL=53
Reply from 101.37.42.196: bytes=32 time=55ms TTL=53
Reply from 101.37.42.196: bytes=32 time=56ms TTL=53
Reply from 101.37.42.196: bytes=32 time=55ms TTL=53
Reply from 101.37.42.196: bytes=32 time=57ms TTL=53
Reply from 101.37.42.196: bytes=32 time=55ms TTL=53
Reply from 101.37.42.196: bytes=32 time=55ms TTL=53
Reply from 101.37.42.196: bytes=32 time=56ms TTL=53
Reply from 101.37.42.196: bytes=32 time=56ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 57ms, Average = 56ms查看 |
GET PING Trace Dig |
|
| 四川成都电信 |
电信 |
四川 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
69.862ms |
51.862ms |
55.682ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=70ms TTL=51
Reply from 101.37.42.196: bytes=32 time=57ms TTL=51
Reply from 101.37.42.196: bytes=32 time=54ms TTL=51
Reply from 101.37.42.196: bytes=32 time=52ms TTL=51
Reply from 101.37.42.196: bytes=32 time=53ms TTL=51
Reply from 101.37.42.196: bytes=32 time=57ms TTL=51
Reply from 101.37.42.196: bytes=32 time=53ms TTL=51
Reply from 101.37.42.196: bytes=32 time=53ms TTL=51
Reply from 101.37.42.196: bytes=32 time=52ms TTL=51
Reply from 101.37.42.196: bytes=32 time=57ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 70ms, Average = 56ms查看 |
GET PING Trace Dig |
|
| 黑龙江齐齐哈尔市联通 |
联通 |
黑龙江 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
55.982ms |
55.179ms |
55.49ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=56ms TTL=52
Reply from 101.37.42.196: bytes=32 time=55ms TTL=52
Reply from 101.37.42.196: bytes=32 time=56ms TTL=52
Reply from 101.37.42.196: bytes=32 time=55ms TTL=52
Reply from 101.37.42.196: bytes=32 time=55ms TTL=52
Reply from 101.37.42.196: bytes=32 time=55ms TTL=52
Reply from 101.37.42.196: bytes=32 time=55ms TTL=52
Reply from 101.37.42.196: bytes=32 time=56ms TTL=52
Reply from 101.37.42.196: bytes=32 time=55ms TTL=52
Reply from 101.37.42.196: bytes=32 time=55ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 56ms, Average = 55ms查看 |
GET PING Trace Dig |
|
| 广东深圳联通 |
联通 |
广东 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
72.563ms |
48.187ms |
55.244ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=49ms TTL=51
Reply from 101.37.42.196: bytes=32 time=52ms TTL=51
Reply from 101.37.42.196: bytes=32 time=48ms TTL=51
Reply from 101.37.42.196: bytes=32 time=55ms TTL=51
Reply from 101.37.42.196: bytes=32 time=57ms TTL=51
Reply from 101.37.42.196: bytes=32 time=53ms TTL=51
Reply from 101.37.42.196: bytes=32 time=73ms TTL=51
Reply from 101.37.42.196: bytes=32 time=63ms TTL=51
Reply from 101.37.42.196: bytes=32 time=54ms TTL=51
Reply from 101.37.42.196: bytes=32 time=48ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 73ms, Average = 55ms查看 |
GET PING Trace Dig |
|
| 宁夏银川电信 |
电信 |
宁夏 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
8 |
2 |
86.925ms |
41.447ms |
54.567ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=76ms TTL=52
Reply from 101.37.42.196: bytes=32 time=87ms TTL=52
Request timed out.
Request timed out.
Reply from 101.37.42.196: bytes=32 time=45ms TTL=52
Reply from 101.37.42.196: bytes=32 time=41ms TTL=52
Reply from 101.37.42.196: bytes=32 time=46ms TTL=52
Reply from 101.37.42.196: bytes=32 time=46ms TTL=52
Reply from 101.37.42.196: bytes=32 time=44ms TTL=52
Reply from 101.37.42.196: bytes=32 time=51ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 8, Lost = 2 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 87ms, Average = 55ms查看 |
GET PING Trace Dig |
|
| 云南昭通市移动 |
移动 |
云南 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
59.894ms |
49.796ms |
54.148ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=52ms TTL=52
Reply from 101.37.42.196: bytes=32 time=60ms TTL=52
Reply from 101.37.42.196: bytes=32 time=58ms TTL=52
Reply from 101.37.42.196: bytes=32 time=52ms TTL=52
Reply from 101.37.42.196: bytes=32 time=50ms TTL=52
Reply from 101.37.42.196: bytes=32 time=52ms TTL=52
Reply from 101.37.42.196: bytes=32 time=50ms TTL=52
Reply from 101.37.42.196: bytes=32 time=60ms TTL=52
Reply from 101.37.42.196: bytes=32 time=50ms TTL=52
Reply from 101.37.42.196: bytes=32 time=58ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 60ms, Average = 54ms查看 |
GET PING Trace Dig |
|
| 印度尼西亚国外 |
国外 |
印度尼西亚 |
8.218.113.144 |
中国香港阿里云 |
10 |
10 |
0 |
54.439ms |
53.939ms |
54.097ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (8.218.113.144) with 32 bytes of data:
Reply from 8.218.113.144: bytes=32 time=54ms TTL=91
Reply from 8.218.113.144: bytes=32 time=54ms TTL=91
Reply from 8.218.113.144: bytes=32 time=54ms TTL=91
Reply from 8.218.113.144: bytes=32 time=54ms TTL=91
Reply from 8.218.113.144: bytes=32 time=54ms TTL=91
Reply from 8.218.113.144: bytes=32 time=54ms TTL=91
Reply from 8.218.113.144: bytes=32 time=54ms TTL=91
Reply from 8.218.113.144: bytes=32 time=54ms TTL=91
Reply from 8.218.113.144: bytes=32 time=54ms TTL=91
Reply from 8.218.113.144: bytes=32 time=54ms TTL=91
Ping statistics for 8.218.113.144:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 54ms, Maximum = 54ms, Average = 54ms查看 |
GET PING Trace Dig |
|
| 云南昭通市联通 |
联通 |
云南 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
54.44ms |
53.52ms |
53.829ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=54ms TTL=52
Reply from 101.37.42.196: bytes=32 time=54ms TTL=52
Reply from 101.37.42.196: bytes=32 time=54ms TTL=52
Reply from 101.37.42.196: bytes=32 time=54ms TTL=52
Reply from 101.37.42.196: bytes=32 time=54ms TTL=52
Reply from 101.37.42.196: bytes=32 time=54ms TTL=52
Reply from 101.37.42.196: bytes=32 time=54ms TTL=52
Reply from 101.37.42.196: bytes=32 time=54ms TTL=52
Reply from 101.37.42.196: bytes=32 time=54ms TTL=52
Reply from 101.37.42.196: bytes=32 time=54ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 54ms, Maximum = 54ms, Average = 54ms查看 |
GET PING Trace Dig |
|
| 陕西商洛市移动 |
移动 |
陕西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
58.04ms |
51.393ms |
52.627ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=52ms TTL=53
Reply from 101.37.42.196: bytes=32 time=51ms TTL=53
Reply from 101.37.42.196: bytes=32 time=53ms TTL=53
Reply from 101.37.42.196: bytes=32 time=52ms TTL=53
Reply from 101.37.42.196: bytes=32 time=52ms TTL=53
Reply from 101.37.42.196: bytes=32 time=52ms TTL=53
Reply from 101.37.42.196: bytes=32 time=58ms TTL=53
Reply from 101.37.42.196: bytes=32 time=53ms TTL=53
Reply from 101.37.42.196: bytes=32 time=52ms TTL=53
Reply from 101.37.42.196: bytes=32 time=52ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 58ms, Average = 53ms查看 |
GET PING Trace Dig |
|
| 黑龙江哈尔滨市联通 |
联通 |
黑龙江 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
64.537ms |
50.199ms |
52.259ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=51ms TTL=51
Reply from 101.37.42.196: bytes=32 time=51ms TTL=51
Reply from 101.37.42.196: bytes=32 time=50ms TTL=51
Reply from 101.37.42.196: bytes=32 time=65ms TTL=51
Reply from 101.37.42.196: bytes=32 time=51ms TTL=51
Reply from 101.37.42.196: bytes=32 time=50ms TTL=51
Reply from 101.37.42.196: bytes=32 time=51ms TTL=51
Reply from 101.37.42.196: bytes=32 time=53ms TTL=51
Reply from 101.37.42.196: bytes=32 time=51ms TTL=51
Reply from 101.37.42.196: bytes=32 time=50ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 65ms, Average = 52ms查看 |
GET PING Trace Dig |
|
| 黑龙江哈尔滨市电信 |
电信 |
黑龙江 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
52.06ms |
51.521ms |
51.711ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=52ms TTL=53
Reply from 101.37.42.196: bytes=32 time=52ms TTL=53
Reply from 101.37.42.196: bytes=32 time=52ms TTL=53
Reply from 101.37.42.196: bytes=32 time=52ms TTL=53
Reply from 101.37.42.196: bytes=32 time=52ms TTL=53
Reply from 101.37.42.196: bytes=32 time=52ms TTL=53
Reply from 101.37.42.196: bytes=32 time=52ms TTL=53
Reply from 101.37.42.196: bytes=32 time=52ms TTL=53
Reply from 101.37.42.196: bytes=32 time=52ms TTL=53
Reply from 101.37.42.196: bytes=32 time=52ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 52ms, Average = 52ms查看 |
GET PING Trace Dig |
|
| 吉林长春市联通 |
联通 |
吉林 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
59ms |
50.099ms |
51.346ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=51ms TTL=51
Reply from 101.37.42.196: bytes=32 time=50ms TTL=51
Reply from 101.37.42.196: bytes=32 time=59ms TTL=51
Reply from 101.37.42.196: bytes=32 time=50ms TTL=51
Reply from 101.37.42.196: bytes=32 time=51ms TTL=51
Reply from 101.37.42.196: bytes=32 time=50ms TTL=51
Reply from 101.37.42.196: bytes=32 time=51ms TTL=51
Reply from 101.37.42.196: bytes=32 time=50ms TTL=51
Reply from 101.37.42.196: bytes=32 time=50ms TTL=51
Reply from 101.37.42.196: bytes=32 time=50ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 59ms, Average = 51ms查看 |
GET PING Trace Dig |
|
| 四川内江市移动 |
移动 |
四川 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
57.46ms |
47.6ms |
49.753ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=48ms TTL=53
Reply from 101.37.42.196: bytes=32 time=48ms TTL=53
Reply from 101.37.42.196: bytes=32 time=57ms TTL=53
Reply from 101.37.42.196: bytes=32 time=49ms TTL=53
Reply from 101.37.42.196: bytes=32 time=48ms TTL=53
Reply from 101.37.42.196: bytes=32 time=48ms TTL=53
Reply from 101.37.42.196: bytes=32 time=48ms TTL=53
Reply from 101.37.42.196: bytes=32 time=48ms TTL=53
Reply from 101.37.42.196: bytes=32 time=54ms TTL=53
Reply from 101.37.42.196: bytes=32 time=50ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 48ms, Maximum = 57ms, Average = 50ms查看 |
GET PING Trace Dig |
|
| 甘肃庆阳联通 |
联通 |
甘肃 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
52.947ms |
47.172ms |
49.396ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=49ms TTL=52
Reply from 101.37.42.196: bytes=32 time=49ms TTL=52
Reply from 101.37.42.196: bytes=32 time=48ms TTL=52
Reply from 101.37.42.196: bytes=32 time=47ms TTL=52
Reply from 101.37.42.196: bytes=32 time=48ms TTL=52
Reply from 101.37.42.196: bytes=32 time=53ms TTL=52
Reply from 101.37.42.196: bytes=32 time=49ms TTL=52
Reply from 101.37.42.196: bytes=32 time=53ms TTL=52
Reply from 101.37.42.196: bytes=32 time=51ms TTL=52
Reply from 101.37.42.196: bytes=32 time=47ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 53ms, Average = 49ms查看 |
GET PING Trace Dig |
|
| 青海西宁市电信 |
电信 |
青海 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
57.454ms |
45.241ms |
48.876ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=50ms TTL=53
Reply from 101.37.42.196: bytes=32 time=57ms TTL=53
Reply from 101.37.42.196: bytes=32 time=46ms TTL=53
Reply from 101.37.42.196: bytes=32 time=48ms TTL=53
Reply from 101.37.42.196: bytes=32 time=46ms TTL=53
Reply from 101.37.42.196: bytes=32 time=45ms TTL=53
Reply from 101.37.42.196: bytes=32 time=47ms TTL=53
Reply from 101.37.42.196: bytes=32 time=48ms TTL=53
Reply from 101.37.42.196: bytes=32 time=52ms TTL=53
Reply from 101.37.42.196: bytes=32 time=50ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 57ms, Average = 49ms查看 |
GET PING Trace Dig |
|
| 上海上海市联通 |
联通 |
上海 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
9 |
1 |
271.435ms |
12.338ms |
48.591ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=15ms TTL=52
Request timed out.
Reply from 101.37.42.196: bytes=32 time=12ms TTL=52
Reply from 101.37.42.196: bytes=32 time=44ms TTL=52
Reply from 101.37.42.196: bytes=32 time=15ms TTL=52
Reply from 101.37.42.196: bytes=32 time=271ms TTL=52
Reply from 101.37.42.196: bytes=32 time=37ms TTL=52
Reply from 101.37.42.196: bytes=32 time=13ms TTL=52
Reply from 101.37.42.196: bytes=32 time=12ms TTL=52
Reply from 101.37.42.196: bytes=32 time=18ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 9, Lost = 1 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 271ms, Average = 49ms查看 |
GET PING Trace Dig |
|
| 山西临汾市移动 |
移动 |
山西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
52.68ms |
45.42ms |
48.082ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=52ms TTL=54
Reply from 101.37.42.196: bytes=32 time=46ms TTL=54
Reply from 101.37.42.196: bytes=32 time=46ms TTL=54
Reply from 101.37.42.196: bytes=32 time=45ms TTL=54
Reply from 101.37.42.196: bytes=32 time=50ms TTL=54
Reply from 101.37.42.196: bytes=32 time=53ms TTL=54
Reply from 101.37.42.196: bytes=32 time=46ms TTL=54
Reply from 101.37.42.196: bytes=32 time=51ms TTL=54
Reply from 101.37.42.196: bytes=32 time=47ms TTL=54
Reply from 101.37.42.196: bytes=32 time=45ms TTL=54
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 53ms, Average = 48ms查看 |
GET PING Trace Dig |
|
| 四川广安市电信 |
电信 |
四川 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
48.32ms |
47.421ms |
47.861ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=48ms TTL=53
Reply from 101.37.42.196: bytes=32 time=48ms TTL=53
Reply from 101.37.42.196: bytes=32 time=48ms TTL=53
Reply from 101.37.42.196: bytes=32 time=47ms TTL=53
Reply from 101.37.42.196: bytes=32 time=48ms TTL=53
Reply from 101.37.42.196: bytes=32 time=48ms TTL=53
Reply from 101.37.42.196: bytes=32 time=48ms TTL=53
Reply from 101.37.42.196: bytes=32 time=48ms TTL=53
Reply from 101.37.42.196: bytes=32 time=48ms TTL=53
Reply from 101.37.42.196: bytes=32 time=48ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 48ms, Average = 48ms查看 |
GET PING Trace Dig |
|
| 吉林长春电信 |
电信 |
吉林 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
49.388ms |
45.787ms |
47.131ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=46ms TTL=51
Reply from 101.37.42.196: bytes=32 time=49ms TTL=51
Reply from 101.37.42.196: bytes=32 time=46ms TTL=51
Reply from 101.37.42.196: bytes=32 time=49ms TTL=51
Reply from 101.37.42.196: bytes=32 time=47ms TTL=51
Reply from 101.37.42.196: bytes=32 time=46ms TTL=51
Reply from 101.37.42.196: bytes=32 time=49ms TTL=51
Reply from 101.37.42.196: bytes=32 time=46ms TTL=51
Reply from 101.37.42.196: bytes=32 time=46ms TTL=51
Reply from 101.37.42.196: bytes=32 time=47ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 49ms, Average = 47ms查看 |
GET PING Trace Dig |
|
| 安徽宿州市电信 |
电信 |
安徽 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
99.36ms |
20.08ms |
47.018ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=63ms TTL=52
Reply from 101.37.42.196: bytes=32 time=51ms TTL=52
Reply from 101.37.42.196: bytes=32 time=99ms TTL=52
Reply from 101.37.42.196: bytes=32 time=28ms TTL=52
Reply from 101.37.42.196: bytes=32 time=58ms TTL=52
Reply from 101.37.42.196: bytes=32 time=87ms TTL=52
Reply from 101.37.42.196: bytes=32 time=23ms TTL=52
Reply from 101.37.42.196: bytes=32 time=20ms TTL=52
Reply from 101.37.42.196: bytes=32 time=20ms TTL=52
Reply from 101.37.42.196: bytes=32 time=20ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 99ms, Average = 47ms查看 |
GET PING Trace Dig |
|
| 吉林松原市联通 |
联通 |
吉林 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
52.459ms |
44.089ms |
46.973ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=46ms TTL=51
Reply from 101.37.42.196: bytes=32 time=46ms TTL=51
Reply from 101.37.42.196: bytes=32 time=48ms TTL=51
Reply from 101.37.42.196: bytes=32 time=46ms TTL=51
Reply from 101.37.42.196: bytes=32 time=44ms TTL=51
Reply from 101.37.42.196: bytes=32 time=52ms TTL=51
Reply from 101.37.42.196: bytes=32 time=48ms TTL=51
Reply from 101.37.42.196: bytes=32 time=46ms TTL=51
Reply from 101.37.42.196: bytes=32 time=45ms TTL=51
Reply from 101.37.42.196: bytes=32 time=49ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 52ms, Average = 47ms查看 |
GET PING Trace Dig |
|
| 云南丽江市电信 |
电信 |
云南 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
47.3ms |
46.68ms |
46.838ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=47ms TTL=53
Reply from 101.37.42.196: bytes=32 time=47ms TTL=53
Reply from 101.37.42.196: bytes=32 time=47ms TTL=53
Reply from 101.37.42.196: bytes=32 time=47ms TTL=53
Reply from 101.37.42.196: bytes=32 time=47ms TTL=53
Reply from 101.37.42.196: bytes=32 time=47ms TTL=53
Reply from 101.37.42.196: bytes=32 time=47ms TTL=53
Reply from 101.37.42.196: bytes=32 time=47ms TTL=53
Reply from 101.37.42.196: bytes=32 time=47ms TTL=53
Reply from 101.37.42.196: bytes=32 time=47ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 47ms, Maximum = 47ms, Average = 47ms查看 |
GET PING Trace Dig |
|
| 吉林松原市电信 |
电信 |
吉林 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
51.172ms |
41.734ms |
46.558ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=46ms TTL=53
Reply from 101.37.42.196: bytes=32 time=49ms TTL=53
Reply from 101.37.42.196: bytes=32 time=42ms TTL=53
Reply from 101.37.42.196: bytes=32 time=46ms TTL=53
Reply from 101.37.42.196: bytes=32 time=45ms TTL=53
Reply from 101.37.42.196: bytes=32 time=45ms TTL=53
Reply from 101.37.42.196: bytes=32 time=50ms TTL=53
Reply from 101.37.42.196: bytes=32 time=46ms TTL=53
Reply from 101.37.42.196: bytes=32 time=46ms TTL=53
Reply from 101.37.42.196: bytes=32 time=51ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 51ms, Average = 47ms查看 |
GET PING Trace Dig |
|
| 辽宁朝阳市电信 |
电信 |
辽宁 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
46.536ms |
46.274ms |
46.435ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=47ms TTL=52
Reply from 101.37.42.196: bytes=32 time=47ms TTL=52
Reply from 101.37.42.196: bytes=32 time=46ms TTL=52
Reply from 101.37.42.196: bytes=32 time=46ms TTL=52
Reply from 101.37.42.196: bytes=32 time=46ms TTL=52
Reply from 101.37.42.196: bytes=32 time=47ms TTL=52
Reply from 101.37.42.196: bytes=32 time=46ms TTL=52
Reply from 101.37.42.196: bytes=32 time=47ms TTL=52
Reply from 101.37.42.196: bytes=32 time=46ms TTL=52
Reply from 101.37.42.196: bytes=32 time=47ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 47ms, Average = 46ms查看 |
GET PING Trace Dig |
|
| 吉林长春市移动 |
移动 |
吉林 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
46.22ms |
45.26ms |
45.575ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=46ms TTL=53
Reply from 101.37.42.196: bytes=32 time=45ms TTL=53
Reply from 101.37.42.196: bytes=32 time=46ms TTL=53
Reply from 101.37.42.196: bytes=32 time=46ms TTL=53
Reply from 101.37.42.196: bytes=32 time=45ms TTL=53
Reply from 101.37.42.196: bytes=32 time=45ms TTL=53
Reply from 101.37.42.196: bytes=32 time=46ms TTL=53
Reply from 101.37.42.196: bytes=32 time=46ms TTL=53
Reply from 101.37.42.196: bytes=32 time=45ms TTL=53
Reply from 101.37.42.196: bytes=32 time=45ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 46ms, Average = 46ms查看 |
GET PING Trace Dig |
|
| 四川成都市联通 |
联通 |
四川 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
45.8ms |
45.3ms |
45.472ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=46ms TTL=52
Reply from 101.37.42.196: bytes=32 time=45ms TTL=52
Reply from 101.37.42.196: bytes=32 time=45ms TTL=52
Reply from 101.37.42.196: bytes=32 time=45ms TTL=52
Reply from 101.37.42.196: bytes=32 time=46ms TTL=52
Reply from 101.37.42.196: bytes=32 time=45ms TTL=52
Reply from 101.37.42.196: bytes=32 time=45ms TTL=52
Reply from 101.37.42.196: bytes=32 time=45ms TTL=52
Reply from 101.37.42.196: bytes=32 time=46ms TTL=52
Reply from 101.37.42.196: bytes=32 time=45ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 46ms, Average = 45ms查看 |
GET PING Trace Dig |
|
| 辽宁葫芦岛市电信 |
电信 |
辽宁 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
49.497ms |
41.778ms |
45.206ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=42ms TTL=51
Reply from 101.37.42.196: bytes=32 time=42ms TTL=51
Reply from 101.37.42.196: bytes=32 time=46ms TTL=51
Reply from 101.37.42.196: bytes=32 time=49ms TTL=51
Reply from 101.37.42.196: bytes=32 time=46ms TTL=51
Reply from 101.37.42.196: bytes=32 time=44ms TTL=51
Reply from 101.37.42.196: bytes=32 time=44ms TTL=51
Reply from 101.37.42.196: bytes=32 time=49ms TTL=51
Reply from 101.37.42.196: bytes=32 time=47ms TTL=51
Reply from 101.37.42.196: bytes=32 time=44ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 49ms, Average = 45ms查看 |
GET PING Trace Dig |
|
| 陕西渭南市移动 |
移动 |
陕西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
47.013ms |
44.26ms |
44.841ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=45ms TTL=54
Reply from 101.37.42.196: bytes=32 time=44ms TTL=54
Reply from 101.37.42.196: bytes=32 time=44ms TTL=54
Reply from 101.37.42.196: bytes=32 time=47ms TTL=54
Reply from 101.37.42.196: bytes=32 time=45ms TTL=54
Reply from 101.37.42.196: bytes=32 time=44ms TTL=54
Reply from 101.37.42.196: bytes=32 time=45ms TTL=54
Reply from 101.37.42.196: bytes=32 time=45ms TTL=54
Reply from 101.37.42.196: bytes=32 time=45ms TTL=54
Reply from 101.37.42.196: bytes=32 time=45ms TTL=54
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 47ms, Average = 45ms查看 |
GET PING Trace Dig |
|
| 重庆重庆市移动 |
移动 |
重庆 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
47.839ms |
44.18ms |
44.658ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=45ms TTL=51
Reply from 101.37.42.196: bytes=32 time=44ms TTL=51
Reply from 101.37.42.196: bytes=32 time=44ms TTL=51
Reply from 101.37.42.196: bytes=32 time=44ms TTL=51
Reply from 101.37.42.196: bytes=32 time=44ms TTL=51
Reply from 101.37.42.196: bytes=32 time=44ms TTL=51
Reply from 101.37.42.196: bytes=32 time=44ms TTL=51
Reply from 101.37.42.196: bytes=32 time=44ms TTL=51
Reply from 101.37.42.196: bytes=32 time=44ms TTL=51
Reply from 101.37.42.196: bytes=32 time=48ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 48ms, Average = 45ms查看 |
GET PING Trace Dig |
|
| 贵州铜仁市电信 |
电信 |
贵州 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
44.638ms |
43.778ms |
44.3ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=44ms TTL=52
Reply from 101.37.42.196: bytes=32 time=44ms TTL=52
Reply from 101.37.42.196: bytes=32 time=45ms TTL=52
Reply from 101.37.42.196: bytes=32 time=44ms TTL=52
Reply from 101.37.42.196: bytes=32 time=44ms TTL=52
Reply from 101.37.42.196: bytes=32 time=45ms TTL=52
Reply from 101.37.42.196: bytes=32 time=44ms TTL=52
Reply from 101.37.42.196: bytes=32 time=45ms TTL=52
Reply from 101.37.42.196: bytes=32 time=44ms TTL=52
Reply from 101.37.42.196: bytes=32 time=44ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 45ms, Average = 44ms查看 |
GET PING Trace Dig |
|
| 甘肃天水市电信 |
电信 |
甘肃 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
56.452ms |
41.432ms |
43.818ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=42ms TTL=51
Reply from 101.37.42.196: bytes=32 time=42ms TTL=51
Reply from 101.37.42.196: bytes=32 time=43ms TTL=51
Reply from 101.37.42.196: bytes=32 time=56ms TTL=51
Reply from 101.37.42.196: bytes=32 time=43ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=44ms TTL=51
Reply from 101.37.42.196: bytes=32 time=43ms TTL=51
Reply from 101.37.42.196: bytes=32 time=42ms TTL=51
Reply from 101.37.42.196: bytes=32 time=42ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 56ms, Average = 44ms查看 |
GET PING Trace Dig |
|
| 辽宁沈阳市联通 |
联通 |
辽宁 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
45.004ms |
42.788ms |
43.658ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=45ms TTL=52
Reply from 101.37.42.196: bytes=32 time=43ms TTL=52
Reply from 101.37.42.196: bytes=32 time=43ms TTL=52
Reply from 101.37.42.196: bytes=32 time=45ms TTL=52
Reply from 101.37.42.196: bytes=32 time=43ms TTL=52
Reply from 101.37.42.196: bytes=32 time=43ms TTL=52
Reply from 101.37.42.196: bytes=32 time=43ms TTL=52
Reply from 101.37.42.196: bytes=32 time=43ms TTL=52
Reply from 101.37.42.196: bytes=32 time=45ms TTL=52
Reply from 101.37.42.196: bytes=32 time=43ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 45ms, Average = 44ms查看 |
GET PING Trace Dig |
|
| 贵州六盘水市联通 |
联通 |
贵州 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
43.748ms |
42.723ms |
43.518ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=43ms TTL=52
Reply from 101.37.42.196: bytes=32 time=44ms TTL=52
Reply from 101.37.42.196: bytes=32 time=44ms TTL=52
Reply from 101.37.42.196: bytes=32 time=43ms TTL=52
Reply from 101.37.42.196: bytes=32 time=44ms TTL=52
Reply from 101.37.42.196: bytes=32 time=44ms TTL=52
Reply from 101.37.42.196: bytes=32 time=44ms TTL=52
Reply from 101.37.42.196: bytes=32 time=44ms TTL=52
Reply from 101.37.42.196: bytes=32 time=44ms TTL=52
Reply from 101.37.42.196: bytes=32 time=43ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 44ms, Average = 44ms查看 |
GET PING Trace Dig |
|
| 广西南宁市电信 |
电信 |
广西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
53.366ms |
37.66ms |
42.956ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=47ms TTL=52
Reply from 101.37.42.196: bytes=32 time=42ms TTL=52
Reply from 101.37.42.196: bytes=32 time=53ms TTL=52
Reply from 101.37.42.196: bytes=32 time=39ms TTL=52
Reply from 101.37.42.196: bytes=32 time=42ms TTL=52
Reply from 101.37.42.196: bytes=32 time=38ms TTL=52
Reply from 101.37.42.196: bytes=32 time=50ms TTL=52
Reply from 101.37.42.196: bytes=32 time=38ms TTL=52
Reply from 101.37.42.196: bytes=32 time=38ms TTL=52
Reply from 101.37.42.196: bytes=32 time=42ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 53ms, Average = 43ms查看 |
GET PING Trace Dig |
|
| 湖南岳阳市移动 |
移动 |
湖南 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
121.361ms |
30.445ms |
42.939ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=37ms TTL=51
Reply from 101.37.42.196: bytes=32 time=31ms TTL=51
Reply from 101.37.42.196: bytes=32 time=30ms TTL=51
Reply from 101.37.42.196: bytes=32 time=121ms TTL=51
Reply from 101.37.42.196: bytes=32 time=49ms TTL=51
Reply from 101.37.42.196: bytes=32 time=37ms TTL=51
Reply from 101.37.42.196: bytes=32 time=31ms TTL=51
Reply from 101.37.42.196: bytes=32 time=31ms TTL=51
Reply from 101.37.42.196: bytes=32 time=31ms TTL=51
Reply from 101.37.42.196: bytes=32 time=31ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 121ms, Average = 43ms查看 |
GET PING Trace Dig |
|
| 广西贵港市移动 |
移动 |
广西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
44.462ms |
41.182ms |
42.347ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=42ms TTL=53
Reply from 101.37.42.196: bytes=32 time=42ms TTL=53
Reply from 101.37.42.196: bytes=32 time=42ms TTL=53
Reply from 101.37.42.196: bytes=32 time=42ms TTL=53
Reply from 101.37.42.196: bytes=32 time=44ms TTL=53
Reply from 101.37.42.196: bytes=32 time=41ms TTL=53
Reply from 101.37.42.196: bytes=32 time=43ms TTL=53
Reply from 101.37.42.196: bytes=32 time=42ms TTL=53
Reply from 101.37.42.196: bytes=32 time=41ms TTL=53
Reply from 101.37.42.196: bytes=32 time=43ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 44ms, Average = 42ms查看 |
GET PING Trace Dig |
|
| 贵州安顺市移动 |
移动 |
贵州 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
48.762ms |
39.146ms |
42.272ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=47ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=43ms TTL=51
Reply from 101.37.42.196: bytes=32 time=39ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=49ms TTL=51
Reply from 101.37.42.196: bytes=32 time=40ms TTL=51
Reply from 101.37.42.196: bytes=32 time=43ms TTL=51
Reply from 101.37.42.196: bytes=32 time=39ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 49ms, Average = 42ms查看 |
GET PING Trace Dig |
|
| 辽宁锦州市移动 |
移动 |
辽宁 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
42.3ms |
41.56ms |
42.044ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=42ms TTL=52
Reply from 101.37.42.196: bytes=32 time=42ms TTL=52
Reply from 101.37.42.196: bytes=32 time=42ms TTL=52
Reply from 101.37.42.196: bytes=32 time=42ms TTL=52
Reply from 101.37.42.196: bytes=32 time=42ms TTL=52
Reply from 101.37.42.196: bytes=32 time=42ms TTL=52
Reply from 101.37.42.196: bytes=32 time=42ms TTL=52
Reply from 101.37.42.196: bytes=32 time=42ms TTL=52
Reply from 101.37.42.196: bytes=32 time=42ms TTL=52
Reply from 101.37.42.196: bytes=32 time=42ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 42ms, Average = 42ms查看 |
GET PING Trace Dig |
|
| 内蒙古鄂尔多斯市电信 |
电信 |
内蒙古 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
41.98ms |
41.7ms |
41.833ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=42ms TTL=52
Reply from 101.37.42.196: bytes=32 time=42ms TTL=52
Reply from 101.37.42.196: bytes=32 time=42ms TTL=52
Reply from 101.37.42.196: bytes=32 time=42ms TTL=52
Reply from 101.37.42.196: bytes=32 time=42ms TTL=52
Reply from 101.37.42.196: bytes=32 time=42ms TTL=52
Reply from 101.37.42.196: bytes=32 time=42ms TTL=52
Reply from 101.37.42.196: bytes=32 time=42ms TTL=52
Reply from 101.37.42.196: bytes=32 time=42ms TTL=52
Reply from 101.37.42.196: bytes=32 time=42ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 42ms, Average = 42ms查看 |
GET PING Trace Dig |
|
| 天津天津市移动 |
移动 |
天津 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
48.586ms |
39.92ms |
41.636ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=49ms TTL=51
Reply from 101.37.42.196: bytes=32 time=40ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=40ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=42ms TTL=51
Reply from 101.37.42.196: bytes=32 time=40ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 49ms, Average = 42ms查看 |
GET PING Trace Dig |
|
| 山西晋城市移动 |
移动 |
山西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
42.98ms |
40.761ms |
41.496ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=43ms TTL=52
Reply from 101.37.42.196: bytes=32 time=41ms TTL=52
Reply from 101.37.42.196: bytes=32 time=41ms TTL=52
Reply from 101.37.42.196: bytes=32 time=41ms TTL=52
Reply from 101.37.42.196: bytes=32 time=41ms TTL=52
Reply from 101.37.42.196: bytes=32 time=41ms TTL=52
Reply from 101.37.42.196: bytes=32 time=41ms TTL=52
Reply from 101.37.42.196: bytes=32 time=41ms TTL=52
Reply from 101.37.42.196: bytes=32 time=43ms TTL=52
Reply from 101.37.42.196: bytes=32 time=41ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 43ms, Average = 41ms查看 |
GET PING Trace Dig |
|
| 贵州遵义市电信 |
电信 |
贵州 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
44.14ms |
38.701ms |
41.198ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=44ms TTL=51
Reply from 101.37.42.196: bytes=32 time=43ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=39ms TTL=51
Reply from 101.37.42.196: bytes=32 time=42ms TTL=51
Reply from 101.37.42.196: bytes=32 time=40ms TTL=51
Reply from 101.37.42.196: bytes=32 time=40ms TTL=51
Reply from 101.37.42.196: bytes=32 time=43ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Ping statistics for 101.37.42.196:
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 |
|
| 海南文昌市移动 |
移动 |
海南 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
41.438ms |
40.598ms |
41.181ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 41ms, Average = 41ms查看 |
GET PING Trace Dig |
|
| 山西运城市联通 |
联通 |
山西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
43.953ms |
39.722ms |
41.019ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Reply from 101.37.42.196: bytes=32 time=44ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Reply from 101.37.42.196: bytes=32 time=41ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Reply from 101.37.42.196: bytes=32 time=41ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Reply from 101.37.42.196: bytes=32 time=42ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Reply from 101.37.42.196: bytes=32 time=42ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 44ms, Average = 41ms查看 |
GET PING Trace Dig |
|
| 广东茂名市移动 |
移动 |
广东 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
43.037ms |
38.546ms |
40.952ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=42ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Reply from 101.37.42.196: bytes=32 time=42ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Reply from 101.37.42.196: bytes=32 time=43ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Reply from 101.37.42.196: bytes=32 time=42ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Reply from 101.37.42.196: bytes=32 time=42ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 43ms, Average = 41ms查看 |
GET PING Trace Dig |
|
| 云南昆明市移动 |
移动 |
云南 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
42ms |
39.639ms |
40.835ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=42ms TTL=51
Reply from 101.37.42.196: bytes=32 time=40ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=40ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=40ms TTL=51
Reply from 101.37.42.196: bytes=32 time=42ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=40ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 42ms, Average = 41ms查看 |
GET PING Trace Dig |
|
| 河北衡水市联通 |
联通 |
河北 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
44.848ms |
39.182ms |
40.56ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=41ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=45ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Reply from 101.37.42.196: bytes=32 time=44ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 45ms, Average = 41ms查看 |
GET PING Trace Dig |
|
| 海南琼海市电信 |
电信 |
海南 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
43.433ms |
38.466ms |
40.41ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=39ms TTL=52
Reply from 101.37.42.196: bytes=32 time=39ms TTL=52
Reply from 101.37.42.196: bytes=32 time=43ms TTL=52
Reply from 101.37.42.196: bytes=32 time=38ms TTL=52
Reply from 101.37.42.196: bytes=32 time=43ms TTL=52
Reply from 101.37.42.196: bytes=32 time=39ms TTL=52
Reply from 101.37.42.196: bytes=32 time=43ms TTL=52
Reply from 101.37.42.196: bytes=32 time=39ms TTL=52
Reply from 101.37.42.196: bytes=32 time=43ms TTL=52
Reply from 101.37.42.196: bytes=32 time=39ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 43ms, Average = 40ms查看 |
GET PING Trace Dig |
|
| 宁夏银川移动 |
移动 |
宁夏 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
9 |
1 |
44.961ms |
38.26ms |
40.228ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=40ms TTL=51
Reply from 101.37.42.196: bytes=32 time=45ms TTL=51
Reply from 101.37.42.196: bytes=32 time=39ms TTL=51
Reply from 101.37.42.196: bytes=32 time=38ms TTL=51
Reply from 101.37.42.196: bytes=32 time=39ms TTL=51
Reply from 101.37.42.196: bytes=32 time=40ms TTL=51
Reply from 101.37.42.196: bytes=32 time=41ms TTL=51
Reply from 101.37.42.196: bytes=32 time=43ms TTL=51
Request timed out.
Reply from 101.37.42.196: bytes=32 time=38ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 9, Lost = 1 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 45ms, Average = 40ms查看 |
GET PING Trace Dig |
|
| 台湾台湾 |
台湾 |
台湾 |
8.218.113.144 |
中国香港阿里云 |
10 |
10 |
0 |
44.801ms |
37.3ms |
40.195ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (8.218.113.144) with 32 bytes of data:
Reply from 8.218.113.144: bytes=32 time=45ms TTL=90
Reply from 8.218.113.144: bytes=32 time=39ms TTL=90
Reply from 8.218.113.144: bytes=32 time=41ms TTL=90
Reply from 8.218.113.144: bytes=32 time=37ms TTL=90
Reply from 8.218.113.144: bytes=32 time=40ms TTL=90
Reply from 8.218.113.144: bytes=32 time=39ms TTL=90
Reply from 8.218.113.144: bytes=32 time=40ms TTL=90
Reply from 8.218.113.144: bytes=32 time=39ms TTL=90
Reply from 8.218.113.144: bytes=32 time=44ms TTL=90
Reply from 8.218.113.144: bytes=32 time=38ms TTL=90
Ping statistics for 8.218.113.144:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 45ms, Average = 40ms查看 |
GET PING Trace Dig |
|
| 河北邯郸市移动 |
移动 |
河北 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
43.402ms |
39.52ms |
40.151ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=40ms TTL=51
Reply from 101.37.42.196: bytes=32 time=40ms TTL=51
Reply from 101.37.42.196: bytes=32 time=40ms TTL=51
Reply from 101.37.42.196: bytes=32 time=40ms TTL=51
Reply from 101.37.42.196: bytes=32 time=40ms TTL=51
Reply from 101.37.42.196: bytes=32 time=40ms TTL=51
Reply from 101.37.42.196: bytes=32 time=43ms TTL=51
Reply from 101.37.42.196: bytes=32 time=40ms TTL=51
Reply from 101.37.42.196: bytes=32 time=40ms TTL=51
Reply from 101.37.42.196: bytes=32 time=40ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 43ms, Average = 40ms查看 |
GET PING Trace Dig |
|
| 宁夏银川市移动 |
移动 |
宁夏 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
43.54ms |
38.54ms |
40.112ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Reply from 101.37.42.196: bytes=32 time=41ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Reply from 101.37.42.196: bytes=32 time=44ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 44ms, Average = 40ms查看 |
GET PING Trace Dig |
|
| 四川眉山市联通 |
联通 |
四川 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
41.18ms |
38.94ms |
39.936ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Reply from 101.37.42.196: bytes=32 time=41ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 41ms, Average = 40ms查看 |
GET PING Trace Dig |
|
| 内蒙古包头市电信 |
电信 |
内蒙古 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
40.193ms |
39.712ms |
39.833ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=40ms TTL=52
Reply from 101.37.42.196: bytes=32 time=40ms TTL=52
Reply from 101.37.42.196: bytes=32 time=40ms TTL=52
Reply from 101.37.42.196: bytes=32 time=40ms TTL=52
Reply from 101.37.42.196: bytes=32 time=40ms TTL=52
Reply from 101.37.42.196: bytes=32 time=40ms TTL=52
Reply from 101.37.42.196: bytes=32 time=40ms TTL=52
Reply from 101.37.42.196: bytes=32 time=40ms TTL=52
Reply from 101.37.42.196: bytes=32 time=40ms TTL=52
Reply from 101.37.42.196: bytes=32 time=40ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 40ms, Average = 40ms查看 |
GET PING Trace Dig |
|
| 陕西西安市联通 |
联通 |
陕西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
40.405ms |
39.485ms |
39.726ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=40ms TTL=50
Reply from 101.37.42.196: bytes=32 time=40ms TTL=50
Reply from 101.37.42.196: bytes=32 time=40ms TTL=50
Reply from 101.37.42.196: bytes=32 time=40ms TTL=50
Reply from 101.37.42.196: bytes=32 time=40ms TTL=50
Reply from 101.37.42.196: bytes=32 time=40ms TTL=50
Reply from 101.37.42.196: bytes=32 time=40ms TTL=50
Reply from 101.37.42.196: bytes=32 time=39ms TTL=50
Reply from 101.37.42.196: bytes=32 time=40ms TTL=50
Reply from 101.37.42.196: bytes=32 time=40ms TTL=50
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 40ms, Average = 40ms查看 |
GET PING Trace Dig |
|
| 吉林通化市联通 |
联通 |
吉林 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
42.98ms |
37.681ms |
39.486ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=41ms TTL=53
Reply from 101.37.42.196: bytes=32 time=43ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Reply from 101.37.42.196: bytes=32 time=42ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=38ms TTL=53
Reply from 101.37.42.196: bytes=32 time=38ms TTL=53
Reply from 101.37.42.196: bytes=32 time=38ms TTL=53
Reply from 101.37.42.196: bytes=32 time=38ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 43ms, Average = 39ms查看 |
GET PING Trace Dig |
|
| 四川眉山市移动 |
移动 |
四川 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
39.361ms |
38.74ms |
39.041ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 39ms, Average = 39ms查看 |
GET PING Trace Dig |
|
| 贵州铜仁市移动 |
移动 |
贵州 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
39.42ms |
38.68ms |
39.006ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=39ms TTL=52
Reply from 101.37.42.196: bytes=32 time=39ms TTL=52
Reply from 101.37.42.196: bytes=32 time=39ms TTL=52
Reply from 101.37.42.196: bytes=32 time=39ms TTL=52
Reply from 101.37.42.196: bytes=32 time=39ms TTL=52
Reply from 101.37.42.196: bytes=32 time=39ms TTL=52
Reply from 101.37.42.196: bytes=32 time=39ms TTL=52
Reply from 101.37.42.196: bytes=32 time=39ms TTL=52
Reply from 101.37.42.196: bytes=32 time=39ms TTL=52
Reply from 101.37.42.196: bytes=32 time=39ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 39ms, Average = 39ms查看 |
GET PING Trace Dig |
|
| 广西百色电信 |
电信 |
广西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
41.14ms |
38.62ms |
38.988ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=41ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 41ms, Average = 39ms查看 |
GET PING Trace Dig |
|
| 河南三门峡市移动 |
移动 |
河南 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
43.397ms |
36.891ms |
38.928ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=37ms TTL=50
Reply from 101.37.42.196: bytes=32 time=38ms TTL=50
Reply from 101.37.42.196: bytes=32 time=37ms TTL=50
Reply from 101.37.42.196: bytes=32 time=39ms TTL=50
Reply from 101.37.42.196: bytes=32 time=39ms TTL=50
Reply from 101.37.42.196: bytes=32 time=40ms TTL=50
Reply from 101.37.42.196: bytes=32 time=40ms TTL=50
Reply from 101.37.42.196: bytes=32 time=43ms TTL=50
Reply from 101.37.42.196: bytes=32 time=38ms TTL=50
Reply from 101.37.42.196: bytes=32 time=38ms TTL=50
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 43ms, Average = 39ms查看 |
GET PING Trace Dig |
|
| 山东临沂市电信 |
电信 |
山东 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
69.495ms |
30.583ms |
38.823ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=37ms TTL=53
Reply from 101.37.42.196: bytes=32 time=69ms TTL=53
Reply from 101.37.42.196: bytes=32 time=32ms TTL=53
Reply from 101.37.42.196: bytes=32 time=33ms TTL=53
Reply from 101.37.42.196: bytes=32 time=48ms TTL=53
Reply from 101.37.42.196: bytes=32 time=37ms TTL=53
Reply from 101.37.42.196: bytes=32 time=31ms TTL=53
Reply from 101.37.42.196: bytes=32 time=36ms TTL=53
Reply from 101.37.42.196: bytes=32 time=32ms TTL=53
Reply from 101.37.42.196: bytes=32 time=34ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 69ms, Average = 39ms查看 |
GET PING Trace Dig |
|
| 河北邢台市移动 |
移动 |
河北 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
78.553ms |
32.776ms |
38.673ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=34ms TTL=53
Reply from 101.37.42.196: bytes=32 time=33ms TTL=53
Reply from 101.37.42.196: bytes=32 time=34ms TTL=53
Reply from 101.37.42.196: bytes=32 time=35ms TTL=53
Reply from 101.37.42.196: bytes=32 time=35ms TTL=53
Reply from 101.37.42.196: bytes=32 time=35ms TTL=53
Reply from 101.37.42.196: bytes=32 time=33ms TTL=53
Reply from 101.37.42.196: bytes=32 time=37ms TTL=53
Reply from 101.37.42.196: bytes=32 time=79ms TTL=53
Reply from 101.37.42.196: bytes=32 time=33ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 79ms, Average = 39ms查看 |
GET PING Trace Dig |
|
| 北京北京市移动 |
移动 |
北京 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
45.391ms |
36.174ms |
38.575ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=45ms TTL=52
Reply from 101.37.42.196: bytes=32 time=39ms TTL=52
Reply from 101.37.42.196: bytes=32 time=37ms TTL=52
Reply from 101.37.42.196: bytes=32 time=38ms TTL=52
Reply from 101.37.42.196: bytes=32 time=36ms TTL=52
Reply from 101.37.42.196: bytes=32 time=36ms TTL=52
Reply from 101.37.42.196: bytes=32 time=36ms TTL=52
Reply from 101.37.42.196: bytes=32 time=45ms TTL=52
Reply from 101.37.42.196: bytes=32 time=36ms TTL=52
Reply from 101.37.42.196: bytes=32 time=37ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 45ms, Average = 39ms查看 |
GET PING Trace Dig |
|
| 重庆重庆市联通 |
联通 |
重庆 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
39.5ms |
38ms |
38.541ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=39ms TTL=52
Reply from 101.37.42.196: bytes=32 time=40ms TTL=52
Reply from 101.37.42.196: bytes=32 time=39ms TTL=52
Reply from 101.37.42.196: bytes=32 time=38ms TTL=52
Reply from 101.37.42.196: bytes=32 time=38ms TTL=52
Reply from 101.37.42.196: bytes=32 time=38ms TTL=52
Reply from 101.37.42.196: bytes=32 time=38ms TTL=52
Reply from 101.37.42.196: bytes=32 time=39ms TTL=52
Reply from 101.37.42.196: bytes=32 time=39ms TTL=52
Reply from 101.37.42.196: bytes=32 time=38ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 38ms, Maximum = 40ms, Average = 39ms查看 |
GET PING Trace Dig |
|
| 广西梧州市联通 |
联通 |
广西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
41.58ms |
35.96ms |
37.89ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=42ms TTL=53
Reply from 101.37.42.196: bytes=32 time=36ms TTL=53
Reply from 101.37.42.196: bytes=32 time=36ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=37ms TTL=53
Reply from 101.37.42.196: bytes=32 time=36ms TTL=53
Reply from 101.37.42.196: bytes=32 time=38ms TTL=53
Reply from 101.37.42.196: bytes=32 time=38ms TTL=53
Reply from 101.37.42.196: bytes=32 time=36ms TTL=53
Reply from 101.37.42.196: bytes=32 time=40ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 42ms, Average = 38ms查看 |
GET PING Trace Dig |
|
| 河南许昌市联通 |
联通 |
河南 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
38.92ms |
36.58ms |
37.701ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=37ms TTL=53
Reply from 101.37.42.196: bytes=32 time=37ms TTL=53
Reply from 101.37.42.196: bytes=32 time=38ms TTL=53
Reply from 101.37.42.196: bytes=32 time=38ms TTL=53
Reply from 101.37.42.196: bytes=32 time=37ms TTL=53
Reply from 101.37.42.196: bytes=32 time=37ms TTL=53
Reply from 101.37.42.196: bytes=32 time=38ms TTL=53
Reply from 101.37.42.196: bytes=32 time=39ms TTL=53
Reply from 101.37.42.196: bytes=32 time=37ms TTL=53
Reply from 101.37.42.196: bytes=32 time=38ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 39ms, Average = 38ms查看 |
GET PING Trace Dig |
|
| 山西忻州市联通 |
联通 |
山西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
37.933ms |
36.504ms |
37.305ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=38ms TTL=53
Reply from 101.37.42.196: bytes=32 time=37ms TTL=53
Reply from 101.37.42.196: bytes=32 time=37ms TTL=53
Reply from 101.37.42.196: bytes=32 time=38ms TTL=53
Reply from 101.37.42.196: bytes=32 time=37ms TTL=53
Reply from 101.37.42.196: bytes=32 time=37ms TTL=53
Reply from 101.37.42.196: bytes=32 time=37ms TTL=53
Reply from 101.37.42.196: bytes=32 time=37ms TTL=53
Reply from 101.37.42.196: bytes=32 time=38ms TTL=53
Reply from 101.37.42.196: bytes=32 time=37ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 38ms, Average = 37ms查看 |
GET PING Trace Dig |
|
| 河南南阳移动 |
移动 |
河南 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
52.106ms |
33.013ms |
35.976ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=34ms TTL=52
Reply from 101.37.42.196: bytes=32 time=34ms TTL=52
Reply from 101.37.42.196: bytes=32 time=34ms TTL=52
Reply from 101.37.42.196: bytes=32 time=34ms TTL=52
Reply from 101.37.42.196: bytes=32 time=34ms TTL=52
Reply from 101.37.42.196: bytes=32 time=52ms TTL=52
Reply from 101.37.42.196: bytes=32 time=34ms TTL=52
Reply from 101.37.42.196: bytes=32 time=34ms TTL=52
Reply from 101.37.42.196: bytes=32 time=33ms TTL=52
Reply from 101.37.42.196: bytes=32 time=37ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 52ms, Average = 36ms查看 |
GET PING Trace Dig |
|
| 贵州遵义市联通 |
联通 |
贵州 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
36.02ms |
35.64ms |
35.759ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=36ms TTL=53
Reply from 101.37.42.196: bytes=32 time=36ms TTL=53
Reply from 101.37.42.196: bytes=32 time=36ms TTL=53
Reply from 101.37.42.196: bytes=32 time=36ms TTL=53
Reply from 101.37.42.196: bytes=32 time=36ms TTL=53
Reply from 101.37.42.196: bytes=32 time=36ms TTL=53
Reply from 101.37.42.196: bytes=32 time=36ms TTL=53
Reply from 101.37.42.196: bytes=32 time=36ms TTL=53
Reply from 101.37.42.196: bytes=32 time=36ms TTL=53
Reply from 101.37.42.196: bytes=32 time=36ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 36ms, Average = 36ms查看 |
GET PING Trace Dig |
|
| 重庆重庆市联通 |
联通 |
重庆 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
35.879ms |
34.78ms |
35.519ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=35ms TTL=52
Reply from 101.37.42.196: bytes=32 time=36ms TTL=52
Reply from 101.37.42.196: bytes=32 time=36ms TTL=52
Reply from 101.37.42.196: bytes=32 time=36ms TTL=52
Reply from 101.37.42.196: bytes=32 time=36ms TTL=52
Reply from 101.37.42.196: bytes=32 time=36ms TTL=52
Reply from 101.37.42.196: bytes=32 time=35ms TTL=52
Reply from 101.37.42.196: bytes=32 time=36ms TTL=52
Reply from 101.37.42.196: bytes=32 time=36ms TTL=52
Reply from 101.37.42.196: bytes=32 time=35ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 36ms, Average = 36ms查看 |
GET PING Trace Dig |
|
| 山东菏泽市移动 |
移动 |
山东 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
35.377ms |
34.62ms |
34.885ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=35ms TTL=52
Reply from 101.37.42.196: bytes=32 time=35ms TTL=52
Reply from 101.37.42.196: bytes=32 time=35ms TTL=52
Reply from 101.37.42.196: bytes=32 time=35ms TTL=52
Reply from 101.37.42.196: bytes=32 time=35ms TTL=52
Reply from 101.37.42.196: bytes=32 time=35ms TTL=52
Reply from 101.37.42.196: bytes=32 time=35ms TTL=52
Reply from 101.37.42.196: bytes=32 time=35ms TTL=52
Reply from 101.37.42.196: bytes=32 time=35ms TTL=52
Reply from 101.37.42.196: bytes=32 time=35ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 35ms, Average = 35ms查看 |
GET PING Trace Dig |
|
| 山西朔州市电信 |
电信 |
山西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
35.121ms |
34.151ms |
34.558ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=35ms TTL=52
Reply from 101.37.42.196: bytes=32 time=34ms TTL=52
Reply from 101.37.42.196: bytes=32 time=34ms TTL=52
Reply from 101.37.42.196: bytes=32 time=34ms TTL=52
Reply from 101.37.42.196: bytes=32 time=35ms TTL=52
Reply from 101.37.42.196: bytes=32 time=35ms TTL=52
Reply from 101.37.42.196: bytes=32 time=35ms TTL=52
Reply from 101.37.42.196: bytes=32 time=35ms TTL=52
Reply from 101.37.42.196: bytes=32 time=34ms TTL=52
Reply from 101.37.42.196: bytes=32 time=34ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 35ms, Average = 35ms查看 |
GET PING Trace Dig |
|
| 广西玉林市联通 |
联通 |
广西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
37.452ms |
32.726ms |
34.405ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=35ms TTL=53
Reply from 101.37.42.196: bytes=32 time=34ms TTL=53
Reply from 101.37.42.196: bytes=32 time=37ms TTL=53
Reply from 101.37.42.196: bytes=32 time=34ms TTL=53
Reply from 101.37.42.196: bytes=32 time=35ms TTL=53
Reply from 101.37.42.196: bytes=32 time=34ms TTL=53
Reply from 101.37.42.196: bytes=32 time=34ms TTL=53
Reply from 101.37.42.196: bytes=32 time=33ms TTL=53
Reply from 101.37.42.196: bytes=32 time=34ms TTL=53
Reply from 101.37.42.196: bytes=32 time=33ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 37ms, Average = 34ms查看 |
GET PING Trace Dig |
|
| 重庆重庆市电信 |
电信 |
重庆 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
36.461ms |
31.94ms |
33.965ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=34ms TTL=53
Reply from 101.37.42.196: bytes=32 time=34ms TTL=53
Reply from 101.37.42.196: bytes=32 time=34ms TTL=53
Reply from 101.37.42.196: bytes=32 time=34ms TTL=53
Reply from 101.37.42.196: bytes=32 time=34ms TTL=53
Reply from 101.37.42.196: bytes=32 time=32ms TTL=53
Reply from 101.37.42.196: bytes=32 time=36ms TTL=53
Reply from 101.37.42.196: bytes=32 time=35ms TTL=53
Reply from 101.37.42.196: bytes=32 time=34ms TTL=53
Reply from 101.37.42.196: bytes=32 time=34ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 36ms, Average = 34ms查看 |
GET PING Trace Dig |
|
| 山东临沂市移动 |
移动 |
山东 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
35.132ms |
33.597ms |
33.932ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=34ms TTL=48
Reply from 101.37.42.196: bytes=32 time=34ms TTL=48
Reply from 101.37.42.196: bytes=32 time=34ms TTL=48
Reply from 101.37.42.196: bytes=32 time=34ms TTL=48
Reply from 101.37.42.196: bytes=32 time=35ms TTL=48
Reply from 101.37.42.196: bytes=32 time=34ms TTL=48
Reply from 101.37.42.196: bytes=32 time=34ms TTL=48
Reply from 101.37.42.196: bytes=32 time=34ms TTL=48
Reply from 101.37.42.196: bytes=32 time=34ms TTL=48
Reply from 101.37.42.196: bytes=32 time=34ms TTL=48
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 35ms, Average = 34ms查看 |
GET PING Trace Dig |
|
| 陕西安康市电信 |
电信 |
陕西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
35.312ms |
33.435ms |
33.846ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=34ms TTL=53
Reply from 101.37.42.196: bytes=32 time=35ms TTL=53
Reply from 101.37.42.196: bytes=32 time=34ms TTL=53
Reply from 101.37.42.196: bytes=32 time=33ms TTL=53
Reply from 101.37.42.196: bytes=32 time=33ms TTL=53
Reply from 101.37.42.196: bytes=32 time=35ms TTL=53
Reply from 101.37.42.196: bytes=32 time=34ms TTL=53
Reply from 101.37.42.196: bytes=32 time=34ms TTL=53
Reply from 101.37.42.196: bytes=32 time=33ms TTL=53
Reply from 101.37.42.196: bytes=32 time=34ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 35ms, Average = 34ms查看 |
GET PING Trace Dig |
|
| 陕西咸阳市电信 |
电信 |
陕西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
33.3ms |
32.12ms |
32.726ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=33ms TTL=53
Reply from 101.37.42.196: bytes=32 time=33ms TTL=53
Reply from 101.37.42.196: bytes=32 time=33ms TTL=53
Reply from 101.37.42.196: bytes=32 time=33ms TTL=53
Reply from 101.37.42.196: bytes=32 time=33ms TTL=53
Reply from 101.37.42.196: bytes=32 time=33ms TTL=53
Reply from 101.37.42.196: bytes=32 time=32ms TTL=53
Reply from 101.37.42.196: bytes=32 time=32ms TTL=53
Reply from 101.37.42.196: bytes=32 time=32ms TTL=53
Reply from 101.37.42.196: bytes=32 time=32ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 33ms, Average = 33ms查看 |
GET PING Trace Dig |
|
| 陕西商洛市联通 |
联通 |
陕西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
32.8ms |
32.46ms |
32.596ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=33ms TTL=52
Reply from 101.37.42.196: bytes=32 time=33ms TTL=52
Reply from 101.37.42.196: bytes=32 time=33ms TTL=52
Reply from 101.37.42.196: bytes=32 time=33ms TTL=52
Reply from 101.37.42.196: bytes=32 time=32ms TTL=52
Reply from 101.37.42.196: bytes=32 time=32ms TTL=52
Reply from 101.37.42.196: bytes=32 time=33ms TTL=52
Reply from 101.37.42.196: bytes=32 time=33ms TTL=52
Reply from 101.37.42.196: bytes=32 time=32ms TTL=52
Reply from 101.37.42.196: bytes=32 time=33ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 33ms, Average = 33ms查看 |
GET PING Trace Dig |
|
| 重庆重庆市电信 |
电信 |
重庆 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
33.68ms |
31.96ms |
32.54ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=32ms TTL=53
Reply from 101.37.42.196: bytes=32 time=32ms TTL=53
Reply from 101.37.42.196: bytes=32 time=32ms TTL=53
Reply from 101.37.42.196: bytes=32 time=33ms TTL=53
Reply from 101.37.42.196: bytes=32 time=32ms TTL=53
Reply from 101.37.42.196: bytes=32 time=32ms TTL=53
Reply from 101.37.42.196: bytes=32 time=32ms TTL=53
Reply from 101.37.42.196: bytes=32 time=32ms TTL=53
Reply from 101.37.42.196: bytes=32 time=33ms TTL=53
Reply from 101.37.42.196: bytes=32 time=34ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 34ms, Average = 33ms查看 |
GET PING Trace Dig |
|
| 湖南岳阳市电信 |
电信 |
湖南 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
44.619ms |
28.14ms |
32.028ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=30ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Reply from 101.37.42.196: bytes=32 time=33ms TTL=52
Reply from 101.37.42.196: bytes=32 time=38ms TTL=52
Reply from 101.37.42.196: bytes=32 time=28ms TTL=52
Reply from 101.37.42.196: bytes=32 time=32ms TTL=52
Reply from 101.37.42.196: bytes=32 time=28ms TTL=52
Reply from 101.37.42.196: bytes=32 time=28ms TTL=52
Reply from 101.37.42.196: bytes=32 time=45ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 45ms, Average = 32ms查看 |
GET PING Trace Dig |
|
| 河北保定市联通 |
联通 |
河北 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
34.42ms |
30.8ms |
31.592ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=32ms TTL=52
Reply from 101.37.42.196: bytes=32 time=31ms TTL=52
Reply from 101.37.42.196: bytes=32 time=31ms TTL=52
Reply from 101.37.42.196: bytes=32 time=31ms TTL=52
Reply from 101.37.42.196: bytes=32 time=34ms TTL=52
Reply from 101.37.42.196: bytes=32 time=31ms TTL=52
Reply from 101.37.42.196: bytes=32 time=31ms TTL=52
Reply from 101.37.42.196: bytes=32 time=31ms TTL=52
Reply from 101.37.42.196: bytes=32 time=33ms TTL=52
Reply from 101.37.42.196: bytes=32 time=31ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 34ms, Average = 32ms查看 |
GET PING Trace Dig |
|
| 河南安阳市联通 |
联通 |
河南 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
35.36ms |
30.7ms |
31.452ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=31ms TTL=52
Reply from 101.37.42.196: bytes=32 time=32ms TTL=52
Reply from 101.37.42.196: bytes=32 time=31ms TTL=52
Reply from 101.37.42.196: bytes=32 time=31ms TTL=52
Reply from 101.37.42.196: bytes=32 time=31ms TTL=52
Reply from 101.37.42.196: bytes=32 time=35ms TTL=52
Reply from 101.37.42.196: bytes=32 time=31ms TTL=52
Reply from 101.37.42.196: bytes=32 time=31ms TTL=52
Reply from 101.37.42.196: bytes=32 time=31ms TTL=52
Reply from 101.37.42.196: bytes=32 time=31ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 35ms, Average = 31ms查看 |
GET PING Trace Dig |
|
| 河北保定市电信 |
电信 |
河北 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
31.38ms |
31.12ms |
31.246ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=31ms TTL=53
Reply from 101.37.42.196: bytes=32 time=31ms TTL=53
Reply from 101.37.42.196: bytes=32 time=31ms TTL=53
Reply from 101.37.42.196: bytes=32 time=31ms TTL=53
Reply from 101.37.42.196: bytes=32 time=31ms TTL=53
Reply from 101.37.42.196: bytes=32 time=31ms TTL=53
Reply from 101.37.42.196: bytes=32 time=31ms TTL=53
Reply from 101.37.42.196: bytes=32 time=31ms TTL=53
Reply from 101.37.42.196: bytes=32 time=31ms TTL=53
Reply from 101.37.42.196: bytes=32 time=31ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 31ms, Average = 31ms查看 |
GET PING Trace Dig |
|
| 湖南永州市联通 |
联通 |
湖南 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
30.699ms |
29.86ms |
30.056ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=31ms TTL=52
Reply from 101.37.42.196: bytes=32 time=30ms TTL=52
Reply from 101.37.42.196: bytes=32 time=30ms TTL=52
Reply from 101.37.42.196: bytes=32 time=30ms TTL=52
Reply from 101.37.42.196: bytes=32 time=30ms TTL=52
Reply from 101.37.42.196: bytes=32 time=30ms TTL=52
Reply from 101.37.42.196: bytes=32 time=30ms TTL=52
Reply from 101.37.42.196: bytes=32 time=30ms TTL=52
Reply from 101.37.42.196: bytes=32 time=30ms TTL=52
Reply from 101.37.42.196: bytes=32 time=30ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 31ms, Average = 30ms查看 |
GET PING Trace Dig |
|
| 北京北京市联通 |
联通 |
北京 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
31.981ms |
27.818ms |
29.405ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=30ms TTL=51
Reply from 101.37.42.196: bytes=32 time=30ms TTL=51
Reply from 101.37.42.196: bytes=32 time=28ms TTL=51
Reply from 101.37.42.196: bytes=32 time=32ms TTL=51
Reply from 101.37.42.196: bytes=32 time=30ms TTL=51
Reply from 101.37.42.196: bytes=32 time=29ms TTL=51
Reply from 101.37.42.196: bytes=32 time=30ms TTL=51
Reply from 101.37.42.196: bytes=32 time=29ms TTL=51
Reply from 101.37.42.196: bytes=32 time=28ms TTL=51
Reply from 101.37.42.196: bytes=32 time=28ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 32ms, Average = 29ms查看 |
GET PING Trace Dig |
|
| 北京北京市联通 |
联通 |
北京 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
29.764ms |
28.548ms |
29.364ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=30ms TTL=53
Reply from 101.37.42.196: bytes=32 time=29ms TTL=53
Reply from 101.37.42.196: bytes=32 time=29ms TTL=53
Reply from 101.37.42.196: bytes=32 time=29ms TTL=53
Reply from 101.37.42.196: bytes=32 time=30ms TTL=53
Reply from 101.37.42.196: bytes=32 time=30ms TTL=53
Reply from 101.37.42.196: bytes=32 time=29ms TTL=53
Reply from 101.37.42.196: bytes=32 time=29ms TTL=53
Reply from 101.37.42.196: bytes=32 time=29ms TTL=53
Reply from 101.37.42.196: bytes=32 time=30ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 30ms, Average = 29ms查看 |
GET PING Trace Dig |
|
| 湖北咸宁市移动 |
移动 |
湖北 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
30.348ms |
28.895ms |
29.309ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=30ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Reply from 101.37.42.196: bytes=32 time=30ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 30ms, Average = 29ms查看 |
GET PING Trace Dig |
|
| 湖南常德联通 |
联通 |
湖南 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
32.163ms |
27.102ms |
29.092ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=30ms TTL=52
Reply from 101.37.42.196: bytes=32 time=27ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Reply from 101.37.42.196: bytes=32 time=32ms TTL=52
Reply from 101.37.42.196: bytes=32 time=28ms TTL=52
Reply from 101.37.42.196: bytes=32 time=30ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Reply from 101.37.42.196: bytes=32 time=27ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 32ms, Average = 29ms查看 |
GET PING Trace Dig |
|
| 广东肇庆市电信 |
电信 |
广东 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
31.7ms |
27.9ms |
28.889ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=32ms TTL=53
Reply from 101.37.42.196: bytes=32 time=28ms TTL=53
Reply from 101.37.42.196: bytes=32 time=29ms TTL=53
Reply from 101.37.42.196: bytes=32 time=28ms TTL=53
Reply from 101.37.42.196: bytes=32 time=28ms TTL=53
Reply from 101.37.42.196: bytes=32 time=28ms TTL=53
Reply from 101.37.42.196: bytes=32 time=28ms TTL=53
Reply from 101.37.42.196: bytes=32 time=28ms TTL=53
Reply from 101.37.42.196: bytes=32 time=31ms TTL=53
Reply from 101.37.42.196: bytes=32 time=28ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 32ms, Average = 29ms查看 |
GET PING Trace Dig |
|
| 江西南昌市联通 |
联通 |
江西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
28.88ms |
27.72ms |
28.634ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=29ms TTL=53
Reply from 101.37.42.196: bytes=32 time=28ms TTL=53
Reply from 101.37.42.196: bytes=32 time=29ms TTL=53
Reply from 101.37.42.196: bytes=32 time=29ms TTL=53
Reply from 101.37.42.196: bytes=32 time=29ms TTL=53
Reply from 101.37.42.196: bytes=32 time=29ms TTL=53
Reply from 101.37.42.196: bytes=32 time=29ms TTL=53
Reply from 101.37.42.196: bytes=32 time=29ms TTL=53
Reply from 101.37.42.196: bytes=32 time=29ms TTL=53
Reply from 101.37.42.196: bytes=32 time=29ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 29ms, Average = 29ms查看 |
GET PING Trace Dig |
|
| 湖北武汉市联通 |
联通 |
湖北 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
28.88ms |
28.28ms |
28.622ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Reply from 101.37.42.196: bytes=32 time=28ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Reply from 101.37.42.196: bytes=32 time=28ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 29ms, Average = 29ms查看 |
GET PING Trace Dig |
|
| 河北保定市电信 |
电信 |
河北 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
27.861ms |
27.52ms |
27.649ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=28ms TTL=52
Reply from 101.37.42.196: bytes=32 time=28ms TTL=52
Reply from 101.37.42.196: bytes=32 time=28ms TTL=52
Reply from 101.37.42.196: bytes=32 time=28ms TTL=52
Reply from 101.37.42.196: bytes=32 time=28ms TTL=52
Reply from 101.37.42.196: bytes=32 time=28ms TTL=52
Reply from 101.37.42.196: bytes=32 time=28ms TTL=52
Reply from 101.37.42.196: bytes=32 time=28ms TTL=52
Reply from 101.37.42.196: bytes=32 time=28ms TTL=52
Reply from 101.37.42.196: bytes=32 time=28ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 28ms, Average = 28ms查看 |
GET PING Trace Dig |
|
| 山东德州市电信 |
电信 |
山东 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
37.66ms |
24.44ms |
27.289ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=24ms TTL=52
Reply from 101.37.42.196: bytes=32 time=25ms TTL=52
Reply from 101.37.42.196: bytes=32 time=27ms TTL=52
Reply from 101.37.42.196: bytes=32 time=26ms TTL=52
Reply from 101.37.42.196: bytes=32 time=27ms TTL=52
Reply from 101.37.42.196: bytes=32 time=25ms TTL=52
Reply from 101.37.42.196: bytes=32 time=26ms TTL=52
Reply from 101.37.42.196: bytes=32 time=25ms TTL=52
Reply from 101.37.42.196: bytes=32 time=38ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 38ms, Average = 27ms查看 |
GET PING Trace Dig |
|
| 天津天津市联通 |
联通 |
天津 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
28.681ms |
26.594ms |
27.174ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=28ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=29ms TTL=53
Reply from 101.37.42.196: bytes=32 time=29ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 29ms, Average = 27ms查看 |
GET PING Trace Dig |
|
| 福建宁德市移动 |
移动 |
福建 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
35.373ms |
25.657ms |
27.051ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Reply from 101.37.42.196: bytes=32 time=26ms TTL=52
Reply from 101.37.42.196: bytes=32 time=26ms TTL=52
Reply from 101.37.42.196: bytes=32 time=26ms TTL=52
Reply from 101.37.42.196: bytes=32 time=26ms TTL=52
Reply from 101.37.42.196: bytes=32 time=26ms TTL=52
Reply from 101.37.42.196: bytes=32 time=26ms TTL=52
Reply from 101.37.42.196: bytes=32 time=26ms TTL=52
Reply from 101.37.42.196: bytes=32 time=26ms TTL=52
Reply from 101.37.42.196: bytes=32 time=35ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 35ms, Average = 27ms查看 |
GET PING Trace Dig |
|
| 湖北黄石移动 |
移动 |
湖北 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
37.078ms |
23.274ms |
27.044ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=27ms TTL=52
Reply from 101.37.42.196: bytes=32 time=27ms TTL=52
Reply from 101.37.42.196: bytes=32 time=26ms TTL=52
Reply from 101.37.42.196: bytes=32 time=26ms TTL=52
Reply from 101.37.42.196: bytes=32 time=26ms TTL=52
Reply from 101.37.42.196: bytes=32 time=25ms TTL=52
Reply from 101.37.42.196: bytes=32 time=27ms TTL=52
Reply from 101.37.42.196: bytes=32 time=27ms TTL=52
Reply from 101.37.42.196: bytes=32 time=37ms TTL=52
Reply from 101.37.42.196: bytes=32 time=23ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 37ms, Average = 27ms查看 |
GET PING Trace Dig |
|
| 湖北孝感市电信 |
电信 |
湖北 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
28.62ms |
26.181ms |
26.965ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=29ms TTL=53
Reply from 101.37.42.196: bytes=32 time=26ms TTL=53
Reply from 101.37.42.196: bytes=32 time=26ms TTL=53
Reply from 101.37.42.196: bytes=32 time=26ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=28ms TTL=53
Reply from 101.37.42.196: bytes=32 time=26ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 29ms, Average = 27ms查看 |
GET PING Trace Dig |
|
| 湖南长沙市电信 |
电信 |
湖南 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
27.502ms |
26.258ms |
26.795ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=26ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=26ms TTL=53
Reply from 101.37.42.196: bytes=32 time=28ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 28ms, Average = 27ms查看 |
GET PING Trace Dig |
|
| 天津天津市联通 |
联通 |
天津 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
37.46ms |
23.72ms |
26.715ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=24ms TTL=52
Reply from 101.37.42.196: bytes=32 time=37ms TTL=52
Reply from 101.37.42.196: bytes=32 time=27ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Reply from 101.37.42.196: bytes=32 time=24ms TTL=52
Reply from 101.37.42.196: bytes=32 time=24ms TTL=52
Reply from 101.37.42.196: bytes=32 time=24ms TTL=52
Reply from 101.37.42.196: bytes=32 time=24ms TTL=52
Reply from 101.37.42.196: bytes=32 time=24ms TTL=52
Reply from 101.37.42.196: bytes=32 time=29ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 37ms, Average = 27ms查看 |
GET PING Trace Dig |
|
| 山东德州市联通 |
联通 |
山东 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
27.431ms |
25.71ms |
26.613ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=26ms TTL=51
Reply from 101.37.42.196: bytes=32 time=27ms TTL=51
Reply from 101.37.42.196: bytes=32 time=26ms TTL=51
Reply from 101.37.42.196: bytes=32 time=27ms TTL=51
Reply from 101.37.42.196: bytes=32 time=26ms TTL=51
Reply from 101.37.42.196: bytes=32 time=26ms TTL=51
Reply from 101.37.42.196: bytes=32 time=27ms TTL=51
Reply from 101.37.42.196: bytes=32 time=27ms TTL=51
Reply from 101.37.42.196: bytes=32 time=27ms TTL=51
Reply from 101.37.42.196: bytes=32 time=26ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 27ms, Average = 27ms查看 |
GET PING Trace Dig |
|
| 福建泉州市移动 |
移动 |
福建 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
9 |
1 |
30.828ms |
23.302ms |
26.333ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=27ms TTL=49
Request timed out.
Reply from 101.37.42.196: bytes=32 time=27ms TTL=49
Reply from 101.37.42.196: bytes=32 time=30ms TTL=49
Reply from 101.37.42.196: bytes=32 time=25ms TTL=49
Reply from 101.37.42.196: bytes=32 time=23ms TTL=49
Reply from 101.37.42.196: bytes=32 time=24ms TTL=49
Reply from 101.37.42.196: bytes=32 time=26ms TTL=49
Reply from 101.37.42.196: bytes=32 time=31ms TTL=49
Reply from 101.37.42.196: bytes=32 time=23ms TTL=49
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 9, Lost = 1 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 31ms, Average = 26ms查看 |
GET PING Trace Dig |
|
| 福建宁德市电信 |
电信 |
福建 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
8 |
2 |
30.592ms |
0ms |
25.948ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Request timed out.
Reply from 101.37.42.196: bytes=32 time=25ms TTL=52
Reply from 101.37.42.196: bytes=32 time=22ms TTL=52
Reply from 101.37.42.196: bytes=32 time=30ms TTL=52
Request timed out.
Reply from 101.37.42.196: bytes=32 time=27ms TTL=52
Reply from 101.37.42.196: bytes=32 time=31ms TTL=52
Reply from 101.37.42.196: bytes=32 time=23ms TTL=52
Reply from 101.37.42.196: bytes=32 time=25ms TTL=52
Reply from 101.37.42.196: bytes=32 time=25ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 8, Lost = 2 (20% loss),
Approximate round trip times in milli-seconds:
Minimum <1ms , Maximum = 31ms, Average = 26ms查看 |
GET PING Trace Dig |
|
| 安徽阜阳市移动 |
移动 |
安徽 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
44.42ms |
18.021ms |
25.826ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=32ms TTL=53
Reply from 101.37.42.196: bytes=32 time=19ms TTL=53
Reply from 101.37.42.196: bytes=32 time=25ms TTL=53
Reply from 101.37.42.196: bytes=32 time=19ms TTL=53
Reply from 101.37.42.196: bytes=32 time=44ms TTL=53
Reply from 101.37.42.196: bytes=32 time=24ms TTL=53
Reply from 101.37.42.196: bytes=32 time=30ms TTL=53
Reply from 101.37.42.196: bytes=32 time=19ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=18ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 44ms, Average = 26ms查看 |
GET PING Trace Dig |
|
| 江西赣州市移动 |
移动 |
江西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
27.141ms |
16.66ms |
25.643ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=26ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=26ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=17ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 27ms, Average = 26ms查看 |
GET PING Trace Dig |
|
| 福建莆田市电信 |
电信 |
福建 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
55.989ms |
20.518ms |
25.58ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=21ms TTL=52
Reply from 101.37.42.196: bytes=32 time=21ms TTL=52
Reply from 101.37.42.196: bytes=32 time=21ms TTL=52
Reply from 101.37.42.196: bytes=32 time=22ms TTL=52
Reply from 101.37.42.196: bytes=32 time=24ms TTL=52
Reply from 101.37.42.196: bytes=32 time=21ms TTL=52
Reply from 101.37.42.196: bytes=32 time=24ms TTL=52
Reply from 101.37.42.196: bytes=32 time=56ms TTL=52
Reply from 101.37.42.196: bytes=32 time=21ms TTL=52
Reply from 101.37.42.196: bytes=32 time=26ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 56ms, Average = 26ms查看 |
GET PING Trace Dig |
|
| 福建泉州市电信 |
电信 |
福建 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
24.8ms |
24.26ms |
24.649ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=25ms TTL=53
Reply from 101.37.42.196: bytes=32 time=25ms TTL=53
Reply from 101.37.42.196: bytes=32 time=24ms TTL=53
Reply from 101.37.42.196: bytes=32 time=25ms TTL=53
Reply from 101.37.42.196: bytes=32 time=25ms TTL=53
Reply from 101.37.42.196: bytes=32 time=25ms TTL=53
Reply from 101.37.42.196: bytes=32 time=25ms TTL=53
Reply from 101.37.42.196: bytes=32 time=25ms TTL=53
Reply from 101.37.42.196: bytes=32 time=25ms TTL=53
Reply from 101.37.42.196: bytes=32 time=25ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 25ms, Average = 25ms查看 |
GET PING Trace Dig |
|
| 山东济南市联通 |
联通 |
山东 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
25.42ms |
24ms |
24.403ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=24ms TTL=53
Reply from 101.37.42.196: bytes=32 time=24ms TTL=53
Reply from 101.37.42.196: bytes=32 time=24ms TTL=53
Reply from 101.37.42.196: bytes=32 time=25ms TTL=53
Reply from 101.37.42.196: bytes=32 time=24ms TTL=53
Reply from 101.37.42.196: bytes=32 time=24ms TTL=53
Reply from 101.37.42.196: bytes=32 time=24ms TTL=53
Reply from 101.37.42.196: bytes=32 time=24ms TTL=53
Reply from 101.37.42.196: bytes=32 time=24ms TTL=53
Reply from 101.37.42.196: bytes=32 time=25ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 25ms, Average = 24ms查看 |
GET PING Trace Dig |
|
| 湖南郴州市联通 |
联通 |
湖南 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
24.7ms |
24.12ms |
24.31ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=25ms TTL=52
Reply from 101.37.42.196: bytes=32 time=24ms TTL=52
Reply from 101.37.42.196: bytes=32 time=24ms TTL=52
Reply from 101.37.42.196: bytes=32 time=24ms TTL=52
Reply from 101.37.42.196: bytes=32 time=24ms TTL=52
Reply from 101.37.42.196: bytes=32 time=24ms TTL=52
Reply from 101.37.42.196: bytes=32 time=24ms TTL=52
Reply from 101.37.42.196: bytes=32 time=24ms TTL=52
Reply from 101.37.42.196: bytes=32 time=24ms TTL=52
Reply from 101.37.42.196: bytes=32 time=25ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 25ms, Average = 24ms查看 |
GET PING Trace Dig |
|
| 湖北潜江市联通 |
联通 |
湖北 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
25.2ms |
23.1ms |
23.848ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=23ms TTL=53
Reply from 101.37.42.196: bytes=32 time=25ms TTL=53
Reply from 101.37.42.196: bytes=32 time=23ms TTL=53
Reply from 101.37.42.196: bytes=32 time=24ms TTL=53
Reply from 101.37.42.196: bytes=32 time=24ms TTL=53
Reply from 101.37.42.196: bytes=32 time=23ms TTL=53
Reply from 101.37.42.196: bytes=32 time=23ms TTL=53
Reply from 101.37.42.196: bytes=32 time=23ms TTL=53
Reply from 101.37.42.196: bytes=32 time=25ms TTL=53
Reply from 101.37.42.196: bytes=32 time=24ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 25ms, Average = 24ms查看 |
GET PING Trace Dig |
|
| 江苏连云港市联通 |
联通 |
江苏 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
28.342ms |
20.032ms |
23.818ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=27ms TTL=52
Reply from 101.37.42.196: bytes=32 time=23ms TTL=52
Reply from 101.37.42.196: bytes=32 time=28ms TTL=52
Reply from 101.37.42.196: bytes=32 time=23ms TTL=52
Reply from 101.37.42.196: bytes=32 time=20ms TTL=52
Reply from 101.37.42.196: bytes=32 time=25ms TTL=52
Reply from 101.37.42.196: bytes=32 time=25ms TTL=52
Reply from 101.37.42.196: bytes=32 time=20ms TTL=52
Reply from 101.37.42.196: bytes=32 time=24ms TTL=52
Reply from 101.37.42.196: bytes=32 time=24ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 28ms, Average = 24ms查看 |
GET PING Trace Dig |
|
| 江苏盐城市移动 |
移动 |
江苏 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
30.776ms |
18.81ms |
23.456ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=21ms TTL=53
Reply from 101.37.42.196: bytes=32 time=24ms TTL=53
Reply from 101.37.42.196: bytes=32 time=19ms TTL=53
Reply from 101.37.42.196: bytes=32 time=31ms TTL=53
Reply from 101.37.42.196: bytes=32 time=23ms TTL=53
Reply from 101.37.42.196: bytes=32 time=19ms TTL=53
Reply from 101.37.42.196: bytes=32 time=27ms TTL=53
Reply from 101.37.42.196: bytes=32 time=23ms TTL=53
Reply from 101.37.42.196: bytes=32 time=20ms TTL=53
Reply from 101.37.42.196: bytes=32 time=28ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 31ms, Average = 23ms查看 |
GET PING Trace Dig |
|
| 河南洛阳市电信 |
电信 |
河南 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
22.922ms |
22.763ms |
22.832ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=23ms TTL=51
Reply from 101.37.42.196: bytes=32 time=23ms TTL=51
Reply from 101.37.42.196: bytes=32 time=23ms TTL=51
Reply from 101.37.42.196: bytes=32 time=23ms TTL=51
Reply from 101.37.42.196: bytes=32 time=23ms TTL=51
Reply from 101.37.42.196: bytes=32 time=23ms TTL=51
Reply from 101.37.42.196: bytes=32 time=23ms TTL=51
Reply from 101.37.42.196: bytes=32 time=23ms TTL=51
Reply from 101.37.42.196: bytes=32 time=23ms TTL=51
Reply from 101.37.42.196: bytes=32 time=23ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 23ms, Average = 23ms查看 |
GET PING Trace Dig |
|
| 河南洛阳市电信 |
电信 |
河南 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
22.714ms |
22.623ms |
22.668ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=23ms TTL=51
Reply from 101.37.42.196: bytes=32 time=23ms TTL=51
Reply from 101.37.42.196: bytes=32 time=23ms TTL=51
Reply from 101.37.42.196: bytes=32 time=23ms TTL=51
Reply from 101.37.42.196: bytes=32 time=23ms TTL=51
Reply from 101.37.42.196: bytes=32 time=23ms TTL=51
Reply from 101.37.42.196: bytes=32 time=23ms TTL=51
Reply from 101.37.42.196: bytes=32 time=23ms TTL=51
Reply from 101.37.42.196: bytes=32 time=23ms TTL=51
Reply from 101.37.42.196: bytes=32 time=23ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 23ms, Average = 23ms查看 |
GET PING Trace Dig |
|
| 福建宁德市联通 |
联通 |
福建 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
22.88ms |
21.76ms |
22.04ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=22ms TTL=51
Reply from 101.37.42.196: bytes=32 time=22ms TTL=51
Reply from 101.37.42.196: bytes=32 time=22ms TTL=51
Reply from 101.37.42.196: bytes=32 time=22ms TTL=51
Reply from 101.37.42.196: bytes=32 time=22ms TTL=51
Reply from 101.37.42.196: bytes=32 time=22ms TTL=51
Reply from 101.37.42.196: bytes=32 time=22ms TTL=51
Reply from 101.37.42.196: bytes=32 time=23ms TTL=51
Reply from 101.37.42.196: bytes=32 time=22ms TTL=51
Reply from 101.37.42.196: bytes=32 time=22ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 22ms, Maximum = 23ms, Average = 22ms查看 |
GET PING Trace Dig |
|
| 安徽宿州市联通 |
联通 |
安徽 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
44.245ms |
17.605ms |
21.917ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=20ms TTL=52
Reply from 101.37.42.196: bytes=32 time=20ms TTL=52
Reply from 101.37.42.196: bytes=32 time=44ms TTL=52
Reply from 101.37.42.196: bytes=32 time=18ms TTL=52
Reply from 101.37.42.196: bytes=32 time=18ms TTL=52
Reply from 101.37.42.196: bytes=32 time=18ms TTL=52
Reply from 101.37.42.196: bytes=32 time=18ms TTL=52
Reply from 101.37.42.196: bytes=32 time=27ms TTL=52
Reply from 101.37.42.196: bytes=32 time=18ms TTL=52
Reply from 101.37.42.196: bytes=32 time=20ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 44ms, Average = 22ms查看 |
GET PING Trace Dig |
|
| 湖北黄冈市电信 |
电信 |
湖北 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
21.5ms |
21.04ms |
21.21ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=21ms TTL=53
Reply from 101.37.42.196: bytes=32 time=21ms TTL=53
Reply from 101.37.42.196: bytes=32 time=22ms TTL=53
Reply from 101.37.42.196: bytes=32 time=21ms TTL=53
Reply from 101.37.42.196: bytes=32 time=21ms TTL=53
Reply from 101.37.42.196: bytes=32 time=21ms TTL=53
Reply from 101.37.42.196: bytes=32 time=21ms TTL=53
Reply from 101.37.42.196: bytes=32 time=21ms TTL=53
Reply from 101.37.42.196: bytes=32 time=21ms TTL=53
Reply from 101.37.42.196: bytes=32 time=21ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 22ms, Average = 21ms查看 |
GET PING Trace Dig |
|
| 江西赣州市联通 |
联通 |
江西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
20.859ms |
20.486ms |
20.726ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=20ms TTL=52
Reply from 101.37.42.196: bytes=32 time=21ms TTL=52
Reply from 101.37.42.196: bytes=32 time=21ms TTL=52
Reply from 101.37.42.196: bytes=32 time=21ms TTL=52
Reply from 101.37.42.196: bytes=32 time=21ms TTL=52
Reply from 101.37.42.196: bytes=32 time=21ms TTL=52
Reply from 101.37.42.196: bytes=32 time=21ms TTL=52
Reply from 101.37.42.196: bytes=32 time=21ms TTL=52
Reply from 101.37.42.196: bytes=32 time=21ms TTL=52
Reply from 101.37.42.196: bytes=32 time=21ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 21ms, Average = 21ms查看 |
GET PING Trace Dig |
|
| 江苏盐城市联通 |
联通 |
江苏 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
23.14ms |
19.58ms |
20.645ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=21ms TTL=51
Reply from 101.37.42.196: bytes=32 time=23ms TTL=51
Reply from 101.37.42.196: bytes=32 time=20ms TTL=51
Reply from 101.37.42.196: bytes=32 time=21ms TTL=51
Reply from 101.37.42.196: bytes=32 time=20ms TTL=51
Reply from 101.37.42.196: bytes=32 time=20ms TTL=51
Reply from 101.37.42.196: bytes=32 time=20ms TTL=51
Reply from 101.37.42.196: bytes=32 time=22ms TTL=51
Reply from 101.37.42.196: bytes=32 time=20ms TTL=51
Reply from 101.37.42.196: bytes=32 time=20ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 23ms, Average = 21ms查看 |
GET PING Trace Dig |
|
| 浙江宁波市电信 |
电信 |
浙江 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
31.683ms |
12.605ms |
20.3ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=13ms TTL=52
Reply from 101.37.42.196: bytes=32 time=31ms TTL=52
Reply from 101.37.42.196: bytes=32 time=21ms TTL=52
Reply from 101.37.42.196: bytes=32 time=17ms TTL=52
Reply from 101.37.42.196: bytes=32 time=16ms TTL=52
Reply from 101.37.42.196: bytes=32 time=14ms TTL=52
Reply from 101.37.42.196: bytes=32 time=32ms TTL=52
Reply from 101.37.42.196: bytes=32 time=13ms TTL=52
Reply from 101.37.42.196: bytes=32 time=27ms TTL=52
Reply from 101.37.42.196: bytes=32 time=21ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 32ms, Average = 20ms查看 |
GET PING Trace Dig |
|
| 意大利国外 |
国外 |
意大利 |
8.211.32.8 |
德国黑森法兰克福阿里云 |
10 |
10 |
0 |
20.38ms |
19.54ms |
19.94ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (8.211.32.8) with 32 bytes of data:
Reply from 8.211.32.8: bytes=32 time=20ms TTL=88
Reply from 8.211.32.8: bytes=32 time=20ms TTL=88
Reply from 8.211.32.8: bytes=32 time=20ms TTL=88
Reply from 8.211.32.8: bytes=32 time=20ms TTL=88
Reply from 8.211.32.8: bytes=32 time=20ms TTL=88
Reply from 8.211.32.8: bytes=32 time=20ms TTL=88
Reply from 8.211.32.8: bytes=32 time=20ms TTL=88
Reply from 8.211.32.8: bytes=32 time=20ms TTL=88
Reply from 8.211.32.8: bytes=32 time=20ms TTL=88
Reply from 8.211.32.8: bytes=32 time=20ms TTL=88
Ping statistics for 8.211.32.8:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 20ms, Average = 20ms查看 |
GET PING Trace Dig |
|
| 江西新余市电信 |
电信 |
江西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
19.8ms |
19.261ms |
19.596ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=20ms TTL=53
Reply from 101.37.42.196: bytes=32 time=19ms TTL=53
Reply from 101.37.42.196: bytes=32 time=20ms TTL=53
Reply from 101.37.42.196: bytes=32 time=20ms TTL=53
Reply from 101.37.42.196: bytes=32 time=19ms TTL=53
Reply from 101.37.42.196: bytes=32 time=20ms TTL=53
Reply from 101.37.42.196: bytes=32 time=20ms TTL=53
Reply from 101.37.42.196: bytes=32 time=20ms TTL=53
Reply from 101.37.42.196: bytes=32 time=19ms TTL=53
Reply from 101.37.42.196: bytes=32 time=20ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 20ms, Average = 20ms查看 |
GET PING Trace Dig |
|
| 江西上饶市电信 |
电信 |
江西 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
18.961ms |
18.74ms |
18.825ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=19ms TTL=53
Reply from 101.37.42.196: bytes=32 time=19ms TTL=53
Reply from 101.37.42.196: bytes=32 time=19ms TTL=53
Reply from 101.37.42.196: bytes=32 time=19ms TTL=53
Reply from 101.37.42.196: bytes=32 time=19ms TTL=53
Reply from 101.37.42.196: bytes=32 time=19ms TTL=53
Reply from 101.37.42.196: bytes=32 time=19ms TTL=53
Reply from 101.37.42.196: bytes=32 time=19ms TTL=53
Reply from 101.37.42.196: bytes=32 time=19ms TTL=53
Reply from 101.37.42.196: bytes=32 time=19ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 19ms, Average = 19ms查看 |
GET PING Trace Dig |
|
| 江苏常州市移动 |
移动 |
江苏 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
18.895ms |
18.678ms |
18.767ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=19ms TTL=54
Reply from 101.37.42.196: bytes=32 time=19ms TTL=54
Reply from 101.37.42.196: bytes=32 time=19ms TTL=54
Reply from 101.37.42.196: bytes=32 time=19ms TTL=54
Reply from 101.37.42.196: bytes=32 time=19ms TTL=54
Reply from 101.37.42.196: bytes=32 time=19ms TTL=54
Reply from 101.37.42.196: bytes=32 time=19ms TTL=54
Reply from 101.37.42.196: bytes=32 time=19ms TTL=54
Reply from 101.37.42.196: bytes=32 time=19ms TTL=54
Reply from 101.37.42.196: bytes=32 time=19ms TTL=54
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = 19ms, Average = 19ms查看 |
GET PING Trace Dig |
|
| 上海上海市电信 |
电信 |
上海 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
21.861ms |
15.048ms |
18.119ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=22ms TTL=52
Reply from 101.37.42.196: bytes=32 time=19ms TTL=52
Reply from 101.37.42.196: bytes=32 time=17ms TTL=52
Reply from 101.37.42.196: bytes=32 time=15ms TTL=52
Reply from 101.37.42.196: bytes=32 time=18ms TTL=52
Reply from 101.37.42.196: bytes=32 time=22ms TTL=52
Reply from 101.37.42.196: bytes=32 time=15ms TTL=52
Reply from 101.37.42.196: bytes=32 time=16ms TTL=52
Reply from 101.37.42.196: bytes=32 time=18ms TTL=52
Reply from 101.37.42.196: bytes=32 time=19ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 15ms, Maximum = 22ms, Average = 18ms查看 |
GET PING Trace Dig |
|
| 安徽宣城市联通 |
联通 |
安徽 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
18.277ms |
17.18ms |
17.848ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=18ms TTL=53
Reply from 101.37.42.196: bytes=32 time=18ms TTL=53
Reply from 101.37.42.196: bytes=32 time=17ms TTL=53
Reply from 101.37.42.196: bytes=32 time=18ms TTL=53
Reply from 101.37.42.196: bytes=32 time=18ms TTL=53
Reply from 101.37.42.196: bytes=32 time=18ms TTL=53
Reply from 101.37.42.196: bytes=32 time=18ms TTL=53
Reply from 101.37.42.196: bytes=32 time=17ms TTL=53
Reply from 101.37.42.196: bytes=32 time=18ms TTL=53
Reply from 101.37.42.196: bytes=32 time=17ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 18ms, Average = 18ms查看 |
GET PING Trace Dig |
|
| 江苏南通市电信 |
电信 |
江苏 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
20.863ms |
16.091ms |
16.784ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=16ms TTL=52
Reply from 101.37.42.196: bytes=32 time=16ms TTL=52
Reply from 101.37.42.196: bytes=32 time=16ms TTL=52
Reply from 101.37.42.196: bytes=32 time=21ms TTL=52
Reply from 101.37.42.196: bytes=32 time=17ms TTL=52
Reply from 101.37.42.196: bytes=32 time=16ms TTL=52
Reply from 101.37.42.196: bytes=32 time=16ms TTL=52
Reply from 101.37.42.196: bytes=32 time=16ms TTL=52
Reply from 101.37.42.196: bytes=32 time=16ms TTL=52
Reply from 101.37.42.196: bytes=32 time=16ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 21ms, Average = 17ms查看 |
GET PING Trace Dig |
|
| 安徽六安市电信 |
电信 |
安徽 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
17.38ms |
16.4ms |
16.712ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=17ms TTL=51
Reply from 101.37.42.196: bytes=32 time=17ms TTL=51
Reply from 101.37.42.196: bytes=32 time=16ms TTL=51
Reply from 101.37.42.196: bytes=32 time=17ms TTL=51
Reply from 101.37.42.196: bytes=32 time=16ms TTL=51
Reply from 101.37.42.196: bytes=32 time=17ms TTL=51
Reply from 101.37.42.196: bytes=32 time=17ms TTL=51
Reply from 101.37.42.196: bytes=32 time=17ms TTL=51
Reply from 101.37.42.196: bytes=32 time=17ms TTL=51
Reply from 101.37.42.196: bytes=32 time=17ms TTL=51
Ping statistics for 101.37.42.196:
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 |
|
| 上海上海市电信 |
电信 |
上海 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
18.787ms |
13.508ms |
15.246ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=16ms TTL=51
Reply from 101.37.42.196: bytes=32 time=14ms TTL=51
Reply from 101.37.42.196: bytes=32 time=16ms TTL=51
Reply from 101.37.42.196: bytes=32 time=19ms TTL=51
Reply from 101.37.42.196: bytes=32 time=14ms TTL=51
Reply from 101.37.42.196: bytes=32 time=16ms TTL=51
Reply from 101.37.42.196: bytes=32 time=17ms TTL=51
Reply from 101.37.42.196: bytes=32 time=14ms TTL=51
Reply from 101.37.42.196: bytes=32 time=14ms TTL=51
Reply from 101.37.42.196: bytes=32 time=15ms TTL=51
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 19ms, Average = 15ms查看 |
GET PING Trace Dig |
|
| 上海上海市联通 |
联通 |
上海 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
16.044ms |
14.358ms |
14.912ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=15ms TTL=53
Reply from 101.37.42.196: bytes=32 time=15ms TTL=53
Reply from 101.37.42.196: bytes=32 time=15ms TTL=53
Reply from 101.37.42.196: bytes=32 time=15ms TTL=53
Reply from 101.37.42.196: bytes=32 time=14ms TTL=53
Reply from 101.37.42.196: bytes=32 time=15ms TTL=53
Reply from 101.37.42.196: bytes=32 time=16ms TTL=53
Reply from 101.37.42.196: bytes=32 time=14ms TTL=53
Reply from 101.37.42.196: bytes=32 time=15ms TTL=53
Reply from 101.37.42.196: bytes=32 time=14ms TTL=53
Ping statistics for 101.37.42.196:
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 |
|
| 上海上海市移动 |
移动 |
上海 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
20.779ms |
11.092ms |
12.976ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=13ms TTL=52
Reply from 101.37.42.196: bytes=32 time=12ms TTL=52
Reply from 101.37.42.196: bytes=32 time=12ms TTL=52
Reply from 101.37.42.196: bytes=32 time=11ms TTL=52
Reply from 101.37.42.196: bytes=32 time=12ms TTL=52
Reply from 101.37.42.196: bytes=32 time=12ms TTL=52
Reply from 101.37.42.196: bytes=32 time=13ms TTL=52
Reply from 101.37.42.196: bytes=32 time=21ms TTL=52
Reply from 101.37.42.196: bytes=32 time=12ms TTL=52
Reply from 101.37.42.196: bytes=32 time=12ms TTL=52
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 21ms, Average = 13ms查看 |
GET PING Trace Dig |
|
| 浙江宁波移动 |
移动 |
浙江 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
15.46ms |
9.78ms |
11.894ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=10ms TTL=54
Reply from 101.37.42.196: bytes=32 time=12ms TTL=54
Reply from 101.37.42.196: bytes=32 time=15ms TTL=54
Reply from 101.37.42.196: bytes=32 time=10ms TTL=54
Reply from 101.37.42.196: bytes=32 time=11ms TTL=54
Reply from 101.37.42.196: bytes=32 time=10ms TTL=54
Reply from 101.37.42.196: bytes=32 time=14ms TTL=54
Reply from 101.37.42.196: bytes=32 time=13ms TTL=54
Reply from 101.37.42.196: bytes=32 time=11ms TTL=54
Reply from 101.37.42.196: bytes=32 time=12ms TTL=54
Ping statistics for 101.37.42.196:
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 |
|
| 上海上海市移动 |
移动 |
上海 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
11.97ms |
9.967ms |
10.866ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=10ms TTL=53
Reply from 101.37.42.196: bytes=32 time=10ms TTL=53
Reply from 101.37.42.196: bytes=32 time=11ms TTL=53
Reply from 101.37.42.196: bytes=32 time=11ms TTL=53
Reply from 101.37.42.196: bytes=32 time=10ms TTL=53
Reply from 101.37.42.196: bytes=32 time=11ms TTL=53
Reply from 101.37.42.196: bytes=32 time=12ms TTL=53
Reply from 101.37.42.196: bytes=32 time=10ms TTL=53
Reply from 101.37.42.196: bytes=32 time=12ms TTL=53
Reply from 101.37.42.196: bytes=32 time=12ms TTL=53
Ping statistics for 101.37.42.196:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 12ms, Average = 11ms查看 |
GET PING Trace Dig |
|
| 浙江杭州市联通 |
联通 |
浙江 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
11.052ms |
9.894ms |
10.354ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=10ms TTL=55
Reply from 101.37.42.196: bytes=32 time=10ms TTL=55
Reply from 101.37.42.196: bytes=32 time=10ms TTL=55
Reply from 101.37.42.196: bytes=32 time=10ms TTL=55
Reply from 101.37.42.196: bytes=32 time=11ms TTL=55
Reply from 101.37.42.196: bytes=32 time=10ms TTL=55
Reply from 101.37.42.196: bytes=32 time=10ms TTL=55
Reply from 101.37.42.196: bytes=32 time=11ms TTL=55
Reply from 101.37.42.196: bytes=32 time=10ms TTL=55
Reply from 101.37.42.196: bytes=32 time=10ms TTL=55
Ping statistics for 101.37.42.196:
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 |
|
| 浙江温州市联通 |
联通 |
浙江 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
10.854ms |
9.883ms |
10.342ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=10ms TTL=54
Reply from 101.37.42.196: bytes=32 time=10ms TTL=54
Reply from 101.37.42.196: bytes=32 time=10ms TTL=54
Reply from 101.37.42.196: bytes=32 time=10ms TTL=54
Reply from 101.37.42.196: bytes=32 time=11ms TTL=54
Reply from 101.37.42.196: bytes=32 time=10ms TTL=54
Reply from 101.37.42.196: bytes=32 time=10ms TTL=54
Reply from 101.37.42.196: bytes=32 time=11ms TTL=54
Reply from 101.37.42.196: bytes=32 time=10ms TTL=54
Reply from 101.37.42.196: bytes=32 time=11ms TTL=54
Ping statistics for 101.37.42.196:
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 |
|
| 美国国外 |
国外 |
美国 |
47.251.169.254 |
美国加利福尼亚圣克拉拉阿里云 |
10 |
10 |
0 |
9.676ms |
9.05ms |
9.356ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (47.251.169.254) with 32 bytes of data:
Reply from 47.251.169.254: bytes=32 time=9ms TTL=88
Reply from 47.251.169.254: bytes=32 time=9ms TTL=88
Reply from 47.251.169.254: bytes=32 time=10ms TTL=88
Reply from 47.251.169.254: bytes=32 time=9ms TTL=88
Reply from 47.251.169.254: bytes=32 time=9ms TTL=88
Reply from 47.251.169.254: bytes=32 time=10ms TTL=88
Reply from 47.251.169.254: bytes=32 time=9ms TTL=88
Reply from 47.251.169.254: bytes=32 time=9ms TTL=88
Reply from 47.251.169.254: bytes=32 time=10ms TTL=88
Reply from 47.251.169.254: bytes=32 time=9ms TTL=88
Ping statistics for 47.251.169.254:
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 |
|
| 浙江宁波市移动 |
移动 |
浙江 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
9.406ms |
8.853ms |
9.112ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=9ms TTL=55
Reply from 101.37.42.196: bytes=32 time=9ms TTL=55
Reply from 101.37.42.196: bytes=32 time=9ms TTL=55
Reply from 101.37.42.196: bytes=32 time=9ms TTL=55
Reply from 101.37.42.196: bytes=32 time=9ms TTL=55
Reply from 101.37.42.196: bytes=32 time=9ms TTL=55
Reply from 101.37.42.196: bytes=32 time=9ms TTL=55
Reply from 101.37.42.196: bytes=32 time=9ms TTL=55
Reply from 101.37.42.196: bytes=32 time=9ms TTL=55
Reply from 101.37.42.196: bytes=32 time=9ms TTL=55
Ping statistics for 101.37.42.196:
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 |
|
| 浙江绍兴市电信 |
电信 |
浙江 |
101.37.42.196 |
中国浙江杭州阿里云 |
10 |
10 |
0 |
8.544ms |
7.672ms |
7.955ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (101.37.42.196) with 32 bytes of data:
Reply from 101.37.42.196: bytes=32 time=9ms TTL=55
Reply from 101.37.42.196: bytes=32 time=8ms TTL=55
Reply from 101.37.42.196: bytes=32 time=8ms TTL=55
Reply from 101.37.42.196: bytes=32 time=8ms TTL=55
Reply from 101.37.42.196: bytes=32 time=8ms TTL=55
Reply from 101.37.42.196: bytes=32 time=8ms TTL=55
Reply from 101.37.42.196: bytes=32 time=8ms TTL=55
Reply from 101.37.42.196: bytes=32 time=8ms TTL=55
Reply from 101.37.42.196: bytes=32 time=8ms TTL=55
Reply from 101.37.42.196: bytes=32 time=8ms TTL=55
Ping statistics for 101.37.42.196:
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 |
|
| 澳门澳门 |
澳门 |
澳门 |
8.218.113.144 |
中国香港阿里云 |
10 |
10 |
0 |
7.82ms |
7.4ms |
7.665ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (8.218.113.144) with 32 bytes of data:
Reply from 8.218.113.144: bytes=32 time=8ms TTL=90
Reply from 8.218.113.144: bytes=32 time=7ms TTL=90
Reply from 8.218.113.144: bytes=32 time=8ms TTL=90
Reply from 8.218.113.144: bytes=32 time=8ms TTL=90
Reply from 8.218.113.144: bytes=32 time=7ms TTL=90
Reply from 8.218.113.144: bytes=32 time=8ms TTL=90
Reply from 8.218.113.144: bytes=32 time=8ms TTL=90
Reply from 8.218.113.144: bytes=32 time=8ms TTL=90
Reply from 8.218.113.144: bytes=32 time=8ms TTL=90
Reply from 8.218.113.144: bytes=32 time=8ms TTL=90
Ping statistics for 8.218.113.144:
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 |
|
| 香港香港 |
香港 |
香港 |
8.218.113.144 |
中国香港阿里云 |
10 |
10 |
0 |
5.4ms |
5.251ms |
5.298ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (8.218.113.144) with 32 bytes of data:
Reply from 8.218.113.144: bytes=32 time=5ms TTL=93
Reply from 8.218.113.144: bytes=32 time=5ms TTL=93
Reply from 8.218.113.144: bytes=32 time=5ms TTL=93
Reply from 8.218.113.144: bytes=32 time=5ms TTL=93
Reply from 8.218.113.144: bytes=32 time=5ms TTL=93
Reply from 8.218.113.144: bytes=32 time=5ms TTL=93
Reply from 8.218.113.144: bytes=32 time=5ms TTL=93
Reply from 8.218.113.144: bytes=32 time=5ms TTL=93
Reply from 8.218.113.144: bytes=32 time=5ms TTL=93
Reply from 8.218.113.144: bytes=32 time=5ms TTL=93
Ping statistics for 8.218.113.144:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 5ms, Average = 5ms查看 |
GET PING Trace Dig |
|
| 澳门澳门 |
澳门 |
澳门 |
8.217.195.80 |
中国香港阿里云 |
10 |
10 |
0 |
4.96ms |
4.4ms |
4.612ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (8.217.195.80) with 32 bytes of data:
Reply from 8.217.195.80: bytes=32 time=5ms TTL=93
Reply from 8.217.195.80: bytes=32 time=4ms TTL=93
Reply from 8.217.195.80: bytes=32 time=4ms TTL=93
Reply from 8.217.195.80: bytes=32 time=5ms TTL=93
Reply from 8.217.195.80: bytes=32 time=5ms TTL=93
Reply from 8.217.195.80: bytes=32 time=5ms TTL=93
Reply from 8.217.195.80: bytes=32 time=5ms TTL=93
Reply from 8.217.195.80: bytes=32 time=5ms TTL=93
Reply from 8.217.195.80: bytes=32 time=4ms TTL=93
Reply from 8.217.195.80: bytes=32 time=5ms TTL=93
Ping statistics for 8.217.195.80:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 5ms, Average = 5ms查看 |
GET PING Trace Dig |
|
| 香港香港 |
香港 |
香港 |
8.217.195.80 |
中国香港阿里云 |
10 |
10 |
0 |
2.067ms |
1.951ms |
1.981ms |
32B |
PING metaverse.101.com
PING metaverse.101.com (8.217.195.80) with 32 bytes of data:
Reply from 8.217.195.80: bytes=32 time=2ms TTL=96
Reply from 8.217.195.80: bytes=32 time=2ms TTL=96
Reply from 8.217.195.80: bytes=32 time=2ms TTL=96
Reply from 8.217.195.80: bytes=32 time=2ms TTL=96
Reply from 8.217.195.80: bytes=32 time=2ms TTL=96
Reply from 8.217.195.80: bytes=32 time=2ms TTL=96
Reply from 8.217.195.80: bytes=32 time=2ms TTL=96
Reply from 8.217.195.80: bytes=32 time=2ms TTL=96
Reply from 8.217.195.80: bytes=32 time=2ms TTL=96
Reply from 8.217.195.80: bytes=32 time=2ms TTL=96
Ping statistics for 8.217.195.80:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 2ms, Average = 2ms查看 |
GET PING Trace Dig |
|
| 广东深圳电信 |
电信 |
广东 |
|
* |
0 |
0 |
0 |
0ms |
0ms |
0ms |
|
PING metaverse.101.com
PING metaverse.101.com () with 0 bytes of data:
Reply from : bytes=0 time=5ms TTL=93
Reply from : bytes=0 time=5ms TTL=93
Reply from : bytes=0 time=5ms TTL=93
Reply from : bytes=0 time=5ms TTL=93
Reply from : bytes=0 time=5ms TTL=93
Reply from : bytes=0 time=5ms TTL=93
Reply from : bytes=0 time=5ms TTL=93
Reply from : bytes=0 time=5ms TTL=93
Reply from : bytes=0 time=5ms TTL=93
Reply from : bytes=0 time=5ms TTL=93
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 metaverse.101.com
PING metaverse.101.com () with 0 bytes of data:
Reply from : bytes=0 time=42ms TTL=51
Reply from : bytes=0 time=40ms TTL=51
Reply from : bytes=0 time=41ms TTL=51
Reply from : bytes=0 time=40ms TTL=51
Reply from : bytes=0 time=41ms TTL=51
Reply from : bytes=0 time=40ms TTL=51
Reply from : bytes=0 time=42ms TTL=51
Reply from : bytes=0 time=41ms TTL=51
Reply from : bytes=0 time=41ms TTL=51
Reply from : bytes=0 time=40ms TTL=51
Ping statistics for :
Packets: Sent = 0, Received = 0, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum <1ms , Maximum <1ms , Average <1ms 查看 |
GET PING Trace Dig |
|
| 内蒙古呼和浩特市联通 |
联通 |
内蒙古 |
|
* |
0 |
0 |
0 |
0ms |
0ms |
0ms |
|
PING metaverse.101.com
PING metaverse.101.com () with 0 bytes of data:
Reply from : bytes=0 time=13ms TTL=52
Reply from : bytes=0 time=31ms TTL=52
Reply from : bytes=0 time=21ms TTL=52
Reply from : bytes=0 time=17ms TTL=52
Reply from : bytes=0 time=16ms TTL=52
Reply from : bytes=0 time=14ms TTL=52
Reply from : bytes=0 time=32ms TTL=52
Reply from : bytes=0 time=13ms TTL=52
Reply from : bytes=0 time=27ms TTL=52
Reply from : bytes=0 time=21ms TTL=52
Ping statistics for :
Packets: Sent = 0, Received = 0, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum <1ms , Maximum <1ms , Average <1ms 查看 |
GET PING Trace Dig |
|
| 内蒙古兴安盟移动 |
移动 |
内蒙古 |
|
* |
0 |
0 |
0 |
0ms |
0ms |
0ms |
|
PING metaverse.101.com
PING metaverse.101.com () with 0 bytes of data:
Reply from : bytes=0 time=52ms TTL=52
Reply from : bytes=0 time=60ms TTL=52
Reply from : bytes=0 time=58ms TTL=52
Reply from : bytes=0 time=52ms TTL=52
Reply from : bytes=0 time=50ms TTL=52
Reply from : bytes=0 time=52ms TTL=52
Reply from : bytes=0 time=50ms TTL=52
Reply from : bytes=0 time=60ms TTL=52
Reply from : bytes=0 time=50ms TTL=52
Reply from : bytes=0 time=58ms TTL=52
Ping statistics for :
Packets: Sent = 0, Received = 0, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum <1ms , Maximum <1ms , Average <1ms 查看 |
GET PING Trace Dig |
|
| 江苏常州市电信 |
电信 |
江苏 |
|
* |
0 |
0 |
0 |
0ms |
0ms |
0ms |
|
PING metaverse.101.com
PING metaverse.101.com () with 0 bytes of data:
Reply from : bytes=0 time=8ms TTL=90
Reply from : bytes=0 time=7ms TTL=90
Reply from : bytes=0 time=8ms TTL=90
Reply from : bytes=0 time=8ms TTL=90
Reply from : bytes=0 time=7ms TTL=90
Reply from : bytes=0 time=8ms TTL=90
Reply from : bytes=0 time=8ms TTL=90
Reply from : bytes=0 time=8ms TTL=90
Reply from : bytes=0 time=8ms TTL=90
Reply from : bytes=0 time=8ms TTL=90
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 |
|
