Home Sign Up Sign In
902115

用上海国际精品网的朋友请进.最好有多余 E3 1230 或 I7 CPU 电脑空余

  •   
  •   902115 · May 29, 2015 · 5326 views
    This topic created in 4029 days ago, the information mentioned may be changed or developed.
    本人坐标广州
    使用电信100M
    只能报装电信.无法装移动
    去日本CONOHA效果很烂
    一直都是用台湾中华电信做中转
    但是电信去中华电信效果时好时坏

    上海是否有人能提供下国际精品网的线路让我测试下去日本CONOHA的质量
    租了CONOHA 17个IP的VPS
    日本目前就他家有多IP的VPS
    如果效果好的话
    分部分带宽我使用
    我帮你承担宽带和国际精品网的费用
    3Q
  • conoha
  • 电信
  • VPS
    25 replies  •  2015-07-02 07:08:30 +08:00
    902115
        1
    902115  
    OP
       May 29, 2015
    Pinging 157.7.117.199 with 32 bytes of data:

    Reply from 157.7.117.199: bytes=32 time=149ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=156ms TTL=48
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=158ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=163ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=158ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=163ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=169ms TTL=48
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=168ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=160ms TTL=48
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=161ms TTL=48
    Request timed out.
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=172ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=165ms TTL=48
    Request timed out.
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=170ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=159ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=150ms TTL=48
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=172ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=170ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=172ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=172ms TTL=48
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=168ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=138ms TTL=48
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=171ms TTL=48
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=170ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=143ms TTL=48
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=154ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=151ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=159ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=170ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=170ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=173ms TTL=48
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=172ms TTL=48
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=181ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=153ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=158ms TTL=48
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=172ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=159ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=163ms TTL=48
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=187ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=171ms TTL=48
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=170ms TTL=48
    Request timed out.
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=160ms TTL=48
    Request timed out.
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=163ms TTL=48
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=171ms TTL=48
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=160ms TTL=48
    Request timed out.
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=176ms TTL=48
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=173ms TTL=48
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=159ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=170ms TTL=48
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=182ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=179ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=182ms TTL=48
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=171ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=174ms TTL=48
    Reply from 157.7.117.199: bytes=32 time=172ms TTL=48
    Request timed out.
    Reply from 157.7.117.199: bytes=32 time=181ms TTL=48
    902115
        2
    902115  
    OP
       May 29, 2015
    这效果我也是醉了
    Sharuru
        3
    Sharuru  
       May 29, 2015
    这边测了一下，47ms，25% 掉包，感觉不是很理想。
    halczy
        4
    halczy  
       May 29, 2015


    广州这边有香港SoftLayer, 10ms延迟.
    goodbest
        5
    goodbest  
       May 29, 2015
    广州为什么不去conoha新加坡
    goodbest
        6
    goodbest  
       May 29, 2015
    @902115
    conoha新版有新加坡可选，测试网关163.44.132.1

    顺便，小尾巴，注册可得1k日元
    https://www.conoha.jp/referral/?token=Bze63ejH7Uphh.3bwt8ju2_SPfD5GBfFSxIYi1RQ6yOiIgzzV7k-HLY
    xenme
        7
    xenme  
       May 29, 2015
    1. 上海电信100M，上行只有4M，最近搞活动升级到10M 了，分享给你还是比较捉急
    2. 即使在广州，离香港那么近，搞个 VPS，绕香港，也比绕上海快多了啊
    PESH
        8
    PESH  
       May 29, 2015
    换个IP段 ping 会减100MS
    902115
        9
    902115  
    OP
       May 29, 2015
    这边测了一下，47ms，25% 掉包，感觉不是很理想。

    我试了移动还可以
    值钱联通的效果还OK
    后来也不行了
    电信更加蛋疼
    902115
        10
    902115  
    OP
       May 29, 2015
    广州这边有香港SoftLayer, 10ms延迟
    OK
    我找下
    3Q
    bellchu
        11
    bellchu  
       May 29, 2015
    为啥要17个IP的V P S......

    广州用香港Softlayer是多么幸福的事情

    CN2过到日本的大多数网络都要15个以上的HOP，像conoha这种用ntt的都是掉包很多的

    另外：要E3和i7做啥用？
    902115
        12
    902115  
    OP
       May 29, 2015
    广州为什么不去conoha新加坡
    因为需要用到日本IP
    汗
    没想过CONOHA新加坡中转
    因为不知道有新加坡版
    哈
    3Q
    晚点买一个试下
    902115
        13
    902115  
    OP
       May 29, 2015
    1. 上海电信100M，上行只有4M，最近搞活动升级到10M 了，分享给你还是比较捉急
    2. 即使在广州，离香港那么近，搞个 VPS，绕香港，也比绕上海快多了啊
    1:200M的国际精品网有20M上传
    我大概10M足以
    2:香港的VPS.经常无缘无故大规模丢包
    可能是我没买到好的吧
    902115
        14
    902115  
    OP
       May 29, 2015
    换个IP段 ping 会减100MS
    换了多个段了
    之前电信过去还行
    现在简直没法用
    来去弄个新加坡CONOHA试下
    3Q
    PESH
        15
    PESH  
       May 29, 2015
    我这佛山电信在5月初起 出口也特别慢了 之前出口到新加坡 ping都在50以下用SS可跑到40M 现在动不动就180-200MS多 用SS只有1-2M 现在晚上连接美国LA的更慢了 以前晚上也有30M 现在变个位数 看来不只是我这里慢 可恶的14.213 IP段
    xenme
        16
    xenme  
       May 30, 2015 via iPhone
    @902115 可惜我家是换不了200m了，100m签了两年还有一年
    Actrace
        17
    Actrace  
       May 30, 2015
    vxtrans的中国节点转出去会好很多.
    aiguozhedaodan
        18
    aiguozhedaodan  
       May 30, 2015 via Android
    一直以来
    电信去日本kddi略强于ntt
    如果需要带宽不大，买个阿里云或者腾讯云，甚至是那种廉价的北京多线bgp的vps（出国走联通），都会好很多
    hack520
        19
    hack520  
       May 30, 2015 via iPhone
    买softlayer jp 的vps呗,电信过去跑cn2，联通过去跑ntt。
    902115
        20
    902115  
    OP
       May 30, 2015
    为啥要17个IP的V P S......

    广州用香港Softlayer是多么幸福的事情

    CN2过到日本的大多数网络都要15个以上的HOP，像conoha这种用ntt的都是掉包很多的

    另外：要E3和i7做啥用？

    脱机挂挂日服游戏
    每个IP只挂一个账号
    小号养大号
    哈哈
    laiyingdong
        21
    laiyingdong  
       May 30, 2015
    国际精品网就算有也给不了你呀。况且也好不到哪里去 我用阿里云测试了一下 还是会丢包 就忍忍吧
    lguan
        22
    lguan  
       Jun 3, 2015
    我在上海，用的也是国际精品网，30M下，10M上，我自己用的是linode日本的VPS，到日本的效果还是不错的，结果给你做个参考

    ```
    PING 157.7.117.199 (157.7.117.199): 56 data bytes
    64 bytes from 157.7.117.199: icmp_seq=0 ttl=48 time=68.204 ms
    64 bytes from 157.7.117.199: icmp_seq=1 ttl=48 time=57.037 ms
    64 bytes from 157.7.117.199: icmp_seq=2 ttl=48 time=57.589 ms
    64 bytes from 157.7.117.199: icmp_seq=3 ttl=48 time=57.169 ms
    64 bytes from 157.7.117.199: icmp_seq=4 ttl=48 time=56.639 ms
    64 bytes from 157.7.117.199: icmp_seq=5 ttl=48 time=57.665 ms
    64 bytes from 157.7.117.199: icmp_seq=6 ttl=48 time=57.738 ms
    64 bytes from 157.7.117.199: icmp_seq=7 ttl=48 time=57.781 ms
    64 bytes from 157.7.117.199: icmp_seq=8 ttl=48 time=56.248 ms
    64 bytes from 157.7.117.199: icmp_seq=9 ttl=48 time=57.407 ms
    64 bytes from 157.7.117.199: icmp_seq=10 ttl=48 time=57.189 ms
    64 bytes from 157.7.117.199: icmp_seq=11 ttl=48 time=56.778 ms
    64 bytes from 157.7.117.199: icmp_seq=12 ttl=48 time=57.101 ms
    64 bytes from 157.7.117.199: icmp_seq=13 ttl=48 time=57.299 ms
    64 bytes from 157.7.117.199: icmp_seq=14 ttl=48 time=56.860 ms
    64 bytes from 157.7.117.199: icmp_seq=15 ttl=48 time=57.350 ms
    64 bytes from 157.7.117.199: icmp_seq=16 ttl=48 time=57.104 ms
    64 bytes from 157.7.117.199: icmp_seq=17 ttl=48 time=57.606 ms
    64 bytes from 157.7.117.199: icmp_seq=18 ttl=48 time=56.957 ms
    64 bytes from 157.7.117.199: icmp_seq=19 ttl=48 time=57.141 ms
    64 bytes from 157.7.117.199: icmp_seq=20 ttl=48 time=57.374 ms
    64 bytes from 157.7.117.199: icmp_seq=21 ttl=48 time=57.796 ms
    64 bytes from 157.7.117.199: icmp_seq=22 ttl=48 time=57.523 ms
    64 bytes from 157.7.117.199: icmp_seq=23 ttl=48 time=56.724 ms
    64 bytes from 157.7.117.199: icmp_seq=24 ttl=48 time=57.663 ms
    64 bytes from 157.7.117.199: icmp_seq=25 ttl=48 time=56.872 ms
    64 bytes from 157.7.117.199: icmp_seq=26 ttl=48 time=57.447 ms
    64 bytes from 157.7.117.199: icmp_seq=27 ttl=48 time=57.388 ms
    64 bytes from 157.7.117.199: icmp_seq=28 ttl=48 time=57.479 ms
    64 bytes from 157.7.117.199: icmp_seq=29 ttl=48 time=57.136 ms
    64 bytes from 157.7.117.199: icmp_seq=30 ttl=48 time=56.901 ms
    64 bytes from 157.7.117.199: icmp_seq=31 ttl=48 time=56.966 ms
    64 bytes from 157.7.117.199: icmp_seq=32 ttl=48 time=57.636 ms
    64 bytes from 157.7.117.199: icmp_seq=33 ttl=48 time=57.390 ms
    64 bytes from 157.7.117.199: icmp_seq=34 ttl=48 time=56.980 ms
    64 bytes from 157.7.117.199: icmp_seq=35 ttl=48 time=56.697 ms
    64 bytes from 157.7.117.199: icmp_seq=36 ttl=48 time=57.055 ms
    ^C
    --- 157.7.117.199 ping statistics ---
    37 packets transmitted, 37 packets received, 0.0% packet loss
    round-trip min/avg/max/stddev = 56.248/57.511/68.204/1.818 ms
    ```
    digimoon
        23
    digimoon  
       Jun 4, 2015
    同问广州用户如果需要日本ip目前有什么好的解决方法，现在在用的这家ss慢成狗
    aru
        24
    aru  
       Jun 4, 2015
    softlayer 日本节点效果还不错，价格贵了点，如果有几个人共享还可以
    regeditms
        25
    regeditms  
       Jul 2, 2015
    @aru 据说softlayer 回国不是走cn2的
    About   ·   Help   ·   Advertise   ·   Blog   ·   API   ·   FAQ   ·   Solana   ·   941 Online   Highest 6679   ·     Select Language
    创意工作者们的社区
    World is powered by solitude
    VERSION: 3.9.8.5 · 72ms · UTC 19:50 · PVG 03:50 · LAX 12:50 · JFK 15:50
    ♥ Do have faith in what you're doing.