Random high ping spikes on WIFI Need Help

[SirJosh]

Hey

In the last couple of months I have noticed that my ping has been slowly increasing and the rate of high ping spikes had doubled. It was not that long ago that I was able to play at 60ms, but now I am at (75-100) plus with the additional frequent spikes in ping that reach up to 500-1000ms. It's become really frustrating and now finally I've had it. I am on wireless and have been for a long time, it's just only recently that my latency in games has been bad.

As I said, spikes occur randomly and can last for seconds, even minutes. I would be playing at 75ms then suddenly it would spike up to 300ms and it would stay there for a few minutes. My download speed has been going fine, it's just been my latency.

I had this problem a few nights ago so I changed the wifi channel to 1 and restarted the whole modem. The ping was back to normal again. Now I am just completely confused.

Things I've tried:
.Restarting the modem
.Flushing the dns
.Cleaning the cache
.Uninstalling and reinstalling the wireless adapter using device manager
.Updated all my drivers
.Anti-virus scan
.Changed wifi channels

Here is some extra tests I have done using cmd
Ping google's servers
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Computer>ping google.com.au

Pinging google.com.au [74.125.237.175] with 32 bytes of data:
Reply from 74.125.237.175: bytes=32 time=77ms TTL=53
Reply from 74.125.237.175: bytes=32 time=76ms TTL=53
Reply from 74.125.237.175: bytes=32 time=111ms TTL=53
Reply from 74.125.237.175: bytes=32 time=79ms TTL=53

Ping statistics for 74.125.237.175:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 76ms, Maximum = 111ms, Average = 85ms

C:\Users\Computer>ping google.com.au

Pinging google.com.au [74.125.237.175] with 32 bytes of data:
Reply from 74.125.237.175: bytes=32 time=76ms TTL=53
Reply from 74.125.237.175: bytes=32 time=92ms TTL=53
Reply from 74.125.237.175: bytes=32 time=85ms TTL=53
Reply from 74.125.237.175: bytes=32 time=81ms TTL=53

Ping statistics for 74.125.237.175:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 76ms, Maximum = 92ms, Average = 83ms

C:\Users\Computer>

Pinging router

C:\Users\Computer>ping -n 30 -l 1000 192.168.1.254

Pinging 192.168.1.254 with 1000 bytes of data:
Reply from 192.168.1.254: bytes=1000 time=1ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=4ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=2ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=1ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=7ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=2ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=3ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=11ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=3ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=1ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=2ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=3ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=2ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=710ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=2ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=1ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=1ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=2ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=2ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=1ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=5ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=3ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=2ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=2ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=3ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=2ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=1ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=1ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=2ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=4ms TTL=64

Ping statistics for 192.168.1.254:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 710ms, Average = 26ms

If you guys need any more info, please tell me

 

[i7Baby]

Use ethernet cable instead

Put the router next to your PC or your PC next to the router.

See if they improve things.

 

[SirJosh]

Use ethernet cable instead

Put the router next to your PC or your PC next to the router.

See if they improve things.

Unfortunately the modem is too far away from my computer to be able to use an ethernet cable. I cannot move it into a different spot as it is connected to another computer that doesn't allow wireless.

 

[i7Baby]

Any other users on the network?

Maybe your wifi isn't working properly because its to far away from the router. How far away? Through walls and floors?

 

[SirJosh]

Any other users on the network?

Maybe your wifi isn't working properly because its to far away from the router. How far away? Through walls and floors?

We've got around 3 or 4 devices total that are connected to the network and the router is only two walls away from me. Still, I never use to get these sort of latency problems before. It is only just began to occur in the last few months.

 

[i7Baby]

Things get old.

What wifi card in your PC?

What router you got?

 

[SirJosh]

I'm not sure if any of these things are wifi cards but here is what I found:
ASUS PCE-N53 300Mbps 11n dual band Wireless PCI-E card
Microsoft Virtual WiFi Miniport Adapter #2
Realtek PCIe GBE Family Controller #2

My router is a Billion(Brand) BiPAC 7800NL(Model)

 

[SirJosh]

A thing I did notice for when I was pinging my router was that at one reply it spikes up to 710 ms
Reply from 192.168.1.254: bytes=1000 time=2ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=710ms TTL=64
Reply from 192.168.1.254: bytes=1000 time=2ms TTL=64

Is this normal? Is it a problem with my router or the signal between it?

 

[FreeTickets]

I have same issue, this started two weeks ago. Pinging router or google, time = 1ms, 1ms, 1ms, 700ms, 1ms. so every 4 sends, 1 is off. Still haven't found a solution so will attempt a Powerline fix.