立即登录 免费注册
美国主机侦探论坛»论坛 › 国外VPS云主机 › ecvps内陆地区怎么好像掉包挺严重的？
raksmart活动促销

分享

写回答

发帖

ecvps内陆地区怎么好像掉包挺严重的？

国外VPS云主机 国外VPS云主机 2583 人阅读 | 7 人回复

发表于 2010-2-19 22:29:45 | 显示全部楼层 |阅读模式

今天买了个 ecvps  自己上海电信PING在250左右

然后让朋友帮忙测试一下，西安电信
Pinging 206.217.212.96 with 32 bytes of data:
Request timed out.
Reply from 206.217.212.96: bytes=32 time=341ms TTL=53
Request timed out.
Request timed out.
Request timed out.
Reply from 206.217.212.96: bytes=32 time=341ms TTL=53
Reply from 206.217.212.96: bytes=32 time=345ms TTL=53
Reply from 206.217.212.96: bytes=32 time=339ms TTL=53
Reply from 206.217.212.96: bytes=32 time=343ms TTL=53
Reply from 206.217.212.96: bytes=32 time=349ms TTL=53
Request timed out.
Reply from 206.217.212.96: bytes=32 time=358ms TTL=53
Reply from 206.217.212.96: bytes=32 time=360ms TTL=53
Reply from 206.217.212.96: bytes=32 time=357ms TTL=53
Reply from 206.217.212.96: bytes=32 time=354ms TTL=53
Reply from 206.217.212.96: bytes=32 time=353ms TTL=53
Reply from 206.217.212.96: bytes=32 time=357ms TTL=53
Reply from 206.217.212.96: bytes=32 time=358ms TTL=53
Reply from 206.217.212.96: bytes=32 time=468ms TTL=53
Reply from 206.217.212.96: bytes=32 time=354ms TTL=53
Request timed out.
Reply from 206.217.212.96: bytes=32 time=355ms TTL=53
Request timed out.
Reply from 206.217.212.96: bytes=32 time=340ms TTL=53
Reply from 206.217.212.96: bytes=32 time=341ms TTL=53

掉包及延迟都挺严重的.....     这个是达拉斯SL机房的

然后我让朋友接着PING论坛
Pinging bbs.idcspy.com [174.37.172.189] with 32 bytes of data
Reply from 174.37.172.189: bytes=32 time=263ms TTL=51
Reply from 174.37.172.189: bytes=32 time=266ms TTL=51
Reply from 174.37.172.189: bytes=32 time=260ms TTL=51
Reply from 174.37.172.189: bytes=32 time=266ms TTL=51
Reply from 174.37.172.189: bytes=32 time=268ms TTL=51
Reply from 174.37.172.189: bytes=32 time=262ms TTL=51
Reply from 174.37.172.189: bytes=32 time=265ms TTL=51
Reply from 174.37.172.189: bytes=32 time=266ms TTL=51
Reply from 174.37.172.189: bytes=32 time=265ms TTL=51
Reply from 174.37.172.189: bytes=32 time=259ms TTL=51
Reply from 174.37.172.189: bytes=32 time=259ms TTL=51
Reply from 174.37.172.189: bytes=32 time=266ms TTL=51
Reply from 174.37.172.189: bytes=32 time=267ms TTL=51
Reply from 174.37.172.189: bytes=32 time=265ms TTL=51
Reply from 174.37.172.189: bytes=32 time=266ms TTL=51
Reply from 174.37.172.189: bytes=32 time=272ms TTL=51
Reply from 174.37.172.189: bytes=32 time=262ms TTL=51
Reply from 174.37.172.189: bytes=32 time=258ms TTL=51
Reply from 174.37.172.189: bytes=32 time=264ms TTL=51
Reply from 174.37.172.189: bytes=32 time=263ms TTL=51
Reply from 174.37.172.189: bytes=32 time=259ms TTL=51
Reply from 174.37.172.189: bytes=32 time=265ms TTL=51
Reply from 174.37.172.189: bytes=32 time=266ms TTL=51
Reply from 174.37.172.189: bytes=32 time=263ms TTL=51
Reply from 174.37.172.189: bytes=32 time=264ms TTL=51
Reply from 174.37.172.189: bytes=32 time=265ms TTL=51
Reply from 174.37.172.189: bytes=32 time=263ms TTL=51

