New 90002 error

[Gofur]

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.

[Gofur]

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 <1 ms <1 ms <1 ms 192.168.1.1
2 4 ms 8 ms 3 ms 192.168.0.1
3 * 28 ms 24 ms cpe-70-112-88-1.austin.res.rr.com [70.112.88.1]

4 19 ms 20 ms 19 ms tge2-1.ausutxla02h.texas.rr.com [66.68.5.89]
5 26 ms 23 ms 28 ms tge0-15-0-2.ausutxla01r.texas.rr.com [24.175.42.
232]
6 24 ms 18 ms 28 ms agg10.ausutxla02r.texas.rr.com [24.175.41.205]
7 26 ms 26 ms 23 ms agg11.ausxtxir01r.texas.rr.com [24.175.41.206]
8 30 ms 33 ms 28 ms agg10.ausxtxir02r.texas.rr.com [24.175.41.209]
9 34 ms 28 ms 28 ms agg22.hstqtxl301r.texas.rr.com [24.175.41.48]
10 34 ms 38 ms 48 ms ae-2-0.cr0.hou30.tbone.rr.com [66.109.6.108]
11 30 ms 37 ms 32 ms ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39]
12 29 ms 38 ms 38 ms 107.14.19.97
13 63 ms 69 ms 67 ms ix-23-0.tcore2.DT8-Dallas.as6453.net [66.110.57.
97]
14 72 ms 78 ms 78 ms if-2-2.tcore1.DT8-Dallas.as6453.net [66.110.56.5
]
15 74 ms 80 ms 77 ms 64.86.78.5
16 74 ms 74 ms 78 ms if-22-2.tcore2.CT8-Chicago.as6453.net [64.86.79.
1]
17 103 ms 78 ms 78 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96
.45]
18 73 ms 78 ms 73 ms 66.198.96.50
19 83 ms 68 ms 79 ms 192.34.76.2
20 75 ms 78 ms 78 ms 199.91.189.234
21 81 ms 74 ms 78 ms 199.91.189.57

Trace complete.


So i got some new developments here. A few extra hops compared to traces a few days ago. I also might add that i went a whole 24+ hours w/o a d/c (hope im not jinxing myself here). Any idea what this might mean Raist?

*Edit* - Forgot to add that since the arris DG1670 is a modem/router combo, i turned off all its wireless routing and added a Netgear wireless router between it and my desktop. I did this a few days ago and would still get d/c's, but it did seem to help with the speed.

[Raist]

Saw where TWC was looking into some issues in Austin, TX and several spots around Ohio. Some of it was addressing "circular routing" issues that were causing unwanted delays in transit (like how you are stuck in the Austin/Dallas area for a while--some were seeing twice as many hops as you are... was pretty ugly). It's possible that whatever fixes they've been implementing elsewhere are starting to roll out to more markets. They've started rolling out more speed upgrades in select areas as well. With any luck, congestion will gradually improve from here out. Their outage map is slowly improving in the middle of the US at least. Northeast and Southern Cali are still a mess though....but there is progress being made for most other markets.

ooh... just noticed a buggy vlan up in Montreal may finally be out of the picture now too. Was harassing Ormuco and SE about that a while back--was right there at the hand-off into Ormuco's address that starts with 192. It was throwing 200ms+ spikes periodically. Nice to see what you're getting with those segments is staying under 100ms. Looks like it's trying to smoothen out up there.