PDA

View Full Version : Random Ping Spikes


Inf.
13-08-2007, 16:21
ok, for the past month or so ive been getting ping spikes of between 200-1000 every 5-10seconds for approximately 2-3 seconds each.

The effect this is having on gaming is ridiculous, especially with games that have a very sensitive netcode, such as Quake 4. Here's an example of the problem, and two tracert screenshots showing the point at which the spike occurs:

www.dgcoding.co.uk/Q4lagwtf.rar <-- video showing the effects

www.dgcoding.co.uk/tracertspike.JPG

www.dgcoding.co.uk/tracertspike2.JPG

the server i am pinging in the examples above is a Quake 4 server chosen at random

the above problem occurs on -all- server in all games, and is present even when not gaming. I do have a netgear router, but all ports are opened and ive had the same router for atleast a year, the problem has only been occuring for a few months. There is a 25page thread on VM ping issues on the World of Warcraft EU technical forums, thus this problem is occuring to many people

link to thread : http://forums.wow-europe.com/thread.html?topicId=207050797&sid=1

I have contacted VM about the problem, but they deny the problem is there end and i very much doubt they care enough to even look into it. Any help on fixing this would be appreciated

thanks <3

Hugh
13-08-2007, 17:06
Have you tried it without the router?

This would then prove (probably) it wasn't the router.....

btw, still can't see your traceroutes.

Inf.
13-08-2007, 17:12
yeh the [img] or [IMG] tags refuse to work, just copy/paste the address into browser

tried without router, problem remains

Hugh
13-08-2007, 17:21
Inf.,
I pinged the ip address that seems to be causing an issue
"C:\Documents and Settings\xxxx.xxxxxxxxxxxxx>ping 62.31.224.225
Pinging 62.31.224.225 with 32 bytes of data:
Reply from 62.31.224.225: bytes=32 time=22ms TTL=245
Reply from 62.31.224.225: bytes=32 time=70ms TTL=245
Reply from 62.31.224.225: bytes=32 time=18ms TTL=245
Reply from 62.31.224.225: bytes=32 time=18ms TTL=245
Ping statistics for 62.31.224.225:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 70ms, Average = 32ms
I did this a few times, and got averages of 17ms to 36ms. What do you get if you ping it?

Here's what I got on a tracert:-
C:\Documents and Settings\xxxx.xxxxxxxxxxx>tracert 213.208.119.120
Tracing route to 213.208.119.120 over a maximum of 30 hops
1 2 ms 1 ms 1 ms 192.168.1.1
2 10 ms 9 ms 9 ms xx.xxx.xxx.1
3 33 ms 8 ms 9 ms leed-t2cam1-b-ge911.inet.ntl.com [80.0.55.25]
4 226 ms 10 ms 9 ms host80-0-50-146.no-dns-yet.ntli.net [80.0.50.146]
5 142 ms 9 ms 9 ms lee-bb-b-so-020-0.inet.ntl.com [213.105.175.69]
6 10 ms 9 ms 17 ms lee-bb-a-ge-000-0.inet.ntl.com [62.253.187.185]
7 15 ms 14 ms 24 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
8 80 ms 14 ms 15 ms tele-ic-2-as0-0.inet.ntl.com [62.253.184.6]
9 182 ms 17 ms 15 ms 212.250.14.42
10 85 ms 14 ms 18 ms g2-48-5.ar01.tn5.bb.pipex.net [62.72.140.14]
11 58 ms 16 ms 15 ms ge-0-0-0-3801.jolt-gw.cust.pipex.net [212.241.241.14]
12 27 ms 14 ms 19 ms 213.208.119.120
Trace complete.
C:\Documents and Settings\Hugh.>tracert 213.208.119.120
Tracing route to 213.208.119.120 over a maximum of 30 hops
1 1 ms 2 ms 1 ms 192.168.1.1
2 7 ms 7 ms 9 ms xx.xxx.xxx.1
3 9 ms 9 ms 9 ms leed-t2cam1-b-ge911.inet.ntl.com [80.0.55.25]
4 9 ms 9 ms 9 ms host80-0-50-146.no-dns-yet.ntli.net [80.0.50.146]
5 8 ms 10 ms 12 ms lee-bb-b-so-020-0.inet.ntl.com [213.105.175.69]
6 10 ms 9 ms 11 ms lee-bb-a-ge-000-0.inet.ntl.com [62.253.187.185]
7 120 ms 15 ms 14 ms pop-bb-b-so-100-0.inet.ntl.com [62.253.185.238]
8 14 ms 31 ms 15 ms tele-ic-2-as0-0.inet.ntl.com [62.253.184.6]
9 15 ms 15 ms 16 ms 212.250.14.42
10 15 ms 15 ms 13 ms g2-48-5.ar01.tn5.bb.pipex.net [62.72.140.14]
11 16 ms 15 ms 14 ms ge-0-0-0-3801.jolt-gw.cust.pipex.net [212.241.241.14]
12 102 ms 15 ms 15 ms 213.208.119.120
Trace complete.

