View Full Version : Im getting high ping (350+)
davo_cabe
03-28-2011, 07:41 PM
hi all
I just get in the server this week and have this annoying ping: 350, 400 and high... then lags a lot, but with 0% packet loss, i used to get 200 - 230 ping... the server was moved to another place?, i dont know why im getting this high ping, it didnt happens in the others servers i play. I checked my connection and is ok, maybe someone is getting the same problem?
(sorry for my bad english)
Gravity
03-28-2011, 07:52 PM
Yea i have the same problem :/
If you are having connection issues I need you to go to start run and type cmd
once cmd is open you need to ping 209.160.77.226 and also tracert 209.160.77.226
I can then send to network engineers to troubleshoot. Help me help you :)
|uK|Chronox
03-29-2011, 08:44 AM
My ping varies a too much sometimes so im posting mine lol.
http://i56.tinypic.com/33dw7zr.png
SilverWing
03-29-2011, 09:42 AM
u forgot to scratch one out chronox fail
davo_cabe
03-29-2011, 11:50 AM
this?
http://img851.imageshack.us/img851/2569/dibujovvk.png
|uK|Chronox
03-29-2011, 01:38 PM
Ya i noticed that while uploading it, but im too lazy to re-upload it :)
I use netspeed 10000 btw, does netpseed make a difference ?
Try netspeed 20000 although I don't think it will help. It is an ISP issue for the both of you though. I've traced you both from the server and it is definitely on your ISP network...
Here are serverside traceroutes.
davo (twice)
traceroute to 190.188.253.233 (190.188.253.233), 30 hops max, 60 byte packets
1 h-vl202-d3.acc.dca2.hopone.net (209.160.72.2) 0.593 ms 0.613 ms 0.685 ms
2 gec13.core1.dca2.hopone.net (209.160.60.241) 0.309 ms 0.368 ms 0.443 ms
3 gec11.core2.dca2.hopone.net (66.36.224.58) 0.400 ms 0.475 ms 0.510 ms
4 dca-edge-18.inet.qwest.net (209.160.62.133) 1.334 ms 1.387 ms 1.422 ms
5 atx-brdr-01.inet.qwest.net (67.14.14.134) 17.983 ms 18.032 ms 18.075 ms
6 63.146.26.214 (63.146.26.214) 111.674 ms 111.196 ms 110.982 ms
7 cablevision.baires3.bai.seabone.net (195.22.220.118) 251.731 ms 251.764 ms 251.662 ms
8 221-165-89-200.fibertel.com.ar (200.89.165.221) 251.195 ms 255.502 ms 255.425 ms
9 198-165-89-200.fibertel.com.ar (200.89.165.198) 252.056 ms 251.854 ms 255.443 ms
10 106-165-89-200.fibertel.com.ar (200.89.165.106) 255.376 ms 255.253 ms 255.271 ms
11 * * *
12 * * *
13 233-253-188-190.cab.prima.net.ar (190.188.253.233) 266.594 ms 266.333 ms 269.698 ms
1 h-vl202-d3.acc.dca2.hopone.net (209.160.72.2) 0.632 ms 0.659 ms 0.697 ms
2 gec13.core1.dca2.hopone.net (209.160.60.241) 0.311 ms 0.376 ms 0.451 ms
3 gec11.core2.dca2.hopone.net (66.36.224.58) 0.409 ms 0.482 ms 0.558 ms
4 dca-edge-18.inet.qwest.net (209.160.62.133) 1.346 ms 1.408 ms 1.444 ms
5 atx-brdr-01.inet.qwest.net (67.14.14.134) 17.957 ms 17.997 ms 18.031 ms
6 63.146.26.214 (63.146.26.214) 107.924 ms * *
7 * * cablevision.baires3.bai.seabone.net (195.22.220.118) 253.020 ms
8 * 221-165-89-200.fibertel.com.ar (200.89.165.221) 252.092 ms 252.133 ms
9 198-165-89-200.fibertel.com.ar (200.89.165.198) 252.066 ms 252.126 ms 252.168 ms
10 106-165-89-200.fibertel.com.ar (200.89.165.106) 255.525 ms 254.612 ms 254.672 ms
11 * * *
12 * * *
13 233-253-188-190.cab.prima.net.ar (190.188.253.233) 283.691 ms 283.868 ms 284.713 ms
Chronox, same for you. Contact your ISP with your traceroutes and the serverside traces because the latency occurs on their network.
root@sls-ga22p16:~# traceroute -I 190.67.39.94
traceroute to 190.67.39.94 (190.67.39.94), 30 hops max, 60 byte packets
1 h-vl202-d3.acc.dca2.hopone.net (209.160.72.2) 0.427 ms 0.450 ms 0.521 ms
2 gec13.core1.dca2.hopone.net (209.160.60.241) 0.270 ms 0.315 ms 0.350 ms
3 ge-7-27.car1.washington1.level3.net (66.36.224.189) 0.761 ms 0.801 ms 0.940 ms
4 ae-2-70.edge3.Washington4.Level3.net (4.69.149.82) 1.315 ms 1.365 ms 1.437 ms
5 TELEFONICA.edge3.Washington4.Level3.net (4.53.112.42) 91.387 ms 91.428 ms 91.462 ms
6 Xe4-1-0-0-grtmiabr4.red.telefonica-wholesale.net (213.140.36.178) 67.838 ms 67.730 ms 67.774 ms
7 So7-0-2-0-grtmiana3.red.telefonica-wholesale.net (213.140.37.77) 91.258 ms 91.102 ms Xe2-0-6-0-grtmiana2.red.telefonica-wholesale.net.119.142.94.in-addr.arpa (94.142.119.229) 185.081 ms
8 GE7-0-0-0-gramiana2.red.telefonica-wholesale.net.121.142.94.in-addr.arpa (94.142.121.137) 91.406 ms GE6-0-0-0-gramiana2.red.telefonica-wholesale.net.121.142.94.in-addr.arpa (94.142.121.133) 108.391 ms 108.422 ms
9 Colombia-Telecom-4-2-2-0-gramiana2.red.telefonica-wholesale.net (84.16.8.246) 159.743 ms 159.692 ms Colombia-Telecom-4-2-0-0-gramiana2.red.telefonica-wholesale.net (84.16.8.74) 156.438 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
root@sls-ga22p16:~# traceroute -I 190.67.39.94
traceroute to 190.67.39.94 (190.67.39.94), 30 hops max, 60 byte packets
1 h-vl202-d3.acc.dca2.hopone.net (209.160.72.2) 0.484 ms 0.511 ms 0.585 ms
2 gec13.core1.dca2.hopone.net (209.160.60.241) 0.330 ms 0.384 ms 0.419 ms
3 ge-7-27.car1.washington1.level3.net (66.36.224.189) 0.910 ms 0.946 ms 0.981 ms
4 ae-2-70.edge3.Washington4.Level3.net (4.69.149.82) 61.963 ms 62.041 ms 62.076 ms
5 TELEFONICA.edge3.Washington4.Level3.net (4.53.112.42) 70.419 ms 70.470 ms 70.505 ms
6 Xe4-1-0-0-grtmiabr4.red.telefonica-wholesale.net (213.140.36.178) 66.012 ms 66.035 ms 66.080 ms
7 Xe2-0-6-0-grtmiana2.red.telefonica-wholesale.net.119.142.94.in-addr.arpa (94.142.119.229) 140.829 ms So7-0-2-0-grtmiana3.red.telefonica-wholesale.net (213.140.37.77) 89.573 ms Xe6-1-1-0-grtmiana3.red.telefonica-wholesale.net.123.142.94.in-addr.arpa (94.142.123.1) 92.766 ms
8 GE6-0-0-0-gramiana2.red.telefonica-wholesale.net.121.142.94.in-addr.arpa (94.142.121.133) 89.719 ms GE7-0-0-0-gramiana2.red.telefonica-wholesale.net.121.142.94.in-addr.arpa (94.142.121.137) 89.646 ms GE6-0-0-0-gramiana2.red.telefonica-wholesale.net.121.142.94.in-addr.arpa (94.142.121.133) 89.591 ms
9 Colombia-Telecom-4-2-0-0-gramiana2.red.telefonica-wholesale.net (84.16.8.74) 155.490 ms 153.677 ms 153.618 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
davo_cabe
03-29-2011, 05:06 PM
oh ok, so its an isp problem... i cant fix it, thanks for the help $carface
Gravity
03-29-2011, 07:10 PM
Yay !
Normal Ping ( 120 - 160) :P
|uK|Anthrax
03-29-2011, 07:36 PM
My ping is
( 230 - 610 ) yy'
|uK|Chronox
03-30-2011, 12:10 AM
So if i contact them my normal 100-140 ping would be lowered a bit if they do something ?
If they can replicate your issue, which they should be able to they will hopefully fix it. You wouldn't get a better ping per se but you would get a better overall connection without the timeouts on your connection where the stars are in your traceroute
|uK|B|aZe//.
03-30-2011, 08:28 AM
you can fix it davo you just have to complain and show these results!
davo_cabe
03-30-2011, 12:37 PM
oh ok i will try it, thanks again for the help ;)
[R]^Osyris
09-12-2014, 06:47 PM
1973
I have so much lag... is some problem of ISP? =/
Moskva
09-12-2014, 07:41 PM
It has been 3 years, 3 damn years
~~D4RR3N~~
09-12-2014, 09:04 PM
It has been 3 years, 3 damn years
It is never too late to revive a dead thread. Never.
You are tracing the wrong IP???
|uK|B|aZe//.
09-17-2014, 08:38 AM
LOL
TimTim
09-17-2014, 02:09 PM
I read the thread title as "Im getting high on ping"... I have not had my coffee yet today.
4.2.3