I too am having this problem with TW, only within certain times, I contacted Blizzard and spent a decent amount of time on the phone with them trying to eliminate the problems, they were most helpful in offering suggestions and trying to narrow the problems down, being proactive on it. The answers they came up with was TW are having problems getting the signals through to the west coast. So trying out all these other servers are fine as long as they are not west coast. We tried Dallas and Boston servers and they were all fine, we also tried this right at high time of the problem, which in turn also gave great latency, then when we tried another west coast same problem. Blizzard then told me to go back to TW and tell them to redirect the route that they send it all through, only TW can do this, if they tell you they cant then they need to look into trying to manage their lines for such a high overload ie: TW hasnt got the lines to support the large amount of people they have and need to expand it to accomodate the growing clientele. Makes sense right.

So I call TW and all I get was some guy who could barely speak english telling me that my router is fine. And while I was trying to explain this to him all he could say was my router is fine, which lead me to beleive thats all he could say. In turn that got me very frusterated that I wanted to drive to TW and demand to be seen then and there. However they did give me an email to send through my traceroute and was told someone would contact me about it. I dont hold my breath on it, but im gonna post it for all of you TW customers to send in your traceroutes to them on a daily basis.

ihelpdesk@nyc.rr.com

In the meantime I will call them on a regular basis to hopefully get a T3 Tech that can say more than your router is fine.

Looks like TW customers in East Coast have horrible lag when connected to LADC

Comcast customers connecting to Boston DC are having lag issues as well.



I am reroling OP druid on Kel'thuzad (boston server) where i get 20ms latency.

I'd like to switch ISP's, as this is probably going to be the only solution to this problem..... however..... I have now been backed into a corner. The only other option in my area (outside of dial up) is Verizon DSL. Their highest service is 3.0 mbps download / 768kbps upload. Normally, this wouldn't be too much of an issue (despite the fact that Road Runner is technically supposed to give me almost double the d/l speeds, but whatever). The problem is this: I don't have a phone jack in my apartment. First Verizon said they need a few days to process an "engineering request" to make sure that DSL is even AVAILABLE. So who knows if they can even give me their 3.0 mbps service and not their 768kbps d/l service....if even any DSL at all! Then they said to call back next week. IF they can confirm that I can get DSL service, it is only then that I can place the order. It would cost me $200 to get a phone jack installed plus the cost of the modem ($70?) which they will not subsidize because I don't have phone service, plus $19.99 set up fee along with a $39.99 monthly fee. Also, DSL will take at LEAST 2 weeks after I order it to be installed. So basically, I'll have to shell out a bunch of dough, wait like 2-3 weeks, just to get lower speeds than what Road Runner promises.

F that.

I have a feeling TimeWarner has some sort of monopoly in this area. I'm in Astoria (Queens), NY btw.

Well tonight, I had some lag but no dc. Lag was not so bad that i couldn't raid. Good to see problem is getting better/solved. Good work to Blizzard if they did this :-D.

---

Q u o t e:
Well tonight, I had some lag but no dc. Lag was not so bad that i couldn't raid. Good to see problem is getting better/solved. Good work to Blizzard if they did this :-D.

---

Dont get your hopes up. Hardly anyone on as most was watching the Olympics opening. It will go back to the normal as of late 2k+ ping tomo. Hope you enjoyed it while it lasted.

I just got my friend on as a trial member and he is having this issue. Only with Shadowsong server which is in the LA Datacenter.

They gave him the run around and told him that the TRACERT shows that this lies outside of RR and i got to contact bliz. Now I read this. It sucks cause my friend joined for Triple XP i am not going to re roll. So I may lose my trial buddy before it starts help this!

Having the same problem too. Please tell me what I can do to fix this. Thanks.


Tracing route to 206.17.111.124 over a maximum of 30 hops



1 1 ms <1 ms <1 ms 192.168.2.1

2 * * * Request timed out.

3 10 ms 7 ms 9 ms gig-2-1-nycmnyu-rtr1.nyc.rr.com [24.29.104.189]

4 10 ms 8 ms 8 ms pos-7-0-nycmnyl-rtr2.nyc.rr.com [24.29.98.25]

5 8 ms 11 ms 8 ms tenge12-1-0-nycmnya-rtr1.nyc.rr.com [24.29.97.42]

6 10 ms 11 ms 19 ms tenge-2-0-0-nwrknjmd-rtr.nyc.rr.com [24.29.119.110]

7 11 ms 9 ms 9 ms 4.79.188.33

8 13 ms 20 ms 15 ms ae-31-53.ebr1.Newark1.Level3.net [4.68.99.94]

9 11 ms 17 ms 18 ms ae-2.ebr1.NewYork1.Level3.net [4.69.132.97]

10 23 ms 18 ms 17 ms ae-81-81.csw3.NewYork1.Level3.net [4.69.134.74]

11 124 ms 209 ms 205 ms ae-33-89.car3.NewYork1.Level3.net [4.68.16.133]

12 12 ms 10 ms 11 ms att-level3-oc192.NewYork1.Level3.net [4.68.127.150]

