Aravisian wrote:I would inspect your local connection, first.
Try running Traceroute and see if you see packet loss and also narrow down where the loss is occurring. If you see no packet loss past your computer or router, then you can look at your computer for the cause.
I could be wrong... just in my own experience, whenever I experienced poor connection or connection loss- the cause was always outside of my machine.
here is the traceroute:
cory@Home:~$ traceroute google.com
traceroute to google.com (172.217.14.206), 30 hops max, 60 byte packets
1 Linksys06873 (192.168.1.1) 37.057 ms 37.038 ms 37.011 ms
2 * * *
3 96-34-107-116.static.unas.or.charter.com (96.34.107.116) 47.328 ms 47.333 ms 47.309 ms
4 96-34-108-170.static.unas.or.charter.com (96.34.108.170) 50.400 ms 50.405 ms 50.390 ms
5 cts02elbgwa-tge-1-0-0.elbg.wa.charter.com (96.34.106.253) 48.618 ms 48.575 ms 48.585 ms
6 96-34-107-212.static.unas.or.charter.com (96.34.107.212) 51.241 ms 47.212 ms 47.092 ms
7 96-34-111-220.static.unas.or.charter.com (96.34.111.220) 47.111 ms 47.023 ms 48.333 ms
8 96-34-108-175.static.unas.or.charter.com (96.34.108.175) 48.358 ms 48.333 ms 48.317 ms
9 96-34-108-160.static.unas.or.charter.com (96.34.108.160) 48.306 ms 48.291 ms 48.263 ms
10 bbr02sttlwa-bue-4.sttl.wa.charter.com (96.34.0.56) 49.847 ms 49.786 ms 103.598 ms
11 prr01sttlwa-bue-2.sttl.wa.charter.com (96.34.3.39) 102.178 ms 103.442 ms 102.094 ms
12 72.14.194.48 (72.14.194.48) 102.189 ms 102.132 ms 102.113 ms
13 74.125.243.177 (74.125.243.177) 102.083 ms * *
14 209.85.254.246 (209.85.254.246) 102.039 ms 108.170.233.154 (108.170.233.154) 100.593 ms 108.170.233.158 (108.170.233.158) 100.548 ms
15 108.170.245.108 (108.170.245.108) 41.945 ms sea30s01-in-f14.1e100.net (172.217.14.206) 38.950 ms 108.170.245.107 (108.170.245.107) 37.694 ms