So odd....
Spoke with my ISP. They were essentially useless.
Earlier this morning, I had about a 4% packet loss. Then I ran tracert....and seen hop 9 and 10....timing out, and assumed that was the issue.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\GamingRig>tracert 71.252.137.153
Tracing route to static-71-252-137-153.dllstx.fios.frontiernet.net [71.252.137.1
53]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms mynetwork [192.168.2.1]
2 13 ms 19 ms 3 ms 10.11.7.209
3 5 ms 5 ms 4 ms 10.178.206.14
4 11 ms 4 ms 4 ms 10.178.206.15
5 9 ms 7 ms 7 ms tcore3-barrie18_bundle-ether1.net.bell.ca [64.23
0.100.166]
6 9 ms 7 ms 7 ms tcore4-toronto63_hu1-13-0-0.net.bell.ca [64.230.
50.172]
7 10 ms 7 ms 7 ms tcore4-torontoxn_hundredgige0-8-0-0.net.bell.ca
[64.230.50.15]
8 15 ms 6 ms 7 ms bx1-torontoxn_et4-0-0.net.bell.ca [64.230.97.159
]
9 * * * Request timed out.
10 * * * Request timed out.
11 48 ms 50 ms 47 ms 4.15.44.126
12 48 ms 48 ms 47 ms ae3---0.scr02.dlls.tx.frontiernet.net [74.40.1.8
1]
13 63 ms 79 ms 87 ms be10---0.lcr22.dlls.tx.frontiernet.net [74.40.3.
26]
14 49 ms 49 ms 49 ms 172.102.50.175
15 51 ms 51 ms 50 ms static-71-252-137-153.dllstx.fios.frontiernet.ne
t [71.252.137.153]
Trace complete.
Well.....seems I no longer have packet loss, but the time outs on hops 9 and 10....still timing out, then all the ms numbers after that, reflect what my daily time is to the server, 50 on avg. Not sure if its been like that all along, as I just moved to Fib Op earlier this year.
Guess I will go with...."if it works, don't try n fix it".................but it sure is odd, why there is two hops timing out, yet I can play the sim.
