W.O.W. → Re: MORE DHCP server problems...

i got off with wow tech support. a tier 2 guy said he sent an email off to the main network support guy for detroit who is in direct contact with at&t. I don't know how much it will help, but this router/lag is simply making gaming and other services unusable for the better part of the day.

Ya, this connectivity/ping/routing problem is getting real stale. I grow tired of paying for a high speed connection with latency that's 3x worse than a dialup for 2/3's of the day.

Maybe I missed something in the TOS? The part that says the connection is only good from 1am to 7am.

And I don't care that this appears to be an ATT problem. WOW is my provider. If they cannot resolve an issue with ATT then the simple fact is that WOW cannot provide me with acceptable service.

This has been over 3 weeks now and appears to be degrading a bit more everyday. I'm tired of WOW support apologizing and being unable to get a handle on this. If they expect me to wait this one out then they should also expect that I'm not going to pay full price for a lousy connection.

End rant...

then switch back to Comcast and quit crying about WOWs "poor" and "unacceptable" service ... since you pay your bills and dislike their performance then switch ... my service has been fine except for the DHCP server issue last week ...

Well imrf, I'm glad ur getting good performance. I should move to Utica. Problem is I dropped ComCast for WOW a month ago - in an attempt to get better performance. I did initially, and was quite content for about 2 weeks..

Do me a favor and run a duplicate traceroute and post the results. (run it sometime between 8 and 11 pm). If It looks like this and ur still happy, well, more power to u.

Tracing route to chi.speakeasy.net [64.81.159.2]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 9 ms 9 ms 10 ms d53-1-230.try.wideopenwest.com [64.53.230.1]
3 19 ms 18 ms 13 ms 172.31.15.252
4 230 ms 32 ms 31 ms 12.119.51.181
5 1187 ms 1161 ms 1173 ms gbr2-p51.dtrmi.ip.att.net [12.123.208.134]
6 1107 ms 1100 ms 1123 ms tbr2-p013002.cgcil.ip.att.net [12.122.10.113]
7 1026 ms 1000 ms 914 ms gbr6-p20.cgcil.ip.att.net [12.122.11.62]
8 899 ms 853 ms 958 ms gar2-p370.cgcil.ip.att.net [12.123.5.221]
9 1062 ms 1133 ms 1149 ms gar1-p3100.chail.ip.att.net [12.123.216.130]
10 * * * Request timed out.
11 960 ms 936 ms 988 ms border5.ge3-1-bbnet1.chg.pnap.net [64.94.32.10]
12 1071 ms 1123 ms 1125 ms chi.speakeasy.net [64.81.159.2]

Trace complete.

So, I guess I'll continue to "cry" until WOW resolves the issue or I run out of tears.. LOL

here is mine, not quit as bad as yours, but it doesnt bother me at all since i have better things to do and sit here and ping/trace route websites all night long, and also that granted they are supposed to provide us internet service they have NO control on what happens outside of their own network, ATT has a problem, they call them up and let ATT know, ATT gets around to fixing the problem at THEIR earliest convenience, WOW cannot just snap their fingers and switch to a different backbone provider nore can they make ATT move any faster than they want too...WOW is aware that there is a problem and i asked their support guy the other day when the DHCP server pooped out and he even agreed and said thats is a major issue but ATT just has not got around to fix the problem, so for us to sit and continuously complain here will do no good, dart your rants to them, we all feel your pain but just dont want to always read the same thing over and over and over again.

Tracing route to chi.speakeasy.net [64.81.159.2]
over a maximum of 30 hops:

1 13 ms 12 ms 12 ms d60-1-182.try.wideopenwest.com [65.60.*.*]
2 10 ms 13 ms 11 ms 172.31.15.253
3 265 ms 270 ms 270 ms 12.124.15.37
4 281 ms 294 ms 295 ms gbr2-p70.dtrmi.ip.att.net [12.123.139.26]
5 * * * Request timed out.
6 274 ms 274 ms 269 ms gbr5-p40.cgcil.ip.att.net [12.122.11.58]
7 272 ms 270 ms 267 ms gar3-p360.cgcil.ip.att.net [12.123.6.1]
8 293 ms 287 ms 293 ms gar1-p340.chail.ip.att.net [12.123.216.134]
9 * * * Request timed out.
10 291 ms 280 ms 278 ms border5.ge4-1-bbnet2.chg.pnap.net [64.94.32.74]

11 244 ms 249 ms 260 ms chi.speakeasy.net [64.81.159.2]

Trace complete.