无掉包现象     为什么同一机房的PING值差距这么大？？？？


然后我又让朋友测试了一下论坛的win7win8兄今天发的测试地址   得出

Pinging 204.152.207.98 with 32 bytes of data:
Request timed out.
Reply from 204.152.207.98: bytes=32 time=236ms TTL=116
Reply from 204.152.207.98: bytes=32 time=237ms TTL=116
Reply from 204.152.207.98: bytes=32 time=233ms TTL=116
Reply from 204.152.207.98: bytes=32 time=238ms TTL=116
Request timed out.
Reply from 204.152.207.98: bytes=32 time=239ms TTL=116
Reply from 204.152.207.98: bytes=32 time=220ms TTL=116
Request timed out.
Request timed out.
Reply from 204.152.207.98: bytes=32 time=243ms TTL=116
Reply from 204.152.207.98: bytes=32 time=241ms TTL=116
Request timed out.
Reply from 204.152.207.98: bytes=32 time=240ms TTL=116
Request timed out.
Request timed out.
Reply from 204.152.207.98: bytes=32 time=212ms TTL=116
Reply from 204.152.207.98: bytes=32 time=214ms TTL=116
Reply from 204.152.207.98: bytes=32 time=213ms TTL=116
Reply from 204.152.207.98: bytes=32 time=216ms TTL=116
Request timed out.
Request timed out.
Reply from 204.152.207.98: bytes=32 time=212ms TTL=116
Reply from 204.152.207.98: bytes=32 time=225ms TTL=116
Request timed out.
Reply from 204.152.207.98: bytes=32 time=213ms TTL=116
Reply from 204.152.207.98: bytes=32 time=218ms TTL=116
Reply from 204.152.207.98: bytes=32 time=219ms TTL=116
Request timed out.
Reply from 204.152.207.98: bytes=32 time=213ms TTL=116
Reply from 204.152.207.98: bytes=32 time=213ms TTL=116
Request timed out.
Reply from 204.152.207.98: bytes=32 time=215ms TTL=116
Reply from 204.152.207.98: bytes=32 time=212ms TTL=116
Request timed out.
Reply from 204.152.207.98: bytes=32 time=215ms TTL=116
Request timed out.
Reply from 204.152.207.98: bytes=32 time=211ms TTL=116
Reply from 204.152.207.98: bytes=32 time=212ms TTL=116
Reply from 204.152.207.98: bytes=32 time=212ms TTL=116
Request timed out.
Reply from 204.152.207.98: bytes=32 time=212ms TTL=116
Reply from 204.152.207.98: bytes=32 time=212ms TTL=116
Request timed out.
Reply from 204.152.207.98: bytes=32 time=213ms TTL=116
Reply from 204.152.207.98: bytes=32 time=221ms TTL=116
Request timed out.
Reply from 204.152.207.98: bytes=32 time=212ms TTL=116
Reply from 204.152.207.98: bytes=32 time=214ms TTL=116
Reply from 204.152.207.98: bytes=32 time=215ms TTL=116
Reply from 204.152.207.98: bytes=32 time=223ms TTL=116
Reply from 204.152.207.98: bytes=32 time=214ms TTL=116
Reply from 204.152.207.98: bytes=32 time=215ms TTL=116
Reply from 204.152.207.98: bytes=32 time=215ms TTL=116
Reply from 204.152.207.98: bytes=32 time=213ms TTL=116
Reply from 204.152.207.98: bytes=32 time=214ms TTL=116
Reply from 204.152.207.98: bytes=32 time=216ms TTL=116
Reply from 204.152.207.98: bytes=32 time=213ms TTL=116
Reply from 204.152.207.98: bytes=32 time=212ms TTL=116
Reply from 204.152.207.98: bytes=32 time=212ms TTL=116
Request timed out.
Reply from 204.152.207.98: bytes=32 time=213ms TTL=116
Reply from 204.152.207.98: bytes=32 time=211ms TTL=116
Reply from 204.152.207.98: bytes=32 time=213ms TTL=116
Reply from 204.152.207.98: bytes=32 time=212ms TTL=116
Request timed out.
Reply from 204.152.207.98: bytes=32 time=213ms TTL=116
Reply from 204.152.207.98: bytes=32 time=213ms TTL=116
Reply from 204.152.207.98: bytes=32 time=213ms TTL=116
Reply from 204.152.207.98: bytes=32 time=262ms TTL=116
Reply from 204.152.207.98: bytes=32 time=212ms TTL=116
Reply from 204.152.207.98: bytes=32 time=212ms TTL=116
Reply from 204.152.207.98: bytes=32 time=232ms TTL=116
Reply from 204.152.207.98: bytes=32 time=213ms TTL=116
Reply from 204.152.207.98: bytes=32 time=214ms TTL=116
Request timed out.

