关于JustHost俄罗斯圣彼得堡VPS怎么样？此文章对JustHost俄罗斯圣彼得堡VPS测评！通过JustHost俄罗斯圣彼得堡VPS带宽质量及流媒体解锁测评结果可以了解关于带宽质量及流媒体解锁测评结果如下疑问：JustHost俄罗斯圣彼得堡VPS好不好？JustHost俄罗斯圣彼得堡VPS线路怎么样？JustHost俄罗斯圣彼得堡VPS国内直连吗？JustHost俄罗斯圣彼得堡VPS带宽能否跑满？JustHost俄罗斯圣彼得堡VPS支持解锁哪些流媒体？JustHost俄罗斯圣彼得堡VPS适合全球哪些地区直连访问？JustHost俄罗斯圣彼得堡VPS适不适合国内直连？JustHost俄罗斯圣彼得堡VPS适合什么业务？
JustHost国外便宜VPS商家当中比较受欢迎的商家之一！是一家成立于2006年的俄罗斯老商家！目前JustHost VPS有多达20个机房可以选择，其中欧美、香港机房有14个，俄罗斯机房有6个！JustHost目前提供中文官网和中文工单支持，同时JustHost还支持支付宝购买！JustHost VPS最大的优势是价格便宜且不限流量！目前JustHost VPS最便宜的折后只需7元左右/月起！JustHost VPS支持免费更换5次机房或者5次IP（更换机房强制更换IP）！其中JustHost VPS欧美、香港机房只支持在欧美、香港机房之间切换，不可切换到俄罗斯机房；俄罗斯机房VPS只支持在俄罗斯6个机房切换，不可切换到欧美、香港机房！
本文重点测评的是JustHost俄罗斯圣彼得堡VPS带宽质量及流媒体解锁测评，不列举JustHost VPS套餐，如果有需求，可以查看下面文章去考虑选择购买！关于JustHost VPS支付宝购买教程、JustHost VPS机房切换教程、JustHost VPS免费更换IP教程、JustHost VPS重装系统教程、JustHost VPS全部套餐整理、JustHost VPS机房测评文章整理、JustHost VPS机房测速IP整理都在下面文章当中！
一、JustHost俄罗斯圣彼得堡VPS测评小结
1、JustHost俄罗斯圣彼得堡VPS对于国内用户来说直连是不太友好的，延迟相对较高，电信240毫秒左右、联通180毫秒左右、移动340毫秒左右，线路方面电信去程绕欧洲、联通去程直连、移动去程绕美国，回程方面电信绕欧洲、联通部分绕美国部分绕欧部分直连、移动绕欧！
2、JustHost俄罗斯圣彼得堡VPS带宽质量方面，国内联通基本可以跑满200M上下行带宽、电信、联通150M左右，国际方向测试节点基本可以跑满200M上下行带宽！
3、JustHost俄罗斯圣彼得堡VPS流媒体解锁方面，从测试结果看不支持解锁Disney+和Netflix等流媒体！
4、JustHost俄罗斯圣彼得堡VPS总体来说适合欧洲和北美业务，到这两个地区延迟较低！
二、JustHost俄罗斯圣彼得堡VPS测评结果记录
JustHost俄罗斯圣彼得堡VPS出自IQ Data (Tier-3)机房，下面测评使用的是HDD硬盘1核512M内存套餐，KVM架构、200M带宽不限流量，已经进行了BBR网络优化处理！
1、JustHost俄罗斯圣彼得堡VPS基本信息测试！KVM架构！核512M内存！符合真实信息！硬盘为HDD，读写速度63.0 MB/s，虽然不算优秀，但是可以满足一般业务需求了！
---------------------------------------------------------------------- CPU Model : Intel(R) Xeon(R) CPU E5-2697 v3 @ 2.60GHz CPU Cores : 1 @ 2596.990 MHz CPU Cache : 16384 KB AES-NI : Enabled VM-x/AMD-V : Enabled Total Disk : 5.8 GB (2.0 GB Used) Total Mem : 475.9 MB (92.6 MB Used) System uptime : 0 days, 2 hour 33 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 : Yekaterinburg / RU Region : Sverdlovsk Oblast ---------------------------------------------------------------------- I/O Speed(1st run) : 63.0 MB/s I/O Speed(2nd run) : 63.0 MB/s I/O Speed(3rd run) : 63.1 MB/s I/O Speed(average) : 63.0 MB/s ----------------------------------------------------------------------
2、JustHost俄罗斯圣彼得堡VPS全球各地延迟情况怎么样？适合哪些地区访问？从788测速节点来看JustHost俄罗斯圣彼得堡VPS适合欧洲地区、北美地区、非洲地区业务，此三个地区延迟在200毫秒以内！
| 线路 | 节点数目 | 最快节点 | 最慢节点 | 平均响应 |
|---|---|---|---|---|
| 全部 | 788 | 俄罗斯圣彼得堡(veesp.com) 1.5 毫秒 | 山东济南(移动) 431.7 毫秒 | 173.9 毫秒 |
| 联通线路 | 50 | 内蒙古呼和浩特(联通云) 122.5 毫秒 | 安徽滁州(电信) 226.2 毫秒 | 172.3 毫秒 |
| 电信线路 | 75 | 天津(电信) 176.8 毫秒 | 陕西西安(移动云) 293.0 毫秒 | 225.2 毫秒 |
| 移动线路 | 39 | 山东青岛(联通) 155.0 毫秒 | 山东济南(移动) 431.7 毫秒 | 322.8 毫秒 |
| 东北地区 | 16 | 吉林延边(联通) 159.6 毫秒 | 辽宁沈阳(移动) 348.9 毫秒 | 228.9 毫秒 |
| 华北地区 | 32 | 内蒙古呼和浩特(联通云) 122.5 毫秒 | 天津(移动) 345.2 毫秒 | 212.0 毫秒 |
| 西北地区 | 13 | 甘肃兰州(联通云) 171.3 毫秒 | 陕西西安(移动) 344.5 毫秒 | 216.7 毫秒 |
| 西南地区 | 27 | 贵州贵阳(联通云) 148.5 毫秒 | 四川眉山2(移动) 404.8 毫秒 | 253.8 毫秒 |
| 华中地区 | 19 | 湖南长沙(联通) 168.8 毫秒 | 河南郑州(移动云) 415.2 毫秒 | 242.4 毫秒 |
| 华东地区 | 89 | 山东枣庄(联通) 141.6 毫秒 | 山东济南(移动) 431.7 毫秒 | 238.0 毫秒 |
| 华南地区 | 27 | 广东深圳(联通云) 165.4 毫秒 | 广东深圳(移动) 305.6 毫秒 | 231.3 毫秒 |
| 港澳台 | 44 | 香港(PoloCloud) 190.0 毫秒 | 香港(CN2) 326.8 毫秒 | 250.4 毫秒 |
| 亚洲 | 121 | 哈萨克斯坦阿拉木图(ps.kz) 60.2 毫秒 | 蒙古乌兰巴托 366.6 毫秒 | 210.7 毫秒 |
| 欧洲 | 185 | 俄罗斯圣彼得堡(veesp.com) 1.5 毫秒 | 瑞典法尔肯贝里(glesys.se) 268.9 毫秒 | 49.4 毫秒 |
| 大洋洲 | 23 | 澳大利亚珀斯 242.9 毫秒 | 澳大利亚墨尔本(ZENLAYER-MEL1) 339.1 毫秒 | 294.4 毫秒 |
| 北美洲 | 139 | 美国锡考克斯(virmach.com) 106.1 毫秒 | 美国西雅图(virmach.com) 330.7 毫秒 | 154.7 毫秒 |
| 南美洲 | 33 | 巴西福塔莱萨(gcorelabs) 182.4 毫秒 | 巴西贝洛奥里藏特 277.9 毫秒 | 222.5 毫秒 |
| 非洲 | 20 | 埃及开罗 80.2 毫秒 | 南非约翰内斯堡(华为云) 238.6 毫秒 | 181.6 毫秒 |
| 国外 | 521 | 俄罗斯圣彼得堡(veesp.com) 1.5 毫秒 | 蒙古乌兰巴托 366.6 毫秒 | 141.8 毫秒 |
3、JustHost俄罗斯圣彼得堡VPS国内电信、联通、移动三网访问延迟怎么样？从224个节点的ping测速结果看国内三网平均ping延迟241.8 毫秒！其中联通平均186.0毫秒、电信228.2毫秒、移动338.9毫秒！相对来说联通速度好一丢丢！
| 线路 | 节点数目 | 最快节点 | 最慢节点 | 平均响应 |
|---|---|---|---|---|
| 全部 | 224 | 内蒙古呼和浩特(联通云) 139.5 毫秒 | 浙江杭州(移动) 491.7 毫秒 | 241.8 毫秒 |
| 联通线路 | 50 | 内蒙古呼和浩特(联通云) 139.5 毫秒 | 安徽滁州(电信) 249.8 毫秒 | 186.0 毫秒 |
| 电信线路 | 75 | 天津(电信) 177.8 毫秒 | 陕西西安(移动云) 293.0 毫秒 | 228.2 毫秒 |
| 移动线路 | 39 | 山东青岛(联通) 161.0 毫秒 | 浙江杭州(移动) 491.7 毫秒 | 338.9 毫秒 |
| 东北地区 | 16 | 辽宁沈阳(联通) 171.1 毫秒 | 辽宁沈阳LM2(移动) 355.2 毫秒 | 234.9 毫秒 |
| 华北地区 | 32 | 内蒙古呼和浩特(联通云) 139.5 毫秒 | 天津(移动) 400.0 毫秒 | 222.0 毫秒 |
| 西北地区 | 13 | 陕西西安(联通) 189.3 毫秒 | 陕西西安(移动) 344.6 毫秒 | 224.4 毫秒 |
| 西南地区 | 27 | 贵州贵阳(联通云) 167.3 毫秒 | 四川眉山2(移动) 443.2 毫秒 | 269.2 毫秒 |
| 华中地区 | 19 | 湖南长沙(联通) 168.7 毫秒 | 河南郑州(移动云) 451.6 毫秒 | 252.1 毫秒 |
| 华东地区 | 89 | 山东枣庄(联通) 141.7 毫秒 | 浙江杭州(移动) 491.7 毫秒 | 242.7 毫秒 |
| 华南地区 | 28 | 广西南宁(联通) 178.4 毫秒 | 广东深圳(移动) 305.8 毫秒 | 239.8 毫秒 |
4、JustHost俄罗斯圣彼得堡VPS到国内电信、联通、移动是否可以跑满200M带宽限制？从测试结果来看，国内三网基本可以跑满150M带宽以上，其中联通表现比较友好一点200M上行带宽基本跑满！
---------------------------------------------------------------------- Node Name Upload Speed Download Speed Latency Speedtest.net 208.55 Mbps 200.63 Mbps 7.78 ms Shanghai CT 147.55 Mbps 201.66 Mbps 217.09 ms HeFei 5G CT 131.56 Mbps 193.86 Mbps 223.49 ms Nanjing 5G CT 176.54 Mbps 195.47 Mbps 205.49 ms SuZhou 5G CT 187.47 Mbps 195.73 Mbps 220.43 ms YangZhou 5G CT 155.14 Mbps 196.90 Mbps 200.25 ms Wuhan 5G CT 120.69 Mbps 202.07 Mbps 214.23 ms ChangSha 5G CT 147.83 Mbps 204.62 Mbps 231.87 ms Shanghai 5G CU 164.76 Mbps 186.34 Mbps 278.06 ms WuXi CU 194.83 Mbps 192.50 Mbps 184.18 ms ChangSha CU 191.84 Mbps 4.14 Mbps 181.07 ms ShenYang CU 154.78 Mbps 180.88 Mbps 163.25 ms ZhenZhou 5G CM 122.80 Mbps 16.40 Mbps 414.72 ms BeiJing CM 145.08 Mbps 128.92 Mbps 281.36 ms ChengDou CM 168.75 Mbps 141.15 Mbps 249.47 ms ---------------------------------------------------------------------- Finished in : 9 min 16 sec Timestamp : 2022-12-16 08:39:51 MSK ----------------------------------------------------------------------
5、JustHost俄罗斯圣彼得堡VPS到亚洲港澳台、日本、韩国、新加坡、北美、欧洲地区是否可以跑满200M上下行带宽。从测速结果来看各地测速节点是可以跑满200M上下行带宽限制的。
---------------------------------------------------------------------- Node Name Upload Speed Download Speed Latency Speedtest.net 208.66 Mbps 194.63 Mbps 7.45 ms Hong Kong CN 173.33 Mbps 203.70 Mbps 214.57 ms Hong Kong CN 165.49 Mbps 127.08 Mbps 335.30 ms Macau CN 183.68 Mbps 209.08 Mbps 238.78 ms Taiwan CN 154.16 Mbps 193.61 Mbps 305.80 ms Singapore SG 197.47 Mbps 201.93 Mbps 191.40 ms Singapore SG 140.31 Mbps 188.73 Mbps 284.58 ms Tokyo JP 176.85 Mbps 180.39 Mbps 208.18 ms Tokyo JP 165.54 Mbps 200.40 Mbps 267.21 ms Seoul KR 159.00 Mbps 195.18 Mbps 317.87 ms Los Angeles US 190.59 Mbps 199.95 Mbps 181.11 ms Los Angeles US 195.17 Mbps 199.97 Mbps 178.29 ms Dallas US 197.29 Mbps 199.68 Mbps 150.57 ms Montreal CA 205.41 Mbps 198.03 Mbps 119.14 ms France FR 209.51 Mbps 197.02 Mbps 43.92 ms Paris FR 209.69 Mbps 197.83 Mbps 43.11 ms Amsterdam NL 209.59 Mbps 198.47 Mbps 35.98 ms ---------------------------------------------------------------------- Finished in : 9 min 48 sec Timestamp : 2022-12-16 08:52:39 MSK ----------------------------------------------------------------------
6、JustHost俄罗斯圣彼得堡VPS电信、联通、移动三网去程线路怎么样？直不直连？从国内三网去程路由追踪测试结果来看，电信去程绕欧洲、联通直连俄罗斯远东地区再到机房、移动绕道美国！
JustHost俄罗斯圣彼得堡VPS电信去程路由追踪测试结果如下，显示电信163线路到德国在到俄罗斯，所以电信去程并非直连！
JustHost俄罗斯圣彼得堡VPS联通去程路由追踪测试结果显示联通去程直连俄罗斯远东地区再到机房，所以联通去程没有绕道其他国家！
JustHost俄罗斯圣彼得堡VPS移动去程路由追踪结果显示移动去程是绕道美国的，走LEVEL3线路！
7、JustHost俄罗斯圣彼得堡VPS国内电信、联通、移动三网回程线路怎么样？直不直连？从国内三网回程路由追踪测试结果来看，电信回程绕德国、联通回程部分绕美部分绕欧部分直连、移动回程绕欧洲其他国家。
---------------------------------------------------------------------- 上海电信 traceroute to 101.95.120.109 (101.95.120.109), 30 hops max, 32 byte packets 1 194.87.68.1 0.60 ms AS51659 Russian Federation, Saint Petersburg, relcom.ru 2 spb-imq-cr1.ae54-2778.rascom.as20764.net (81.27.252.26) 0.36 ms AS20764 Russian Federation, Saint Petersburg, rascom.ru 3 * 4 81.173.21.1 33.07 ms AS4134 Germany, Hesse, Frankfurt, cteurope.net 5 * 6 * 7 * 8 101.95.120.109 227.49 ms AS4812 China, Shanghai, ChinaTelecom ---------------------------------------------------------------------- 广州电信 traceroute to 14.215.116.1 (14.215.116.1), 30 hops max, 32 byte packets 1 194.87.68.1 0.62 ms AS51659 Russian Federation, Saint Petersburg, relcom.ru 2 spb-imq-cr1.ae54-2778.rascom.as20764.net (81.27.252.26) 0.30 ms AS20764 Russian Federation, Saint Petersburg, rascom.ru 3 * 4 81.173.21.1 40.94 ms AS4134 Germany, Hesse, Frankfurt, cteurope.net 5 * 6 202.97.12.26 228.76 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom 7 202.97.82.57 239.62 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom 8 113.96.4.78 237.27 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom 9 113.96.4.230 242.93 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom 10 183.58.35.14 242.19 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom 11 183.56.128.10 252.92 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom 12 14.215.116.1 235.29 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom ---------------------------------------------------------------------- 北京电信 traceroute to 219.141.147.210 (219.141.147.210), 30 hops max, 32 byte packets 1 194.87.68.1 0.67 ms AS51659 Russian Federation, Saint Petersburg, relcom.ru 2 spb-imq-cr1.ae54-2778.rascom.as20764.net (81.27.252.26) 5.96 ms AS20764 Russian Federation, Saint Petersburg, rascom.ru 3 * 4 81.173.21.1 37.89 ms AS4134 Germany, Hesse, Frankfurt, cteurope.net 5 * 6 * 7 * 8 * 9 * 10 6.254.120.106.static.bjtelecom.net (106.120.254.6) 185.71 ms AS4847 China, Beijing, ChinaTelecom 11 bj141-147-210.bjtelecom.net (219.141.147.210) 286.63 ms AS4847 China, Beijing, ChinaTelecom ---------------------------------------------------------------------- 杭州电信 traceroute to 60.176.0.1 (60.176.0.1), 30 hops max, 32 byte packets 1 194.87.68.1 0.53 ms AS51659 Russian Federation, Saint Petersburg, relcom.ru 2 spb-imq-cr1.ae54-2778.rascom.as20764.net (81.27.252.26) 0.31 ms AS20764 Russian Federation, Saint Petersburg, rascom.ru 3 * 4 81.173.21.1 31.74 ms AS4134 Germany, Hesse, Frankfurt, cteurope.net 5 * 6 * 7 * 8 202.97.102.26 227.12 ms AS4134 China, Zhejiang, Hangzhou, ChinaTelecom 9 220.191.198.154 219.09 ms AS4134 China, Zhejiang, Hangzhou, ChinaTelecom 10 60.176.0.1 213.67 ms AS4134 China, Zhejiang, Hangzhou, ChinaTelecom ---------------------------------------------------------------------- 贵阳电信 traceroute to 58.42.224.1 (58.42.224.1), 30 hops max, 32 byte packets 1 194.87.68.1 3.92 ms AS51659 Russian Federation, Saint Petersburg, relcom.ru 2 spb-imq-cr1.ae54-2778.rascom.as20764.net (81.27.252.26) 2.46 ms AS20764 Russian Federation, Saint Petersburg, rascom.ru 3 * 4 81.173.21.1 30.92 ms AS4134 Germany, Hesse, Frankfurt, cteurope.net 5 * 6 202.97.38.94 260.25 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom 7 202.97.91.221 241.11 ms AS4134 China, Guangdong, Guangzhou, ChinaTelecom 8 * 9 * 10 58.42.224.1 252.26 ms AS4134 China, Guizhou, Guiyang, ChinaTelecom ---------------------------------------------------------------------- 深圳电信 traceroute to 58.60.188.222 (58.60.188.222), 30 hops max, 32 byte packets 1 194.87.68.1 0.67 ms AS51659 Russian Federation, Saint Petersburg, relcom.ru 2 spb-imq-cr1.ae54-2778.rascom.as20764.net (81.27.252.26) 0.24 ms AS20764 Russian Federation, Saint Petersburg, rascom.ru 3 * 4 81.173.21.1 32.93 ms AS4134 Germany, Hesse, Frankfurt, cteurope.net 5 * 6 * 7 * 8 14.147.127.14 233.53 ms AS134774 China, Guangdong, Shenzhen, ChinaTelecom 9 * 10 58.60.188.222 238.16 ms AS4134 China, Guangdong, Shenzhen, ChinaTelecom ---------------------------------------------------------------------- 上海联通 traceroute to 210.22.97.1 (210.22.97.1), 30 hops max, 32 byte packets 1 194.87.68.1 0.58 ms AS51659 Russian Federation, Saint Petersburg, relcom.ru 2 spb-imq-cr1.ae54-2778.rascom.as20764.net (81.27.252.26) 0.47 ms AS20764 Russian Federation, Saint Petersburg, rascom.ru 3 * 4 et-3-0-21-509.edge4.Stockholm2.Level3.net (212.73.250.201) 14.04 ms AS3356 Sweden, Stockholm County, Stockholm, level3.com 5 4.69.209.165 177.64 ms AS3356 United States, California, San Jose, level3.com 6 * 7 219.158.97.181 233.94 ms AS4837 China, Shanghai, ChinaUnicom 8 219.158.8.177 229.86 ms AS4837 China, Shanghai, ChinaUnicom 9 * 10 * 11 112.64.250.202 229.22 ms AS17621 China, Shanghai, ChinaUnicom 12 210.22.97.1 220.26 ms AS17621 China, Shanghai, ChinaUnicom ---------------------------------------------------------------------- 广州联通 traceroute to 210.21.4.130 (210.21.4.130), 30 hops max, 32 byte packets 1 194.87.68.1 0.81 ms AS51659 Russian Federation, Saint Petersburg, relcom.ru 2 spb-imq-cr1.ae54-2778.rascom.as20764.net (81.27.252.26) 0.45 ms AS20764 Russian Federation, Saint Petersburg, rascom.ru 3 * 4 et-3-0-21-509.edge4.Stockholm2.Level3.net (212.73.250.201) 10.86 ms AS3356 Sweden, Stockholm County, Stockholm, level3.com 5 ae3.30.edge1.LosAngeles6.level3.net (4.69.153.125) 186.68 ms AS3356 United States, California, Los Angeles, level3.com 6 * 7 219.158.98.49 240.72 ms AS4837 China, Guangdong, Guangzhou, ChinaUnicom 8 219.158.96.210 250.58 ms AS4837 China, Guangdong, Guangzhou, ChinaUnicom 9 219.158.103.217 259.78 ms AS4837 China, Guangdong, Guangzhou, ChinaUnicom 10 157.18.0.158 256.92 ms AS17816 China, Guangdong, Guangzhou, ChinaUnicom 11 120.80.91.66 257.15 ms AS17816 China, Guangdong, Guangzhou, ChinaUnicom 12 gz1-dns.gdgz.cncnet.net (210.21.4.130) 268.52 ms AS17622 China, Guangdong, Guangzhou, ChinaUnicom ---------------------------------------------------------------------- 北京联通 traceroute to 202.106.50.1 (202.106.50.1), 30 hops max, 32 byte packets 1 194.87.68.1 115.50 ms AS51659 Russian Federation, Saint Petersburg, relcom.ru 2 spb-imq-cr1.ae54-2778.rascom.as20764.net (81.27.252.26) 184.42 ms AS20764 Russian Federation, Saint Petersburg, rascom.ru 3 * 4 mskn18ra.transtelecom.net (188.43.228.198) 223.27 ms AS20485 Russian Federation, Moscow, ttk.ru 5 * 6 * 7 * 8 * 9 * 10 202.96.12.34 292.64 ms AS4808 China, Beijing, ChinaUnicom 11 202.106.50.1 279.57 ms AS4808 China, Beijing, ChinaUnicom ---------------------------------------------------------------------- 杭州联通 traceroute to 221.12.1.227 (221.12.1.227), 30 hops max, 32 byte packets 1 194.87.68.1 145.77 ms AS51659 Russian Federation, Saint Petersburg, relcom.ru 2 spb-imq-cr1.ae54-2778.rascom.as20764.net (81.27.252.26) 160.41 ms AS20764 Russian Federation, Saint Petersburg, rascom.ru 3 * 4 * 5 be3376.ccr21.sto03.atlas.cogentco.com (130.117.50.225) 160.11 ms AS174 Sweden, Stockholm County, Stockholm, cogentco.com 6 be2555.rcr21.cph01.atlas.cogentco.com (154.54.61.237) 164.03 ms AS174 Denmark, Capital Region of Denmark, Copenhagen, cogentco.com 7 be2496.ccr41.ham01.atlas.cogentco.com (154.54.61.221) 175.15 ms AS174 Germany, Hamburg, cogentco.com 8 be2797.ccr41.fra03.atlas.cogentco.com (154.54.58.225) 191.93 ms AS174 Germany, Hesse, Frankfurt, cogentco.com 9 be2845.rcr22.fra06.atlas.cogentco.com (154.54.56.190) 190.48 ms AS174 Germany, Hesse, Frankfurt, cogentco.com 10 be2844.agr21.fra06.atlas.cogentco.com (130.117.0.30) 183.90 ms AS174 Germany, Hesse, Frankfurt, cogentco.com 11 be3167.nr51.b037206-0.fra06.atlas.cogentco.com (154.25.14.78) 190.86 ms AS174 Germany, Hesse, Frankfurt, cogentco.com 12 * 13 219.158.14.85 273.05 ms AS4837 China, Guangdong, Guangzhou, ChinaUnicom 14 219.158.4.45 283.67 ms AS4837 China, Guangdong, Guangzhou, ChinaUnicom 15 219.158.3.153 207.97 ms AS4837 China, Guangdong, Guangzhou, ChinaUnicom 16 219.158.101.178 173.33 ms AS4837 China, Zhejiang, Hangzhou, ChinaUnicom 17 101.71.244.34 173.84 ms AS4837 China, Zhejiang, Hangzhou, ChinaUnicom 18 * 19 221.12.1.227 177.47 ms AS4837 China, Zhejiang, Hangzhou, ChinaUnicom ---------------------------------------------------------------------- 贵阳联通 traceroute to 58.16.28.1 (58.16.28.1), 30 hops max, 32 byte packets 1 194.87.68.1 0.66 ms AS51659 Russian Federation, Saint Petersburg, relcom.ru 2 spb-imq-cr1.ae54-2778.rascom.as20764.net (81.27.252.26) 0.42 ms AS20764 Russian Federation, Saint Petersburg, rascom.ru 3 * 4 * 5 be3377.ccr22.sto03.atlas.cogentco.com (154.54.36.89) 12.08 ms AS174 Sweden, Stockholm County, Stockholm, cogentco.com 6 be2557.rcr21.cph01.atlas.cogentco.com (154.54.61.241) 21.46 ms AS174 Denmark, Capital Region of Denmark, Copenhagen, cogentco.com 7 be2504.ccr42.ham01.atlas.cogentco.com (154.54.61.229) 27.10 ms AS174 Germany, Hamburg, cogentco.com 8 be2798.ccr42.fra03.atlas.cogentco.com (154.54.58.229) 35.52 ms AS174 Germany, Hesse, Frankfurt, cogentco.com 9 be2846.rcr22.fra06.atlas.cogentco.com (154.54.37.30) 35.61 ms AS174 Germany, Hesse, Frankfurt, cogentco.com 10 be2844.agr21.fra06.atlas.cogentco.com (130.117.0.30) 35.47 ms AS174 Germany, Hesse, Frankfurt, cogentco.com 11 be3167.nr51.b037206-0.fra06.atlas.cogentco.com (154.25.14.78) 35.70 ms AS174 Germany, Hesse, Frankfurt, cogentco.com 12 * 13 219.158.14.189 168.11 ms AS4837 China, Guangdong, Guangzhou, ChinaUnicom 14 219.158.4.29 181.10 ms AS4837 China, Guangdong, Guangzhou, ChinaUnicom 15 219.158.3.17 180.25 ms AS4837 China, Guangdong, Guangzhou, ChinaUnicom 16 219.158.117.26 187.03 ms AS4837 China, Guizhou, Guiyang, ChinaUnicom 17 * 18 58.16.28.1 173.54 ms AS4837 China, Guizhou, Guiyang, ChinaUnicom ---------------------------------------------------------------------- 深圳联通 traceroute to 210.21.196.6 (210.21.196.6), 30 hops max, 32 byte packets 1 194.87.68.1 64.28 ms AS51659 Russian Federation, Saint Petersburg, relcom.ru 2 spb-imq-cr1.ae54-2778.rascom.as20764.net (81.27.252.26) 80.15 ms AS20764 Russian Federation, Saint Petersburg, rascom.ru 3 * 4 mskn18ra.transtelecom.net (188.43.228.198) 58.53 ms AS20485 Russian Federation, Moscow, ttk.ru 5 * 6 * 7 * 8 * 9 219.158.18.65 141.82 ms AS4837 China, Beijing, ChinaUnicom 10 * 11 * 12 120.80.144.38 190.43 ms AS17623 China, Guangdong, Shenzhen, ChinaUnicom 13 dns2-ftcg.gdsz.cncnet.net (210.21.196.6) 162.62 ms AS17623 China, Guangdong, Shenzhen, ChinaUnicom ---------------------------------------------------------------------- 上海移动 traceroute to 211.136.112.200 (211.136.112.200), 30 hops max, 32 byte packets 1 194.87.68.1 0.81 ms AS51659 Russian Federation, Saint Petersburg, relcom.ru 2 spb-imq-cr1.ae54-2778.rascom.as20764.net (81.27.252.26) 0.34 ms AS20764 Russian Federation, Saint Petersburg, rascom.ru 3 * 4 mskn18ra.transtelecom.net (188.43.228.198) 8.27 ms AS20485 Russian Federation, Moscow, ttk.ru 5 * 6 * 7 223.118.18.46 36.00 ms AS58453 Germany, Hesse, Frankfurt, ChinaMobile 8 223.120.15.210 424.32 ms AS58453 China, Shanghai, ChinaMobile 9 221.183.89.182 375.50 ms AS9808 China, Shanghai, ChinaMobile 10 221.183.89.69 389.33 ms AS9808 China, Shanghai, ChinaMobile 11 221.183.89.46 430.29 ms AS9808 China, Shanghai, ChinaMobile 12 * 13 221.181.125.138 387.06 ms AS24400 China, Shanghai, ChinaMobile 14 211.136.112.252 374.43 ms AS24400 China, Shanghai, ChinaMobile 15 211.136.112.200 386.95 ms AS24400 China, Shanghai, ChinaMobile ---------------------------------------------------------------------- 广州移动 traceroute to 221.183.90.217 (221.183.90.217), 30 hops max, 32 byte packets 1 194.87.68.1 0.89 ms AS51659 Russian Federation, Saint Petersburg, relcom.ru 2 spb-imq-cr1.ae54-2778.rascom.as20764.net (81.27.252.26) 0.33 ms AS20764 Russian Federation, Saint Petersburg, rascom.ru 3 * 4 mskn18ra.transtelecom.net (188.43.228.198) 7.92 ms AS20485 Russian Federation, Moscow, ttk.ru 5 * 6 * 7 223.118.18.46 37.14 ms AS58453 Germany, Hesse, Frankfurt, ChinaMobile 8 223.120.15.234 283.32 ms AS58453 China, Guangdong, Guangzhou, ChinaMobile 9 221.183.55.94 237.49 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile 10 221.176.24.61 290.59 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile 11 221.176.24.205 232.73 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile 12 111.24.5.185 286.07 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile 13 221.183.97.86 290.49 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile 14 221.183.90.217 311.60 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile ---------------------------------------------------------------------- 北京移动 traceroute to 221.130.33.1 (221.130.33.1), 30 hops max, 32 byte packets 1 194.87.68.1 0.60 ms AS51659 Russian Federation, Saint Petersburg, relcom.ru 2 spb-imq-cr1.ae54-2778.rascom.as20764.net (81.27.252.26) 25.54 ms AS20764 Russian Federation, Saint Petersburg, rascom.ru 3 * 4 mskn18ra.transtelecom.net (188.43.228.198) 52.30 ms AS20485 Russian Federation, Moscow, ttk.ru 5 * 6 * 7 223.118.21.82 35.59 ms AS58453 Germany, Hesse, Frankfurt, ChinaMobile 8 223.120.16.142 270.44 ms AS58453 China, Shanghai, ChinaMobile 9 221.183.89.174 305.39 ms AS9808 China, Shanghai, ChinaMobile 10 221.183.89.69 262.14 ms AS9808 China, Shanghai, ChinaMobile 11 * 12 * 13 * 14 211.136.67.106 331.76 ms AS56048 China, Beijing, ChinaMobile 15 211.136.66.129 357.65 ms AS56048 China, Beijing, ChinaMobile 16 211.136.58.122 332.33 ms AS56048 China, Beijing, ChinaMobile 17 221.130.33.1 333.00 ms AS56048 China, Beijing, ChinaMobile ---------------------------------------------------------------------- 杭州移动 traceroute to 211.140.13.188 (211.140.13.188), 30 hops max, 32 byte packets 1 194.87.68.1 122.58 ms AS51659 Russian Federation, Saint Petersburg, relcom.ru 2 spb-imq-cr1.ae54-2778.rascom.as20764.net (81.27.252.26) 111.64 ms AS20764 Russian Federation, Saint Petersburg, rascom.ru 3 * 4 mskn18ra.transtelecom.net (188.43.228.198) 156.72 ms AS20485 Russian Federation, Moscow, ttk.ru 5 * 6 * 7 223.118.18.46 135.73 ms AS58453 Germany, Hesse, Frankfurt, ChinaMobile 8 223.120.12.186 539.93 ms AS58453 China, Shanghai, ChinaMobile 9 221.183.89.178 575.99 ms AS9808 China, Shanghai, ChinaMobile 10 221.183.89.33 435.93 ms AS9808 China, Shanghai, ChinaMobile 11 221.183.89.10 426.92 ms AS9808 China, Shanghai, ChinaMobile 12 * 13 221.183.46.174 348.66 ms AS9808 China, Beijing, ChinaMobile 14 * 15 ns3.zj.chinamobile.com (211.140.13.188) 438.84 ms AS56041 China, Zhejiang, Hangzhou, ChinaMobile ---------------------------------------------------------------------- 贵阳移动 traceroute to 211.139.0.10 (211.139.0.10), 30 hops max, 32 byte packets 1 194.87.68.1 0.66 ms AS51659 Russian Federation, Saint Petersburg, relcom.ru 2 spb-imq-cr1.ae54-2778.rascom.as20764.net (81.27.252.26) 0.49 ms AS20764 Russian Federation, Saint Petersburg, rascom.ru 3 * 4 mskn18ra.transtelecom.net (188.43.228.198) 9.06 ms AS20485 Russian Federation, Moscow, ttk.ru 5 * 6 * 7 223.118.21.82 36.65 ms AS58453 Germany, Hesse, Frankfurt, ChinaMobile 8 223.120.16.142 271.47 ms AS58453 China, Shanghai, ChinaMobile 9 221.183.89.174 305.85 ms AS9808 China, Shanghai, ChinaMobile 10 221.183.89.69 262.62 ms AS9808 China, Shanghai, ChinaMobile 11 * 12 * 13 211.139.0.10 332.57 ms AS9808 China, Guizhou, Guiyang, ChinaMobile ---------------------------------------------------------------------- 深圳移动 traceroute to 120.196.165.24 (120.196.165.24), 30 hops max, 32 byte packets 1 194.87.68.1 2.19 ms AS51659 Russian Federation, Saint Petersburg, relcom.ru 2 spb-imq-cr1.ae54-2778.rascom.as20764.net (81.27.252.26) 1.56 ms AS20764 Russian Federation, Saint Petersburg, rascom.ru 3 * 4 et-3-0-21-444.edge4.Stockholm2.Level3.net (212.73.250.177) 15.87 ms AS3356 Sweden, Stockholm County, Stockholm, level3.com 5 ae2.3222.edge9.Frankfurt1.level3.net (4.69.167.118) 36.01 ms AS3356 Germany, Hesse, Frankfurt, level3.com 6 4.68.110.26 35.84 ms AS3356 Germany, Hesse, Frankfurt, level3.com 7 223.120.10.85 36.62 ms AS58453 Germany, Hesse, Frankfurt, ChinaMobile 8 223.120.15.230 227.03 ms AS58453 China, Guangdong, Guangzhou, ChinaMobile 9 221.183.55.82 236.19 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile 10 221.183.52.85 287.68 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile 11 221.183.68.146 289.36 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile 12 111.24.5.165 254.80 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile 13 221.183.71.74 260.99 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile 14 221.183.110.170 314.19 ms AS9808 China, Guangdong, Guangzhou, ChinaMobile 15 ns6.gd.cnmobile.net (120.196.165.24) 313.60 ms AS56040 China, Guangdong, Shenzhen, ChinaMobile ----------------------------------------------------------------------
8、JustHost俄罗斯圣彼得堡VPS支持解锁哪些流媒体！JustHost俄罗斯圣彼得堡VPS流媒体解锁测试结果如下，从测试结果看分配的IP不支持解锁Disney+和Netflix等流媒体！
** 测试时间: Fri Dec 16 08:51:25 MSK 2022 ** 正在测试IPv4解锁情况 -------------------------------- ** 您的网络为: LLC Baxet (195.58.*.*) ============[ 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: Associated with [RASCOM] 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: EUR ======================================= ===============[ 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:5:*:*) ============[ 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: Associated with [RASCOM] 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) =======================================
