Need help troubleshooting extreme network latency

[ylin0811]

It's pretty much what I've been doing for the past few days, just to see.

I mean are there any performance benefits inherent when using the 5GHz band, even when you don't utilize the full gigabit speeds?

You can stick with 5ghz. Try different non-dfs channels and see if that makes any difference.

 

[John Connor]

It's pretty much what I've been doing for the past few days, just to see.

I mean are there any performance benefits inherent when using the 5GHz band, even when you don't utilize the full gigabit speeds?

Performance wise in 5GHz you're looking at a less crowded band and gigabit speeds. If you don't have like a NAS or something like a media server you really don't need AC in 5GHz.

How old is the Asus? You might want to see about a new one or a different router.

Were any of those ping tests using an ethernet cable or just 5GHz? Try an ethernet cable and use www.pingtest.net once.

 

[TooMuchStarbucks]

Actually just experienced about a minute of extreme latency even on the 2.4GHz channel. Unfortunately my desktop isn't in the same room with my router, so it's hard to test something with a wired connection during these brief windows.

 

[ylin0811]

Note the packet loss percentage in between your gateway and 8.8.8.8. Your 192.168.1.1 has 3% packet loss, while 8.8.8.8 has 4% (7-3) packet loss. The packet loss is either occurring inside comcast's network, or you have some interference going on with your wireless at 2.4ghz band.

One of the very remote possibilities is the shared memory space on your asus router. I've only seen this less than 5 times out of hundreds of cases i've seen, and this is if comcast doesn't admit any fault with their backbone juniper/cisco/quagga equipment.

When a packet travels from your internet or your pc, your router will create a nat entry and store that in the protected memory space. If the memory space is corrupted, you will experience packet loss because the router will not be able to un-translate the packet from the global to a local address. However, the only way to see this would be to perform a packet capture on the ingress interface facing your isp.

But i still think the issue is on the comcast side, because your 5ghz pingplotter result didn't show any packet loss on the first hop. If there is truly a issue with your router's protected memory space or the radio, you will get high rtt and/or packet loss on the first hop.

I would recommend you try the following:

1. Reset the router back to factory default settings, and reconfigure all the settings for the router. Don't touch any qos/wmm settings. Leave the security on WPA2.

2. Go to best buy or another store and purchase a router. Use the router for a couple days and see if the issue shows up. If it doesn't, then all is well. If not, you will still have to pursue with comcast.

If you don't get any luck with comcast, you might be able to escalate this case by sending an email to peering@comcast.com and include your ticket number and a detailed description of the issue. If the issue is truly caused by comcast, it will have to be fixed by folks who handle the peering and backbone routing.

 

[John Connor]

If you could plug in right to the modem with a laptop and run a ping test that could help in knowing if it's Comcast or not. Just single out the WIFI.