HELP!!!! consistent ping spike problems directly from router

[corymacrae]

I have been having bad lag spike issues constantly impacting my performance when gaming. I have attempted to rule out all interference by having all my devices on the 2.4 ghz network while keeping only my pc on the 5ghz about 2 meters away from the router in the next room. I am able to replicate this on any wireless interface i check it on from android to other laptops and even a surface tablets, but all yield identical results. The only other wireless devices at all (ie apple tv, wireless home phone, walkie talkie, anything with a wireless wave etc.) are a couple cell phones, a smart tv, occasionally an apple tv, chrome cast, tablets(although ive disconnected them all in an attempt to reduce lag) and a microwave all exclusively using the 2.4 ghz network

pinging my router should show that this is not an isp issue and indeed a router issue


Router: actiontec R1000H (r3000H Bell fibre op router)

This is my ping of cmd and notice the intervals in between spikes as they are incredibly consistent, especially on continuous ping mode

Pinging 192.168.2.1 with 32 bytes of data:
Reply from 192.168.2.1: bytes=32 time=3ms TTL=64
Reply from 192.168.2.1: bytes=32 time=3ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=491ms TTL=64
Reply from 192.168.2.1: bytes=32 time=186ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=227ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=3ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=3ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=475ms TTL=64
Reply from 192.168.2.1: bytes=32 time=166ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=155ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=2ms TTL=64
Reply from 192.168.2.1: bytes=32 time=1ms TTL=64

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

 

[J_E_D_70]

I'd write down all my settings and then do a factory reset (usually a recessed button, hold for 10 seconds).

Failing that, probably time for a new router. I had an odd ping issue a few years ago and tried to fix it by flashing the bios with DD WRT but still no luck. Seems like once a router starts to flake out there's not much you can do.

But, if you're only 2 meters away why not run cat 5 thru the wall? Put it near a baseboard and use faceplates.

One more thing - do you have a spare wireless card (or can borrow one) to double check that it's not on the client side? Could also uninstall and reinstall wireless driver.

 

[RARRAF]

a powerline adaptor might be a good choice the cheaper ones are ok and quite good far better than wifi
http://www.pcadvisor.co.uk/test-centre/network-wifi/20-best-powerline-adapters-2017-uk-3490638/