搜索到
3
篇与
日本VPS测试
的结果
-
![ShockHosting日本机房VPS简单测试]()
ShockHosting日本机房VPS简单测试 ShockHosting怎么样? ShockHosting好用吗这个月11号ShockHosting发了个新上日本东京机房的邮件，并且表示其他机房可以申请转移到日本，刚好好VPS手里有个美国的也没数据就发工单申请新开了一个，这里做个简单的测试，方便大家参考。ShockHosting成立于2013年，目前提供的VPS主机可以选择11个数据中心，包括美国洛杉矶、芝加哥、达拉斯、杰克逊维尔、新泽西、澳大利亚、新加坡、日本、荷兰和英国等。官方网站：https://shockhosting.net/机房及配置前面我们说过VPS主机开设在日本东京机房，配置为单核CPU，2GB内存，30GB SSD硬盘，1TB月流量，1Gbps端口，操作系统为CentOS7.*基本测试信息IO和带宽测试使用两个一键包分别测试，下面是第一次测试结果，IO性能和带宽都还是不错的。第二次测试，结果与第一次差不多，下面的带宽测试中加入了大量中国大陆节点，这个带宽还行。去程路由使用在线工具分别从中国电信、移动和联通对主机进行线路测试。三网测试电信优于联通优于移动，移动用户慎选。回程路由回程路由直接在VPS中使用一键包测试，并在下面贴出测试结果。广州电信 traceroute to 14.215.116.1 (14.215.116.1), 30 hops max, 32 byte packets 1 * 2 180.149.230.201 0.37 ms AS136557 日本, 东京都, 东京, infusionglobal.in 3 180.149.230.255 0.54 ms AS136557 日本, 东京都, 东京, infusionglobal.in 4 unn-156-146-32-138.cdn77.com (156.146.32.138) 0.26 ms * CDN77.COM 骨干网, cdn77.com 5 vl1109.lax-cs2-core-1.cdn77.com (185.156.45.17) 108.71 ms * 美国, 加利福尼亚州, 洛杉矶, datacamp.co.uk 8 * 9 202.97.12.46 160.04 ms AS4134 中国, 广东, 广州, chinatelecom.com.cn, 电信 10 * 12 121.14.50.202 270.64 ms AS58466 中国, 广东, 广州, chinatelecom.com.cn, 电信 13 183.56.128.2 156.08 ms AS58466 中国, 广东, 广州, chinatelecom.com.cn, 电信 14 14.215.116.1 272.62 ms AS58466 中国, 广东, 广州, chinatelecom.com.cn, 电信 ---------------------------------------------------------------------- 上海电信 traceroute to 101.95.120.109 (101.95.120.109), 30 hops max, 32 byte packets 1 * 2 180.149.230.201 0.34 ms AS136557 日本, 东京都, 东京, infusionglobal.in 3 180.149.230.255 0.51 ms AS136557 日本, 东京都, 东京, infusionglobal.in 4 unn-156-146-32-138.cdn77.com (156.146.32.138) 0.27 ms * CDN77.COM 骨干网, cdn77.com 5 * 6 ae-19.r30.tokyjp05.jp.bb.gin.ntt.net (129.250.6.130) 2.09 ms AS2914 日本, 东京都, 东京, ntt.com 7 * 8 202.97.94.9 64.06 ms AS4134 中国, 上海, chinatelecom.com.cn, 电信 9 202.97.51.162 69.09 ms AS4134 中国, 上海, chinatelecom.com.cn, 电信 12 * 13 101.95.120.109 75.83 ms AS4812 中国, 上海, chinatelecom.com.cn, 电信 ---------------------------------------------------------------------- 厦门电信 traceroute to 117.28.254.129 (117.28.254.129), 30 hops max, 32 byte packets 1 * 2 180.149.230.201 0.29 ms AS136557 日本, 东京都, 东京, infusionglobal.in 3 180.149.230.255 0.47 ms AS136557 日本, 东京都, 东京, infusionglobal.in 4 unn-156-146-32-138.cdn77.com (156.146.32.138) 0.33 ms * CDN77.COM 骨干网, cdn77.com 5 * 6 ae-2.a00.tokyjp04.jp.bb.gin.ntt.net (129.250.2.69) 1.26 ms AS2914 日本, 东京都, 东京, ntt.com 7 * 8 59.43.184.177 52.90 ms * 中国, 上海, chinatelecom.com.cn, 电信 9 59.43.187.61 58.99 ms * 中国, 上海, chinatelecom.com.cn, 电信 10 * 11 59.43.138.186 63.14 ms * 中国, 福建, chinatelecom.com.cn, 电信 12 * 13 27.159.81.190 62.55 ms AS133775 中国, 福建, 厦门, chinatelecom.com.cn, 电信 14 117.25.141.106 55.71 ms AS133775 中国, 福建, 厦门, chinatelecom.com.cn, 电信 15 117.28.254.129 62.75 ms AS4809 中国, 福建, 厦门, chinatelecom.com.cn, 电信 ---------------------------------------------------------------------- 重庆联通 traceroute to 113.207.25.138 (113.207.25.138), 30 hops max, 32 byte packets 1 * 2 180.149.230.201 0.25 ms AS136557 日本, 东京都, 东京, infusionglobal.in 3 180.149.230.255 0.49 ms AS136557 日本, 东京都, 东京, infusionglobal.in 4 unn-156-146-32-138.cdn77.com (156.146.32.138) 0.23 ms * CDN77.COM 骨干网, cdn77.com 5 * 6 ae-19.r30.tokyjp05.jp.bb.gin.ntt.net (129.250.6.130) 1.26 ms AS2914 日本, 东京都, 东京, ntt.com 7 * 12 113.207.25.138 201.33 ms AS4837 中国, 重庆, chinaunicom.com, 联通 ---------------------------------------------------------------------- 成都联通 traceroute to 119.6.6.6 (119.6.6.6), 30 hops max, 32 byte packets 1 * 2 180.149.230.201 0.27 ms AS136557 日本, 东京都, 东京, infusionglobal.in 3 180.149.230.255 0.47 ms AS136557 日本, 东京都, 东京, infusionglobal.in 4 unn-156-146-32-138.cdn77.com (156.146.32.138) 0.28 ms * CDN77.COM 骨干网, cdn77.com 5 * 6 ae-19.r30.tokyjp05.jp.bb.gin.ntt.net (129.250.6.130) 1.11 ms AS2914 日本, 东京都, 东京, ntt.com 7 * 10 219.158.18.65 165.62 ms AS4837 中国, 北京, chinaunicom.com, 联通 11 219.158.98.42 181.54 ms AS4837 中国, 四川, 成都, chinaunicom.com, 联通 12 * 13 119.7.220.226 194.13 ms AS4837 中国, 四川, 成都, chinaunicom.com, 联通 14 119.6.6.6 176.14 ms AS4837 中国, 四川, 成都, chinaunicom.com, 联通 ---------------------------------------------------------------------- 上海移动 traceroute to 120.204.197.126 (120.204.197.126), 30 hops max, 32 byte packets 1 * 2 180.149.230.201 0.28 ms AS136557 日本, 东京都, 东京, infusionglobal.in 3 180.149.230.255 1.73 ms AS136557 日本, 东京都, 东京, infusionglobal.in 4 unn-156-146-32-138.cdn77.com (156.146.32.138) 0.34 ms * CDN77.COM 骨干网, cdn77.com 5 * 6 ae-19.r30.tokyjp05.jp.bb.gin.ntt.net (129.250.6.130) 17.74 ms AS2914 日本, 东京都, 东京, ntt.com 7 ae-2.r26.tkokhk01.hk.bb.gin.ntt.net (129.250.2.51) 47.21 ms AS2914 中国, 香港, ntt.com 8 ae-0.a02.tkokhk01.hk.bb.gin.ntt.net (129.250.5.33) 50.48 ms AS2914 中国, 香港, ntt.com 15 * 16 111.24.3.89 279.67 ms AS9808 中国, 上海, chinamobile.com, 移动 27 * 28 120.204.197.126 279.08 ms AS9808 中国, 上海, chinamobile.com, 移动 ---------------------------------------------------------------------- 成都移动 traceroute to 183.221.253.100 (183.221.253.100), 30 hops max, 32 byte packets 1 * 2 180.149.230.201 0.27 ms AS136557 日本, 东京都, 东京, infusionglobal.in 3 180.149.230.255 0.49 ms AS136557 日本, 东京都, 东京, infusionglobal.in 4 unn-156-146-32-138.cdn77.com (156.146.32.138) 0.25 ms * CDN77.COM 骨干网, cdn77.com 5 * 6 ae-19.r30.tokyjp05.jp.bb.gin.ntt.net (129.250.6.130) 0.82 ms AS2914 日本, 东京都, 东京, ntt.com 7 ae-2.r26.tkokhk01.hk.bb.gin.ntt.net (129.250.2.51) 58.57 ms AS2914 中国, 香港, ntt.com 8 ae-0.a02.tkokhk01.hk.bb.gin.ntt.net (129.250.5.33) 53.73 ms AS2914 中国, 香港, ntt.com 9 ce-0-0-1.a02.tkokhk01.hk.ce.gin.ntt.net (203.131.241.86) 49.49 ms AS2914 中国, 香港, ntt.com 10 * 11 223.120.2.10 258.23 ms AS58453 中国, 广东, 广州, chinamobile.com, 移动 12 221.183.68.125 250.40 ms AS9808 中国, 广东, 广州, chinamobile.com, 移动 13 * 14 221.176.22.157 253.24 ms AS9808 中国, 广东, 广州, chinamobile.com, 移动 23 * 24 183.221.253.100 239.18 ms AS9808 中国, 四川, 成都, chinamobile.com, 移动 ---------------------------------------------------------------------- 成都教育网 traceroute to 202.112.14.151 (202.112.14.151), 30 hops max, 32 byte packets 1 * 2 180.149.230.201 0.42 ms AS136557 日本, 东京都, 东京, infusionglobal.in 3 180.149.230.255 0.49 ms AS136557 日本, 东京都, 东京, infusionglobal.in 4 unn-156-146-32-138.cdn77.com (156.146.32.138) 0.26 ms * CDN77.COM 骨干网, cdn77.com 5 ix-et-2-1-5-0.tcore1.tv2-tokyo.as6453.net (180.87.180.17) 56.56 ms AS6453 日本, 东京都, 东京, tatacommunications.com 6 if-et-21-2.hcore1.kv8-chiba.as6453.net (120.29.217.67) 52.58 ms AS6453 日本, 千叶县, 千叶市, tatacommunications.com 7 if-ae-6-2.tcore1.sv1-santaclara.as6453.net (63.243.250.56) 104.77 ms AS6453 美国, 加利福尼亚州, 圣克拉拉, tatacommunications.com 8 if-ae-8-2.tcore1.lvw-losangeles.as6453.net (66.110.59.8) 120.20 ms AS6453 美国, 加利福尼亚州, 洛杉矶, tatacommunications.com 9 * 13 101.4.112.14 182.48 ms AS4538 中国, 陕西, 西安, edu.cn, 教育网 14 101.4.112.18 204.39 ms AS4538 中国, 四川, 成都, edu.cn, 教育网 15 101.4.116.158 199.33 ms AS4538 中国, 四川, 成都, edu.cn, 教育网 16 * 19 202.112.14.151 195.95 ms AS24355 中国, 四川, 成都, edu.cn, 教育网Ping测试使用IPIP.NET选取中国大陆、港澳台和亚洲共两百多个节点ping测试，中规中矩吧，毕竟不是美西。总的来说，同一个运营商在国内不同地区的延迟差距也很大，比如电信有些地区ping值很低，但有些地区延迟较高。不过机器的带宽目前还是比较充裕，而且主机IO不错。 -
![Gcore(gcorelabs)日本VPS简单测试]()
Gcore(gcorelabs)日本VPS简单测试 之聚分享过几次G-core的产品信息，成立于2011年的卢森堡商家gcorelabs运营超过30个机房的VPS主机、CDN和独立服务器产品，其中俄罗斯远东地区伯力、海参崴、亚洲地区日本、韩国、中国香港等都有一定的地理位置优势，而且价格便宜，最低每月仅1.08欧元起。最近促销活动较少，我将下单部分比较感兴趣的机房最低套餐进行一个简单的测试并贴出来以便大家参考。官方网站：https://gcorelabs.com/cn/hosting/vds/机房及配置本次购买的是日本机房(Japan,Tokyo)最低套餐：1核心CPU+512MB内存+20GB硬盘+50M带宽=€4.49/月，操作系统为CentOS7.*基本信息VPS管理面板商家提供了独立的vmmanager面板，主机开通邮件里面有面板地址和登录账户密码等信息，在面板中可以进行重启、开关机、重装、VNC等等各项功能。磁盘IO测试信息带宽测试IO和带宽测试等均使用一键包，本机带宽为50M，不同区域测试基本正常范畴。去程路由首先是去程路由，通过各个地区的电信、联通和移动网络去程测试，下图为上海电信和四川电信，同时我也试了其他几个区域电信，基本上差不多。再来看看联通去程线路，与电信一样，走NTT去日本，国内各地区一样，所以我只贴了一张。国内移动，分别为成都移动、江苏移动和沈阳移动三个区域测试，感觉北方好于南方，华中和华南移动一般绕香港或者美国质量一般。回程路由回程线路使用一键包，直接复制上来(所试地区较多，请下拉查看)。Traceroute to China, Beijing CU (TCP Mode, Max 30 Hop) ============================================================ traceroute to 123.125.99.1 (123.125.99.1), 30 hops max, 60 byte packets 1 92.38.178.1 0.25 ms http: json http: json 2 10.255.16.182 0.27 ms http: json http: json 3 10.255.16.188 0.34 ms http: json http: json 4 61.200.80.169 1.26 ms http: json http: json 5 129.250.2.100 1.33 ms http: json http: json 6 129.250.7.81 9.14 ms http: json http: json 7 129.250.7.31 8.95 ms http: json http: json 8 219.158.32.33 170.86 ms http: json http: json 9 219.158.16.81 167.80 ms http: json http: json 10 219.158.4.169 206.95 ms http: json http: json 11 * 12 219.232.11.134 84.17 ms http: json http: json 13 61.148.158.106 76.04 ms http: json http: json 14 61.135.113.158 75.45 ms http: json http: json 15 * 16 * 17 123.125.99.1 78.01 ms http: json http: json Traceroute to China, Beijing CT (TCP Mode, Max 30 Hop) ============================================================ traceroute to 180.149.128.9 (180.149.128.9), 30 hops max, 60 byte packets 1 92.38.178.1 0.33 ms http: json http: json 2 10.255.16.181 0.35 ms http: json http: json 3 10.255.16.187 0.35 ms http: json http: json 4 61.200.80.169 1.18 ms http: json http: json 5 * 6 129.250.3.28 1.83 ms http: json http: json 7 129.250.66.54 89.39 ms http: json http: json 8 202.97.62.137 90.04 ms http: json http: json 9 * 10 218.30.28.30 88.94 ms http: json http: json 11 218.30.25.226 216.51 ms http: json http: json 12 180.149.128.9 88.70 ms http: json http: json Traceroute to China, Beijing CM (TCP Mode, Max 30 Hop) ============================================================ traceroute to 211.136.25.153 (211.136.25.153), 30 hops max, 60 byte packets 1 92.38.178.1 0.33 ms http: json http: json 2 10.255.16.181 0.30 ms http: json http: json 3 10.255.16.187 0.34 ms http: json http: json 4 61.200.80.169 1.16 ms http: json http: json 5 * 6 129.250.7.79 8.58 ms http: json http: json 7 129.250.6.98 50.01 ms http: json http: json 8 * 9 129.250.6.98 50.89 ms http: json http: json 10 * 11 223.120.2.53 52.15 ms http: json http: json 12 * 13 * 14 * 15 111.24.2.241 107.83 ms http: json http: json 16 * 17 * 18 211.136.67.166 90.69 ms http: json http: json 19 * 20 * 21 211.136.95.226 106.00 ms http: json http: json 22 211.136.95.226 100.94 ms http: json http: json 23 211.136.25.153 91.27 ms http: json http: json Traceroute to China, Shanghai CU (TCP Mode, Max 30 Hop) ============================================================ traceroute to 58.247.8.158 (58.247.8.158), 30 hops max, 60 byte packets 1 92.38.178.1 0.32 ms http: json http: json 2 10.255.16.181 0.33 ms http: json http: json 3 10.255.16.187 0.35 ms http: json http: json 4 61.200.80.169 1.20 ms http: json http: json 5 * 6 129.250.7.81 9.18 ms http: json http: json 7 129.250.2.40 9.15 ms http: json http: json 8 129.250.66.86 39.36 ms http: json http: json 9 219.158.19.86 44.50 ms http: json http: json 10 219.158.19.69 189.61 ms http: json http: json 11 * 12 139.226.228.46 197.64 ms http: json http: json 13 139.226.225.22 77.42 ms http: json http: json 14 58.247.8.153 191.85 ms http: json http: json 30 * Traceroute to China, Shanghai CT (TCP Mode, Max 30 Hop) ============================================================ traceroute to 180.153.28.5 (180.153.28.5), 30 hops max, 60 byte packets 1 92.38.178.1 0.34 ms http: json http: json 2 10.255.16.181 0.44 ms http: json http: json 3 10.255.16.188 0.44 ms http: json http: json 4 63.222.57.173 1.32 ms http: json http: json 5 129.250.6.128 3.40 ms http: json http: json 6 218.30.53.84 212.71 ms http: json http: json 7 202.97.51.61 137.82 ms http: json http: json 8 202.97.50.194 117.24 ms http: json http: json 9 202.97.94.238 128.72 ms http: json http: json 10 * 11 * 12 101.95.207.226 340.17 ms http: json http: json 13 * 14 180.153.28.5 110.09 ms http: 503 http: 503 Traceroute to China, Shanghai CM (TCP Mode, Max 30 Hop) ============================================================ traceroute to 221.183.55.22 (221.183.55.22), 30 hops max, 60 byte packets 1 92.38.178.1 0.31 ms http: 503 http: 503 2 10.255.16.182 0.32 ms http: 503 http: 503 3 10.255.16.187 0.40 ms http: 503 http: 503 4 61.200.80.169 1.29 ms http: 503 http: 503 5 63.218.164.66 99.80 ms http: 503 http: 503 6 129.250.7.79 8.69 ms http: 503 http: 503 7 129.250.2.43 54.84 ms http: 503 http: 503 8 129.250.5.28 54.50 ms http: 503 http: 503 9 223.118.3.249 51.79 ms http: 503 http: 503 10 * 11 221.183.55.22 227.69 ms http: 503 http: 503 Traceroute to China, Guangzhou CU (TCP Mode, Max 30 Hop) ============================================================ traceroute to 210.21.4.130 (210.21.4.130), 30 hops max, 60 byte packets 1 92.38.178.1 0.31 ms http: 503 http: 503 2 10.255.16.181 0.30 ms http: 503 http: 503 3 10.255.16.187 0.39 ms http: 503 http: 503 4 61.200.80.173 1.47 ms http: 503 http: 503 5 * 6 129.250.3.33 1.84 ms http: 503 http: 503 7 219.158.42.5 168.71 ms http: 503 http: 503 8 219.158.103.33 80.55 ms http: 503 http: 503 9 219.158.103.217 111.14 ms http: 503 http: 503 10 120.83.0.62 223.80 ms http: 503 http: 503 11 120.80.175.78 116.35 ms http: 503 http: 503 30 * Traceroute to China, Guangzhou CT (TCP Mode, Max 30 Hop) ============================================================ traceroute to 113.108.209.1 (113.108.209.1), 30 hops max, 60 byte packets 1 92.38.178.1 0.35 ms http: 503 http: 503 2 10.255.16.181 0.32 ms http: 503 http: 503 3 10.255.16.188 0.35 ms http: 503 http: 503 4 61.200.80.169 1.28 ms http: 503 http: 503 5 129.250.6.128 1.46 ms http: 503 http: 503 6 129.250.3.22 1.80 ms http: 503 http: 503 7 202.97.86.178 208.01 ms http: 503 http: 503 8 * 9 202.97.94.125 66.60 ms http: 503 http: 503 10 * 11 * 12 113.108.209.1 70.41 ms http: 503 http: 503 Traceroute to China, Guangzhou CM (TCP Mode, Max 30 Hop) ============================================================ traceroute to 120.196.212.25 (120.196.212.25), 30 hops max, 60 byte packets 1 92.38.178.1 0.39 ms http: 503 http: 503 2 10.255.16.181 0.25 ms http: 503 http: 503 3 10.255.16.187 0.40 ms http: 503 http: 503 4 61.200.80.173 1.51 ms http: 503 http: 503 5 129.250.2.100 1.45 ms http: 503 http: 503 6 129.250.7.79 8.48 ms http: 503 http: 503 7 129.250.2.43 57.53 ms http: 503 http: 503 8 * 9 223.120.2.53 48.26 ms http: 503 http: 503 10 * 11 223.120.2.53 51.83 ms http: 503 http: 503 12 221.183.52.85 58.22 ms http: 503 http: 503 13 221.183.55.78 65.04 ms http: 503 http: 503 14 111.24.4.237 56.06 ms http: 503 http: 503 15 221.176.22.105 168.29 ms http: 503 http: 503 16 211.136.196.246 72.04 ms http: 503 http: 503 17 111.24.5.22 66.66 ms http: 503 http: 503 18 211.136.249.117 158.72 ms http: 503 http: 503 19 * 20 * 21 120.196.212.25 61.05 ms http: 503 http: 503 Traceroute to China, Shanghai CU AS9929 (TCP Mode, Max 30 Hop) ============================================================ traceroute to 210.13.66.238 (210.13.66.238), 30 hops max, 60 byte packets 1 92.38.178.1 0.44 ms http: 503 http: 503 2 10.255.16.181 0.36 ms http: 503 http: 503 3 10.255.16.187 0.52 ms http: 503 http: 503 4 10.255.16.160 0.39 ms http: 503 http: 503 5 61.200.80.169 1.16 ms http: 503 http: 503 6 129.250.6.126 2.26 ms http: 503 http: 503 7 129.250.8.54 33.28 ms http: 503 http: 503 8 129.250.8.54 34.79 ms http: 503 http: 503 9 218.105.2.205 32.54 ms http: 503 http: 503 10 218.105.2.210 50.54 ms http: 503 http: 503 11 210.13.116.82 33.53 ms http: 503 http: 503 12 210.13.66.237 89.76 ms http: 503 http: 503 13 210.13.66.238 37.32 ms http: 503 http: 503 Traceroute to China, Shanghai CT CN2 (TCP Mode, Max 30 Hop) ============================================================ traceroute to 58.32.0.1 (58.32.0.1), 30 hops max, 60 byte packets 1 92.38.178.1 0.36 ms http: 503 http: 503 2 10.255.16.182 0.39 ms http: 503 http: 503 3 10.255.16.188 0.37 ms http: 503 http: 503 4 63.222.57.173 1.21 ms http: 503 http: 503 5 63.223.17.50 52.20 ms http: 503 http: 503 6 117.103.177.106 1.60 ms http: 503 http: 503 7 59.43.183.1 52.10 ms http: 503 http: 503 8 59.43.248.242 111.25 ms http: 503 http: 503 9 59.43.130.217 55.32 ms http: 503 http: 503 10 * 11 101.95.88.226 60.84 ms http: 503 http: 503 12 58.32.0.1 65.42 ms http: 503 http: 503 Traceroute to China, Guangzhou CT CN2 Gaming Broadband (TCP Mode, Max 30 Hop) ============================================================ traceroute to 119.121.0.1 (119.121.0.1), 30 hops max, 60 byte packets 1 92.38.178.1 0.34 ms http: 503 http: 503 2 10.255.16.182 0.32 ms http: 503 http: 503 3 10.255.16.188 0.41 ms http: 503 http: 503 4 61.200.80.169 1.30 ms http: 503 http: 503 5 129.250.2.130 1.51 ms http: 503 http: 503 6 117.103.177.106 1.56 ms http: 503 http: 503 7 59.43.247.114 53.74 ms http: 503 http: 503 8 * 9 59.43.130.101 55.34 ms http: 503 http: 503 10 59.43.144.210 57.61 ms http: 503 http: 503 11 183.57.161.10 59.50 ms http: 503 http: 503 12 119.121.0.1 65.88 ms http: 503 http: 503 Traceroute to China, Beijing Dr.Peng Home Network (TCP Mode, Max 30 Hop) ============================================================ traceroute to 14.131.128.1 (14.131.128.1), 30 hops max, 60 byte packets 1 92.38.178.1 0.37 ms http: 503 http: 503 2 10.255.16.182 0.32 ms http: 503 http: 503 3 10.255.16.187 0.33 ms http: 503 http: 503 4 61.200.80.173 1.57 ms http: 503 http: 503 5 129.250.6.126 2.45 ms http: 503 http: 503 6 129.250.7.81 9.47 ms http: 503 http: 503 7 129.250.7.33 9.20 ms http: 503 http: 503 8 129.250.8.26 84.55 ms http: 503 http: 503 9 219.158.3.141 54.48 ms http: 503 http: 503 10 * 11 123.126.0.254 115.76 ms http: 503 http: 503 12 61.148.153.238 116.91 ms http: 503 http: 503 30 * Traceroute to China, Beijing Dr.Peng Network IDC Network (TCP Mode, Max 30 Hop) ============================================================ traceroute to 211.167.230.100 (211.167.230.100), 30 hops max, 60 byte packets 1 92.38.178.1 0.37 ms http: 503 http: 503 2 10.255.16.181 0.34 ms http: 503 http: 503 3 10.255.16.188 0.33 ms http: 503 http: 503 4 61.200.80.173 1.43 ms http: 503 http: 503 5 129.250.6.128 1.38 ms http: 503 http: 503 6 129.250.7.79 10.42 ms http: 503 http: 503 7 129.250.7.31 8.64 ms http: 503 http: 503 8 129.250.9.186 150.80 ms http: 503 http: 503 9 219.158.16.77 58.64 ms http: 503 http: 503 10 219.158.18.65 99.69 ms http: 503 http: 503 11 * 12 202.106.193.2 213.14 ms http: 503 http: 503 13 61.51.37.206 100.36 ms http: 503 http: 503 14 218.241.244.18 207.89 ms http: 503 http: 503 15 218.241.252.14 91.34 ms http: 503 http: 503 16 218.241.253.134 199.12 ms http: 503 http: 503 17 211.167.230.100 98.22 ms http: 503 http: 503 Traceroute to China, Beijing CERNET (TCP Mode, Max 30 Hop) ============================================================ traceroute to 202.205.109.205 (202.205.109.205), 30 hops max, 60 byte packets 1 92.38.178.1 0.45 ms http: 503 http: 503 2 10.255.16.181 0.31 ms http: 503 http: 503 3 10.255.16.188 0.34 ms http: 503 http: 503 4 10.255.16.161 0.46 ms http: 503 http: 503 5 63.222.57.173 1.21 ms http: 503 http: 503 6 63.223.33.197 1.19 ms http: 503 http: 503 7 120.29.217.109 0.94 ms http: 503 http: 503 8 120.29.217.109 0.94 ms http: 503 http: 503 9 180.87.180.13 3.31 ms http: 503 http: 503 10 209.58.86.142 112.20 ms http: 503 http: 503 11 63.243.251.1 105.61 ms http: 503 http: 503 12 66.110.59.182 174.29 ms http: 503 http: 503 13 101.4.117.213 169.59 ms http: 503 http: 503 14 101.4.117.101 171.83 ms http: 503 http: 503 15 101.4.117.101 169.50 ms http: 503 http: 503 16 202.112.38.82 169.92 ms http: 503 http: 503 17 202.112.38.158 166.39 ms http: 503 http: 503 18 202.205.109.205 169.83 ms http: 503 http: 503 Traceroute to China, Beijing CSTNET (TCP Mode, Max 30 Hop) ============================================================ traceroute to 159.226.254.1 (159.226.254.1), 30 hops max, 60 byte packets 1 92.38.178.1 0.36 ms http: 503 http: 503 2 10.255.16.181 0.40 ms http: 503 http: 503 3 10.255.16.187 0.32 ms http: 503 http: 503 4 10.255.16.161 0.45 ms http: 503 http: 503 5 63.222.57.173 0.82 ms http: 503 http: 503 6 63.223.15.70 50.90 ms http: 503 http: 503 7 63.223.17.94 52.79 ms http: 503 http: 503 8 159.226.254.1 89.15 ms http: 503 http: 503 Traceroute to China, Beijing GCable (TCP Mode, Max 30 Hop) ============================================================ traceroute to 211.156.140.17 (211.156.140.17), 30 hops max, 60 byte packets 1 92.38.178.1 0.31 ms http: 503 http: 503 2 10.255.16.182 0.38 ms http: 503 http: 503 3 10.255.16.187 0.35 ms http: 503 http: 403 4 61.200.80.169 1.62 ms http: 503 http: 403 5 129.250.6.128 15.77 ms http: 503 http: 403 6 218.30.53.84 214.91 ms http: 503 http: 403 7 129.250.66.54 90.67 ms http: 503 http: 403 8 * 9 202.97.34.157 93.39 ms http: 403 http: 403 10 219.141.142.121 91.15 ms http: 403 http: 403 11 * 12 106.120.252.158 256.15 ms http: 403 http: 403 13 * 14 211.156.128.225 203.82 ms http: 403 http: 403 15 211.156.128.85 89.14 ms http: 403 http: 403 16 211.156.140.17 93.13 ms http: 403 http: 403Ping测试使用IPIP.NET在全国和亚太地区测试结果，毕竟亚洲地区，绝大多数地区的低ping还是不错的。 接下来我还将试试这个商家的俄罗斯伯力和美国的机房，慢慢把感兴趣的都测试一遍看看我本地哪个区域给力些，感兴趣的也可以直接在他们的官网查看：https://gcorelabs.com -
![GigsGigsCloud日本CN2线路简单测试]()
GigsGigsCloud日本CN2线路简单测试 昨天分享过GigsGigsCloud上线日本VPS的信息，分为两种线路：CN2和软银，手头有一台JP-V系列CN2线路所以测试下，主要针对机器性能、不同宽带线路等进行记录，方便大家参考。总体测试下来感觉机器性能和线路不错，带宽充裕，价格小贵，不适合折腾练手适合安心做站选择。官方网站GGC官网：https://www.gigsgigscloud.com日本VPS产品介绍：https://www.vpsok.net/coupons/article_7469.html基本测试上图包括了机器硬件配置，磁盘IO和世界各地下载情况。Superspeed测试这张主要提供了国内不同地区、不同宽带上传下载及延迟路由线路测试首先是去程，电信联通为CN2，移动软银，先看电信去程信息。联通去程信息移动去程信息回程使用命令测试如下。-----------------中国电信----------------- [Info] 测试路由 到 广州电信(天翼云) 中 ... traceroute to 14.215.116.1 (14.215.116.1), 30 hops max, 60 byte packets 1 103.68.223.1 0.42 ms AS55799,AS63916 {"as":"AS55799,AS63916","area":"日本\t东京都\t东京\t\ttechavenue.net\t35.709026\t139.731993"} 2 * 3 59.43.183.53 36.08 ms * {"as":"*","area":"中国\t中国\t\t\t电信\t36.894402\t104.166"} 4 59.43.187.69 36.45 ms * {"as":"*","area":"中国\t上海\t上海\t\t电信\t31.224349\t121.476753"} 5 59.43.138.49 39.22 ms * {"as":"*","area":"中国\t上海\t上海\t\t电信\t31.224349\t121.476753"} 6 59.43.80.138 40.35 ms * {"as":"*","area":"中国\t上海\t上海\t\t电信\t31.224349\t121.476753"} 7 202.97.82.150 64.53 ms AS4134 {"as":"AS4134","area":"中国\t广东\t广州\t\t电信\t23.12911\t113.264385"} 8 183.59.12.197 61.10 ms AS58543 {"as":"AS58543","area":"中国\t广东\t广州\t\t电信\t23.12911\t113.264385"} 9 183.56.128.2 61.41 ms AS58543 {"as":"AS58543","area":"中国\t广东\t广州\t\t电信\t23.12911\t113.264385"} 10 14.215.116.1 61.98 ms AS58543 {"as":"AS58543","area":"中国\t广东\t广州\t\t电信\t23.12911\t113.264385"} [Info] 测试路由 到 广州电信(天翼云) 完成 ！ -----------------中国联通----------------- [Info] 测试路由 到 河南郑州联通 中 ... traceroute to 61.168.23.74 (61.168.23.74), 30 hops max, 60 byte packets 1 103.68.223.1 0.32 ms AS55799,AS63916 {"as":"AS55799,AS63916","area":"日本\t东京都\t东京\t\ttechavenue.net\t35.709026\t139.731993"} 2 * 3 59.43.186.185 35.52 ms * {"as":"*","area":"中国\t上海\t上海\t\t电信\t31.224349\t121.476753"} 4 59.43.247.61 46.88 ms * {"as":"*","area":"中国\t上海\t上海\t\t电信\t31.224349\t121.476753"} 5 59.43.138.69 37.35 ms * {"as":"*","area":"中国\t上海\t上海\t\t电信\t31.224349\t121.476753"} 6 59.43.46.85 58.56 ms * {"as":"*","area":"中国\t北京\t北京\t\t电信\t39.938884\t116.397459"} 7 219.158.40.165 58.87 ms AS4837 {"as":"AS4837","area":"中国\t北京\t北京\t\t联通\t39.938884\t116.397459"} 8 * 9 219.158.4.70 60.88 ms AS4837 {"as":"AS4837","area":"中国\t河南\t郑州\t\t联通\t34.762501\t113.653023"} 10 pc62.zz.ha.cn (61.168.28.62) 71.89 ms AS4837 {"as":"AS4837","area":"中国\t河南\t郑州\t\t联通\t34.762501\t113.653023"} 11 pc6.zz.ha.cn (61.168.17.6) 60.83 ms AS4837 {"as":"AS4837","area":"中国\t河南\t郑州\t\t联通\t34.762501\t113.653023"} 12 pc74.zz.ha.cn (61.168.23.74) 60.51 ms AS4837 {"as":"AS4837","area":"中国\t河南\t郑州\t\t联通\t34.762501\t113.653023"} [Info] 测试路由 到 河南郑州联通 完成 ！ -----------------中国移动----------------- [Info] 测试路由 到 四川成都移动 中 ... traceroute to 183.221.247.9 (183.221.247.9), 30 hops max, 60 byte packets 1 103.68.223.1 0.25 ms AS55799,AS63916 {"as":"AS55799,AS63916","area":"日本\t东京都\t东京\t\ttechavenue.net\t35.709026\t139.731993"} 2 * 3 59.43.183.53 35.95 ms * {"as":"*","area":"中国\t中国\t\t\t电信\t36.894402\t104.166"} 4 * 5 * 6 59.43.80.78 39.29 ms * {"as":"*","area":"中国\t上海\t上海\t\t电信\t31.224349\t121.476753"} 7 202.97.36.210 70.74 ms AS4134 {"as":"AS4134","area":"中国\t四川\t成都\t\t电信\t30.658529\t104.075546"} 8 * 9 * 10 221.176.20.221 95.04 ms AS9808 {"as":"AS9808","area":"中国\t四川\t成都\t\t移动\t30.658529\t104.075546"} 11 221.183.19.46 95.72 ms AS9808 {"as":"AS9808","area":"中国\t四川\t成都\t\t移动\t30.658529\t104.075546"} 12 117.139.26.249 98.51 ms AS9808 {"as":"AS9808","area":"中国\t四川\t成都\t\t移动\t30.658529\t104.075546"} 13 117.172.50.46 99.62 ms AS9808 {"as":"AS9808","area":"中国\t四川\t成都\t\t移动\t30.658529\t104.075546"} 14 117.172.4.46 97.69 ms AS9808 {"as":"AS9808","area":"中国\t四川\t成都\t\t移动\t30.658529\t104.075546"} 15 183.221.240.70 101.87 ms AS9808 {"as":"AS9808","area":"中国\t四川\t成都\t\t移动\t30.658529\t104.075546"} 16 * 17 * 18 * [Info] 测试路由 到 四川成都移动 完成 ！ Ping测试从中国各区域和亚洲地区230个节点进行了ping测试，整体均值较低。其他总的来说，机器的质量不错，线路电信联通去程CN2移动软银，回程三网CN2，估计影响购买的主要就是价格了，如果能在价格上有一定幅度的优惠就更好了，对日本VPS有兴趣的也可以等商家接下来的日本软银线路产品。
