Read the forum guidelines
Problem seems to have started popping up last tThursday, but since then my house seems to have periods of time where the network speed slows the a crawl and I'm barely able to use the network (and definitely unable to run any multiplayer games). I've tried a bunch of different simple fixes but to no avail, so I'm at a loss on what I should try next.
What I've tried already
I noticed in this thread a guy says anything over 1-2ms on a ping to 192.168.0.1 is a problem, and here is my ping output:
Pinging 192.168.0.1 with 32 bytes of data:Reply from 192.168.0.1: bytes=32 time=6ms TTL=64Reply from 192.168.0.1: bytes=32 time=3ms TTL=64Reply from 192.168.0.1: bytes=32 time=10ms TTL=64Reply from 192.168.0.1: bytes=32 time=7ms TTL=64Ping statistics for 192.168.0.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 3ms, Maximum = 10ms, Average = 6ms
Here is also my connection information which I grabbed from my netgear admin panel:
Lastly, here's a tracert of google.com:
Tracing route to google.com [2607:f8b0:4007:80d::200e]over a maximum of 30 hops:1 4 ms 9 ms 6 ms 2600:8801:2980:81d:a02:8eff:fec6:6662 2 245 ms 119 ms 318 ms 2600:8801:29ff:ffff::1111 3 427 ms * 82 ms 2001:578:601:fffc:500::1c 4 24 ms 143 ms 30 ms 2001:578:604::1a 5 65 ms 48 ms 42 ms 2001:578:1:0:172:17:249:79 6 59 ms 110 ms 77 ms 2001:578:20:c100::5:1 7 184 ms 235 ms 48 ms 2001:4860:0:1004::e 8 43 ms 89 ms 59 ms 2001:4860::c:4001:13cf 9 45 ms 49 ms 309 ms 2001:4860::c:4000:de3d 10 215 ms 49 ms 332 ms 2001:4860::1:0:c432 11 * 78 ms 132 ms 2001:4860:0:110d::1 12 185 ms 94 ms 36 ms 2001:4860:0:1::1f01 13 372 ms 259 ms 50 ms lax28s10-in-x0e.1e100.net [2607:f8b0:4007:80d::200e]Trace complete.
Any ideas on what I should try?
Long story short, gateways are bad. I would suggest buying a separate modem and router. But besides that, can you explain how the coaxial gets from the street to that modem? Your downstream levels look on the high side. Are you going through a coaxial signal amp?
One simple thing to try, to rule out a signal issue to the modem. Disconnect the coaxial from the back of the modem (still have ethernet connected from modem>PC) and then try to ping 192.168.0.1. If still above 1ms, you know it's not the signal.
Thanks for the reply! I'll try pinging my router with it unplugged when I'm home today to see what I get. The Modem/Router is only a month or so old, but it might just be faulty.By the way, if I buy a new Modem & Router do I need to call Cox to let them know? Or can I just switch it out with no issues and Cox will detect my new equipment?EDIT: I'm not sure about how my coaxial gets from the street to the modem. We currently have it plugged in upstairs so there's a change it's going through some type of splitter. There are two other cable connections in the house.Should I aim to remove the splitter for a stronger signal? I'm pretty noobish at ground cables when it comes to internet, though I'm dedicated to put the work in to improve my signal.
I wouldn't touch the coaxial/cable until we rule out the gateway. There would have to be some strange and strong interference on the cable line for it to cause latency spikes like that, but anything is possible.
If it is a bad gateway, instead of just swapping out for a new one, I would suggest getting a stand alone modem like the Arris SB6183 or Netgear CM500. Then buy your own router. If you like Netgear, anything in the Nighthawk family is great. I am partial to Asus so like the Asus RT-AC68P. There are lots of other options depending on your budget. Newegg and SmallNetBuilder are two websites useful for user and peer review.
As for the signal, I will give suggestions once I know more about how everything is wired together. In general though, you want the modem on the FIRST splitter, and NOT on the amp.
By the way, I assume the ethernet you are connecting from your PC to the modem/router is less then 10 feet right? It isn't some 100 foot ethernet you bought at Walmart or anything is it? I only ask because that could be causing the latency and putting us on a wild goose chase.