NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R7000 Wifi issues
I've had my trusty R7000 for a few months now and it's done very well, up until maybe a month or so ago. All of a sudden my wifi performance took a nose dive, however it wasn't my bandwidth, seems li...
So hitting the reset button solved my issues. Now I wish I knew what was causing it. Thanks for your help!
Here are the results, as you can see on the 12th one it timed out. Does the same on a repeat. What do I do with this info?
C:\WINDOWS\system32>tracert www.google.com
Tracing route to www.google.com [74.125.21.105]
over a maximum of 30 hops:
1 31 ms 29 ms 31 ms 10.109.1.1
2 33 ms 43 ms 30 ms 45.32.128.1
3 30 ms 31 ms 31 ms xe-1-2-2.cr1.sjc2.us.as4436.gtt.net [69.22.143.237]
4 31 ms 31 ms 32 ms xe-11-3-1.sjc12.ip4.gtt.net [89.149.184.237]
5 31 ms 31 ms 32 ms as15169.sjc10.ip4.gtt.net [199.229.230.134]
6 44 ms 31 ms 31 ms 216.239.49.170
7 97 ms 97 ms 97 ms 209.85.246.38
8 82 ms 91 ms 84 ms 216.239.46.240
9 83 ms 71 ms 70 ms 209.85.240.23
10 96 ms 95 ms 99 ms 72.14.234.3
11 94 ms 96 ms 97 ms 209.85.142.153
12 * * * Request timed out.
13 97 ms 95 ms 96 ms yv-in-f105.1e100.net [74.125.21.105]
Timeouts can occur at a hop if that node doesn’t respond to ping.
You posted results are pretty close to mine (testing from the UK) and that output doesn’t look particularly odd to me. The idea is that if you find a site that appears to have high latency then this can occur if data is being delayed between your computer and the destination, and a tracert can often identify where this is occurring. If tracert shows no particular lags, then you can look at other possibilities like a slow server, your own computer firewall or AV software, or slow / unresponsive scripts.