Horrible Latency Road Runner/TWC/BH cont 3

(Locked)

90 Pandaren Hunter
9805
Continued from http://us.battle.net/wow/en/forum/topic/6572967451 and http://us.battle.net/wow/en/forum/topic/6521342140

Are you experience bad world latency, but, your home is fine? Do you use Road Runner, Time Warner Cable, or Bright House? If so, this thread is for you! This kind of latency is causing major problems, disconnections, complete lag that you can't log in/out without forcing World of Warcraft to close. NPCs can't be interacted, auction house freezes, everyone is frozen but your character, etc. This is most common on the New York realms, there has been many reports for this happening on the Chicago realms as well.

How can I help Blizzard fix this faster?
They know what it is, most you can do to help is post the following:

1) Your city/state.
2) Your ISP: Bright House, Road Runner, Time Warner Cable
3) Your traceroute. https://us.battle.net/support/en/article/performing-a-traceroute For aesthetic purposes to make it easier to read post it in [code][/code] tags.

How do I find my server IP?
Quickest way is from the official fansite, Wowpedia: http://www.wowpedia.org/US_realm_list_by_datacenter

Is there an expected fix?
Yes, yes there is. It's coming soon. Blizzard is aware of the issue:
09/11/2012 09:57 AMPosted by Velnrak
Thank you again for posting the information I've asked for. Our network engineers are confident they've isolated the bottleneck, which appears to have been saturated for several hours a day for the past week. They're working with the peering partners to get this resolved as quickly as possible. Thank you very much for your patience.

What does this mean? It means basically too much traffic, and the pathway is a bit too small for it. A traffic jam on a 4 lane road, but, only two lanes are available, but, you can't get through at the rate it's intended at. - Mcfluff of Area 52

Why is it taking so long to fix?
Networking and peering issues are long and complicated to fix, especially when it's live. They need to figure out:
1) What went wrong.
2) Why did it go wrong.
3) How to stop it from happening again.
4) Working with multiple relays and data centers to correct.
5) Find a fix.
6) Apply a fix.
7) Restart the services.
8) Hope it works without harming others.

It goes on and on and it is a vicious cycle.

Will we be compensated for lost time since this started on August, 28th?
Likely, no. Because there is no way to sort between ISPs to show whom is having the active problems.

I restarted WoW it's working now! But, it stopped working!
This is common. Works for a few moments then you'd get lag spikes again. These happen all the time in random places and are prominent in Battlegrounds and Dungeons/Raids.

09/10/2012 09:26 AMPosted by Velnrak
If you're not a Road Runner-related customer, please create your own thread, and we can troubleshoot in your thread.


LATEST UPDATE:
We're continuing to pursue a solution for this issue, but unfortunately I have no progress to report. There are several degrees of separation to the source of the issue, which means our network engineers are talking to AT&T, who are trying to get updates from their peering partner. I'll be sure to report updates as I get them. Thanks again for your patience =)
85 Worgen Death Knight
8075
bump
90 Orc Shaman
13480
Still happening to me as well. We have a Cox thread here http://us.battle.net/wow/en/forum/topic/6606432028?page=1
90 Human Mage
13915
Everything has been fine for a couple days now on Aerie Peak.

1) San Diego/CA
2) Road Runner, Time Warner Cable
3)


>tracert 199.107.7.1

Tracing route to 199.107.7.1 over a maximum of 30 hops

1 16 ms 58 ms 8 ms cpe-76-88-64-1.san.res.rr.com [76.88.64.1]
2 20 ms 10 ms 11 ms ge7-4.sndaca78-cer01.socal.rr.com [76.167.13.185]
3 30 ms 17 ms 28 ms tge0-8-0-11.sndhcaax-ccr01.socal.rr.com [72.129.2.2]
4 17 ms 19 ms 29 ms agg22.lsancarc-ccr01.socal.rr.com [72.129.1.0]
5 31 ms 68 ms 22 ms 107.14.19.32
6 14 ms 14 ms 30 ms ae-0-0.pr0.lax00.tbone.rr.com [66.109.6.135]
7 11 ms 14 ms 27 ms ix-5-0-0-0.tcore2.LVW-LosAngeles.as6453.net [64.86.252.153]
8 25 ms 26 ms 30 ms if-2-2.tcore1.LVW-LosAngeles.as6453.net [66.110.59.1]
9 18 ms 16 ms 15 ms 66.110.59.42
10 96 ms 90 ms 87 ms cr2.la2ca.ip.att.net [12.122.84.218]
11 84 ms 103 ms 84 ms cr1.slkut.ip.att.net [12.122.30.29]
12 88 ms 90 ms 91 ms cr2.dvmco.ip.att.net [12.122.30.26]
13 85 ms 99 ms 88 ms cr1.cgcil.ip.att.net [12.122.31.86]
14 86 ms 86 ms 84 ms cr1.cl2oh.ip.att.net [12.122.2.206]
15 79 ms 91 ms 79 ms cr2.cl2oh.ip.att.net [12.122.2.126]
16 84 ms 84 ms 86 ms cr2.phlpa.ip.att.net [12.122.2.210]
17 142 ms 121 ms 107 ms gar1.pitpa.ip.att.net [12.122.107.85]
18 93 ms 92 ms 159 ms 12-122-254-242.attens.net [12.122.254.242]
19 89 ms 86 ms 94 ms mdf001c7613r0003-gig-10-1.nyc3.attens.net [63.240.65.10]
20 * * * Request timed out.