13 21 ms 18 ms 22 ms tbr1.n54ny.ip.att.net [12.123.0.90]

14 21 ms 21 ms 21 ms cr2.n54ny.ip.att.net [12.122.16.141]

15 18 ms 17 ms 19 ms cr1.cb1ma.ip.att.net [12.122.31.126]

16 18 ms 39 ms 22 ms tbr1.cb1ma.ip.att.net [12.122.20.138]

17 19 ms 18 ms 19 ms 12.127.5.109

18 17 ms 19 ms 17 ms 12-122-254-14.attens.net [12.122.254.14]

19 20 ms 18 ms 20 ms mdf001c7613r0004-gig-12-1.bos1.attens.net [12.130.0.174]

20 * * * Request timed out.

21 * * * Request timed out.

22 * * * Request timed out.

23 * * * Request timed out.

24 * * * Request timed out.

25 * * * Request timed out.

26 * * * Request timed out.

27 * * * Request timed out.

28 * * * Request timed out.

29 * * * Request timed out.

30 * * * Request timed out.



Trace complete.

---

Q u o t e:
Having the same problem too. Please tell me what I can do to fix this. Thanks.


Tracing route to 206.17.111.124 over a maximum of 30 hops



1 1 ms <1 ms <1 ms 192.168.2.1

2 * * * Request timed out.

3 10 ms 7 ms 9 ms gig-2-1-nycmnyu-rtr1.nyc.rr.com [24.29.104.189]

4 10 ms 8 ms 8 ms pos-7-0-nycmnyl-rtr2.nyc.rr.com [24.29.98.25]

5 8 ms 11 ms 8 ms tenge12-1-0-nycmnya-rtr1.nyc.rr.com [24.29.97.42]

6 10 ms 11 ms 19 ms tenge-2-0-0-nwrknjmd-rtr.nyc.rr.com [24.29.119.110]

7 11 ms 9 ms 9 ms 4.79.188.33

8 13 ms 20 ms 15 ms ae-31-53.ebr1.Newark1.Level3.net [4.68.99.94]

9 11 ms 17 ms 18 ms ae-2.ebr1.NewYork1.Level3.net [4.69.132.97]

10 23 ms 18 ms 17 ms ae-81-81.csw3.NewYork1.Level3.net [4.69.134.74]

11 124 ms 209 ms 205 ms ae-33-89.car3.NewYork1.Level3.net [4.68.16.133]

12 12 ms 10 ms 11 ms att-level3-oc192.NewYork1.Level3.net [4.68.127.150]

13 21 ms 18 ms 22 ms tbr1.n54ny.ip.att.net [12.123.0.90]

14 21 ms 21 ms 21 ms cr2.n54ny.ip.att.net [12.122.16.141]

15 18 ms 17 ms 19 ms cr1.cb1ma.ip.att.net [12.122.31.126]

16 18 ms 39 ms 22 ms tbr1.cb1ma.ip.att.net [12.122.20.138]

17 19 ms 18 ms 19 ms 12.127.5.109

18 17 ms 19 ms 17 ms 12-122-254-14.attens.net [12.122.254.14]

19 20 ms 18 ms 20 ms mdf001c7613r0004-gig-12-1.bos1.attens.net [12.130.0.174]

20 * * * Request timed out.

21 * * * Request timed out.

22 * * * Request timed out.

23 * * * Request timed out.

24 * * * Request timed out.

25 * * * Request timed out.

26 * * * Request timed out.

27 * * * Request timed out.

28 * * * Request timed out.

29 * * * Request timed out.

30 * * * Request timed out.



Trace complete.

---

Step 1 is learning to read before posting they want you to send it to them via email in a text format.
Step 2 ???
Step 3 Profit

great thanks. i did read the previous posts and it doesn't seem like blizzard can do anything about this problem. looks like i'll be transferring servers again!

I think I'm going to cancel subscription. Obviously Blizzard doesn't care one bit regardless of how long this goes on for nor about their customers.

Good bye.

---

Q u o t e:
I think I'm going to cancel subscription. Obviously Blizzard doesn't care one bit regardless of how long this goes on for nor about their customers.

---

Blizzard can only do so much of this, the majority of the problem lies with TW.. Tw can reroute the signal to take a different route to reach the west coast however they do not wish to do this.. so its gg TW not Blizzard.

Posting on here as well does not always get noticed, call Blizzard as I was talking to them yesterday they were chatting about they have had very LITTLE calls regarding this... the guys on the phones are not in charge of the forums, so they have no idea of the problems.

I'm in California and I have Time Warner... I've had about 300-800ms 75% of the time over the past month... It's like, really annoying. I'm not even considering calling them because I know I'll get some random from India to tell me to restart my modem like I have done 32985982398582935 times.

I would advice everyone to stay away from TW, BECAUSE IT %%%*ING SUCKS ALL THE TIME!

---

Q u o t e:
I think I'm going to cancel subscription. Obviously Blizzard doesn't care one bit regardless of how long this goes on for nor about their customers.

Good bye.

---

