High Latency related to Battlegroup?

Technical Support
Prev 1 2 3 101 Next
Hi,

Everyone here speaking from Arizona/Cox who has this issue right now probably had it about a month ago also if you were connecting to the same servers from the same area.

Your latency and in-game performance took a nosedive on 9 January because on this day, Cox swapped back from routing through a stable server to routing through Cognet hosted servers which are consistently terrible for WoW.

I've had constant (independent) internet issues with Cox to the point that I run and log daily tracerts to my server (Illidan - Rampage) in order to diagnose the source of issues as soon as they arise. I noted that between 8 January and 9 January, my path from Illidan was reverted back to using Cognet, after I had managed to get them to use an alternative route a month ago after suffering similar issues.

I'm working very hard to get this fixed presently because - suffice it to say I can't raid at all and in my guild this is very bad. Anyhow, to answer the question, OP, for this specific issue, the latency you are experiencing is related to battlegroup because certain servers aren't routed through Cognet. I suggest that for any server that you're iinterested in playing on presently, run a trace route. If you see this subdomain come up repeatedly

atlas.cognetco.com

Chances are you're going to be experiencing a lot of latency issues until the problem is re-resolved.

The "blame" as it were in this case (besides obviously falling on Cognet) is shared somewhat between ATT (Blizzard's ISP) and Cox, because both companies have to choose to peer to Cognet for the intermediate hops. This said, I've gotten this issue resolved once in the past through many, many, many hours spent talking to Cox. I've never spoken to Blizzard nor ATT about the problem. Thus, it is wholly within Cox's power to fix what's going on, but good luck finding someone who works there who knows how to do so.
01/10/2013 09:05 PMPosted by Omniscient
Phoenix, AZ. Lag on my main servers Bloodhoof and Stormrage, but not Antonidas. Don't know why this would start up, but it's obviously something Blizzard did since it was after a tuesday maintenance.


Hi Omniscient,

This had nothing to do with Tuesday maintenance. In fact, on Tuesday specifically, connections were just fine, if you happened to raid that day. It has entirely to do with Cox swapping back to routing through Cognet.

*edit* I've noted some people saying the issue is confied to the Chicago datacentre. This isn't quite accurate, although out of all of the servers I've pinged, the Chicago servers are the worst. They also uncoincidentally happen to use the most Cognet hops.

Try connecting to a server on Emberstorm. This battlegroup is located on a datacentre in Phoenix. I am getting around 85-150 ping here with casual (nongrouping, nonraiding) play, whilst other people I know on these servers connecting from halfway accross the country can maintain sub-80 ms connections smoothly. I should note that when I ran a tracert to the server Quel'Dorei, one hop appeared to have the Cognet subdomain.
Hi Omniscient,

This had nothing to do with Tuesday maintenance. In fact, on Tuesday specifically, connections were just fine, if you happened to raid that day. It has entirely to do with Cox swapping back to routing through Cognet.


I'd love to here what the reasoning is that someone from outside the US is being routed through those servers though.... ./sigh.

Caused a lot of raid headaches and now I feel terrible for being a burden on guild progression.
Hi,

Everyone here speaking from Arizona/Cox who has this issue right now probably had it about a month ago also if you were connecting to the same servers from the same area.

Your latency and in-game performance took a nosedive on 9 January because on this day, Cox swapped back from routing through a stable server to routing through Cognet hosted servers which are consistently terrible for WoW.

I've had constant (independent) internet issues with Cox to the point that I run and log daily tracerts to my server (Illidan - Rampage) in order to diagnose the source of issues as soon as they arise. I noted that between 8 January and 9 January, my path from Illidan was reverted back to using Cognet, after I had managed to get them to use an alternative route a month ago after suffering similar issues.

I'm working very hard to get this fixed presently because - suffice it to say I can't raid at all and in my guild this is very bad. Anyhow, to answer the question, OP, for this specific issue, the latency you are experiencing is related to battlegroup because certain servers aren't routed through Cognet. I suggest that for any server that you're iinterested in playing on presently, run a trace route. If you see this subdomain come up repeatedly

atlas.cognetco.com

Chances are you're going to be experiencing a lot of latency issues until the problem is re-resolved.

The "blame" as it were in this case (besides obviously falling on Cognet) is shared somewhat between ATT (Blizzard's ISP) and Cox, because both companies have to choose to peer to Cognet for the intermediate hops. This said, I've gotten this issue resolved once in the past through many, many, many hours spent talking to Cox. I've never spoken to Blizzard nor ATT about the problem. Thus, it is wholly within Cox's power to fix what's going on, but good luck finding someone who works there who knows how to do so.


You sir, are correct. Cognet comes up many times in my trace. This issue started for me yesterday.
Okay so the question is: Does Cox do this because its cheaper contractually? And if so, do they have the power/authority to route individual IP addresses around Cogent?
I play on burning blade same as OP and I am about 2,500 miles away on the east coast and experience the same latency spikes I am on metrocast.

I would like some actual proof of your theory, especially since it's not just people using Cox that are running into this problem, thanks.


Here's a partial tracert to Illidan taken from 8 January at 19h, and one taken from 9 January at the same time. I've edited out the first five hops as they're irrelevant, haven't changed, and I don't feel comfortable posting them on a public forum.

8 January tracert - solid 77ms throughout raid night

6 langbprj02-ae2.rd.la.cox.net [68.1.1.19]
7 216.156.65.25.ptr.us.xo.net [216.156.65.25]
8 216.156.4.2.ptr.us.xo.net [216.156.4.2]
9 205.158.79.242.ptr.us.xo.net [205.158.79.242]
10 cr2.la2ca.ip.att.net [12.123.30.190]
11 cr1.slkut.ip.att.net [12.122.30.29]
12 cr2.dvmco.ip.att.net [12.122.30.26]
13 cr1.cgcil.ip.att.net [12.122.31.86]
14 gar2.clboh.ip.att.net [12.122.133.197]
15 12.122.251.22
16 63.240.130.210
17 * * *

9 January tracert - 600 - 1500+ ms when attempting a raid

6 langbprj02-ae2.rd.la.cox.net [68.1.1.19]
7 te7-5.ccr02.lax05.atlas.cogentco.com [154.54.13.129]
8 te0-1-0-1.ccr22.lax01.atlas.cogentco.com [130.117.50.89]
9 te0-3-0-6.ccr22.iah01.atlas.cogentco.com [154.54.3.185]
10 te0-4-0-6.ccr22.dfw01.atlas.cogentco.com [154.54.0.206]
11 te0-2-0-6.ccr22.mci01.atlas.cogentco.com [154.54.85.153]
12 te0-5-0-4.ccr22.ord01.atlas.cogentco.com [154.54.45.150]
13 te0-5-0-3.ccr22.ord03.atlas.cogentco.com [154.54.43.234]
14 att.ord03.atlas.cogentco.com [154.54.12.86]
15 cr1.cgcil.ip.att.net [12.122.84.54]
16 gar2.clboh.ip.att.net [12.122.133.197]
17 12.122.251.22
18 63.240.130.210
19 * * *

It's interesting that the non Cognet route is also more efficient and that does result in a noticable net reduction in latency, even without the packet loss.

*edit*
I'm speaking mainly for people in the Arizona, USA area using Cox who have these issues. If you don't use Cox or live in a different area, I have no idea about the specifics of your issue. I only know as much as I do about my area's problem because the exact same thing was going on a month ago and Cox's rerouting the servers fixed it.

@the person who asked about cost-cutting : I was on the phone with Cox tech support for two hours earlier today to no avail with getting an actual fix out, but I was told that it's possible that they pushed some sort of server update, and the reroute made a month ago wasn't "saved" and therefore was overwritten/rolled back with the update. The tech I was connected to was not actually from my area and could not confirm that this is what happened, but suggested it as a possible explanation for the situation. I don't know anything about networks beyond what I've had to learn in order to argue my way to sometimes-working service out here in Arizona, so I don't know how plausible this theory is.
So basically all we from AZ can do is stick our thumb in our butts and wait for the Cox or Blizz to fix it?
im almost always under 75 lat but these last few weeks its been bad.
3 30 ms 30 ms 30 ms gi9-7.ccr01.iad01.atlas.cogentco.com [38.122.66.161]
4 30 ms 30 ms 30 ms te2-2.ccr02.iad01.atlas.cogentco.com [154.54.26.93]
5 30 ms 30 ms 30 ms te0-0-0-6.ccr22.iad02.atlas.cogentco.com [154.54.31.193]
6 31 ms 35 ms 33 ms te0-2-0-4.ccr22.dca01.atlas.cogentco.com [154.54.7.157]
7 43 ms 43 ms 43 ms te0-3-0-7.ccr22.atl01.atlas.cogentco.com [154.54.42.202]
8 57 ms 57 ms 56 ms te0-0-0-1.ccr22.iah01.atlas.cogentco.com [154.54.5.94]
9 92 ms * 93 ms te0-2-0-3.ccr22.lax01.atlas.cogentco.com [154.54.45.2]
10 93 ms 94 ms 93 ms te0-6-0-0.ccr22.lax05.atlas.cogentco.com [130.117.50.90]
11 134 ms 135 ms 135 ms att.lax05.atlas.cogentco.com [154.54.11.10]
12 140 ms 138 ms 140 ms cr2.la2ca.ip.att.net [12.122.84.218]
13 133 ms 134 ms 131 ms gar20.la2ca.ip.att.net [12.122.128.181]
14 136 ms 135 ms 136 ms 12-122-254-238.attens.net [12.122.254.238]
15 336 ms 210 ms 235 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
16 * * * Request timed out.ad
So we need to drop from Cox to switch to Centurylink. Y/Y?
01/10/2013 10:31 PMPosted by Omniscient
So we need to drop from Cox to switch to Centurylink. Y/Y?


Considering how terrible Century Link is, no.


Then what is our fix here?
@Omniscient : I've posted the tracerts. I don't know what kind of "proof" you require. I 'm posting from a level 2 because I don't want records of my internet issues coming up in forum/Google searches for my character's name. This might be erring on the side of paranoia, but I would prefer to be safe rather than sorry. I want to help out as much as I can because I've had the issue before and gotten it resolved, and would like to contribute to a resolution again. I'll continue to work on doing so whether you believe me or not.

don"t copy your first 2 jumps? beside mine are both under 9ms so i know the issue isn't there.
Bleh I messed up my post.

@Aycheff : When I called Cox, I eventually did get a resolution last time. I plan on continuing to try this avenue of action.

@Omniscient : I'm not a Blizzard employee. It's possible that Blizzard could swap something on their end that would resolve the issue. I've just had success doing it through Cox before, so I personally will try that route again. I would welcome any fix that works, regardless of the party that instigates it.

Join the Conversation

Return to Forum