yes I get sporadic high ping but I've been running a lot of HoTs and every one of them has been fine.
100 Orc Mage
14430
This is not a ISP specific issue. So im a bit concerned that Blizzard Support is asking people to make their own threads in regards to their ISP.

IP Hop that appears to be the cause is apparently used by all ISP's to connect to Blizzards datacenter. Which in itself is strange, for the company who owns the IP HOP is a consulting firm.

Edit:
Reading through CSC's corporate breakdown i possibly found the cause. Chances are they added on another layer of security to that IP HOP after the security breach last month. And it is causing a bottleneck during peak times.
Edited by Mahdii on 9/21/2012 9:47 PM PDT
90 Orc Shaman
13480
This is not a ISP specific issue. So im a bit concerned that Blizzard Support is asking people to make their own threads in regards to their ISP.

IP Hop that appears to be the cause is apparently used by all ISP's to connect to Blizzards datacenter. Which in itself is strange, for the company who owns the IP HOP is a consulting firm.

Edit:
Reading through CSC's corporate breakdown i possibly found the cause. Chances are they added on another layer of security to that IP HOP after the security breach last month. And it is causing a bottleneck during peak times.


The reason they asked for the ISP is to see how each ISP is interacting with their data-centers and also to help narrow down where the cause happens. This isn't just CSC (Computer Sciences Corporation) since well it is AT&T. I don't know where you are getting your information (since you have yet to share anything on any post), but from looking up each IP separately (where the main jump in latency starts) I am seeing AT&T listed every time. Now CSC did have a contract with AT&T, but that was for 10 years back in 1999 I am not sure if they renewed it or renegotiated after it was up.
Edited by Zurotal on 9/21/2012 10:59 PM PDT
85 Undead Priest
14015
Crossing fingers here... But it seems to be fixed for me.
Yesterday, I've done multiple traces, and played with amazing great latency.
There were a few weird latency spikes when I entered the game fresh, and once when I switched continents from Orgrimmar to Shatt. But all in all stable, and I don't see any package losses in the ATT network anymore.

I hope it stays that way.
Thanks Blizz Techs. Awesome work.
96 Night Elf Druid
13900
Had been going really well this week until this morning. Thought it was fixed but now playing with 21000ms total.

Just for funsies

Orlando
Brighthouse

Tracing route to 12.129.206.130 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.1.1
2 1 ms <1 ms <1 ms z69-94-216-1.ips.direcpath.com [69.94.216.1]
3 11 ms 10 ms 10 ms 172.24.1.41
4 11 ms 10 ms 10 ms 172.24.0.13
5 11 ms 11 ms 10 ms 172.24.0.242
6 11 ms 10 ms 10 ms xe-3-1-1.mpr3.atl6.us.above.net [64.125.175.233]
7 11 ms 10 ms 10 ms xe-0-0-0.mpr4.atl6.us.above.net [64.125.31.42]
8 11 ms 11 ms 11 ms 192.205.35.233
9 65 ms 63 ms 63 ms cr1.attga.ip.att.net [12.123.22.26]
10 60 ms 59 ms 59 ms cr2.dlstx.ip.att.net [12.122.28.174]
11 61 ms 63 ms 63 ms cr2.la2ca.ip.att.net [12.122.28.178]
12 58 ms 58 ms 58 ms gar29.la2ca.ip.att.net [12.122.129.241]
13 60 ms 59 ms 59 ms 12-122-254-234.attens.net [12.122.254.234]
14 60 ms 60 ms 97 ms 12.129.193.250
15 * * * Request timed out.
16 * * * Request timed out.
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.
100 Pandaren Rogue
17430
BUMP

Been fine the last few days, thought maybe it was finally solved - and then WHAM around noon or so I got slammed with horrible lag again. In an effort to correct it by re-connecting to the game as we had been doing, I am now stuck on 'Connecting' after I log in with my id and such - and it times out.