So quit playing WOw because TWC wont fix a problem, yet keep paying TWC.. good logic... As already stated Blizzard can only do so much... Id keep flooding their call centers with calls, maybe even get ahold of corproate and make some noise.. It cant hurt to keep trying.

It sucks you guys are still having to deal with this. It reminds me of the same problem they had last year.

---

Q u o t e:


So quit playing WOw because TWC wont fix a problem, yet keep paying TWC.. good logic... As already stated Blizzard can only do so much... Id keep flooding their call centers with calls, maybe even get ahold of corproate and make some noise.. It cant hurt to keep trying.

It sucks you guys are still having to deal with this. It reminds me of the same problem they had last year.

---

TWC has no problem with any other. I quit wow because it is the only issue and I can't play it. Why would I continue playing Wow since TWC won't fix the problem? Do you need a better logic?

I have called Time Warner several times, they keep telling me the same thing...

we can't do anything about it

so....gg warhammer or some other game?

I've been noticing lag spikes and delays for a couple of weeks, it was annoying but still playable. This weekend it just got ridiculous--solid red bars of latency on both pcs with both accounts...I will have to research it to see if playing on another realm makes any difference or not, and I haven't ran the scan on it either. My son and I play together using TWC/BrightHouse here in central FL. I didn't think much of it at first, thought it was just us, but when the disconnects starting coming one after the other over and over--there is no point in even tyring to play. I've only been using this broadband connection for 2 months when I moved to my current location, always heard it was so much faster but haven't seen any difference that I noticed. I've had WoW on DSL the last two years but it isn't available here, and there aren't even any phone jacks in this place anyway it costs $90 to have one put in and I'm only here for 6 months. Shame, if I have to play like this dial-up was better! I recall having a very similar problem with the DSL before, Blizzard had posted about and acknowledged that, it was fixed but at the time I had to unplug my modem and reset it every single time I got disconnected. I haven't called them, and really didn't want to, I keep thinking anything I need is going to cost me more money lol. It will be fixed eventually, it's just a matter of how many of us want to wait that long. No way this is all just coincidence.

---

Q u o t e:
ATT = TimeWarner/RoadRunner right? As soon as my tracert hits their stuff the ping doubles. Clearly ATT is not to blame though, its someone else!

---

This exactly. I recently transferred my main from Madoran (Dallas Datacenter) to Kilrogg (Los Angeles Datacenter) and my ping went from around 150-200 ms on Madoran, to 300-400 ms on Kilrogg.

Tracert to Kilrogg gets me this:

---

Q u o t e:
Tracing route to 12-129-225-26.attens.net [12.129.225.26]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 46 ms 47 ms 46 ms 10.34.39.1
3 47 ms 46 ms 48 ms so-1-2-0-0.CORE-RTR1.CHI01.verizon-gni.net [130.
81.36.184]
4 45 ms 48 ms 47 ms so-7-2-0-0.BB-RTR1.CHI01.verizon-gni.net [130.81
.20.56]
5 46 ms 47 ms 47 ms 0.so-0-0-0.XT1.CHI4.ALTER.NET [152.63.0.229]
6 48 ms 63 ms 48 ms 0.so-5-0-0.XL1.CHI13.ALTER.NET [152.63.64.18]
7 50 ms 49 ms 50 ms 0.so-6-0-0.BR2.CHI13.ALTER.NET [152.63.73.25]
8 49 ms 50 ms 49 ms uu-gw.cgcil.ip.att.net [192.205.35.181]
9 114 ms 113 ms 208 ms tbr1.cgcil.ip.att.net [12.122.87.250]
10 113 ms 124 ms 113 ms cr1.cgcil.ip.att.net [12.122.17.145]
11 117 ms 118 ms 119 ms cr1.sffca.ip.att.net [12.122.4.121]
12 120 ms 119 ms 119 ms cr1.la2ca.ip.att.net [12.122.3.122]
13 114 ms 113 ms 115 ms tbr1.la2ca.ip.att.net [12.122.19.162]
14 110 ms 111 ms 110 ms gar5.la2ca.ip.att.net [12.127.3.185]
15 117 ms 120 ms 116 ms 12.122.255.74
16 117 ms 115 ms 117 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.12
9.193.242]
17 121 ms 122 ms 115 ms 12.129.209.99
18 118 ms 118 ms 119 ms 12-129-225-26.attens.net [12.129.225.26]

Trace complete.

---

As soon as it hits the ATT (TimeWarner) servers the pings more than double.... We should really start a legitimate petition about this, apparantly its been going on for a long long time.

---

Q u o t e:

ihelpdesk@nyc.rr.com

In the meantime I will call them on a regular basis to hopefully get a T3 Tech that can say more than your router is fine.

---

For the 3rd time I will post this. If you guys are not finding the solution with Time Warner,

HERE IS THE COMPLAINT FORM THAT GOES STRAIGHT TO THE NEW YORK DEPARTMENT OF INFORMATION TECHNOLOGY & TELECOMMUNICATION. GO GO GO!

http://www.nyc.gov/html/doitt/html/consumer/consumer_cable_service_form.shtml

What makes you think ppl havent tried that already?