Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\Ruiz>tracert 199.91.189.57

Tracing route to 199.91.189.57 over a maximum of 30 hops

1 9 ms 8 ms 9 ms 192.168.0.1
2 22 ms 28 ms 28 ms cpe-70-112-88-1.austin.res.rr.com [70.112.88.1]

3 30 ms 28 ms 28 ms tge2-1.ausutxla02h.texas.rr.com [66.68.5.89]
4 27 ms 28 ms 19 ms tge0-15-0-3.ausutxla01r.texas.rr.com [24.175.42.
234]
5 23 ms 39 ms 38 ms agg22.dllatxl301r.texas.rr.com [24.175.41.46]
6 40 ms 28 ms 28 ms ae-8-0.cr0.dfw10.tbone.rr.com [66.109.6.52]
7 26 ms 28 ms 58 ms 107.14.19.97
8 22 ms 28 ms 29 ms ix-23-0.tcore2.DT8-Dallas.as6453.net [66.110.57.
97]
9 67 ms 66 ms 79 ms if-2-2.tcore1.DT8-Dallas.as6453.net [66.110.56.5
]
10 71 ms 68 ms 80 ms 64.86.78.5
11 69 ms 78 ms 78 ms if-22-2.tcore2.CT8-Chicago.as6453.net [64.86.79.
1]
12 120 ms 78 ms 58 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96
.45]
13 62 ms 86 ms 81 ms 66.198.96.50
14 66 ms 68 ms 68 ms 192.34.76.2
15 91 ms 78 ms 75 ms 199.91.189.234
16 68 ms 68 ms 78 ms 199.91.189.57

Trace complete.



Sadly not much of a change on this end. Not as many spikes and time outs as before. Then again im running this at 2am rather then evening like before so who knows. What struck me as odd was this time I had to turn off my firewall to even get any kind of response. Otherwise it would just time out the whole way down.