JustHost俄罗斯莫斯科DataLine机房VPS怎么样?JustHost俄罗斯莫斯科DataLine机房VPS好不好?J俄罗斯莫斯科DataLine机房VPS怎么样?JustHost俄罗斯莫斯科DataLine机房VPS带宽质量怎么样?俄罗斯莫斯科DataLine机房VPS支持解锁哪些流媒体?俄罗斯莫斯科DataLine机房VPS适合哪些地区访问?下面一起看看俄罗斯莫斯科DataLine机房VPS性能及带宽质量测评结果。
JustHost是一家来自俄罗斯的商家,JustHost一直从事便宜的俄罗斯VPS,目前JustHost有俄罗斯6个机房选择,美国有达拉斯VPS、洛杉矶VPS可以选择,德国有法兰克福VPS,芬兰VPS(赫尔辛基)、加拿大VPS(多伦多)法国VPS(巴黎)、荷兰VPS、波兰VPS(华沙)、西班牙VPS(马德里)、英国VPS(伦敦),目前JustHost新上线香港VPS、意大利VPS(巴勒莫)、美国亚特兰大VPS和拉脱维亚VPS、20个机房的VPS可选!JustHost最大的特点是价格便宜,提供中文官网支持、200Mbps峰值带宽、不限月流量、最低只需大约是$1.6/月起,每台VPS支持免费更换5次IP!性价比高不高这个毋庸置疑了!
官方网站:https://justhost.asia
JustHost当前官方新增了多种加密货币的付款方式,具体包括:Etherium, Bitcoin Cash, Dash, Litecoin, Zcach, USDT (TRC-20), USDT (ERC-20), Tron, TRX;原来的付款方式依旧支持:信用卡、PayPal、支付宝、银联、webmoney、苹果pay、谷歌Pay等。
VPS介绍:
所有VPS均为KVM虚拟,最低给200M带,不限流量,自定义选择VPS配置的时候依次选择:操作系统、数据中心、CPU核心、内存、硬盘大小、带宽、IPv4、IPv6、付款周期、硬盘类型(SAS、SSD、NVMe)
- 8折优惠码:LET20 ,续费不涨价!
VPS资源DIY购买:https://justhost.asia/zh/services/vps
1、JustHost俄罗斯莫斯科DataLine机房VPS测评机器基本信息测试结果。KVM架构,E5-2697 v4处理器,1核512M内存,已经进行BBR网络优化!HDD硬盘读写速度为63.0 MB/s,HDD硬盘读写速度较为一般。
----------------------------------------------------------------------
CPU Model : Intel(R) Xeon(R) CPU E5-2697 v4 @ 2.30GHz
CPU Cores : 1 @ 2297.338 MHz
CPU Cache : 16384 KB
AES-NI : Enabled
VM-x/AMD-V : Disabled
Total Disk : 5.8 GB (2.0 GB Used)
Total Mem : 475.9 MB (92.4 MB Used)
System uptime : 0 days, 0 hour 9 min
Load average : 0.00, 0.00, 0.00
OS : CentOS Linux release 7.9.2009 (Core)
Arch : x86_64 (64 Bit)
Kernel : 5.10.159-1.el7.x86_64
TCP CC : bbr
Virtualization : KVM
Organization : AS51659 LLC Baxet
Location : Moscow / RU
Region : Moscow
----------------------------------------------------------------------
I/O Speed(1st run) : 62.9 MB/s
I/O Speed(2nd run) : 63.1 MB/s
I/O Speed(3rd run) : 63.1 MB/s
I/O Speed(average) : 63.0 MB/s
----------------------------------------------------------------------
2、JustHost俄罗斯莫斯科DataLine机房VPS到全球哪里地方延迟低?从782全球节点ping延迟测试来看,到欧洲地区速度较好58.3毫秒,其次是国内速度在150毫秒左右,再次是北美洲和非洲地区!总体来说到全球速度都较为不错!
线路 | 节点数目 | 最快节点 | 最慢节点 | 平均响应 |
---|---|---|---|---|
全部 | 782 | 俄罗斯莫斯科(ZENLAYER-MOW3) 1.2 毫秒 | 江苏南通(移动) 1024.1 毫秒 | 157.9 毫秒 |
联通线路 | 50 | 北京(联通) 100.0 毫秒 | 江苏南京(联通) 205.0 毫秒 | 133.5 毫秒 |
电信线路 | 75 | 天津(电信) 93.9 毫秒 | 广东广州(联通) 574.1 毫秒 | 136.3 毫秒 |
移动线路 | 39 | 河南郑州(联通-west.cn) 123.6 毫秒 | 江苏南通(移动) 1024.1 毫秒 | 227.5 毫秒 |
东北地区 | 16 | 辽宁沈阳(电信) 104.6 毫秒 | 辽宁沈阳(移动云) 222.5 毫秒 | 142.4 毫秒 |
华北地区 | 31 | 天津(电信) 93.9 毫秒 | 北京(青云三区A) 280.0 毫秒 | 130.6 毫秒 |
西北地区 | 13 | 陕西西安(天翼云二区) 107.3 毫秒 | 陕西西安(电信) 394.5 毫秒 | 164.6 毫秒 |
西南地区 | 27 | 贵州贵阳(联通云) 131.1 毫秒 | 云南昆明(移动云) 242.2 毫秒 | 165.9 毫秒 |
华中地区 | 19 | 河南郑州(天翼云) 102.6 毫秒 | 河南郑州(移动) 217.7 毫秒 | 147.2 毫秒 |
华东地区 | 87 | 山东济南(电信-xf) 103.9 毫秒 | 江苏南通(移动) 1024.1 毫秒 | 159.1 毫秒 |
华南地区 | 28 | 广东广州(腾讯云) 124.2 毫秒 | 广东广州(联通) 574.1 毫秒 | 174.6 毫秒 |
港澳台 | 44 | 香港(咕咕云) 176.8 毫秒 | 香港2(无忧云) 324.7 毫秒 | 244.7 毫秒 |
亚洲 | 122 | 哈萨克斯坦阿拉木图(ps.kz) 53.6 毫秒 | 日本大阪(AMAZON) 372.3 毫秒 | 222.1 毫秒 |
欧洲 | 184 | 俄罗斯莫斯科(ZENLAYER-MOW3) 1.2 毫秒 | 瑞典法尔肯贝里(glesys.se) 400.8 毫秒 | 58.3 毫秒 |
大洋洲 | 22 | 澳大利亚珀斯 247.6 毫秒 | 澳大利亚墨尔本(ZENLAYER-MEL1) 337.1 毫秒 | 306.2 毫秒 |
北美洲 | 136 | 美国波士顿(axcelx.com) 112.8 毫秒 | 美国西雅图(virmach.com) 321.8 毫秒 | 163.1 毫秒 |
南美洲 | 33 | 巴西福塔莱萨(gcorelabs) 190.1 毫秒 | 巴西贝洛奥里藏特 277.5 毫秒 | 232.8 毫秒 |
非洲 | 20 | 埃及开罗 88.3 毫秒 | 南非约翰内斯堡(华为云) 247.9 毫秒 | 190.6 毫秒 |
国外 | 517 | 俄罗斯莫斯科(ZENLAYER-MOW3) 1.2 毫秒 | 瑞典法尔肯贝里(glesys.se) 400.8 毫秒 | 151.3 毫秒 |
3、JustHost俄罗斯莫斯科DataLine机房VPS到国内三网延迟高不高?从220个国内电信、联通、移动ping测试结果来看,三网平均延迟153.4毫秒,算较为不错的了!其中电信、联通延迟都较为不错在130毫秒以内,移动延迟相对搞一点平均延迟240毫秒了!所以JustHost俄罗斯莫斯科DataLine机房VPS从延迟来看电信、联通用户比较适合,移动相对差一点!
线路 | 节点数目 | 最快节点 | 最慢节点 | 平均响应 |
---|---|---|---|---|
全部 | 220 | 北京(天翼云) 92.7 毫秒 | 江苏南通(移动) 1603.1 毫秒 | 153.4 毫秒 |
联通线路 | 50 | 北京(联通) 100.9 毫秒 | 陕西西安(联通) 332.4 毫秒 | 135.5 毫秒 |
电信线路 | 75 | 北京(天翼云) 92.7 毫秒 | 陕西西安(移动云) 213.0 毫秒 | 126.8 毫秒 |
移动线路 | 39 | 河南郑州(联通-west.cn) 123.5 毫秒 | 江苏南通(移动) 1603.1 毫秒 | 241.0 毫秒 |
东北地区 | 16 | 辽宁大连(电信) 106.6 毫秒 | 辽宁沈阳(移动云) 220.0 毫秒 | 140.8 毫秒 |
华北地区 | 31 | 北京(天翼云) 92.7 毫秒 | 北京(青云三区A) 280.0 毫秒 | 131.0 毫秒 |
西北地区 | 13 | 陕西西安(天翼云二区) 109.1 毫秒 | 陕西西安(联通) 332.4 毫秒 | 157.4 毫秒 |
西南地区 | 27 | 贵州贵阳(联通云) 131.1 毫秒 | 四川眉山2(移动) 244.8 毫秒 | 165.6 毫秒 |
华中地区 | 19 | 河南郑州(天翼云) 102.6 毫秒 | 湖北襄阳(移动云) 211.1 毫秒 | 145.9 毫秒 |
华东地区 | 87 | 山东济宁(CN2) 103.1 毫秒 | 江苏南通(移动) 1603.1 毫秒 | 162.9 毫秒 |
华南地区 | 27 | 广东广州(腾讯云-轻量) 123.8 毫秒 | 广东广州(移动) 223.1 毫秒 | 146.6 毫秒 |
4、JustHost俄罗斯莫斯科DataLine机房VPS到国内电信、联通、移动是否可以跑满200M带宽限制?从测速节点来看,国内三网可以跑满200M上下行带宽限制。
----------------------------------------------------------------------
Node Name Upload Speed Download Speed Latency
Speedtest.net 180.64 Mbps 192.08 Mbps 0.63 ms
Shanghai CT 194.21 Mbps 191.91 Mbps 122.42 ms
HeFei 5G CT 201.05 Mbps 160.35 Mbps 125.04 ms
Nanjing 5G CT 195.61 Mbps 190.85 Mbps 116.96 ms
SuZhou 5G CT 205.03 Mbps 190.96 Mbps 116.45 ms
YangZhou 5G CT 202.49 Mbps 190.21 Mbps 120.28 ms
Wuhan 5G CT 193.65 Mbps 190.96 Mbps 128.95 ms
ChangSha 5G CT 188.78 Mbps 200.40 Mbps 135.33 ms
Shanghai 5G CU 200.34 Mbps 184.71 Mbps 125.15 ms
WuXi CU 203.50 Mbps 174.21 Mbps 123.20 ms
ChangSha CU 198.11 Mbps 9.51 Mbps 135.38 ms
ShenYang CU 168.14 Mbps 160.27 Mbps 126.96 ms
ZhenZhou 5G CM 177.47 Mbps 188.71 Mbps 195.15 ms
BeiJing CM 193.20 Mbps 148.31 Mbps 188.42 ms
ChengDou CM 169.49 Mbps 128.75 Mbps 253.78 ms
----------------------------------------------------------------------
Finished in : 8 min 48 sec
Timestamp : 2022-12-16 04:32:42 MSK
----------------------------------------------------------------------
5、JustHost俄罗斯莫斯科DataLine机房VPS亚太香港、台湾、日本、韩国、新加坡、北美美国及加拿大和欧洲地区能否跑满200M上下带宽限制?从测速节点看上述地区所有节点都是可以跑满200M左右上下行的!
----------------------------------------------------------------------
Node Name Upload Speed Download Speed Latency
Speedtest.net 175.72 Mbps 190.61 Mbps 0.59 ms
Hong Kong CN 194.40 Mbps 183.53 Mbps 188.46 ms
Hong Kong CN 176.92 Mbps 166.99 Mbps 223.27 ms
Macau CN 179.62 Mbps 202.35 Mbps 242.13 ms
Taiwan CN 155.35 Mbps 188.11 Mbps 299.38 ms
Singapore SG 177.74 Mbps 190.81 Mbps 181.75 ms
Singapore SG 187.86 Mbps 187.76 Mbps 209.15 ms
Tokyo JP 157.22 Mbps 181.10 Mbps 277.25 ms
Tokyo JP 169.20 Mbps 196.20 Mbps 230.49 ms
Seoul KR 158.50 Mbps 89.38 Mbps 265.09 ms
Los Angeles US 195.40 Mbps 191.77 Mbps 181.85 ms
Los Angeles US 190.96 Mbps 190.98 Mbps 183.92 ms
Dallas US 203.64 Mbps 186.40 Mbps 155.59 ms
Montreal CA 202.65 Mbps 188.76 Mbps 120.78 ms
France FR 207.12 Mbps 193.96 Mbps 63.25 ms
Paris FR 210.31 Mbps 190.47 Mbps 47.42 ms
Amsterdam NL 211.73 Mbps 189.42 Mbps 43.18 ms
----------------------------------------------------------------------
Finished in : 10 min 7 sec
Timestamp : 2022-12-16 04:48:10 MSK
----------------------------------------------------------------------
6、JustHost俄罗斯莫斯科DataLine机房VPS电信、联通、移动三网去程线路怎么样?直不直连,走什么线路?从JustHost俄罗斯莫斯科DataLine机房VPS去程路由追踪看,电信、联通去程是直连俄罗斯的,移动去程先绕线欧洲国家!电信去程走CN2 GT线路到俄罗斯,联通去程走AS4837线路到俄罗斯对接TTK线路到机房,移动去程CMI先到欧洲再对接LEVEL3线路到俄罗斯!
7、JustHost俄罗斯莫斯科DataLine机房VPS国内电信、联通、移动三网回程是否直连?回程线路怎么样?从JustHost俄罗斯莫斯科DataLine机房VPS国内三网回程路由追踪测试结果来看,电信回程走CN2直连、联通回程也走CN2直连、移动回程也走CN2直连!
----------------------------------------------------------------------
上海电信
traceroute to 101.95.120.109 (101.95.120.109), 30 hops max, 32 byte packets
1 45.129.2.1 0.75 ms AS51659 Russian Federation, Moscow, iteleport.ru
2 *
3 *
4 145.14.89.1 1.24 ms * Russian Federation, Moscow, cteurope.net
5 59.43.246.17 89.07 ms * China, Beijing, ChinaTelecom
6 59.43.247.126 202.39 ms * China, Shanghai, ChinaTelecom
7 *
8 *
9 *
10 101.95.120.109 121.06 ms AS4812 China, Shanghai, ChinaTelecom
----------------------------------------------------------------------
广州电信
traceroute to 14.215.116.1 (14.215.116.1), 30 hops max, 32 byte packets
1 45.129.2.1 18.30 ms AS51659 Russian Federation, Moscow, iteleport.ru
2 *
3 *
4 145.14.89.1 1.31 ms * Russian Federation, Moscow, cteurope.net
5 59.43.246.17 101.90 ms * China, Beijing, ChinaTelecom
6 59.43.182.246 124.74 ms * China, Guangdong, Guangzhou, ChinaTelecom
7 59.43.245.30 125.93 ms * China, ChinaTelecom
8 202.97.91.193 138.94 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom
9 202.97.91.5 144.15 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom
10 *
11 183.2.167.253 250.10 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom
12 183.56.129.2 261.34 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom
13 14.215.116.1 286.01 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom
----------------------------------------------------------------------
北京电信
traceroute to 219.141.147.210 (219.141.147.210), 30 hops max, 32 byte packets
1 45.129.2.1 113.10 ms AS51659 Russian Federation, Moscow, iteleport.ru
2 *
3 *
4 145.14.89.1 141.33 ms * Russian Federation, Moscow, cteurope.net
5 59.43.246.17 207.07 ms * China, Beijing, ChinaTelecom
6 59.43.246.142 175.17 ms * China, Beijing, ChinaTelecom
7 202.97.58.93 169.71 ms AS4134 China, Beijing, ChinaTelecom
8 202.97.53.9 183.64 ms AS4134 China, Beijing, ChinaTelecom
9 *
10 6.254.120.106.static.bjtelecom.net (106.120.254.6) 244.11 ms AS4847 China, Beijing, ChinaTelecom
11 bj141-147-210.bjtelecom.net (219.141.147.210) 242.92 ms AS4847 China, Beijing, ChinaTelecom
----------------------------------------------------------------------
杭州电信
traceroute to 60.176.0.1 (60.176.0.1), 30 hops max, 32 byte packets
1 45.129.2.1 148.75 ms AS51659 Russian Federation, Moscow, iteleport.ru
2 *
3 *
4 145.14.89.1 76.27 ms * Russian Federation, Moscow, cteurope.net
5 59.43.246.17 218.18 ms * China, Beijing, ChinaTelecom
6 59.43.182.226 239.97 ms * China, Shanghai, ChinaTelecom
7 *
8 *
9 *
10 202.97.102.6 220.35 ms AS4134 China, Zhejiang, Hangzhou, ChinaTelecom
11 *
12 60.176.0.1 150.72 ms AS4134 China, Zhejiang, Hangzhou, ChinaTelecom
----------------------------------------------------------------------
贵阳电信
traceroute to 58.42.224.1 (58.42.224.1), 30 hops max, 32 byte packets
1 45.129.2.1 4.85 ms AS51659 Russian Federation, Moscow, iteleport.ru
2 *
3 *
4 145.14.89.1 1.24 ms * Russian Federation, Moscow, cteurope.net
5 59.43.246.17 89.08 ms * China, Beijing, ChinaTelecom
6 59.43.247.98 141.36 ms * China, Guangdong, Guangzhou, ChinaTelecom
7 59.43.244.138 153.00 ms * China, Guangdong, Guangzhou, ChinaTelecom
8 *
9 202.97.71.237 122.65 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom
10 202.97.97.30 139.10 ms AS4134 China, Guizhou, Guiyang, ChinaTelecom
11 61.189.177.158 163.90 ms AS4134 China, Guizhou, Guiyang, ChinaTelecom
12 58.42.224.1 140.96 ms AS4134 China, Guizhou, Guiyang, ChinaTelecom
----------------------------------------------------------------------
深圳电信
traceroute to 58.60.188.222 (58.60.188.222), 30 hops max, 32 byte packets
1 45.129.2.1 0.54 ms AS51659 Russian Federation, Moscow, iteleport.ru
2 *
3 *
4 145.14.89.1 1.31 ms * Russian Federation, Moscow, cteurope.net
5 59.43.246.17 89.04 ms * China, Beijing, ChinaTelecom
6 59.43.182.246 124.70 ms * China, Guangdong, Guangzhou, ChinaTelecom
7 59.43.244.130 125.40 ms * China, Guangdong, Guangzhou, ChinaTelecom
8 202.97.12.46 154.51 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom
9 202.97.94.141 125.88 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom
10 14.147.127.94 128.24 ms AS134774 China, Guangdong, Shenzhen, ChinaTelecom
11 *
12 58.60.188.222 127.79 ms AS4134 China, Guangdong, Shenzhen, ChinaTelecom
----------------------------------------------------------------------
上海联通
traceroute to 210.22.97.1 (210.22.97.1), 30 hops max, 32 byte packets
1 45.129.2.1 0.50 ms AS51659 Russian Federation, Moscow, iteleport.ru
2 *
3 *
4 145.14.89.1 1.55 ms * Russian Federation, Moscow, cteurope.net
5 59.43.246.17 89.18 ms * China, Beijing, ChinaTelecom
6 59.43.182.226 116.83 ms * China, Shanghai, ChinaTelecom
7 *
8 *
9 202.97.71.33 117.71 ms AS4134 China, Shanghai, ChinaTelecom
10 202.97.87.158 120.94 ms AS4134 China, Shanghai, ChinaTelecom
11 *
12 219.158.8.225 128.90 ms AS4837 China, Shanghai, ChinaUnicom
13 *
14 112.64.250.202 135.07 ms AS17621 China, Shanghai, ChinaUnicom
15 210.22.97.1 125.32 ms AS17621 China, Shanghai, ChinaUnicom
----------------------------------------------------------------------
广州联通
traceroute to 210.21.4.130 (210.21.4.130), 30 hops max, 32 byte packets
1 45.129.2.1 15.07 ms AS51659 Russian Federation, Moscow, iteleport.ru
2 *
3 *
4 145.14.89.1 1.29 ms * Russian Federation, Moscow, cteurope.net
5 59.43.246.17 93.85 ms * China, Beijing, ChinaTelecom
6 59.43.247.98 125.26 ms * China, Guangdong, Guangzhou, ChinaTelecom
7 59.43.244.138 132.45 ms * China, Guangdong, Guangzhou, ChinaTelecom
8 202.97.91.146 140.55 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom
9 202.97.22.57 163.94 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom
10 *
11 *
12 *
13 120.86.0.182 223.24 ms AS17816 China, Guangdong, Guangzhou, ChinaUnicom
14 120.80.79.186 227.22 ms AS17622 China, Guangdong, Guangzhou, ChinaUnicom
15 gz1-dns.gdgz.cncnet.net (210.21.4.130) 237.54 ms AS17622 China, Guangdong, Guangzhou, ChinaUnicom
----------------------------------------------------------------------
北京联通
traceroute to 202.106.50.1 (202.106.50.1), 30 hops max, 32 byte packets
1 45.129.2.1 0.72 ms AS51659 Russian Federation, Moscow, iteleport.ru
2 *
3 *
4 145.14.89.1 1.36 ms * Russian Federation, Moscow, cteurope.net
5 59.43.246.17 91.55 ms * China, Beijing, ChinaTelecom
6 59.43.246.142 89.55 ms * China, Beijing, ChinaTelecom
7 *
8 202.97.61.137 161.73 ms AS4134 China, Beijing, ChinaTelecom
9 *
10 *
11 *
12 202.96.12.66 130.14 ms AS4808 China, Beijing, ChinaUnicom
13 202.106.50.1 174.42 ms AS4808 China, Beijing, ChinaUnicom
----------------------------------------------------------------------
杭州联通
traceroute to 221.12.1.227 (221.12.1.227), 30 hops max, 32 byte packets
1 45.129.2.1 45.08 ms AS51659 Russian Federation, Moscow, iteleport.ru
2 *
3 *
4 145.14.89.1 26.71 ms * Russian Federation, Moscow, cteurope.net
5 59.43.246.17 95.55 ms * China, Beijing, ChinaTelecom
6 59.43.182.226 256.64 ms * China, Shanghai, ChinaTelecom
7 *
8 202.97.50.194 192.83 ms AS4134 China, Shanghai, ChinaTelecom
9 202.97.61.85 122.92 ms AS4134 China, Shanghai, ChinaTelecom
10 202.97.23.226 123.00 ms AS4134 China, Zhejiang, Jinhua, ChinaTelecom
11 *
12 *
13 219.158.7.193 140.31 ms AS4837 China, Zhejiang, Hangzhou, ChinaUnicom
14 *
15 *
16 221.12.1.227 125.11 ms AS4837 China, Zhejiang, Hangzhou, ChinaUnicom
----------------------------------------------------------------------
贵阳联通
traceroute to 58.16.28.1 (58.16.28.1), 30 hops max, 32 byte packets
1 45.129.2.1 28.69 ms AS51659 Russian Federation, Moscow, iteleport.ru
2 *
3 *
4 145.14.89.1 3.24 ms * Russian Federation, Moscow, cteurope.net
5 59.43.246.17 116.60 ms * China, Beijing, ChinaTelecom
6 59.43.182.246 150.07 ms * China, Guangdong, Guangzhou, ChinaTelecom
7 59.43.244.134 166.88 ms * China, Guangdong, Guangzhou, ChinaTelecom
8 202.97.94.97 140.59 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom
9 202.97.72.1 168.52 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom
10 202.97.96.122 141.69 ms AS4134 China, Guizhou, Guiyang, ChinaTelecom
11 *
12 *
13 219.158.99.217 155.75 ms AS4837 China, Guizhou, Guiyang, ChinaUnicom
14 58.16.18.62 151.83 ms AS4837 China, Guizhou, Guiyang, ChinaUnicom
15 58.16.28.1 142.04 ms AS4837 China, Guizhou, Guiyang, ChinaUnicom
----------------------------------------------------------------------
深圳联通
traceroute to 210.21.196.6 (210.21.196.6), 30 hops max, 32 byte packets
1 45.129.2.1 129.84 ms AS51659 Russian Federation, Moscow, iteleport.ru
2 *
3 *
4 145.14.89.1 151.48 ms * Russian Federation, Moscow, cteurope.net
5 59.43.246.17 240.52 ms * China, Beijing, ChinaTelecom
6 59.43.182.246 238.51 ms * China, Guangdong, Guangzhou, ChinaTelecom
7 59.43.245.30 179.80 ms * China, ChinaTelecom
8 202.97.94.97 219.73 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom
9 202.97.82.61 251.27 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom
10 *
11 *
12 *
13 *
14 120.80.144.38 399.55 ms AS17623 China, Guangdong, Shenzhen, ChinaUnicom
15 dns2-ftcg.gdsz.cncnet.net (210.21.196.6) 176.19 ms AS17623 China, Guangdong, Shenzhen, ChinaUnicom
----------------------------------------------------------------------
上海移动
traceroute to 211.136.112.200 (211.136.112.200), 30 hops max, 32 byte packets
1 45.129.2.1 0.62 ms AS51659 Russian Federation, Moscow, iteleport.ru
2 *
3 *
4 145.14.89.1 1.44 ms * Russian Federation, Moscow, cteurope.net
5 59.43.246.17 89.51 ms * China, Beijing, ChinaTelecom
6 59.43.182.226 123.78 ms * China, Shanghai, ChinaTelecom
7 *
8 *
9 *
10 202.97.87.134 123.84 ms AS4134 China, Shanghai, ChinaTelecom
11 *
12 *
13 *
14 211.136.190.234 189.16 ms AS24400 China, Shanghai, ChinaMobile
15 211.136.112.252 189.42 ms AS24400 China, Shanghai, ChinaMobile
16 211.136.112.200 206.63 ms AS24400 China, Shanghai, ChinaMobile
----------------------------------------------------------------------
广州移动
traceroute to 221.183.90.217 (221.183.90.217), 30 hops max, 32 byte packets
1 45.129.2.1 0.65 ms AS51659 Russian Federation, Moscow, iteleport.ru
2 *
3 *
4 145.14.89.1 1.41 ms * Russian Federation, Moscow, cteurope.net
5 59.43.246.17 105.91 ms * China, Beijing, ChinaTelecom
6 59.43.246.154 89.68 ms * China, Beijing, ChinaTelecom
7 202.97.12.49 94.82 ms AS4134 China, Beijing, ChinaTelecom
8 202.97.34.73 97.26 ms AS4134 China, Beijing, ChinaTelecom
9 *
10 *
11 *
12 221.183.90.217 205.82 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile
----------------------------------------------------------------------
北京移动
traceroute to 221.130.33.1 (221.130.33.1), 30 hops max, 32 byte packets
1 45.129.2.1 0.56 ms AS51659 Russian Federation, Moscow, iteleport.ru
2 *
3 *
4 145.14.89.1 19.09 ms * Russian Federation, Moscow, cteurope.net
5 59.43.246.17 89.01 ms * China, Beijing, ChinaTelecom
6 59.43.246.142 89.51 ms * China, Beijing, ChinaTelecom
7 202.97.58.85 90.85 ms AS4134 China, Beijing, ChinaTelecom
8 *
9 *
10 221.183.86.45 188.65 ms AS9808 China, Beijing, ChinaMobile
11 *
12 221.183.76.102 189.59 ms AS9808 China, Beijing, ChinaMobile
13 211.136.66.121 191.50 ms AS56048 China, Beijing, ChinaMobile
14 *
15 211.136.58.118 197.14 ms AS56048 China, Beijing, ChinaMobile
16 221.130.33.1 190.17 ms AS56048 China, Beijing, ChinaMobile
----------------------------------------------------------------------
杭州移动
traceroute to 211.140.13.188 (211.140.13.188), 30 hops max, 32 byte packets
1 45.129.2.1 0.54 ms AS51659 Russian Federation, Moscow, iteleport.ru
2 *
3 *
4 145.14.89.1 1.52 ms * Russian Federation, Moscow, cteurope.net
5 59.43.246.17 89.21 ms * China, Beijing, ChinaTelecom
6 59.43.182.226 116.67 ms * China, Shanghai, ChinaTelecom
7 *
8 *
9 *
10 202.97.23.230 197.85 ms AS4134 China, Zhejiang, Jinhua, ChinaTelecom
11 *
12 *
13 *
14 *
15 221.183.71.78 342.13 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile
16 221.183.110.166 352.04 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile
17 ns3.zj.chinamobile.com (211.140.13.188) 386.11 ms AS56041 China, Zhejiang, Hangzhou, ChinaMobile
----------------------------------------------------------------------
贵阳移动
traceroute to 211.139.0.10 (211.139.0.10), 30 hops max, 32 byte packets
1 45.129.2.1 166.59 ms AS51659 Russian Federation, Moscow, iteleport.ru
2 *
3 *
4 145.14.89.1 122.87 ms * Russian Federation, Moscow, cteurope.net
5 59.43.246.17 292.01 ms * China, Beijing, ChinaTelecom
6 59.43.182.246 288.41 ms * China, Guangdong, Guangzhou, ChinaTelecom
7 *
8 202.97.38.94 260.54 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom
9 202.97.90.157 265.30 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom
10 202.97.97.26 288.63 ms AS4134 China, Guizhou, Guiyang, ChinaTelecom
11 *
12 221.183.95.97 359.24 ms AS9808 China, Guizhou, Guiyang, ChinaMobile
13 221.183.90.161 361.23 ms AS9808 China, Guizhou, Guiyang, ChinaMobile
14 211.139.0.10 361.36 ms AS9808 China, Guizhou, Guiyang, ChinaMobile
----------------------------------------------------------------------
深圳移动
traceroute to 120.196.165.24 (120.196.165.24), 30 hops max, 32 byte packets
1 45.129.2.1 178.78 ms AS51659 Russian Federation, Moscow, iteleport.ru
2 *
3 *
4 145.14.89.1 146.35 ms * Russian Federation, Moscow, cteurope.net
5 59.43.246.17 185.72 ms * China, Beijing, ChinaTelecom
6 59.43.182.246 215.84 ms * China, Guangdong, Guangzhou, ChinaTelecom
7 *
8 202.97.91.193 252.02 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom
9 202.97.91.129 252.20 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom
10 *
11 *
12 *
13 221.183.71.82 353.17 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile
14 221.183.110.170 328.21 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile
15 ns6.gd.cnmobile.net (120.196.165.24) 284.39 ms AS56040 China, Guangdong, Shenzhen, ChinaMobile
----------------------------------------------------------------------
8、JustHost俄罗斯莫斯科DataLine机房VPS支持解锁哪些流媒体?下面是JustHost俄罗斯莫斯科DataLine机房VPS流媒体解锁测试。从测评结果看不支持解锁Netflix、Disney+等流媒体。
** 测试时间: Fri Dec 16 04:50:05 MSK 2022
** 正在测试IPv4解锁情况
--------------------------------
** 您的网络为: LLC Baxet (45.129.*.*)
============[ Multination ]============
Dazn: No
HotStar: No
Disney+: Failed
Netflix: No
YouTube Premium: No
Amazon Prime Video: Yes (Region: RU)
TVBAnywhere+: Yes
iQyi Oversea Region: INTL
Viu.com: No
YouTube CDN: St. Petersburg
Netflix Preferred CDN: ->nslookup: couldn't get address for 'Available': not found
Netflix Preferred CDN: Failed (CDN IP Not Found)
Spotify Registration: No
Steam Currency: RUB
=======================================
===============[ Europe ]==============
Rakuten TV: Yes
Funimation: No
SkyShowTime: Failed (Network Connection)
HBO Max: No
---GB---
Sky Go: No
BritBox: Yes
ITV Hub: No
Channel 4: No
Channel 5: No
BBC iPLAYER: No
Discovery+ UK: No
---FR---
Salto: No
Canal+: No
Molotov: No
---DE---
Joyn: No
Sky: No
ZDF: No
---NL---
NLZIET: Failed
videoland: Failed (Network Connection)
NPO Start Plus: No
---ES---
PANTAYA: No
---IT---
Rai Play: Yes
---RU---
Amediateka: Yes
=======================================
** 正在测试IPv6解锁情况
--------------------------------
** 您的网络为: LLC Baxet (2a00:b700::*:*)
============[ Multination ]============
Dazn: Failed (Network Connection)
HotStar: No
Disney+: Available For [Disney+ RU] Soon
Netflix: No
YouTube Premium: No
Amazon Prime Video: Unsupported
TVBAnywhere+: Failed (Network Connection)
iQyi Oversea Region: Failed
Viu.com: Failed
YouTube CDN: Moscow
Netflix Preferred CDN: ->nslookup: couldn't get address for 'Available': not found
Netflix Preferred CDN: Failed (CDN IP Not Found)
Steam Currency:ation: Failed (Network Connection) ->
=======================================
===============[ Europe ]==============
Rakuten TV: Failed (Network Connection)
Funimation: IPv6 Not Support
SkyShowTime: Failed (Network Connection)
HBO Max: Failed (Network Connection)
---GB---
Sky Go: Failed (Network Connection)
BritBox: Yes
ITV Hub: Failed (Network Connection)
Channel 4: Failed (Network Connection)
Channel 5: IPv6 Not Support
BBC iPLAYER: Failed
Discovery+ UK: IPv6 Not Support
---FR---
Salto: No
Canal+: Failed (Network Connection)
Molotov: No
---DE---
Joyn: Failed (Network Connection)
Sky: Failed (Network Connection)
ZDF: Failed (Network Connection)
---NL---
NLZIET: Failed
videoland: Failed (Network Connection)
NPO Start Plus: Failed (Network Connection)
---ES---
PANTAYA: Failed (Network Connection)
---IT---
Rai Play: Failed (Network Connection)
---RU---
Amediateka: Failed (Network Connection)
=======================================