I honestly doubt it, although it never hurts to test
From what I've seen, if routers are faulty they throw in massive latency on the routers hop or simply don't work at all.
Ah ok.. well it seems to fluctuate a lot but seems more stable presently.. so i started recreating my Plex Music(yah video linkage & music audio sig.. sadly i have to recreate) library so thats going to thrash as it pulls meta data and Sabnzbdplus restarted (they we all off earlier because i was trying to update my server & software when it happened)
This looks more normal..
Code:
traceroute google.com
traceroute to google.com (216.58.223.14), 30 hops max, 60 byte packets
1 10.0.0.1 (10.0.0.1) 0.630 ms 0.648 ms 0.826 ms
2 105-236-4-129-esr-lo.mtnbusiness.co.za (105.236.4.129) 11.204 ms 14.850 ms 16.852 ms
3 ipc-recieve-rb-2a.za.mtnbusiness.net (41.181.178.65) 21.858 ms 24.716 ms 26.958 ms
4 rb-dca-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.120) 30.411 ms 32.302 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net (196.44.0.146) 35.748 ms
5 jh-cr-2.za--rb-cr-1.za-a.mtnns.net (196.44.31.95) 37.684 ms 39.620 ms jh-cr-1.za--rb-cr-2.za.mtnns.net (196.44.0.42) 45.193 ms
6 qux-jh-dca-2.za-b.za.mtnbusiness.net (41.181.165.115) 45.663 ms 35.771 ms 36.087 ms
7 rb-cr-1.za--jh-cr-2.za-b.mtnns.net (196.44.31.170) 15.533 ms rb-cr-1.za--jh-cr-2.za-a.mtnns.net (196.44.31.94) 19.825 ms 21.967 ms
8 41.181.139.109 (41.181.139.109) 28.874 ms 41.181.139.99 (41.181.139.99) 40.920 ms 41.181.139.109 (41.181.139.109) 30.715 ms
9 72.14.194.74 (72.14.194.74) 30.281 ms 33.609 ms 35.656 ms
10 72.14.237.239 (72.14.237.239) 38.555 ms 40.758 ms 43.081 ms
11 jnb01s07-in-f14.1e100.net (216.58.223.14) 58.710 ms 63.373 ms 65.434 ms
