Horrible Latency Road Runner/TWC/BH cont 3

Technical Support
Post Limit:
Prev 1 3 4 5 8 Next
10/01/2012 09:57 PMPosted by Jhamon
It seems that given the timing of this issue and the fact that it is consistent over multiple carriers and locations, not to mention the fact that it makes the game unplayable even from a questing/PVE standpoint I agree with the call for compensation from Blizzard.


I couldn't agree more.
I'm with you on this. I haven't been able to play since Friday on multiple servers, I've talked to my ISP and he's definitely not (major) problem. I live far from the US, and I'm aware that I'll always be a tad laggy compared to "home players," but 10k lag is not even close to playable. The funny thing is the game ran really smoothly on launch day up till Friday, and then- *WHAM*, lag wall.
It really seems to be something on Blizzard's side, not a local occurrence. It seems that the most affected are people playing on US servers from outside the US.

BTW, I really wouldn't mind paying for a transfer from the US servers to the EU ones, but that's not even an option. Switching US servers doesn't help at all (I've tried), and I'm not shelling out all the money and time to re-do my characters from scratch on an EU game.
This topic should never leave page 1.
I have comcast and having the exact same problem. High latency and its been going on for over a week now.
Never be on page 3....BUMP!
bump. i just want to play the damn game without lag issues
How do I go about freezing my account?

I would've been level 90 by now had I not been slowed down by this lag... My experience has been diminished immensely and I'd rather not deal with it for another 3+ weeks.

Let's not even mention the hours I spent diagnosing my newly built PC thinking I had a defective Mobo...
Requires immediate fix!

Another night of no playing.
Thread is being buried purposefully! Fight the injustice!
Our AT&T contact has said that the congestion at the New York peering partner "has been relieved over the last couple of days, but it might be at the expense of other peer locations...We're told the extra capacity is still a couple weeks out."
________________________________________________
Technical Support
http://us.battle.net/support
'Constant change is here to stay.'


Something needs to be done asap. This is beyond acceptable.
Our AT&T contact has said that the congestion at the New York peering partner "has been relieved over the last couple of days, but it might be at the expense of other peer locations...We're told the extra capacity is still a couple weeks out."
________________________________________________
Technical Support
http://us.battle.net/support
'Constant change is here to stay.'


Well, that's just fantastic. BECAUSE THAT'S WHEN MY ISSUE STARTED.

This game is unplayable. I get constant disconnections everywhere, every toon, every realm.

Sometimes I get to play for a whole 15 minutes without getting disconnected, and that's getting pretty damn rare at this point.

I thought it was just my home network, but then I connected to the neighbor and, lo and behold, got disconnected 10 minutes later.

Time Warner Cable. Southern Tier New York.
Lag is insane. For a minute I thought it was just my WoW, but then mumble started lagging too. This is a Comcast issue, folks. Don't take it out on Blizz. Call the ISP direct and complain to them until they get it fixed. I for one am calling Comcast tomorrow to attempt to straighten it out, but one voice only does so much.
I just got out of a bg that was loaded with lag. My world latency jumped to 600-800 during battles. . I also noticed the lag in a dungeon about 10-15 minutes before I entered the bg. This is the first time I have had an issue with the lag. This is also the first time I have played for more than 2 hours straight. :-( Stinks!!!
boloney was running fine for me in cata now lagging not worth doing bg or dungeons
Been experiencing this as well.

Traceroute returns:

Tracing route to 206.18.148.192 over a maximum of 30 hops

1 <1 ms 1 ms <1 ms 10.0.0.1
2 32 ms 19 ms 20 ms c-107-4-174-1.hsd1.wv.comcast.net [107.4.174.1]
3 13 ms 9 ms 9 ms te-9-3-ur01.ashland.va.richmond.comcast.net [68.86.127.113]
4 10 ms 9 ms 10 ms te-1-4-ar01.staplesmllrd.va.richmond.comcast.net [68.86.172.85]
5 19 ms 23 ms 23 ms pos-0-6-0-0-cr01.charlotte.nc.ibone.comcast.net [68.86.91.149]
6 25 ms 23 ms 27 ms 68.86.85.225
7 27 ms 29 ms 27 ms pos-0-4-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.87.138]
8 24 ms 24 ms 24 ms as7018-pe01.56marietta.ga.ibone.comcast.net [75.149.228.86]
9 61 ms 49 ms 52 ms cr2.attga.ip.att.net [12.122.117.98]
10 56 ms 50 ms 53 ms cr1.nsvtn.ip.att.net [12.122.28.106]
11 50 ms 47 ms 51 ms cr2.nsvtn.ip.att.net [12.122.28.70]
12 49 ms 50 ms 51 ms cr1.cl2oh.ip.att.net [12.122.28.74]
13 57 ms 48 ms 50 ms cr1.cgcil.ip.att.net [12.122.2.205]
14 70 ms 47 ms 48 ms gar2.clboh.ip.att.net [12.122.133.197]
15 47 ms 48 ms 48 ms 12.122.251.22
16 50 ms 48 ms 48 ms 63.240.130.214
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
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.

Comp and connection never had any trouble before this....please help, need my raiding fix!
Up.
Still having this issue.
Anyone find a fix for this?
New traceroute from tonight's raid:

Tracing route to 206.18.148.192 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.0.0.1
2 20 ms 24 ms 20 ms c-107-4-174-1.hsd1.wv.comcast.net [107.4.174.1]
3 10 ms 8 ms 9 ms te-9-3-ur01.ashland.va.richmond.comcast.net [68.86.127.113]
4 10 ms 9 ms 8 ms te-1-4-ar01.staplesmllrd.va.richmond.comcast.net [68.86.172.85]
5 21 ms 19 ms 21 ms pos-0-6-0-0-cr01.charlotte.nc.ibone.comcast.net [68.86.91.149]
6 25 ms 27 ms * 68.86.85.225
7 26 ms 26 ms 23 ms pos-0-4-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.87.138]
8 23 ms 23 ms 24 ms as7018-pe01.56marietta.ga.ibone.comcast.net [75.149.228.86]
9 58 ms 52 ms 52 ms cr2.attga.ip.att.net [12.122.117.98]
10 52 ms 63 ms 47 ms cr1.nsvtn.ip.att.net [12.122.28.106]
11 51 ms 51 ms 52 ms cr2.nsvtn.ip.att.net [12.122.28.70]
12 49 ms 52 ms 51 ms cr1.cl2oh.ip.att.net [12.122.28.74]
13 894 ms 51 ms 47 ms cr1.cgcil.ip.att.net [12.122.2.205]
14 48 ms 46 ms 46 ms gar2.clboh.ip.att.net [12.122.133.197]
15 48 ms 50 ms * 12.122.251.22
16 199 ms 201 ms 212 ms 63.240.130.214
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
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.

Please, please, please, give me SOMETHING. I'm gonna lose my raiding spot if I can't get this fixed. People in my guild who live in the same erea aren't having this problem....
Our AT&T contact has said that the congestion at the New York peering partner "has been relieved over the last couple of days, but it might be at the expense of other peer locations...We're told the extra capacity is still a couple weeks out."
________________________________________________
Technical Support
http://us.battle.net/support
'Constant change is here to stay.'


This has got to be the least satisfying response I have ever seen. Your game is unplayable. Quit blaming AT&T, who is your partner, and FIX IT.

Join the Conversation