From what I can see, it's lag on my end AND lag through ATT's peering partners. Gonna update this after I restart my gateway and see if the numbers change.

Edit: Yes indeed it did change from me to bliz-la. Me to Terokkar is still crappy.

Tracert to Blizz-la:
Tracing route to 12.129.254.152 over a maximum of 30 hops

1 45 ms 24 ms 32 ms cpe-75-84-208-1.socal.res.rr.com [75.84.208.1]
2 15 ms 11 ms 16 ms 76.167.3.201
3 86 ms 58 ms 23 ms tge0-9-0-1.ontrcacp-ccr01.socal.rr.com [72.129.5.162]
4 22 ms 23 ms 31 ms agg21.lsanca4-rtr1.socal.rr.com [72.129.5.0]
5 59 ms 80 ms 78 ms ae-5-0.cr0.lax00.tbone.rr.com [66.109.6.102]
6 131 ms 94 ms 51 ms ae-0-0.pr0.lax00.tbone.rr.com [66.109.6.135]
7 47 ms 21 ms 19 ms ix-5-2-1-0.tcore2.LVW-LosAngeles.as6453.net [64.86.252.157]
8 56 ms 17 ms 67 ms if-2-2.tcore1.LVW-LosAngeles.as6453.net [66.110.59.1]
9 135 ms 136 ms 84 ms 66.110.59.42
10 43 ms 84 ms 87 ms cr2.la2ca.ip.att.net [12.122.84.218]
11 54 ms 112 ms 61 ms gar29.la2ca.ip.att.net [12.122.129.241]
12 39 ms 18 ms 17 ms 12-122-254-238.attens.net [12.122.254.238]
13 65 ms 80 ms 91 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
14 * * * Request timed out.


Tracert 2 after gateway restart:
Tracing route to 12.129.254.152 over a maximum of 30 hops

1 36 ms 27 ms 29 ms cpe-75-84-208-1.socal.res.rr.com [75.84.208.1]
2 12 ms 12 ms 15 ms 76.167.3.201
3 20 ms 23 ms 23 ms tge0-9-0-1.ontrcacp-ccr01.socal.rr.com [72.129.5.162]
4 23 ms 15 ms 23 ms agg21.lsanca4-rtr1.socal.rr.com [72.129.5.0]
5 20 ms 15 ms 23 ms ae-5-0.cr0.lax00.tbone.rr.com [66.109.6.102]
6 14 ms 15 ms 15 ms ae-0-0.pr0.lax00.tbone.rr.com [66.109.6.135]
7 16 ms 18 ms 31 ms ix-5-2-1-0.tcore2.LVW-LosAngeles.as6453.net [64.86.252.157]
8 73 ms 31 ms 15 ms if-2-2.tcore1.LVW-LosAngeles.as6453.net [66.110.59.1]
9 15 ms 19 ms 18 ms 66.110.59.42
10 19 ms 22 ms 20 ms cr2.la2ca.ip.att.net [12.122.84.218]
11 17 ms 19 ms 18 ms gar29.la2ca.ip.att.net [12.122.129.241]
12 18 ms 18 ms 18 ms 12-122-254-234.attens.net [12.122.254.234]
13 17 ms 18 ms 19 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
14 * * * Request timed out.


Much MUCH better.

To Terokkar:
Tracing route to 199.107.24.232 over a maximum of 30 hops

1 42 ms 24 ms 40 ms cpe-75-84-208-1.socal.res.rr.com [75.84.208.1]
2 14 ms 102 ms 13 ms 76.167.3.201
3 21 ms 23 ms 35 ms tge0-9-0-0.ontrcacp-ccr01.socal.rr.com [72.129.5.160]
4 26 ms 79 ms 87 ms agg21.lsanca4-rtr1.socal.rr.com [72.129.5.0]
5 141 ms 103 ms 176 ms ae-6-0.cr0.lax00.tbone.rr.com [66.109.6.212]
6 166 ms 185 ms 121 ms 107.14.19.138
7 69 ms 16 ms 18 ms ix-5-2-1-0.tcore2.LVW-LosAngeles.as6453.net [64.86.252.157]
8 15 ms 15 ms 27 ms if-2-2.tcore1.LVW-LosAngeles.as6453.net [66.110.59.1]
9 32 ms 44 ms 26 ms 66.110.59.42
10 85 ms 81 ms 84 ms cr2.la2ca.ip.att.net [12.122.84.218]
11 83 ms 78 ms 80 ms cr1.slkut.ip.att.net [12.122.30.29]
12 111 ms 179 ms 171 ms cr2.dvmco.ip.att.net [12.122.30.26]
13 153 ms 120 ms 159 ms cr1.cgcil.ip.att.net [12.122.31.86]
14 106 ms 90 ms 89 ms cr1.cl2oh.ip.att.net [12.122.2.206]
15 102 ms 83 ms 79 ms cr2.cl2oh.ip.att.net [12.122.2.126]
16 83 ms 86 ms 87 ms cr2.phlpa.ip.att.net [12.122.2.210]
17 89 ms 92 ms 83 ms gar1.pitpa.ip.att.net [12.122.107.85]
18 119 ms 130 ms 95 ms 12-122-254-242.attens.net [12.122.254.242]
19 101 ms 86 ms 101 ms mdf001c7613r0004-gig-12-1.nyc3.attens.net [63.240.65.14]
20 * *