Inf.
13-08-2007, 17:24
you may want to censor the folder name on the bottom part aswell as the top :P

C:\Documents and Settings\Mike>ping 62.31.224.225
Pinging 62.31.224.225 with 32 bytes of data:
Reply from 62.31.224.225: bytes=32 time=10ms TTL=253
Reply from 62.31.224.225: bytes=32 time=12ms TTL=253
Reply from 62.31.224.225: bytes=32 time=217ms TTL=253
Reply from 62.31.224.225: bytes=32 time=22ms TTL=253
Ping statistics for 62.31.224.225:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 217ms, Average = 65ms

the spike can be clearly seen :o

AmAtoL
13-08-2007, 20:22
I know it's no consolation Inf. but the exact same thing happens on Battlefield 2142 for me, doesn't matter which server either.
I usually know something is up when I keep retracing my steps, and turning in the wrong direction repeatedly, it's bl00dy annoying while it lasts.
The ping spikes can go up to 700+, and those are just the ones I see in the game scoreboard. It does settle down, but generally I rarely get any uber connections where the hit recognition is spot on :(. I've had only 2 nights where I would say the connection was what I was expecting, say, in the the last 2 months.

evilmonkey
14-08-2007, 17:26
Ping spikes like this wont affect online gaming as pings are no indication of how the server will treat actual data. Remember ICMP is low priority. only worry about it if every hop in the trace is high.

AmAtoL
14-08-2007, 19:31
Well whatever, but it is impossible to play with a "ping spike" of around 700, like I said in another post, ping is no indication of quality, and that is where VM fall down....on quality.
I know it's hard to pinpoint but something isn't right somewhere, and the browsing speed for a 20 meg connection is a complete joke.

Inf.
14-08-2007, 19:56
the ping spikes -do- affect online gaming as my video shows, especially on engines with a delicate netcode

trevortt
14-08-2007, 19:57
Have Virgin even tried to check your line? I know that on my line UBR03 is a shambles and i have ping spikes in games atleast once a week yet Virgin deny its their fault.

All i ask is a simple diagnostic of the line, not much to ask for really.

Oh and ping spikes do affect online gaming alot.

evilmonkey
15-08-2007, 11:18
Have Virgin even tried to check your line? I know that on my line UBR03 is a shambles and i have ping spikes in games atleast once a week yet Virgin deny its their fault.

All i ask is a simple diagnostic of the line, not much to ask for really.

Oh and ping spikes do affect online gaming alot.

Ping spikes run from your dos prompt do not show that data is not being treated properly as ICMP is not treated the same as the actual data. You need a network quality monitor to check that. When they check the line they will find that their is most likely nothing wrong and point you back to the game server provider. Remember they are only responsible for their own network. But given the state of things you will be told its spyware or a virus on your machine and sent on your way. Would help if someone listed the IPs of the servers in question even just one for testing. But I cant emphasise enough PINGS from DOS DO NOT show data quality over a network.

trevortt
15-08-2007, 18:48
Ping spikes run from your dos prompt do not show that data is not being treated properly as ICMP is not treated the same as the actual data. You need a network quality monitor to check that. When they check the line they will find that their is most likely nothing wrong and point you back to the game server provider. Remember they are only responsible for their own network. But given the state of things you will be told its spyware or a virus on your machine and sent on your way. Would help if someone listed the IPs of the servers in question even just one for testing. But I cant emphasise enough PINGS from DOS DO NOT show data quality over a network.

Well i am having huge ping spikes just pinging my modem so i am now positive its their fault and not mine and i have a clean computer, i daily run avg free, spybot S&D, a-squared anti malware and Adware 2007.

This is not huge spikes but i should be getting 1ms to the modem not 4ms.

Pinging 192.168.100.1 with 32 bytes of data:

Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=5ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63

Ping statistics for 192.168.100.1: MODEM
Packets: Sent = 26, Received = 26, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 6ms, Average = 4ms

evilmonkey
16-08-2007, 11:32
Well i am having huge ping spikes just pinging my modem so i am now positive its their fault and not mine and i have a clean computer, i daily run avg free, spybot S&D, a-squared anti malware and Adware 2007.

This is not huge spikes but i should be getting 1ms to the modem not 4ms.

Pinging 192.168.100.1 with 32 bytes of data:

Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=5ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=6ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63
Reply from 192.168.100.1: bytes=32 time=4ms TTL=63

Ping statistics for 192.168.100.1: MODEM
Packets: Sent = 26, Received = 26, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 6ms, Average = 4ms

not necessarily. How are you connected. I get between 8 and 10 ms to my modem and I have no problems.