这位兄弟的VPS不在达拉斯的SL机房，也是ECVPS的，PING值虽小，但掉包也比较严重

BlueHost，WordPress主机，无限空间和流量，一键安装WordPress，七折优惠
回复

使用道具 举报

回答|共 7 个

txtqq

发表于 2010-2-19 22:34:07 | 显示全部楼层

那个型号的？多少钱？目前网站准备承载多少IP？
HostEase速度快，中文客服，支付宝付款，无限空间流量，五折优惠
回复 支持 反对

使用道具 举报

513706499

发表于 2010-2-19 22:36:56 | 显示全部楼层

你网站那200人在线就有点太恐怖了，1W5的IP怎么能用掉700G流量？  你是什么站？好像很赚钱了？
RAKsmart美国服务器，两大机房，速度快，稳定高
回复 支持 反对

使用道具 举报

dream26

发表于 2010-2-19 22:42:01 | 显示全部楼层

現在很多機房都有這樣問題..一般...也是看地區....你掉包..有時候..其他客戶沒有掉包問題.

BlueHost，WordPress主机，无限空间和流量，一键安装WordPress，七折优惠
回复 支持 反对

使用道具 举报

txtqq

发表于 2010-2-19 22:45:44 | 显示全部楼层

晚上有300人在线了 幸亏基本都是静态的

附带下载rar文档 都比较小 现在打算将rar部分放在国内

挂一些联盟广告，google广告一天才2.5美元，赚不了钱。
RAKsmart美国服务器，两大机房，速度快，稳定高
回复 支持 反对

使用道具 举报

dream26

发表于 2010-2-19 22:51:45 | 显示全部楼层

現在google 很難賺錢了
RAKsmart美国服务器，两大机房，速度快，稳定高
回复 支持 反对

使用道具 举报

usa

发表于 2010-2-20 16:31:21 | 显示全部楼层

现在到处抽得都很厉害！
GG的钱确实是少了，不过GG还是有赚头的，毕竟国内很多联盟没广告了，流量无法最大转化钱，就挂GG混混吧，起码GG稳定。。。
BlueHost美国服务器，CN2线路，千兆独享带宽，超高配超高性能，九折优惠
回复 支持 反对

使用道具 举报

许天隆

发表于 2010-2-20 16:50:38 | 显示全部楼层

原帖由 usa 于 2010-2-20 04:31 PM 发表
现在到处抽得都很厉害！
GG的钱确实是少了，不过GG还是有赚头的，毕竟国内很多联盟没广告了，流量无法最大转化钱，就挂GG混混吧，起码GG稳定。。。 ...

请问 usa 大大 :

如日本机房 .. 如 NTT 等等 ..

对中国内地会有掉包严重的问题吗 ? ( 与美国机房比较 )           
RAKsmart日本服务器，东京机房，CN2线路，速度快，不限流量
回复 支持 反对

使用道具 举报

返回列表
高级模式
B Color Image Link Quote Code Smilies
您需要登录后才可以回帖 登录 | 注册

本版积分规则

513706499

发表主题

© 2005-2026美国主机侦探( 皖B2-20140010 )