C:\Documents and Settings\Administrator>ping ns5.stocksir.cn
Pinging ns5.stocksir.cn [96.9.137.46] with 32 bytes of data:
Reply from 96.9.137.46: bytes=32 time=531ms TTL=41
Request timed out.
Reply from 96.9.137.46: bytes=32 time=618ms TTL=41
Reply from 96.9.137.46: bytes=32 time=537ms TTL=41
Ping statistics for 96.9.137.46:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 531ms, Maximum = 618ms, Average = 562ms作者: 网络寄生虫 时间: 2010-2-25 19:35
C:\Users\Administrator>ping 96.9.137.46
Tracing route to ns5.stocksir.cn [96.9.137.46]
over a maximum of 30 hops:
1 2 ms 2 ms 4 ms 10.3.255.11
2 3 ms 5 ms 2 ms 10.3.255.11
3 * * * Request timed out.
4 1 ms 1 ms 1 ms 10.3.254.21
5 * * * Request timed out.
6 12 ms 7 ms 5 ms 59.44.43.1
7 17 ms 3 ms 3 ms 219.148.225.30
8 3 ms 3 ms 3 ms 219.148.240.117
9 3 ms 3 ms 3 ms 219.148.240.13
10 5 ms 4 ms 6 ms 219.148.209.1
11 72 ms 70 ms 71 ms 219.148.211.145
12 80 ms 78 ms 80 ms 202.97.38.221
13 26 ms 27 ms 26 ms 202.97.53.98
14 289 ms 293 ms 289 ms 202.97.51.186
15 337 ms 336 ms 337 ms 202.97.50.42
16 476 ms * 493 ms 62.156.139.149
17 510 ms 520 ms * 217.239.40.186
18 520 ms 518 ms * vl0018.gwy01.sctn01.hostnoc.net [80.156.160.158]
19 587 ms 552 ms 542 ms ec1-10.agg01.sctn01.hostnoc.net [64.191.19.6]
20 523 ms 523 ms 554 ms ec1-15.vl0111.f2801.sctn01.hostnoc.net [96.9.191
.30]
21 523 ms * * vserver49.hostnoc.net [173.212.213.114]
22 * 489 ms * 96913746.hostnoc.net [96.9.137.46]
23 * 490 ms * 96913746.hostnoc.net [96.9.137.46]
24 * 473 ms * 96913746.hostnoc.net [96.9.137.46]
25 503 ms 506 ms 499 ms 96913746.hostnoc.net [96.9.137.46]
Trace complete.作者: fish 时间: 2010-2-25 19:51
试试 72.44.80.253 达拉斯机房 level3作者: 删除 时间: 2010-2-25 19:53
C:\Documents and Settings\Administrator>ping 72.44.80.253
Pinging 72.44.80.253 with 32 bytes of data:
Reply from 72.44.80.253: bytes=32 time=330ms TTL=45
Reply from 72.44.80.253: bytes=32 time=330ms TTL=46
Reply from 72.44.80.253: bytes=32 time=322ms TTL=45
Request timed out.
Ping statistics for 72.44.80.253:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 322ms, Maximum = 330ms, Average = 327ms作者: addmyin 时间: 2010-2-25 19:58
提示: 作者被禁止或删除 内容自动屏蔽作者: 删除 时间: 2010-2-25 19:58
楼上的打PP!!作者: 删除 时间: 2010-2-25 20:15
一句话把我打发了
Hello,
Currently there is only one datacenter in which the VPS are located. If you look at your traceroute results you can see that packets start dropping before it leave your local area and that the latency grows very high before it reaches us as well. I will look into the main node to see if there is an issue there but this looks more like a specific route having issues than anything else.
14 289 ms 293 ms 289 ms 202.97.51.186
15 337 ms 336 ms 337 ms 202.97.50.42
16 476 ms * 493 ms 62.156.139.149
17 510 ms 520 ms * 217.239.40.186
Best Regards,
Guy W Hopkins
System Administrations Support
BurstNET Technologies作者: gdtv 时间: 2010-2-25 20:29
晕啊,我现在才注意到
我同一台Burst的VPS,原来分配的两个IP是64开头的,ping 300ms,后来加了5个IP,和楼主一样是96.9开头的,和楼主一样也是很慢,380ms
同一台VPS不同的网络?作者: 网络寄生虫 时间: 2010-2-25 20:30
跟他们要64开头的IP作者: 删除 时间: 2010-2-25 20:31
他说他家就一个机房, 可能有不同的线路吧. 我让他帮我换了, 不知道能不能给我换.作者: gdtv 时间: 2010-2-25 20:32
96开头的Ping很慢,不过网站实际访问还是很快,和64开头的一样作者: cnx 时间: 2010-2-25 20:33 http://94.icn.name/tmp/info.php
这是我新上的。作者: 删除 时间: 2010-2-25 20:41
Hello,
Again, it is the route here, not the IP. We have many different IP ranges within the datacenter. I have found nothing on the main node as well that would be causing this. Changing the node and main IP the VPS resides on would not necessarily change the route it takes. You can see from the other remote routes below that this isnt an issue with the IP.
他说这个有道理不?
[[email protected]. ~]$ traceroute 96.9.137.46
1 freeport.rapidvps.net (208.84.149.44) 0.082 ms
2 unallocated-host.rapidvps.net (66.35.95.125) 1.068 ms
3 ge-6-14.car2.Orlando1.Level3.net (4.53.46.81) 8.126 ms
4 ae-2-9.bar2.Orlando1.Level3.net (4.69.133.70) 8.124 ms
5 ae-0-11.bar1.Orlando1.Level3.net (4.69.137.145) 8.103 ms
6 ae-8-8.ebr1.Atlanta2.Level3.net (4.69.137.150) 29.665 ms
7 ae-63-60.ebr3.Atlanta2.Level3.net (4.69.138.4) 29.363 ms
8 ae-2-2.ebr1.Washington1.Level3.net (4.69.132.86) 34.821 ms
9 ae-71-71.csw2.Washington1.Level3.net (4.69.134.134) 42.974 ms
10 ae-24-79.car4.Washington1.Level3.net (4.68.17.70) 31.454 ms
11 62.156.139.129 31.690 ms
12 nyc-sc1-i.NYC.US.NET.DTAG.DE (62.156.131.141) 57.263 ms
13 vl0018.gwy01.sctn01.hostnoc.net (80.156.160.158) 42.637 ms
14 ec1-10.agg01.sctn01.hostnoc.net (64.191.19.6) 42.125 ms
15 ec1-15.vl0111.f2801.sctn01.hostnoc.net (96.9.191.30) 42.036 ms
16 vserver49.hostnoc.net (173.212.213.114) 42.823 ms
17 96913746.hostnoc.net (96.9.137.46) [open] 42.356 ms
[geek@france ~]$ traceroute 96.9.137.46
1 217.70.191.251 0.384 ms
2 vl2.core4-d.gandi.net (217.70.176.132) 0.272 ms
3 po88-jd4.core1-j.gandi.net (217.70.176.225) 0.559 ms
4 he.panap.fr (62.35.254.111) 0.908 ms
5 10gigabitethernet1-3.core1.lon1.he.net (72.52.92.33) 8.087 ms
6 10gigabitethernet4-4.core1.nyc4.he.net (72.52.92.241) 76.065 ms
7 10gigabitethernet1-2.core1.nyc1.he.net (72.52.92.46) 76.203 ms
8 vl0017.gwy03.sctn01.hostnoc.net (216.66.0.214) 87.235 ms
9 ec1-22.gwy01.sctn01.hostnoc.net (96.9.191.33) 87.137 ms
10 ec1-10.agg01.sctn01.hostnoc.net (64.191.19.6) 87.194 ms
11 ec1-15.vl0111.f2801.sctn01.hostnoc.net (96.9.191.30) 100.439 ms
12 vserver49.hostnoc.net (173.212.213.114) 87.314 ms
13 96913746.hostnoc.net (96.9.137.46) [open] 87.467 ms
[geek@singapore ~]$ traceroute 96.9.137.46
1 203.142.24.254 0.639 ms
2 202.157.128.61 0.716 ms
3 203.116.9.193 1.127 ms
4 203.118.3.226 5.356 ms
5 paix.he.net (198.32.176.20) 185.435 ms
6 10gigabitethernet4-1.core1.sjc2.he.net (72.52.92.70) 200.932 ms
7 10gigabitethernet1-3.core1.nyc4.he.net (72.52.92.26) 265.436 ms
8 10gigabitethernet1-2.core1.nyc1.he.net (72.52.92.46) 271.058 ms
9 vl0017.gwy03.sctn01.hostnoc.net (216.66.0.214) 283.548 ms
10 ec1-23.gwy02.sctn01.hostnoc.net (96.9.191.37) 265.426 ms
11 ec1-13.agg02.sctn01.hostnoc.net (64.191.108.46) 270.282 ms
12 ec1-15.f2801.sctn01.hostnoc.net (96.9.156.66) 274.446 ms
13 vserver49.hostnoc.net (173.212.213.114) 265.002 ms
14 96913746.hostnoc.net (96.9.137.46) [open] 270.252 ms
[geek@netherlands ~]$ traceroute 96.9.137.46
1 81.93.58.25 0.642 ms
2 ams-ix.he.net (195.69.145.150) 9.378 ms
3 10gigabitethernet4-1.core1.nyc4.he.net (216.66.24.153) 85.933 ms
4 10gigabitethernet1-2.core1.nyc1.he.net (72.52.92.46) 86.205 ms
5 vl0017.gwy03.sctn01.hostnoc.net (216.66.0.214) 96.855 ms
6 ec1-22.gwy01.sctn01.hostnoc.net (96.9.191.33) 97.213 ms
7 ec1-10.agg01.sctn01.hostnoc.net (64.191.19.6) 96.884 ms
8 ec1-15.vl0111.f2801.sctn01.hostnoc.net (96.9.191.30) 96.928 ms
9 vserver49.hostnoc.net (173.212.213.114) 97.221 ms
10 96913746.hostnoc.net (96.9.137.46) [open] 97.582 ms作者: fish 时间: 2010-2-25 20:48
是中国电信的问题吧
64走xo.net
94不走,这个burst没法调整的作者: fish 时间: 2010-2-25 20:49 标题: 回复 6# 的帖子 我ping 72.44.80.253 常年是550ms,不管抽不抽作者: pmalc 时间: 2010-2-25 20:54
我的是64的,照样抽作者: 删除 时间: 2010-2-25 21:04
我让他们换IP了
Guy H. 02-25-2010 - 08:01AM
Hello,
I will forward your request to our customer service department in regards to this. Please be aware that there may be some delay in response to your request.作者: blyema 时间: 2010-2-25 23:50
提示: 作者被禁止或删除 内容自动屏蔽作者: fangjianliu 时间: 2010-2-26 11:23
Pinging 96.9.137.46 with 32 bytes of data:
Reply from 96.9.137.46: bytes=32 time=393ms TTL=48
Request timed out.
Reply from 96.9.137.46: bytes=32 time=355ms TTL=48
Reply from 96.9.137.46: bytes=32 time=352ms TTL=48
Ping statistics for 96.9.137.46:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 352ms, Maximum = 393ms, Average = 366ms作者: cpuer 时间: 2010-2-26 19:20
Reply from 96.9.137.46: bytes=32 time=363ms TTL=49
Reply from 96.9.137.46: bytes=32 time=362ms TTL=49
Reply from 96.9.137.46: bytes=32 time=369ms TTL=49
Reply from 96.9.137.46: bytes=32 time=368ms TTL=49
Reply from 96.9.137.46: bytes=32 time=364ms TTL=49
Reply from 96.9.137.46: bytes=32 time=298ms TTL=49
Reply from 96.9.137.46: bytes=32 time=271ms TTL=49
Reply from 96.9.137.46: bytes=32 time=267ms TTL=49
Reply from 96.9.137.46: bytes=32 time=271ms TTL=49
Reply from 96.9.137.46: bytes=32 time=268ms TTL=49
Reply from 96.9.137.46: bytes=32 time=271ms TTL=49
Reply from 96.9.137.46: bytes=32 time=268ms TTL=49
Reply from 96.9.137.46: bytes=32 time=271ms TTL=49
Reply from 96.9.137.46: bytes=32 time=269ms TTL=49
Reply from 96.9.137.46: bytes=32 time=270ms TTL=49
Reply from 96.9.137.46: bytes=32 time=269ms TTL=49
Reply from 96.9.137.46: bytes=32 time=272ms TTL=49
Reply from 96.9.137.46: bytes=32 time=268ms TTL=49
Reply from 96.9.137.46: bytes=32 time=270ms TTL=49
Reply from 96.9.137.46: bytes=32 time=273ms TTL=49
Reply from 96.9.137.46: bytes=32 time=272ms TTL=49
Reply from 96.9.137.46: bytes=32 time=271ms TTL=49
Reply from 96.9.137.46: bytes=32 time=272ms TTL=49
Reply from 96.9.137.46: bytes=32 time=271ms TTL=49
我这访问时正常值。作者: cpuer 时间: 2010-2-26 19:22
原帖由 fish 于 2010-2-25 20:48 发表
是中国电信的问题吧
64走xo.net
94不走,这个burst没法调整的