大家ping 67.220.215.119,丢包好严重

miyug

6sync.com的kvm vps，我和他们反映了，他们说他们那里网络没问题，让我和电信联系解决，晕死，现在晚上有时候站点都打不开。已经有2，3天了。

Request timed out.
Request timed out.
Request timed out.
Reply from 67.220.215.119: bytes=32 time=193ms TTL=51
Reply from 67.220.215.119: bytes=32 time=191ms TTL=51
Reply from 67.220.215.119: bytes=32 time=192ms TTL=51
Reply from 67.220.215.119: bytes=32 time=194ms TTL=51
Reply from 67.220.215.119: bytes=32 time=192ms TTL=51
Reply from 67.220.215.119: bytes=32 time=193ms TTL=51
Reply from 67.220.215.119: bytes=32 time=191ms TTL=51
Reply from 67.220.215.119: bytes=32 time=192ms TTL=51
Reply from 67.220.215.119: bytes=32 time=191ms TTL=51
Reply from 67.220.215.119: bytes=32 time=190ms TTL=51
Reply from 67.220.215.119: bytes=32 time=191ms TTL=51
Reply from 67.220.215.119: bytes=32 time=191ms TTL=51
Reply from 67.220.215.119: bytes=32 time=190ms TTL=51
Reply from 67.220.215.119: bytes=32 time=189ms TTL=51
Reply from 67.220.215.119: bytes=32 time=191ms TTL=51
Reply from 67.220.215.119: bytes=32 time=190ms TTL=51
Reply from 67.220.215.119: bytes=32 time=190ms TTL=51
Reply from 67.220.215.119: bytes=32 time=190ms TTL=51
Reply from 67.220.215.119: bytes=32 time=190ms TTL=51
Reply from 67.220.215.119: bytes=32 time=190ms TTL=51
Reply from 67.220.215.119: bytes=32 time=190ms TTL=51
Reply from 67.220.215.119: bytes=32 time=188ms TTL=51
Reply from 67.220.215.119: bytes=32 time=189ms TTL=51
Reply from 67.220.215.119: bytes=32 time=188ms TTL=51
Reply from 67.220.215.119: bytes=32 time=189ms TTL=51
Reply from 67.220.215.119: bytes=32 time=189ms TTL=51
Reply from 67.220.215.119: bytes=32 time=189ms TTL=51
Reply from 67.220.215.119: bytes=32 time=190ms TTL=51
Reply from 67.220.215.119: bytes=32 time=188ms TTL=51
Request timed out.

Ping statistics for 67.220.215.119:
    Packets: Sent = 1651, Received = 1444, Lost = 207 (12% loss),
Approximate round trip times in milli-seconds:
    Minimum = 188ms, Maximum = 2408ms, Average = 207ms

cpuer

7   (202.97.51.113)  190.920 ms * *
这个节点出现的问题，紧急呼叫电信求助。

miyug

原帖由 cpuer 于 2009-11-14 11:11 发表
贴出来看看，出问题的路由节点应该是中国电信的吧。

miyug@server ~ $  traceroute 61.152.239.220
traceroute to 61.152.239.220 (61.152.239.220), 30 hops max, 40 byte packets
1  67-220-215-65.hosted.static.webnx.com (67.220.215.65)  0.338 ms  0.529 ms  0.799 ms
2  cr3-lax01.webnx.com (67.220.192.102)  0.765 ms  0.731 ms  0.702 ms
3  gige-g2-17.core1.lax2.he.net (216.218.196.189)  0.648 ms  0.619 ms  0.446 ms
4  10gigabitethernet2-1.core1.lax1.he.net (72.52.92.121)  0.697 ms  0.660 ms  0.541 ms
5  64.62.227.34 (64.62.227.34)  28.607 ms  28.576 ms  28.537 ms
6  202.97.49.117 (202.97.49.117)  28.731 ms  29.258 ms  29.329 ms
7   (202.97.51.113)  190.920 ms * *
8  *  (202.97.33.49)  159.512 ms  159.487 ms
9   (202.97.33.57)  162.615 ms  162.580 ms  162.532 ms
10  61.152.86.45 (61.152.86.45)  159.588 ms  167.354 ms  167.410 ms
11  61.152.87.154 (61.152.87.154)  161.641 ms  169.541 ms *
12  * * *
13  61.152.239.220 (61.152.239.220)  190.501 ms  190.610 ms  190.517 ms

cpuer

贴出来看看，出问题的路由节点应该是中国电信的吧。

miyug

原帖由 cpuer 于 2009-11-14 09:55 发表
其实你最好从服务器上做个路由跟踪到你国内本机IP地址，然后贴到WHT上，he.net的人可能会看到。

已经做了，呵呵

cpuer

其实你最好从服务器上做个路由跟踪到你国内本机IP地址，然后贴到WHT上，he.net的人可能会看到。

miyug

原帖由 zhihao 于 2009-11-13 23:00 发表
可能是国际路由的问题，该找相应的线路商，请他们查查结点。和机房无关的。

教你一招：到webhostingtalk上发帖去。

兄弟教我一下如何用英文说一下吧，脑子卡住了一时不知道该怎么表达

cpuer

原帖由 zhihao 于 2009-11-13 23:00 发表
可能是国际路由的问题，该找相应的线路商，请他们查查结点。和机房无关的。

教你一招：到webhostingtalk上发帖去。

可能会结仇的

junhan

我这PING很正常``

lemss

我这边确实有丢包