Time for a new router?

[ImBojo]

I made sure all devices were disconnected and I tested this on two different PCs(both wired) and it produced the same result. If my connection is totally idle and I go to speedtest.net and run a test it raises makes my routers ping increase dramatically. A speedtest on an idle 20mb down connection should not be enough to saturate the line. I've also tried restoring to factory settings and no dice. The ping spikes while running the speed test but then goes back down to 1ms.

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=19ms TTL=64
Reply from 192.168.1.1: bytes=32 time=39ms TTL=64
Reply from 192.168.1.1: bytes=32 time=10ms TTL=64
Reply from 192.168.1.1: bytes=32 time=20ms TTL=64
Reply from 192.168.1.1: bytes=32 time=49ms TTL=64
Reply from 192.168.1.1: bytes=32 time=110ms TTL=64
Reply from 192.168.1.1: bytes=32 time=146ms TTL=64
Reply from 192.168.1.1: bytes=32 time=129ms TTL=64
Reply from 192.168.1.1: bytes=32 time=208ms TTL=64
Reply from 192.168.1.1: bytes=32 time=84ms TTL=64
Reply from 192.168.1.1: bytes=32 time=82ms TTL=64
Reply from 192.168.1.1: bytes=32 time=72ms TTL=64
Reply from 192.168.1.1: bytes=32 time=7ms TTL=64
Reply from 192.168.1.1: bytes=32 time=21ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=20ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=9ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=17ms TTL=64

 

[bill001g]

When you ping the router like this on a wired connection pretty much all you are testing is how busy the router is. Unlike wireless there is no error correction being attempted. It generally means the router is busy doing something else and chooses to do that over respond to your ping.

When you are doing speed test it is running NAT and maybe firewall filters. In generally most routers have more than enough CPU lately. Years ago it was easy to saturate a processor with traffic.

Depends on the router you might be able to see the cpu and memory utilization.

In any case I would try firmware first.

 

[ImBojo]

When you ping the router like this on a wired connection pretty much all you are testing is how busy the router is. Unlike wireless there is no error correction being attempted. It generally means the router is busy doing something else and chooses to do that over respond to your ping.

When you are doing speed test it is running NAT and maybe firewall filters. In generally most routers have more than enough CPU lately. Years ago it was easy to saturate a processor with traffic.

Depends on the router you might be able to see the cpu and memory utilization.

In any case I would try firmware first.

I've tried upgrading, and even downgrading firmware. No luck. If I ping google.com at the same time that ping is 500+.It is making my online games unplayable. I've tried QOS nothing seems to fix this latency problem. This just started sometime last week. I guess I'm going to be need a new router then?

 

[ImBojo]

Really need some more opinions on this guys. Don't want to spend $100 for no reason.