How much latency warrants a complaint?

zonEEE

LA3G wrote: »

I do get 20-40 and less at times but it's the higher pings that prohibit the duration of each gaming session. Can you do a traceroute to an internet address for me and then ping -A it for a few minutes and post the results?

Tracert to a uk counter stike source server

C:\Documents and Settings\Administrator>tracert 193.93.44.47

Tracing route to 193.93.44.47 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.1.1
2 2 ms 1 ms 1 ms 88.151.81.1
3 3 ms 3 ms 2 ms c3-v9-so.fastcom.ie [83.245.74.14]
4 4 ms 4 ms 3 ms c4-v8-so.fastcom.ie [83.245.74.34]
5 774 ms 23 ms 7 ms s1-v7-so.fastcom.ie [83.245.74.29]
6 461 ms 242 ms 163 ms r2-v6-so.fastcom.ie [83.245.74.37]
7 166 ms 233 ms 19 ms mm3078.dublin1.eu.level3.net [212.187.194.65]
8 244 ms * 363 ms so-4-1-0.bbr1.London1.Level3.net [4.68.128.113]

9 409 ms 236 ms 151 ms ae-11-53.car1.London1.Level3.net [4.68.116.79]
10 631 ms 417 ms 640 ms unknown.Level3.net [212.113.11.142]
11 504 ms 136 ms 981 ms 193.93.44.47

Trace complete.

I could do a tracert in a few mins and it would be fine. DRIVES ME MAD! Complete crap for competitive gaming.

BostonB

Mine spikes, and if its bad I get kicked by punkster in COD4 for high pings. Its random so if I try again in 5 or 10 mins I might get away with it. Makes it very hard to play though as you lag, and your accuracy goes to pot.

Antamojo

Can anyone tell me why my request times out on every 2nd hop when I do a tracert?

PogMoThoin

Hope this explains it:

An asterisk, "*", followed by the words "request timed out" is not out of the ordinary. If the tracert had stopped here and continued to respond with "request timed out", then it might have been indicative of a problem. In the above example, the first "request timed out" is where the interface between our network and the rest of the Internet lies. The asterisk "*" is a normal consequence of our security implementation on that junction.

From Here

watty

Some (many?) routers put ICMP (ping) at low priority and may even almost ignore a direct ping. This is to protect against DDOS / POD attacks. So tracert and ping are not as definitive a test as they once were. Many mail servers won't respond to a ping ever.