To Terokkar after gateway restart:

Tracing route to 199.107.24.232 over a maximum of 30 hops

1 39 ms 24 ms 34 ms cpe-75-84-208-1.socal.res.rr.com [75.84.208.1]
2 15 ms 11 ms 12 ms 76.167.3.201
3 27 ms 23 ms 23 ms 72.129.5.160
4 20 ms 20 ms 15 ms agg21.lsanca4-rtr1.socal.rr.com [72.129.5.0]
5 22 ms 15 ms 16 ms 66.109.6.212
6 16 ms 18 ms 22 ms 107.14.19.138
7 19 ms 21 ms 18 ms ix-5-2-1-0.tcore2.LVW-LosAngeles.as6453.net [64.86.252.157]
8 18 ms 15 ms 14 ms if-2-2.tcore1.LVW-LosAngeles.as6453.net [66.110.59.1]
9 19 ms 21 ms 18 ms 66.110.59.42
10 83 ms 80 ms 85 ms cr2.la2ca.ip.att.net [12.122.84.218]
11 85 ms 86 ms 80 ms cr1.slkut.ip.att.net [12.122.30.29]
12 80 ms 79 ms 79 ms cr2.dvmco.ip.att.net [12.122.30.26]
13 87 ms 84 ms * cr1.cgcil.ip.att.net [12.122.31.86]
14 86 ms 83 ms 134 ms cr1.cl2oh.ip.att.net [12.122.2.206]
15 82 ms 83 ms 86 ms cr2.cl2oh.ip.att.net [12.122.2.126]
16 86 ms 88 ms 89 ms cr2.phlpa.ip.att.net [12.122.2.210]
17 81 ms 79 ms 79 ms gar1.pitpa.ip.att.net [12.122.107.85]
18 89 ms 97 ms 93 ms 12-122-254-242.attens.net [12.122.254.242]
19 83 ms 89 ms 82 ms mdf001c7613r0004-gig-12-1.nyc3.attens.net [63.240.65.14]
20 * * * Request timed out.
Edited by Lucrezia on 9/22/2012 12:27 PM PDT
90 Pandaren Hunter
9805
Still some issues! I hope this is fixed by Tuesday!
100 Human Mage
7075
bump
90 Undead Warlock
10715
09/21/2012 03:28 PMPosted by Hikuro
Seems to end at the same IP as the person above me.


It will end at that or one other IP for everyone that does a Tracert to the NY Data center. Those two IP's are the "gateway" into Blizz's servers. You will not see the other side, nor an actual ending a t the IP you entered for it to trace to for security reasons.

From the Wiki page listing all the server IP's:

When doing a traceroute to servers in New York, the last hop should be one of the following:

63.240.65.10
63.240.65.14
Edited by Wraughton on 9/22/2012 4:17 PM PDT
73 Worgen Druid
7165
Glad I came across this post, at least I've an idea what's going on now.
Couldn't get the trace to run, so here's teh bit of info I can offer.
Tampa Bay, Florida
Roadrunner, Brighthouse
have had trouble accessing both Khadgar and Nesingwary (I know Nesingwary to be out of the Phoenix center).
Problems like this could only be worse if it were the expansion opening day.
100 Dwarf Paladin
19795
Been trying to find my issues and glad I came across this. Definitely not a TWC/Roadrunner thing only. I'm on comcast in Colorado and having the exact same issues described and its always world latency so something is going on and I hope to god its fixed by Tuesday
90 Pandaren Hunter
9805
It worked for a while. But, it started acting up again in battlegrounds. :(
90 Orc Shaman
10620
I had this issue until last Tuesday. Since Tuesday maintenance, it has completely gone away for me. Absolutely NO problems or lag since then. Insight/Road Runner in Columbus, OH.
90 Night Elf Priest
7335
Any new info to share on when this is going to be fixed?
90 Pandaren Hunter
9805
Everything seems to be working great! :D

Was it fixed?
This topic is locked.

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)

Reported!

[Close]