vir-tokyo 评测结果 返回主页
最近上头买了一堆小鸡，实际上没啥用，不如做点测评，供大家参考：
## 简介
测评时间：2024-03-14 14:14:09
- [购买链接（含aff）](undefined)
- 产品：undefined
- undefined
## 国外站点访问时间测试
```shell
```
## Yabs测试
```shell
# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
# Yet-Another-Bench-Script #
# v2024-03-05 #
# https://github.com/masonr/yet-another-bench-script #
# ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #
Thu Mar 14 08:41:39 EDT 2024
Basic System Information:
---------------------------------
Uptime : 49 days, 6 hours, 56 minutes
Processor : AMD Ryzen 9 5900X 12-Core Processor
CPU cores : 1 @ 3693.062 MHz
AES-NI : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM : 1.4 GiB
Swap : 256.0 MiB
Disk : 14.5 GiB
Distro : Debian GNU/Linux 10 (buster)
Kernel : 5.10.0-0.deb10.21-rt-amd64
VM Type : KVM
IPv4/IPv6 : ✔ Online / ✔ Online
IPv6 Network Information:
---------------------------------
ISP : xTom Pty Ltd
ASN : AS3258 xTom Pty Ltd
Host : Virtual Machine Solutions LLC
Location : Tokyo, Tokyo (13)
Country : Japan
Preparing system for disk tests...
[0KGenerating fio test file...
[0KRunning fio random mixed R+W disk test with 4k block size...
[0KRunning fio random mixed R+W disk test with 64k block size...
[0KRunning fio random mixed R+W disk test with 512k block size...
[0KRunning fio random mixed R+W disk test with 1m block size...
[0Kfio Disk Speed Tests (Mixed R/W 50/50) (Partition /dev/vda1):
---------------------------------
Block Size | 4k (IOPS) | 64k (IOPS)
------ | --- ---- | ---- ----
Read | 192.39 MB/s (48.0k) | 772.39 MB/s (12.0k)
Write | 192.90 MB/s (48.2k) | 776.46 MB/s (12.1k)
Total | 385.29 MB/s (96.3k) | 1.54 GB/s (24.2k)
| |
Block Size | 512k (IOPS) | 1m (IOPS)
------ | --- ---- | ---- ----
Read | 873.39 MB/s (1.7k) | 731.63 MB/s (714)
Write | 919.80 MB/s (1.7k) | 780.36 MB/s (762)
Total | 1.79 GB/s (3.5k) | 1.51 GB/s (1.4k)
iperf3 Network Speed Tests (IPv4):
---------------------------------
Provider | Location (Link) | Send Speed | Recv Speed | Ping
----- | ----- | ---- | ---- | ----
Performing IPv4 iperf3 send test to Clouvider (Attempt #1 of 3)...
[0KPerforming IPv4 iperf3 send test to Clouvider (Attempt #2 of 3)...
[0KPerforming IPv4 iperf3 send test to Clouvider (Attempt #3 of 3)...
[0KPerforming IPv4 iperf3 recv test from Clouvider (Attempt #1 of 3)...
[0KPerforming IPv4 iperf3 recv test from Clouvider (Attempt #2 of 3)...
[0KPerforming IPv4 iperf3 recv test from Clouvider (Attempt #3 of 3)...
[0KClouvider | London, UK (10G) | busy | busy | 245 ms
Performing IPv4 iperf3 send test to Eranium (Attempt #1 of 3)...
[0KPerforming IPv4 iperf3 send test to Eranium (Attempt #2 of 3)...
[0KPerforming IPv4 iperf3 send test to Eranium (Attempt #3 of 3)...
[0KPerforming IPv4 iperf3 recv test from Eranium (Attempt #1 of 3)...
[0KPerforming IPv4 iperf3 recv test from Eranium (Attempt #2 of 3)...
[0KPerforming IPv4 iperf3 recv test from Eranium (Attempt #3 of 3)...
[0KEranium | Amsterdam, NL (10G) | busy | busy | 234 ms
Performing IPv4 iperf3 send test to HOSTKEY (Attempt #1 of 3)...
[0KPerforming IPv4 iperf3 send test to HOSTKEY (Attempt #2 of 3)...
[0KPerforming IPv4 iperf3 send test to HOSTKEY (Attempt #3 of 3)...
[0KPerforming IPv4 iperf3 recv test from HOSTKEY (Attempt #1 of 3)...
[0KHOSTKEY | Helsinki, FI (10G) | 491 Mbits/sec | 272 Mbits/sec | 282 ms
Performing IPv4 iperf3 send test to Uztelecom (Attempt #1 of 3)...
[0KPerforming IPv4 iperf3 recv test from Uztelecom (Attempt #1 of 3)...
[0KPerforming IPv4 iperf3 recv test from Uztelecom (Attempt #2 of 3)...
[0KUztelecom | Tashkent, UZ (10G) | 522 Mbits/sec | 287 Mbits/sec | 230 ms
Performing IPv4 iperf3 send test to Leaseweb (Attempt #1 of 3)...
[0KPerforming IPv4 iperf3 recv test from Leaseweb (Attempt #1 of 3)...
[0KLeaseweb | Singapore, SG (10G) | 801 Mbits/sec | 565 Mbits/sec | 67.4 ms
Performing IPv4 iperf3 send test to Clouvider (Attempt #1 of 3)...
[0KPerforming IPv4 iperf3 recv test from Clouvider (Attempt #1 of 3)...
[0KPerforming IPv4 iperf3 recv test from Clouvider (Attempt #2 of 3)...
[0KPerforming IPv4 iperf3 recv test from Clouvider (Attempt #3 of 3)...
[0KClouvider | Los Angeles, CA, US (10G) | 823 Mbits/sec | 272 Mbits/sec | 119 ms
Performing IPv4 iperf3 send test to Leaseweb (Attempt #1 of 3)...
[0KPerforming IPv4 iperf3 recv test from Leaseweb (Attempt #1 of 3)...
[0KPerforming IPv4 iperf3 recv test from Leaseweb (Attempt #2 of 3)...
[0KLeaseweb | NYC, NY, US (10G) | 718 Mbits/sec | 278 Mbits/sec | 168 ms
Performing IPv4 iperf3 send test to Edgoo (Attempt #1 of 3)...
[0KPerforming IPv4 iperf3 send test to Edgoo (Attempt #2 of 3)...
[0KPerforming IPv4 iperf3 recv test from Edgoo (Attempt #1 of 3)...
[0KEdgoo | Sao Paulo, BR (1G) | 651 Mbits/sec | 299 Mbits/sec | 280 ms
iperf3 Network Speed Tests (IPv6):
---------------------------------
Provider | Location (Link) | Send Speed | Recv Speed | Ping
----- | ----- | ---- | ---- | ----
Performing IPv6 iperf3 send test to Clouvider (Attempt #1 of 3)...
[0KPerforming IPv6 iperf3 send test to Clouvider (Attempt #2 of 3)...
[0KPerforming IPv6 iperf3 send test to Clouvider (Attempt #3 of 3)...
[0KPerforming IPv6 iperf3 recv test from Clouvider (Attempt #1 of 3)...
[0KPerforming IPv6 iperf3 recv test from Clouvider (Attempt #2 of 3)...
[0KPerforming IPv6 iperf3 recv test from Clouvider (Attempt #3 of 3)...
[0KClouvider | London, UK (10G) | busy | 319 Mbits/sec | 245 ms
Performing IPv6 iperf3 send test to Eranium (Attempt #1 of 3)...
[0KPerforming IPv6 iperf3 send test to Eranium (Attempt #2 of 3)...
[0KPerforming IPv6 iperf3 send test to Eranium (Attempt #3 of 3)...
[0KPerforming IPv6 iperf3 recv test from Eranium (Attempt #1 of 3)...
[0KPerforming IPv6 iperf3 recv test from Eranium (Attempt #2 of 3)...
[0KPerforming IPv6 iperf3 recv test from Eranium (Attempt #3 of 3)...
[0KEranium | Amsterdam, NL (10G) | busy | busy | 230 ms
Performing IPv6 iperf3 send test to Uztelecom (Attempt #1 of 3)...
[0KPerforming IPv6 iperf3 recv test from Uztelecom (Attempt #1 of 3)...
[0KUztelecom | Tashkent, UZ (10G) | 501 Mbits/sec | 193 Mbits/sec | 226 ms
Performing IPv6 iperf3 send test to Leaseweb (Attempt #1 of 3)...
[0KPerforming IPv6 iperf3 send test to Leaseweb (Attempt #2 of 3)...
[0KPerforming IPv6 iperf3 send test to Leaseweb (Attempt #3 of 3)...
[0KPerforming IPv6 iperf3 recv test from Leaseweb (Attempt #1 of 3)...
[0KLeaseweb | Singapore, SG (10G) | busy | 718 Mbits/sec | 67.1 ms
Performing IPv6 iperf3 send test to Clouvider (Attempt #1 of 3)...
[0KPerforming IPv6 iperf3 send test to Clouvider (Attempt #2 of 3)...
[0KPerforming IPv6 iperf3 send test to Clouvider (Attempt #3 of 3)...
[0KPerforming IPv6 iperf3 recv test from Clouvider (Attempt #1 of 3)...
[0KPerforming IPv6 iperf3 recv test from Clouvider (Attempt #2 of 3)...
[0KClouvider | Los Angeles, CA, US (10G) | 817 Mbits/sec | 421 Mbits/sec | 112 ms
Performing IPv6 iperf3 send test to Leaseweb (Attempt #1 of 3)...
[0KPerforming IPv6 iperf3 send test to Leaseweb (Attempt #2 of 3)...
[0KPerforming IPv6 iperf3 recv test from Leaseweb (Attempt #1 of 3)...
[0KPerforming IPv6 iperf3 recv test from Leaseweb (Attempt #2 of 3)...
[0KLeaseweb | NYC, NY, US (10G) | 776 Mbits/sec | 286 Mbits/sec | 169 ms
Performing IPv6 iperf3 send test to Edgoo (Attempt #1 of 3)...
[0KPerforming IPv6 iperf3 recv test from Edgoo (Attempt #1 of 3)...
[0KEdgoo | Sao Paulo, BR (1G) | 608 Mbits/sec | 151 Mbits/sec | 280 ms
Running GB6 benchmark test... *cue elevator music*
[0KGeekbench 6 test failed. Run manually to determine cause.
YABS completed in 14 min 11 sec
```
## 三网回程路由测试
```shell
2024/03/14 08:55:52 正在测试三网回程路由
国家: JP 城市: Tokyo 服务商: AS3258 xTom Pty Ltd
项目地址: https://github.com/zhanghanyun/backtrace
北京电信 219.141.136.12 电信163 [普通线路]
北京联通 202.106.50.1 联通4837[普通线路]
北京移动 221.179.155.161 移动CMI [普通线路]
上海电信 202.96.209.133 测试超时
上海联通 210.22.97.1 联通4837[普通线路]
上海移动 211.136.112.200 移动CMI [普通线路]
广州电信 58.60.188.222 电信163 [普通线路]
广州联通 210.21.196.6 联通4837[普通线路]
广州移动 120.196.165.24 移动CMI [普通线路]
成都电信 61.139.2.69 电信163 [普通线路]
成都联通 119.6.6.6 联通4837[普通线路]
成都移动 211.137.96.205 移动CMI [普通线路]
2024/03/14 08:55:53 测试完成!
```
## 流媒体平台及游戏区域限制测试
```shell
** 正在测试IPv4解锁情况
--------------------------------
** 您的网络为: xTom (45.66.*.*)
============[ Multination ]============
Dazn: 原生解锁 Yes (Region: JP)
TikTok: 原生解锁 IDC IP (Region: JP)
HotStar: No
Disney+: No
Netflix: 原生解锁 Originals Only
YouTube Premium: 原生解锁 Yes (Region: JP)
Amazon Prime Video: 原生解锁 Yes (Region: JP)
TVBAnywhere+: 原生解锁 Yes
iQyi Oversea Region: 原生解锁 JP
Viu.com: No
YouTube CDN: Tokyo
Netflix Preferred CDN: Tokyo
Spotify Registration: No
Steam Currency: JPY
ChatGPT: 原生解锁 Yes
Bing Region: JP
Instagram Licensed Audio: ->
Instagram Licensed Audio: No
=======================================
** 正在测试IPv6解锁情况
--------------------------------
** 您的网络为: xTom (2a12:a300:3600:*:*)
============[ Multination ]============
Dazn: Failed (Network Connection)
TikTok: 原生解锁 Yes (Region: JP)
HotStar: No
Disney+: 原生解锁 Yes (Region: JP)
Netflix: 原生解锁 Yes (Region: JP)
YouTube Premium: 原生解锁 Yes (Region: JP)
Amazon Prime Video: Unsupported
TVBAnywhere+: Failed (Network Connection)
iQyi Oversea Region: Failed
Viu.com: Failed
YouTube CDN: Tokyo
Netflix Preferred CDN: Tokyo
Spotify Registration: No
Steam Currency: Failed (Network Connection)
ChatGPT: Failed
Bing Region: JP
Instagram Licensed Audio: ->
Instagram Licensed Audio: No
=======================================
本次测试已结束，感谢使用此脚本
```
## autotrace具体路由测试
```shell
[信息] Nexttrace最新版本为 v1.2.9
[信息] Nexttrace_x64 下载完成 !
[信息] Debian Nexttrace 检测已下载 !
No:1/9 Traceroute to 中国 深圳 电信 (TCP Mode, Max 30 Hop, IPv4)
===================================================================
NextTrace v1.2.9 2024-03-04T14:32:40Z f96c3e5
[NextTrace API] preferred API IP - 172.67.155.192 - 204.47ms - Misaka.HKG
IP Geo Data Provider: LeoMoeAPI
traceroute to 59.36.216.1, 30 hops max, 52 bytes packets
1 45.66.217.1 AS23959 日本 东京都 东京 owl.net
3.50 ms
2 *
3 91.200.240.71 AS23959 [OWL-JP] 日本 东京都 东京 owl.net
0.66 ms
4 211.14.4.178 AS9607 [JPNIC-NET] 日本 东京都 东京 bbtower.co.jp
0.96 ms
5 172.29.0.10 * RFC1918
0.77 ms
6 210.138.130.225 AS2497 [APNIC-AP] 日本 东京都 东京 iij.ad.jp
1.84 ms
7 58.138.98.53 AS2497 [IIJ] 日本 东京都 东京 iij.ad.jp
1.53 ms
8 58.138.100.206 AS2497 [IIJ] 日本 东京都 东京 iij.ad.jp
1.22 ms
9 203.215.236.65 AS4134 [CHINANET-FJ] 日本 东京都 东京 chinatelecom.com.cn 电信
37.36 ms
10 202.97.81.201 AS4134 [CHINANET-BB] 中国 北京 chinatelecom.com.cn 电信
54.82 ms
11 *
12 *
13 *
14 119.147.61.110 AS4134 [CHINANET-GD] 中国 广东 深圳 chinatelecom.com.cn 电信
59.92 ms
15 59.36.216.1 AS4134 中国 广东 江门市 chinatelecom.com.cn 电信
62.53 ms
No:2/9 Traceroute to 中国 上海 电信 (TCP Mode, Max 30 Hop, IPv4)
===================================================================
NextTrace v1.2.9 2024-03-04T14:32:40Z f96c3e5
[NextTrace API] preferred API IP - [2606:4700:3031::6815:28b0] - 218.47ms - Misaka.HKG
IP Geo Data Provider: LeoMoeAPI
traceroute to 101.226.41.65, 30 hops max, 52 bytes packets
1 45.66.217.1 AS23959 日本 东京都 东京 owl.net
0.90 ms
2 *
3 91.200.240.71 AS23959 [OWL-JP] 日本 东京都 东京 owl.net
1.14 ms
4 211.14.4.222 AS9607 [JPNIC-NET] 日本 东京都 东京 bbtower.co.jp
0.58 ms
5 172.29.0.10 * RFC1918
0.80 ms
6 210.138.130.225 AS2497 [APNIC-AP] 日本 东京都 东京 iij.ad.jp
2.91 ms
7 58.138.98.53 AS2497 [IIJ] 日本 东京都 东京 iij.ad.jp
1.97 ms
8 58.138.100.206 AS2497 [IIJ] 日本 东京都 东京 iij.ad.jp
1.56 ms
9 203.215.236.65 AS4134 [CHINANET-FJ] 日本 东京都 东京 chinatelecom.com.cn 电信
37.52 ms
10 *
11 *
12 *
13 *
14 *
15 *
16 101.226.41.65 AS4812 [CHINANET-SH] 中国 上海 chinatelecom.cn 电信
48.79 ms
No:3/9 Traceroute to 中国 北京 电信 (TCP Mode, Max 30 Hop, IPv4)
===================================================================
NextTrace v1.2.9 2024-03-04T14:32:40Z f96c3e5
[NextTrace API] preferred API IP - [2606:4700:3031::6815:28b0] - 203.94ms - Misaka.HKG
IP Geo Data Provider: LeoMoeAPI
traceroute to 220.181.53.1, 30 hops max, 52 bytes packets
1 *
2 *
3 91.200.240.71 AS23959 [OWL-JP] 日本 东京都 东京 owl.net
0.66 ms
4 211.14.4.222 AS9607 [JPNIC-NET] 日本 东京都 东京 bbtower.co.jp
0.75 ms
5 172.29.0.10 * RFC1918
0.71 ms
6 210.138.130.225 AS2497 [APNIC-AP] 日本 东京都 东京 iij.ad.jp
1.79 ms
7 58.138.98.53 AS2497 [IIJ] 日本 东京都 东京 iij.ad.jp
12.38 ms
8 58.138.101.58 AS2497 [IIJ] 日本 东京都 东京 iij.ad.jp
1.60 ms
9 203.215.236.65 AS4134 [CHINANET-FJ] 日本 东京都 东京 chinatelecom.com.cn 电信
37.32 ms
10 *
11 *
12 202.97.51.205 AS4134 [CHINANET-BB] 中国 上海 chinatelecom.com.cn
41.20 ms
13 *
14 *
15 *
16 *
17 220.181.53.1 AS23724 [CHINANET-IDC] 中国 北京 bjtelecom.net 电信
70.46 ms
No:4/9 Traceroute to 中国 广州 联通 (TCP Mode, Max 30 Hop, IPv4)
===================================================================
NextTrace v1.2.9 2024-03-04T14:32:40Z f96c3e5
[NextTrace API] preferred API IP - 104.21.40.176 - 191.00ms - Misaka.HKG
IP Geo Data Provider: LeoMoeAPI
traceroute to 210.21.4.130, 30 hops max, 52 bytes packets
1 45.66.217.1 AS23959 日本 东京都 东京 owl.net
0.87 ms
2 *
3 91.200.240.71 AS23959 [OWL-JP] 日本 东京都 东京 owl.net
0.70 ms
4 211.14.4.222 AS9607 [JPNIC-NET] 日本 东京都 东京 bbtower.co.jp
0.73 ms
5 172.29.0.10 * RFC1918
1.03 ms
6 210.138.130.225 AS2497 [APNIC-AP] 日本 东京都 东京 iij.ad.jp
6.64 ms
7 *
8 *
9 *
10 219.158.12.229 AS4837 [CU169-BACKBONE] 中国 上海 X-I chinaunicom.cn 联通
56.12 ms
11 219.158.19.86 AS4837 [CU169-BACKBONE] 中国 上海 chinaunicom.cn 联通
74.58 ms
12 219.158.19.81 AS4837 [CU169-BACKBONE] 中国 上海 chinaunicom.cn 联通
63.70 ms
13 *
14 120.82.0.158 AS17816 [APNIC-AP] 中国 广东 广州 chinaunicom.cn 联通
138.32 ms
15 120.80.91.62 AS17816 [APNIC-AP] 中国 广东 广州 chinaunicom.cn 联通
69.62 ms
16 *
17 *
18 *
19 *
20 *
{"error":"Challenge does not exist or has expired"}
RetToken failed 3 times, please try again after a while, exit
No:5/9 Traceroute to 中国 上海 联通 (TCP Mode, Max 30 Hop, IPv4)
===================================================================
NextTrace v1.2.9 2024-03-04T14:32:40Z f96c3e5
[NextTrace API] preferred API IP - 104.21.40.176 - 344.68ms - Misaka.LAX
IP Geo Data Provider: LeoMoeAPI
traceroute to 112.65.95.129, 30 hops max, 52 bytes packets
1 45.66.217.1 AS23959 日本 东京都 东京 owl.net
1.52 ms
2 *
3 91.200.240.71 AS23959 [OWL-JP] 日本 东京都 东京 owl.net
0.88 ms
4 211.14.4.178 AS9607 [JPNIC-NET] 日本 东京都 东京 bbtower.co.jp
0.97 ms
5 172.29.0.10 * RFC1918
3.08 ms
6 210.138.130.225 AS2497 [APNIC-AP] 日本 东京都 东京 iij.ad.jp
1.89 ms
7 *
8 58.138.112.34 AS2497 [IIJ] 日本 东京都 东京 iij.ad.jp
22.08 ms
9 202.232.1.158 AS2497 [JPNIC-NET] 日本 东京都 东京 iij.ad.jp
55.53 ms
10 219.158.24.57 AS4837 [CU169-BACKBONE] 中国 上海 chinaunicom.cn 联通
68.28 ms
11 219.158.113.138 AS4837 [CU169-BACKBONE] 中国 上海 chinaunicom.cn 联通
60.62 ms
12 *
13 *
14 210.22.66.174 AS17621 [APNIC-AP] 中国 上海 chinaunicom.cn 联通
97.63 ms
15 112.65.95.129 AS17621 [APNIC-AP] 中国 上海 chinaunicom.cn 联通
47.85 ms
No:6/9 Traceroute to 中国 北京 联通 (TCP Mode, Max 30 Hop, IPv4)
===================================================================
NextTrace v1.2.9 2024-03-04T14:32:40Z f96c3e5
[NextTrace API] preferred API IP - 104.21.40.176 - 199.35ms - Misaka.HKG
IP Geo Data Provider: LeoMoeAPI
traceroute to 61.49.140.217, 30 hops max, 52 bytes packets
1 45.66.217.1 AS23959 日本 东京都 东京 owl.net
1.38 ms
2 *
3 91.200.240.71 AS23959 [OWL-JP] 日本 东京都 东京 owl.net
1.14 ms
4 211.14.4.178 AS9607 [JPNIC-NET] 日本 东京都 东京 bbtower.co.jp
0.69 ms
5 172.29.0.10 * RFC1918
0.93 ms
6 210.138.130.225 AS2497 [APNIC-AP] 日本 东京都 东京 iij.ad.jp
2.08 ms
7 58.138.98.77 AS2497 [IIJ] 日本 东京都 东京 iij.ad.jp
1.99 ms
8 *
9 *
10 219.158.24.57 AS4837 [CU169-BACKBONE] 中国 上海 chinaunicom.cn 联通
74.33 ms
11 219.158.8.173 AS4837 [CU169-BACKBONE] 中国 上海 chinaunicom.cn 联通
58.02 ms
12 219.158.7.133 AS4837 [CU169-BACKBONE] 中国 上海 chinaunicom.cn 联通
44.54 ms
13 219.158.6.189 AS4837 [CU169-BACKBONE] 中国 北京 chinaunicom.cn 联通
72.49 ms
14 *
15 *
16 61.49.140.217 AS4808 中国 北京 chinaunicom.cn 联通
118.27 ms
No:7/9 Traceroute to 中国 深圳 移动 (TCP Mode, Max 30 Hop, IPv4)
===================================================================
NextTrace v1.2.9 2024-03-04T14:32:40Z f96c3e5
[NextTrace API] preferred API IP - 104.21.40.176 - 192.86ms - Misaka.HKG
IP Geo Data Provider: LeoMoeAPI
traceroute to 120.233.53.1, 30 hops max, 52 bytes packets
1 45.66.217.1 AS23959 日本 东京都 东京 owl.net
3.07 ms
2 *
3 91.200.240.71 AS23959 [OWL-JP] 日本 东京都 东京 owl.net
0.56 ms
4 211.14.4.178 AS9607 [JPNIC-NET] 日本 东京都 东京 bbtower.co.jp
0.73 ms
5 172.29.0.11 * RFC1918
0.83 ms
6 *
7 4.69.226.254 AS3356 日本 东京都 东京 level3.com
9.37 ms
8 4.68.38.226 AS3356 日本 东京都 东京 level3.com
61.86 ms
9 223.120.2.189 AS58453 [CMI-INT] 日本 东京都 东京 cmi.chinamobile.com 移动
57.78 ms
10 223.120.2.182 AS58453 [CMI-INT] 中国 香港 cmi.chinamobile.com 移动
66.47 ms
11 221.183.55.58 AS9808 [CMNET] 中国 广东 广州 chinamobile.com 移动
85.14 ms
12 221.183.92.21 AS9808 [CMNET] 中国 广东 广州 chinamobile.com 移动
78.01 ms
13 *
14 *
15 211.136.204.74 AS56040 [CMNET] 中国 广东 广州 chinamobile.com 移动
79.18 ms
16 *
17 120.233.53.1 AS56040 [APNIC-AP] 中国 广东 深圳 chinamobile.com 移动
86.40 ms
No:8/9 Traceroute to 中国 上海 移动 (TCP Mode, Max 30 Hop, IPv4)
===================================================================
NextTrace v1.2.9 2024-03-04T14:32:40Z f96c3e5
[NextTrace API] preferred API IP - 104.21.40.176 - 195.66ms - Misaka.HKG
IP Geo Data Provider: LeoMoeAPI
traceroute to 183.194.216.129, 30 hops max, 52 bytes packets
1 45.66.217.1 AS23959 日本 东京都 东京 owl.net
11.50 ms
2 *
3 91.200.240.71 AS23959 [OWL-JP] 日本 东京都 东京 owl.net
0.89 ms
4 211.14.4.222 AS9607 [JPNIC-NET] 日本 东京都 东京 bbtower.co.jp
0.71 ms
5 172.29.0.10 * RFC1918
0.87 ms
6 210.138.130.225 AS2497 [APNIC-AP] 日本 东京都 东京 iij.ad.jp
1.79 ms
7 *
8 58.138.114.230 AS2497 [IIJ] 日本 东京都 东京 iij.ad.jp
1.80 ms
9 210.130.133.6 AS2497 [APNIC-AP] 日本 东京都 东京 iij.ad.jp
52.29 ms
10 *
11 221.183.89.174 AS9808 [CMNET] 中国 上海 回国到达层 chinamobile.com 移动
54.17 ms
12 221.183.89.33 AS9808 [CMNET] 中国 上海 chinamobile.com 移动
61.85 ms
13 *
14 *
15 *
16 183.194.216.129 AS9808 [APNIC-AP] 中国 上海 chinamobile.com 移动
112.09 ms
No:9/9 Traceroute to 中国 北京 移动 (TCP Mode, Max 30 Hop, IPv4)
===================================================================
NextTrace v1.2.9 2024-03-04T14:32:40Z f96c3e5
[NextTrace API] preferred API IP - [2606:4700:3031::6815:28b0] - 258.94ms - Misaka.HKG
IP Geo Data Provider: LeoMoeAPI
traceroute to 211.136.25.153, 30 hops max, 52 bytes packets
1 45.66.217.1 AS23959 日本 东京都 东京 owl.net
0.87 ms
2 *
3 91.200.240.71 AS23959 [OWL-JP] 日本 东京都 东京 owl.net
0.92 ms
4 211.14.4.178 AS9607 [JPNIC-NET] 日本 东京都 东京 bbtower.co.jp
0.65 ms
5 172.29.0.10 * RFC1918
0.70 ms
6 210.138.130.225 AS2497 [APNIC-AP] 日本 东京都 东京 iij.ad.jp
1.98 ms
7 *
8 58.138.114.254 AS2497 [IIJ] 日本 东京都 东京 iij.ad.jp
1.74 ms
9 210.130.133.6 AS2497 [APNIC-AP] 日本 东京都 东京 iij.ad.jp
52.39 ms
10 223.118.2.238 AS58453 [CMI-INT] 日本 东京都 东京 cmi.chinamobile.com 移动
55.36 ms
11 221.183.55.106 AS9808 [CMNET] 中国 北京 回国到达层 chinamobile.com 移动
89.42 ms
12 221.183.46.250 AS9808 [CMNET] 中国 北京 chinamobile.com 移动
98.32 ms
13 221.183.89.118 AS9808 [CMNET] 中国 北京 chinamobile.com 移动
98.20 ms
14 *
15 *
16 *
17 *
18 *
19 *
20 *
21 211.136.25.153 AS56048 [CMNET] 中国 北京 chinamobile.com 移动
99.85 ms
```