买
TYO Pro 上线
月付9折循环: tyo-10off
季付8折循环: tyo-20off
年付7折循环: tyo-30off
购买地址: https://nnc.sh/store/tyo-pro
测
系统信息
-> System Information
CPU Model Name: AMD EPYC 7B13 64-Core Processor
CPU Cache Size: L1: 128.00 KB / L2: 512.00 KB / L3: 16.00 MB
CPU Specifications: 1 vCPU(s)
Virtualization Ready: Yes (Based on AMD-V, Nested Virtualization Enabled)
Virtualization Type: KVM
Memory Usage: 135.02 MiB / 962.52 MiB
Swap Usage: [ no swap partition or swap file detected ]
Disk Usage: 1.53 GiB / 9.68 GiB
Boot Disk: /dev/sda1
OS Release: Debian GNU/Linux 11 (bullseye) (x86_64)
Kernel Version: 6.3.8-x64v1-xanmod1
-> Network Information
IPv4-IP Address: [AU] 5.226.50.*
IPv4-AS Information: AS38136 - Akari Networks
IPv4-GeoIP Location: Australia Victoria Melbourne
IPv6-IP Address: [JP] 2407:cdc0:8005::*
IPv6-AS Information: AS38136 - Akari Networks
IPv6-GeoIP Location: Japan Tokyo Tokyo
硬件性能
-> CPU Performance Test (Fast mode, 1-Pass @ 5sec)
1 Thread(s) Test: 3609.12 Scores (1.00x)
-> Disk Performance Test (Using FIO, Direct mode, 32 IO-Depth)
Write Test (4K-Block): 328.95 MB/s (84210 IOPS)
Read Test (4K-Block): 471.70 MB/s (120754 IOPS)
Write Test (128K-Block): 2439.02 MB/s (19512 IOPS)
Read Test (128K-Block): 4347.83 MB/s (34782 IOPS)
YABS
Basic System Information:
---------------------------------
Uptime : 0 days, 0 hours, 22 minutes
Processor : AMD EPYC 7B13 64-Core Processor
CPU cores : 1 @ 2245.776 MHz
AES-NI : ✔ Enabled
VM-x/AMD-V : ✔ Enabled
RAM : 962.5 MiB
Swap : 0.0 KiB
Disk : 9.8 GiB
Distro : Debian GNU/Linux 11 (bullseye)
Kernel : 6.3.8-x64v1-xanmod1
VM Type : KVM
IPv4/IPv6 : ✔ Online / ✔ Online
IPv6 Network Information:
---------------------------------
ISP : Akari Networks (Tokyo)
ASN : AS38136 Akari Networks
Location : Tokyo, Tokyo (13)
Country : Japan
fio Disk Speed Tests (Mixed R/W 50/50):
---------------------------------
Block Size | 4k (IOPS) | 64k (IOPS)
------ | --- ---- | ---- ----
Read | 129.53 MB/s (32.3k) | 129.77 MB/s (2.0k)
Write | 129.87 MB/s (32.4k) | 130.45 MB/s (2.0k)
Total | 259.40 MB/s (64.8k) | 260.22 MB/s (4.0k)
| |
Block Size | 512k (IOPS) | 1m (IOPS)
------ | --- ---- | ---- ----
Read | 129.99 MB/s (253) | 126.91 MB/s (123)
Write | 136.90 MB/s (267) | 135.36 MB/s (132)
Total | 266.89 MB/s (520) | 262.27 MB/s (255)
iperf3 Network Speed Tests (IPv4):
---------------------------------
Provider | Location (Link) | Send Speed | Recv Speed | Ping
----- | ----- | ---- | ---- | ----
Clouvider | London, UK (10G) | busy | 860 Mbits/sec | 219 ms
Scaleway | Paris, FR (10G) | busy | busy | 240 ms
NovoServe | North Holland, NL (40G) | 708 Mbits/sec | 803 Mbits/sec | 240 ms
Uztelecom | Tashkent, UZ (10G) | busy | 1.28 Gbits/sec | 414 ms
Clouvider | NYC, NY, US (10G) | busy | 373 Mbits/sec | 170 ms
Clouvider | Dallas, TX, US (10G) | busy | 400 Mbits/sec | 141 ms
Clouvider | Los Angeles, CA, US (10G) | 686 Mbits/sec | 844 Mbits/sec | 116 ms
iperf3 Network Speed Tests (IPv6):
---------------------------------
Provider | Location (Link) | Send Speed | Recv Speed | Ping
----- | ----- | ---- | ---- | ----
Clouvider | London, UK (10G) | 732 Mbits/sec | 965 Mbits/sec | 219 ms
Scaleway | Paris, FR (10G) | busy | 1.94 Gbits/sec | 209 ms
NovoServe | North Holland, NL (40G) | 718 Mbits/sec | 725 Mbits/sec | 236 ms
Uztelecom | Tashkent, UZ (10G) | busy | 1.28 Gbits/sec | 362 ms
Clouvider | NYC, NY, US (10G) | busy | 1.22 Gbits/sec | 168 ms
Clouvider | Dallas, TX, US (10G) | 1.25 Gbits/sec | 1.52 Gbits/sec | 141 ms
Clouvider | Los Angeles, CA, US (10G) | 1.56 Gbits/sec | 1.92 Gbits/sec | 116 ms
speedtest
国内
————————————————————————————————————————————————————————————————————
测速服务器信息 ↑ 上传/Mbps ↓ 下载/Mbps ↕ 延迟/ms ϟ 抖动/ms
————————————————————————————————————————————————————————————————————
电信|上海 ↑ 1036.9 正常 ↓ 167.2 正常 ↕ 33.1 ϟ 4.9
电信|江苏镇江5G ↑ 869.2 正常 ↓ 211.0 正常 ↕ 37.0 ϟ 5.9
电信|江苏南京5G ↑ 1770.2 正常 ↓ 112.2 正常 ↕ 34.9 ϟ 4.2
电信|安徽合肥5G ↑ 1080.0 正常 ↓ 68.4 正常 ↕ 38.1 ϟ 4.9
电信|天津5G ↑ 1010.3 正常 ↓ 24.6 正常 ↕ 50.1 ϟ 13.1
电信|天津 ↑ 1275.6 正常 ↓ 82.1 正常 ↕ 52.9 ϟ 3.0
电信|四川成都 ↑ 11.4 正常 ↓ 3.7 正常 ↕ 105.9 ϟ 228.7
电信|甘肃兰州 ↑ 131.2 正常 ↓ 32.4 正常 ↕ 65.1 ϟ 3.0
联通|河南郑州5G ↑ 1843.9 正常 ↓ 140.4 正常 ↕ 84.4 ϟ 5.5
联通|湖南长沙5G ↑ 129.9 正常 ↓ 4.0 正常 ↕ 246.6 ϟ 17.5
联通|辽宁沈阳 ↑ 3.7 正常 ↓ 1.4 正常 ↕ 284.7 ϟ 6.9
联通|福建福州 ↑ 1189.7 正常 ↓ 13.3 正常 ↕ 80.7 ϟ 6.8
移动|北京 ↑ 3984.1 正常 ↓ 3671.2 正常 ↕ 87.7 ϟ 3.0
流媒体
** 测试时间: Thu Oct 19 19:08:41 CST 2023
** 正在测试IPv4解锁情况
--------------------------------
** 您的网络为: Pasargad Network (5.226.*.*)
============[ Multination ]============
Dazn: Yes (Region: JP)
HotStar: Yes (Region: SG)
Disney+: Yes (Region: JP)
Netflix: Yes (Region: JP)
YouTube Premium: Yes (Region: JP)
Amazon Prime Video: Yes (Region: JP)
TVBAnywhere+: Yes
iQyi Oversea Region: JP
Viu.com: Yes (Region: HK)
YouTube CDN: PITTIX in Pittsburgh, PA
Netflix Preferred CDN: Tokyo
Spotify Registration: No
Steam Currency: JPY
ChatGPT: Yes
=======================================
===============[ Japan ]===============
DMM: Yes
DMM TV: Yes
Abema.TV: Yes
Niconico: Yes
music.jp: Yes
Telasa: Yes
U-NEXT: Failed (Network Connection)
Hulu Japan: Yes
TVer: Yes
GYAO!: Yes
WOWOW: Failed
VideoMarket: Failed (Unexpected Result: 404)
FOD(Fuji TV): Yes
Radiko: Yes (City: TOKYO)
Karaoke@DAM: Yes
J:com On Demand: Yes
---Game---
Kancolle Japan: No
Pretty Derby Japan: Yes
Konosuba Fantastic Days: Yes
Princess Connect Re:Dive Japan: Yes
World Flipper Japan: Yes
Project Sekai: Colorful Stage: Yes
=======================================
** 正在测试IPv6解锁情况
--------------------------------
** 您的网络为: Akari Networks (2407:cdc0:8005:*:*)
============[ Multination ]============
Dazn: Failed (Network Connection)
HotStar: Yes (Region: SG)
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: Yes
=======================================
===============[ Japan ]===============
DMM: Unsupported
DMM TV: Unsupported
Abema.TV: Failed (Network Connection)
Niconico: Failed (Network Connection)
music.jp: No
Telasa: Failed (Network Connection)
Paravi: Failed (Network Connection)
U-NEXT: Failed (Network Connection)
Hulu Japan: Yes
TVer: Failed (Network Connection)
GYAO!: IPv6 Not Supported
WOWOW: Failed
VideoMarket: IPv6 Not Supported
FOD(Fuji TV): No
Radiko: Unsupported
Karaoke@DAM: Failed (Network Connection)
J:com On Demand: Failed (Network Connection)
---Game---
Kancolle Japan: No
Pretty Derby Japan: Failed (Network Connection)
Konosuba Fantastic Days: Failed (Network Connection)
Princess Connect Re:Dive Japan: Failed (Network Connection)
World Flipper Japan: Yes
Project Sekai: Colorful Stage: Failed (Network Connection)
=======================================
本次测试已结束,感谢使用此脚本
traceroute
感谢 nexttrace
北京电信
[+] Traceroute to China Telecom (Beijing, IPv4) (ICMP Mode, Max 30 Hops)
NextTrace v1.2.0 2023-08-30T12:49:35Z ce46abd
[NextTrace API] prefered API IP - 104.19.29.108 - 0.66ms
IP Geo Data Provider: LeoMoeAPI
traceroute to 45.126.112.33, 30 hops max, 52 bytes packets
1 5.226.50.254 0.25ms AS38136, Tokyo, Tokyo, Japan, akari.net
2 210.173.169.129 1.03ms *, Tokyo, Tokyo, Japan
3 58.138.114.225 1.21ms AS2497, Tokyo, Tokyo, Japan, iij.ad.jp
4 58.138.98.233 4.17ms AS2497, Tokyo, Tokyo, Japan, iij.ad.jp
5 58.138.100.206 1.42ms AS2497, Tokyo, Tokyo, Japan, iij.ad.jp
6 203.215.236.65 1.85ms AS4134, Tokyo, Tokyo, Japan, chinatelecom.com.cn 电信
7 202.97.6.65 33.83ms AS4134, Shanghai, China, chinatelecom.com.cn 电信
8 202.97.74.2 36.50ms AS4134, Shanghai, China, chinatelecom.com.cn 电信
9 202.97.24.169 35.80ms AS4134, Shanghai, China, chinatelecom.com.cn 电信
10 *
11 *
12 *
13 *
14 36.112.226.154 70.93ms AS4847, Beijing, China, chinatelecom.cn
15 1.202.147.202 75.98ms AS4847, Beijing, China, chinatelecom.cn 电信
16 *
17 *
18 45.126.112.33 81.04ms AS4847, Beijing, China, chinatelecom.cn
上海电信
[+] Traceroute to China Telecom (Shanghai, IPv4) (ICMP Mode, Max 30 Hops)
NextTrace v1.2.0 2023-08-30T12:49:35Z ce46abd
[NextTrace API] prefered API IP - 104.19.29.108 - 0.59ms
IP Geo Data Provider: LeoMoeAPI
traceroute to 210.5.157.1, 30 hops max, 52 bytes packets
1 5.226.50.254 0.26ms AS38136, Tokyo, Tokyo, Japan, akari.net
2 210.173.169.129 0.93ms *, Tokyo, Tokyo, Japan
3 58.138.114.249 1.28ms AS2497, Tokyo, Tokyo, Japan, iij.ad.jp
4 58.138.98.241 1.17ms AS2497, Tokyo, Tokyo, Japan, iij.ad.jp
5 58.138.100.206 1.37ms AS2497, Tokyo, Tokyo, Japan, iij.ad.jp
6 203.215.236.65 2.06ms AS4134, Tokyo, Tokyo, Japan, chinatelecom.com.cn 电信
7 202.97.70.29 30.92ms AS4134, Shanghai, China, chinatelecom.com.cn 电信
8 *
9 *
10 *
11 124.74.54.178 33.38ms AS4812, Shanghai, China, chinatelecom.cn 电信
12 58.40.245.94 35.38ms AS4812, Shanghai, China, chinatelecom.cn 电信
13 *
14 *
15 210.5.157.1 34.14ms AS4812, Shanghai, China, chinatelecom.cn 电信
上海电信CN2
NextTrace v1.2.0 2023-08-30T12:49:35Z ce46abd
[NextTrace API] prefered API IP - [2606:4700:3030::ac43:cd76] - 0.63ms
IP Geo Data Provider: LeoMoeAPI
traceroute to 58.32.0.1, 30 hops max, 52 bytes packets
1 5.226.50.254 0.28ms AS38136, Tokyo, Tokyo, Japan, akari.net
2 206.148.24.35 0.31ms AS7578, globalsecurelayer.com , globalsecurelayer.com
3 206.148.24.34 0.39ms AS7578, globalsecurelayer.com , globalsecurelayer.com
4 206.148.24.47 0.50ms AS7578, Tokyo, Tokyo, Japan, globalsecurelayer.com
5 206.148.24.66 79.20ms AS7578, globalsecurelayer.com , globalsecurelayer.com
6 206.148.24.70 79.47ms AS7578, globalsecurelayer.com , globalsecurelayer.com
7 206.148.24.75 79.36ms AS7578, globalsecurelayer.com , globalsecurelayer.com
8 103.16.102.53 81.56ms AS4809, chinatelecom.com.cn , chinatelecom.com.cn
9 59.43.249.234 143.46ms *, Shanghai, China, chinatelecom.cn 电信
10 *
11 59.43.138.49 149.31ms *, Shanghai, China, chinatelecom.cn 电信
12 101.95.88.218 87.67ms AS4812, Shanghai, China, chinatelecom.cn 电信
13 58.32.0.1 143.81ms AS4812, Shanghai, China, chinatelecom.cn 电信
广州电信
[+] Traceroute to China Telecom (Guangzhou, IPv4) (ICMP Mode, Max 30 Hops)
NextTrace v1.2.0 2023-08-30T12:49:35Z ce46abd
[NextTrace API] prefered API IP - 104.19.29.108 - 0.60ms
IP Geo Data Provider: LeoMoeAPI
traceroute to 113.108.209.1, 30 hops max, 52 bytes packets
1 5.226.50.254 0.25ms AS38136, Tokyo, Tokyo, Japan, akari.net
2 210.173.169.129 0.95ms *, Tokyo, Tokyo, Japan
3 58.138.114.249 1.55ms AS2497, Tokyo, Tokyo, Japan, iij.ad.jp
4 58.138.98.241 1.82ms AS2497, Tokyo, Tokyo, Japan, iij.ad.jp
5 58.138.100.54 1.22ms AS2497, Tokyo, Tokyo, Japan, iij.ad.jp
6 203.215.237.9 2.21ms *, Tokyo, Tokyo, Japan, 电信
7 *
8 202.97.66.226 52.32ms AS4134, Guangzhou, Guangdong, China, chinatelecom.com.cn 电信
9 *
10 *
11 113.108.209.1 58.92ms AS4134, Guangzhou, Guangdong, China, chinatelecom.com.cn 电信
北京联通
[+] Traceroute to China Unicom (Beijing, IPv4) (ICMP Mode, Max 30 Hops)
NextTrace v1.2.0 2023-08-30T12:49:35Z ce46abd
[NextTrace API] prefered API IP - 104.26.8.231 - 0.60ms
IP Geo Data Provider: LeoMoeAPI
traceroute to 113.209.132.146, 30 hops max, 52 bytes packets
1 5.226.50.254 0.33ms AS38136, Tokyo, Tokyo, Japan, akari.net
2 206.148.24.35 0.33ms AS7578, globalsecurelayer.com , globalsecurelayer.com
3 206.148.24.34 0.36ms AS7578, globalsecurelayer.com , globalsecurelayer.com
4 206.148.24.47 0.47ms AS7578, Tokyo, Tokyo, Japan, globalsecurelayer.com
5 206.148.24.30 28.83ms AS7578, globalsecurelayer.com , globalsecurelayer.com
6 206.148.24.29 98.80ms AS7578, globalsecurelayer.com , globalsecurelayer.com
7 206.148.24.3 231.71ms AS7578, globalsecurelayer.com , globalsecurelayer.com
8 206.148.27.251 231.47ms AS7578, Washington, Washington, D.C., United States, globalsecurelayer.com
9 64.124.129.52 231.57ms AS6461, Los Angeles, California, United States, zayo.com
10 *
11 64.125.27.39 231.62ms AS6461, Los Angeles, California, United States, zayo.com
12 64.125.14.186 299.11ms AS6461, Los Angeles, California, United States, zayo.com
13 219.158.98.149 305.54ms AS4837, Guangzhou, Guangdong, China, chinaunicom.cn 联通
14 219.158.97.30 306.03ms AS4837, Guangzhou, Guangdong, China, chinaunicom.cn 联通
15 *
16 219.158.112.25 322.51ms AS4837, Beijing, China, chinaunicom.cn 联通
17 *
18 *
19 *
20 *
21 *
22 *
23 *
24 113.209.132.146 408.08ms AS4808, Beijing, China, chinaunicom.cn 联通
上海联通AS9929
[+] Traceroute to China Unicom CUII/AS9929 (Shanghai, IPv4) (ICMP Mode, Max 30 Hops)
NextTrace v1.2.0 2023-08-30T12:49:35Z ce46abd
[NextTrace API] prefered API IP - 104.19.29.108 - 0.54ms
IP Geo Data Provider: LeoMoeAPI
traceroute to 210.13.66.238, 30 hops max, 52 bytes packets
1 5.226.50.254 0.21ms AS38136, Tokyo, Tokyo, Japan, akari.net
2 *
3 101.203.107.81 4.31ms *, Tokyo, Tokyo, Japan, Softbank
4 *
5 *
6 221.111.203.2 169.04ms AS17676, San Jose, California, United States, softbank.jp
7 219.158.97.181 181.30ms AS4837, Shanghai, China, chinaunicom.cn 联通
8 219.158.39.210 181.41ms AS4837, Shanghai, China, chinaunicom.cn 联通
9 218.105.2.205 182.11ms AS9929, Shanghai, China, chinaunicom.cn 联通 CUII
10 218.105.2.210 190.05ms AS9929, Shanghai, China, chinaunicom.cn 联通 CUII
11 210.13.116.82 181.14ms AS9929, Shanghai, China, chinaunicom.cn 联通 CUII
12 *
13 210.13.64.110 185.39ms AS9929, Shanghai, China, chinaunicom.cn 联通 CUII
14 210.13.66.237 184.54ms AS9929, Shanghai, China, chinaunicom.cn 联通 CUII
15 210.13.66.238 194.52ms AS9929, Shanghai, China, chinaunicom.cn 联通 CUII
广州联通
[+] Traceroute to China Unicom (Guangzhou, IPv4) (ICMP Mode, Max 30 Hops)
NextTrace v1.2.0 2023-08-30T12:49:35Z ce46abd
[NextTrace API] prefered API IP - 104.19.29.108 - 0.59ms
IP Geo Data Provider: LeoMoeAPI
traceroute to 210.21.4.130, 30 hops max, 52 bytes packets
1 5.226.50.254 0.28ms AS38136, Tokyo, Tokyo, Japan, akari.net
2 *
3 101.203.107.85 3.41ms *, Tokyo, Tokyo, Japan, Softbank
4 *
5 *
6 *
7 *
8 221.111.202.70 82.34ms AS17676, Beijing, China, softbank.jp
9 219.158.115.158 87.45ms AS4837, Guangzhou, Guangdong, China, chinaunicom.cn 联通
10 219.158.3.165 93.72ms AS4837, Guangzhou, Guangdong, China, chinaunicom.cn 联通
11 219.158.3.33 94.96ms AS4837, Guangzhou, Guangdong, China, chinaunicom.cn 联通
12 120.83.0.58 91.67ms AS17816, Guangzhou, Guangdong, China, chinaunicom.cn 联通
13 120.80.175.78 99.10ms AS17622, Guangzhou, Guangdong, China, chinaunicom.cn 联通
14 210.21.4.130 92.59ms AS17622, Guangzhou, Guangdong, China, chinaunicom.cn 联通
北京移动
[+] Traceroute to China Mobile (Beijing, IPv4) (ICMP Mode, Max 30 Hops)
NextTrace v1.2.0 2023-08-30T12:49:35Z ce46abd
[NextTrace API] prefered API IP - 104.19.29.108 - 0.68ms
IP Geo Data Provider: LeoMoeAPI
traceroute to 183.242.65.12, 30 hops max, 52 bytes packets
1 5.226.50.254 0.20ms AS38136, Tokyo, Tokyo, Japan, akari.net
2 210.173.169.129 0.94ms *, Tokyo, Tokyo, Japan
3 210.130.133.6 1.55ms AS2497, Tokyo, Tokyo, Japan, iij.ad.jp
4 223.118.3.26 1.85ms AS58453, Tokyo, Tokyo, Japan, cmi.chinamobile.com 移动
5 223.120.2.210 92.29ms AS58453, Beijing, China, cmi.chinamobile.com 移动
6 221.183.55.106 88.19ms AS9808, Beijing, China, chinamobile.com 移动
7 221.183.46.250 89.84ms AS9808, Beijing, China, chinamobile.com 移动
8 221.183.89.102 92.85ms AS9808, Beijing, China, chinamobile.com 移动
9 *
10 221.179.158.30 93.07ms AS56048, Beijing, China, chinamobile.com 移动
11 *
12 223.70.199.10 96.88ms AS56048, Beijing, China, chinamobile.com 移动
13 *
14 *
15 183.242.65.12 94.74ms AS56048, Beijing, China, chinamobile.com 移动
上海移动
[+] Traceroute to China Mobile (Shanghai, IPv4) (ICMP Mode, Max 30 Hops)
NextTrace v1.2.0 2023-08-30T12:49:35Z ce46abd
[NextTrace API] prefered API IP - 104.19.29.108 - 0.56ms
IP Geo Data Provider: LeoMoeAPI
traceroute to 117.144.213.77, 30 hops max, 52 bytes packets
1 5.226.50.254 0.45ms AS38136, Tokyo, Tokyo, Japan, akari.net
2 210.173.169.129 1.09ms *, Tokyo, Tokyo, Japan
3 210.130.133.6 1.65ms AS2497, Tokyo, Tokyo, Japan, iij.ad.jp
4 223.120.2.162 55.48ms AS58453, Tokyo, Tokyo, Japan, cmi.chinamobile.com 移动
5 221.183.89.174 81.04ms AS9808, Shanghai, China, chinamobile.com 移动
6 *
7 *
8 221.183.39.130 99.68ms AS9808, Shanghai, China, chinamobile.com 移动
9 211.136.190.242 95.94ms AS24400, Shanghai, China, chinamobile.com 移动
10 *
11 117.144.213.77 97.99ms AS24400, Shanghai, China, chinamobile.com 移动
广州移动
[+] Traceroute to China Mobile (Guangzhou, IPv4) (ICMP Mode, Max 30 Hops)
NextTrace v1.2.0 2023-08-30T12:49:35Z ce46abd
[NextTrace API] prefered API IP - 104.19.29.108 - 0.50ms
IP Geo Data Provider: LeoMoeAPI
traceroute to 183.232.48.167, 30 hops max, 52 bytes packets
1 5.226.50.254 0.50ms AS38136, Tokyo, Tokyo, Japan, akari.net
2 210.173.169.129 1.08ms *, Tokyo, Tokyo, Japan
3 58.138.114.229 1.19ms AS2497, Tokyo, Tokyo, Japan, iij.ad.jp
4 58.138.88.13 3.06ms AS2497, Tokyo, Tokyo, Japan, iij.ad.jp
5 58.138.81.174 54.37ms AS2497, Hong Kong, China, iij.ad.jp
6 210.130.133.10 57.12ms AS2497, Tokyo, Tokyo, Japan, iij.ad.jp
7 *
8 223.120.22.118 81.17ms AS58453, Shanghai, China, cmi.chinamobile.com 移动
9 221.183.89.178 58.13ms AS9808, Shanghai, China, chinamobile.com 移动
10 221.183.89.33 82.12ms AS9808, Shanghai, China, chinamobile.com 移动
11 221.183.89.14 96.65ms AS9808, Shanghai, China, chinamobile.com 移动
12 *
13 *
14 *
15 *
16 183.232.48.167 123.96ms AS56040, Guangzhou, Guangdong, China, chinamobile.com 移动
评
流媒体已经很尽力了!三网用起来都还不错(电信移动走iij,联通走sb,如果未直连需要提交工单反馈)的日本VPS~
跟上次lite一样(上次忘了说了)用的是 XanMod 魔改内核,魔改了什么内容可以参考 -> https://xanmod.org/ 划重点Google's BBRv3 TCP congestion control
评论区