Tried to run some tests on my cell phone hooked up to the wifi. Got mixed test results, started at 80ms ping. Kept testing... each test the ping went up some, reached 298ms once, then went back down again. Ran some tests on the desktop again after keeping the router unplugged for two days.
Did a ping and traceroute test. Here are the results:
Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.
C:\Users\William>ping google.com
Pinging google.com [74.125.228.97] with 32 bytes of data:
Reply from 74.125.228.97: bytes=32 time=44ms TTL=49
Reply from 74.125.228.97: bytes=32 time=49ms TTL=49
Reply from 74.125.228.97: bytes=32 time=41ms TTL=49
Reply from 74.125.228.97: bytes=32 time=40ms TTL=49
Ping statistics for 74.125.228.97:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 49ms, Average = 43ms
C:\Users\William>tracert google.com
Tracing route to google.com [74.125.228.102]
over a maximum of 30 hops:
1 3 ms 3 ms 2 ms 192.168.1.1
2 12 ms 9 ms 10 ms 10.113.64.1
3 372 ms 440 ms 486 ms gi5-2-15-cmts.emirny27-rtr002.cny.northeast.rr.c
om [24.94.32.150]
4 536 ms 539 ms 561 ms ae15.ithcnycy-rtr001.cny.northeast.rr.com [74.74
.108.98]
5 502 ms 475 ms 387 ms rdc-74-74-108-116.cny.east.twcable.com [74.74.10
8.116]
6 317 ms 354 ms 290 ms 107.14.19.104
7 227 ms 237 ms 260 ms ae4.pr1.chi10.tbone.rr.com [66.109.1.66]
8 64 ms 73 ms 65 ms 74.125.48.109
9 28 ms 31 ms 61 ms 209.85.254.122
10 33 ms 29 ms 31 ms 209.85.254.238
11 45 ms 38 ms 37 ms 72.14.232.72
12 64 ms 82 ms 62 ms 72.14.236.147
13 65 ms 66 ms 65 ms 72.14.238.253
14 87 ms 236 ms 201 ms iad23s08-in-f6.1e100.net [74.125.228.102]
Trace complete.
C:\Users\William>
----------------------------------------------------------------------------------------
I ran a second one since the first didnt look terrible. Seems to be pretty good looking right now... Maybe keeping the router off for multiple days fixed it?
C:\Users\William>tracert google.com
Tracing route to google.com [74.125.228.101]
over a maximum of 30 hops:
1 3 ms 2 ms 3 ms 192.168.1.1
2 13 ms 12 ms 13 ms 10.113.64.1
3 13 ms 15 ms 19 ms gi5-2-16-cmts.emirny27-rtr002.cny.northeast.rr.c
om [24.94.32.146]
4 12 ms 13 ms 12 ms ae15.ithcnycy-rtr001.cny.northeast.rr.com [74.74
.108.98]
5 33 ms 31 ms 33 ms rdc-74-74-108-116.cny.east.twcable.com [74.74.10
8.116]
6 33 ms 34 ms 33 ms ae-3-0.cr0.chi10.tbone.rr.com [66.109.6.72]
7 30 ms 31 ms 29 ms ae1.pr1.chi10.tbone.rr.com [107.14.17.194]
8 30 ms 32 ms 27 ms 74.125.48.109
9 39 ms 31 ms 31 ms 209.85.254.122
10 29 ms 29 ms 31 ms 72.14.237.133
11 39 ms 41 ms 38 ms 72.14.232.70
12 39 ms 41 ms 41 ms 72.14.236.153
13 38 ms 37 ms 43 ms 72.14.238.253
14 42 ms 41 ms 43 ms iad23s08-in-f5.1e100.net [74.125.228.101]
Trace complete.
C:\Users\William>
My main question now is if this really fixed it then what caused it in the first place? Or if this is just another temporary fix like I had before what keeps causing it to return?