Horrible Latency Road Runner/TWC/BH cont

Technical Support
Prev 1 24 25 26 Next
Less than a week until MoP and this isn't fixed yet?

I am disappointed in Blizzard.
Looks like whatever was done fixed my problem. Latency issues seemed to have dissipated and my average MS on my new realm is about 20
This is not a ISP specific issue. A IP HOP we are using to get to a certain Blizzard Datacenter is the cause. Issue happens when all of use reach a specific attnets.net IP HOP.

More information on the IP HOP: http://us.battle.net/wow/en/forum/topic/6606432995
Was great all day yesterday but today has been a nightmare...4 days to expac...hope this issue gets fixed :(
Lets just face it, its going to be awhile before everything is back to normal.
I have sitting here for almost a week going through these forums looking for solutions. Hoping that this issue would be fixed soon. However, nothing has been updated in the past 4 days. I have missed raids and had to leave countless dungeon because of this issue. I have read all the rant posts about people cancelling their account and getting refunded for their purchase of MoP thinking they was overreacting. Although, I am getting close to that point myself. I try to play WOW because I love it and enjoy it. Whenever I do try to play, I got to get really lucky and cross my fingers that my world latency does not spike and my game not frezze. I am sick and tired of having to alt f4 the game and try to load back in hoping that will resolve it enough to finish the dungeon. I run dungeons with my fiance which we both run on the same network and literally across from each other in the room. There are times that my game is find while he is experiencing the issues and vice versa. All I am asking is a blue post with updated info and if this is going to be fixed in time for the release of MoP.
almost 5 days since an update ... MoP released in 3 ... is there any update on whether this problem is even close to being partially resolved?

This is a gamebreaking problem for many right now ..
almost 5 days since an update ... MoP released in 3 ... is there any update on whether this problem is even close to being partially resolved?

This is a gamebreaking problem for many right now ..

From what i have seen this is not a Blizzard issue. Please read my last post (#483) on the cause and remedy.

This is one issue that the player base must address. Blizzard involvement isnt mandatory.
I'm having horrible latency issues here too. I'm not part of those ISPs though.
I am on the tanaris server, which might have something to do with this, since tanaris server is in the road runner terriroty.

It's been like this ever since these ISPS have been giving problems.

I mean I'm at 4k latency world and 2k home.

I don't know what to do. I haven't been playing the game for the past week or so because of this.

How long does running a trace route take? I will do one later on with my location, but I'm in North Dakota, which is nowhere near the bad ISPs.
Loc: Birmingham, AL
ISP: BrightHouse Networks
Tracing to Arthas

Tracing route to over a maximum of 30 hops

1 8 ms 11 ms 5 ms
2 8 ms 4 ms 3 ms ten9-0-1.bham15-ser2.bhn.net []
3 10 ms 9 ms 6 ms ten9-0-0.bham01-ser4.bhn.net []
4 32 ms 27 ms 27 ms ten7-1.bham01-cbr2.bhn.net []
5 37 ms 23 ms 31 ms ten0-9-0-4.orld71-cbr3.bhn.net []
6 31 ms 31 ms 29 ms xe-11-3-0.bar1.Orlando1.Level3.net [
7 31 ms 31 ms 32 ms ae-0-11.bar2.Orlando1.Level3.net []

8 32 ms 29 ms 39 ms ae-5-5.ebr2.Miami1.Level3.net []
9 33 ms 30 ms 32 ms ae-2-52.edge2.Miami2.Level3.net []
10 39 ms 39 ms 44 ms
11 83 ms 79 ms 79 ms
12 79 ms 83 ms 84 ms cr2.ormfl.ip.att.net []
13 80 ms 81 ms 86 ms cr1.ormfl.ip.att.net []
14 88 ms 86 ms 83 ms cr2.attga.ip.att.net []
15 87 ms 82 ms 86 ms cr1.nsvtn.ip.att.net []
16 86 ms 83 ms 79 ms cr2.nsvtn.ip.att.net []
17 85 ms 87 ms 86 ms cr1.cl2oh.ip.att.net []
18 84 ms 83 ms 83 ms cr1.cgcil.ip.att.net []
19 84 ms 84 ms 84 ms gar2.clboh.ip.att.net []
20 80 ms 84 ms 80 ms
21 82 ms 87 ms 80 ms
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.
Loc: Grand Forks, ND
ISP: InvisiMax
Tracing to Tanaris (

Tracing route to over a maximum of 30 hops

1 <1 ms <1 ms <1 ms

2 <1 ms <1 ms <1 ms

3 <1 ms <1 ms <1 ms

4 <1 ms 1 ms <1 ms

5 1 ms <1 ms <1 ms

6 1 ms <1 ms 1 ms

7 10 ms 3 ms 4 ms fargo-i1-3592.itd.nd.gov []

8 12 ms 3 ms 4 ms

9 17 ms 17 ms 17 ms sl-gw39-chi-12-0-1.sprintlink.net []

10 18 ms 20 ms 18 ms sl-crs2-chi-0-8-0-2.sprintlink.net []

11 17 ms 18 ms 18 ms sl-st31-chi-0-4-0-0.sprintlink.net []

12 18 ms 18 ms 17 ms

13 40 ms 39 ms 38 ms cr1.cgcil.ip.att.net []

14 38 ms 39 ms 39 ms cr1.cl2oh.ip.att.net []

15 39 ms 39 ms 39 ms cr2.cl2oh.ip.att.net []

16 40 ms 39 ms 41 ms cr2.phlpa.ip.att.net []

17 90 ms 37 ms 37 ms gar1.pitpa.ip.att.net []

18 44 ms 46 ms 47 ms 12-122-254-242.attens.net []

19 46 ms 43 ms 50 ms mdf001c7613r0003-gig-10-1.nyc3.attens.net []

20 * * * Request timed out.

21 * * * Request timed out.

22 * * * Request timed out.

23 * *

Seems to end at the same IP as the person above me.
day 4 still no problems, I dont know what or who did what. But since tuesday/maintenance day, my latency has been excellent.

Time Warner Cable
Los Angeles CA
It seems that all of the trace routes recently posted end at an IP starting with 63.240.
This may be a major clue to our issues here so hopefully this piece of information will help speed up a fix. Ever since patch 5.0 i had major lag issues till this past tuesday. Now everything seems to be working good, gg right? Wrong. I just so happened to level an alt and now im dc'ing just about every 30 seconds in nordrassil. So whys that? Same server, computer etc. but... im dc'ing in whats called a "crossrealm zone". So what really happened last tuesday? Did blizzards peering partners allow for more data to go thru? Or was blizz behind the "fix". It seems like this issue has just got more complicated. Heres the last official word from blizz on this issue...

We received word that one of our peering partners attempted to re-route some traffic last Friday to "better balance the load across their east coast peers to us." "It does appear to have helped them avoid saturating a New York link since then, but it's still running at a pretty heavy load." As you can imagine, "the risk with making adjustments (from either side) is that it may saturate other peers, which could compound the problem."

"We’ve been told that a capacity upgrade with our...peering is in the works. I can’t speak to timelines at this point, but we’ll see what we can find out."

If I could quote from Mogrigg (Thanks Mogrigg!), this may help you visualize the connection:
You -> your ISP -> your ISP's provider -> their peering provider -> AT&T's peering provider -> (problem is here) -> AT&T -> Blizzard

Technical Support
'Constant change is here to stay.'

Lets get this problem resolved once and for all.
Can't wait for more information to be able to play again normally!
Thread's about to cap. Started up a new one.

Please go here: http://us.battle.net/wow/en/forum/topic/6678737822 for part three.

Join the Conversation

Return to Forum