High Latency related to Battlegroup?

(Locked)

90 Blood Elf Priest
12985
I'm assuming we won't get a post from a blue because they don't have any advice on this one right? All we can do is pray Cox (and possibly other companies that route through Cognet?) changes their stuff?

I'll be rather unhappy if I find out I'll be regularly having issues with latency after I just spent 25 bucks to transfer over and raid with my new guild. I've been there just barely 2 weeks and now I can't raid. :-/
Edited by Aisllyn on 1/10/2013 11:38 PM PST
90 Blood Elf Priest
12985
And thank you for the information Illista, that may help when trying to troubleshoot and fix all of this.
2 Night Elf Druid
0
You're welcome. I figure that the more people are actively trying to get this resolved, the better chance one of us will get through to someone, somewhere, who can do something.
100 Goblin Hunter
16695
I live in PA and have Consolidated Communications as my ISP. Its through my phone company. I play on Zul'Jin as well. I have seen cogentco come up on my traces as well:

Tracing route to 63.240.161.189 over a maximum of 30 hops

3 9 ms 10 ms 9 ms gibs-isp-acc-hr0-e10-11.consolidated.net [72.22.30.205]
4 9 ms 9 ms 11 ms tctr-isp-cor-hr2-e3-1.consolidated.net [72.22.17.6]
5 10 ms 10 ms 15 ms te1-8.na41.b016104-1.pit02.atlas.cogentco.com [38.104.120.129]
6 10 ms 9 ms 9 ms te3-1.3509.ccr01.pit02.atlas.cogentco.com [38.20.55.205]
7 13 ms 12 ms 12 ms te4-1.ccr02.cle04.atlas.cogentco.com [154.54.30.9]
8 24 ms 21 ms 22 ms te0-5-0-6.ccr21.ord01.atlas.cogentco.com [154.54.45.130]
9 22 ms 22 ms 21 ms te0-5-0-5.ccr22.ord03.atlas.cogentco.com [154.54.44.162]
10 34 ms 34 ms 34 ms 192.205.37.173
11 49 ms 39 ms 36 ms cr1.cgcil.ip.att.net [12.122.84.54]
12 35 ms * 44 ms gar3.cgcil.ip.att.net [12.122.132.213]
13 36 ms 41 ms 36 ms 12.122.251.22
14 36 ms * 54 ms 63.240.130.214
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.

This was taken 1-10-13 at 9:29pm EST.

So what does that mean for me? I am no where near AZ and have never heard of Cox Internet. Could my ISP be somehow related to Cox and thusly be the reason why I have come across this lately beginning before this week but coming to prominence mainly since the 8th of this year?
Edited by Yodathehulk on 1/11/2013 3:00 AM PST
90 Worgen Druid
10290
for everyone living in AZ, it is not only the cogent servers that are the issue. They are most of the issue, but if you run a tracert during "peak" hours cox is just as much to blame.

I have had terrible MS on burning blade, since Jan 8th anywhere from 125-1500+ It is the worst between ~5-11pm (I conveniently raid from 5-9 xD)

I ran ping plotter to burning blade all evening/night tonight, as was consistently getting HIGH ms from two local cox IP addresses, and dropping packets consistently.

I definetly noticed a correlation between 68.1.1.19 %loss and my MS in game. right now at 4:00am the packet loss is 0 and my ping in game is ~90.

I used to receive ~55-60MS until the first time the cogent servers became an issue, it was better for about a month 70-75, until recently when it has returned to beyond bad.

Best thing we can do is keep calling cox, keep asking for supervisors, and annoy the crap out of them until they finally fix it. 623-594-1000 if you wish to contact cox communications.

edit: I am going under the assumption that posting a ISP's customer support # is not a violation of ToS, since its purpose is to help people with this issue :)
Edited by Ayanami on 1/11/2013 3:37 AM PST
100 Orc Death Knight
17920
Yeah I noticed on a few of my tracert's that "langbprj02-ae2.rd.la.cox.net [68.1.1.19]" has dropped packets. But when I do a "ping 68.1.1.19 -t" I never see a drop (response timed out) so I really don't know what to think other than just constantly calling Cox to try getting them to route me through a non-Cognet path.
90 Undead Mage
10480
Called a few times today to no avail... trying more later
2 Night Elf Druid
0
01/11/2013 04:44 AMPosted by Knucklz
Yeah I noticed on a few of my tracert's that "langbprj02-ae2.rd.la.cox.net [68.1.1.19]" has dropped packets. But when I do a "ping 68.1.1.19 -t" I never see a drop (response timed out) so I really don't know what to think other than just constantly calling Cox to try getting them to route me through a non-Cognet path.


Posted this in another thread ; will repost it here.

I asked elsewhere online about the 68.1.1.19 issues and got this response from someone a lot more knowledgeable in networking than I :

Being that there is no loss before or after that hop it's very likely that router deprioritizes ICMP packets. Basically, it only responds to a set number in a given time frame. Once that number is reached it discards the rest. Hope this helps.

I have no idea how accurate this is in our specific case but it makes sense given that this address ALWAYS shows quite a lot of packet loss, and did so before the latency issues began (i.e, when pathing to the Chicago datacentre was routed through XO and not Cognet).

Again I think the problem here directly is with Cognet, and there are ISPs other than Cox that are peering to Cognet, which is causing issues for anyone unlucky enough to be in that situation. That said, I believe it's a 2-way street between ATT (Blizz ISP) and the user's ISP, because most people connecting to these servers are not having these issues. For example, in my guild, three members of about 30 use Cox in Arizona. All three of us can't raid now ; no one else in the guild has been affected in the slightest.

Last time this happened, calling my ISP (Cox) repeatedly did result in a resolution of the problem. I'm not saying it will this time, or when, but I can only imagine it's preferable by far to inaction.
Edited by Illista on 1/11/2013 7:49 AM PST
90 Blood Elf Priest
12985
Well, I'm seriously looking into Century Link after all this. A very tech savvy friend of mine, who works directly with networking said there is no reason for me not to switch to Century Link, he switched to CL over Cox himself when his only options were Cox or CL (he now lives in Tucson though).

Not that this helps anyone who can't/won't make the switch, but just putting in my thoughts.
90 Human Paladin
12160
01/11/2013 07:49 AMPosted by Illista
Yeah I noticed on a few of my tracert's that "langbprj02-ae2.rd.la.cox.net [68.1.1.19]" has dropped packets. But when I do a "ping 68.1.1.19 -t" I never see a drop (response timed out) so I really don't know what to think other than just constantly calling Cox to try getting them to route me through a non-Cognet path.


Posted this in another thread ; will repost it here.

I asked elsewhere online about the 68.1.1.19 issues and got this response from someone a lot more knowledgeable in networking than I :



this is correct. after speaking to a Cox rep on the DSLreports forums, i started using tools that sends TCP packets instead of just using ICMP. During peak hours when this problem is most severe this is what is seen:

lenn=46 ip=206.18.98.180 ttl=51 DF id=0 sport=3724 flags=SA seq=5176 win=5840 rtt=98.4 ms
len=46 ip=206.18.98.180 ttl=51 DF id=0 sport=3724 flags=SA seq=5177 win=5840 rtt=98.8 ms
len=46 ip=206.18.98.180 ttl=51 DF id=0 sport=3724 flags=SA seq=5179 win=5840 rtt=108.3 ms
len=46 ip=206.18.98.180 ttl=51 DF id=0 sport=3724 flags=SA seq=5181 win=5840 rtt=99.0 ms
len=46 ip=206.18.98.180 ttl=51 DF id=0 sport=3724 flags=SA seq=5182 win=5840 rtt=101.1 ms
len=46 ip=206.18.98.180 ttl=51 DF id=0 sport=3724 flags=SA seq=5183 win=5840 rtt=98.7 ms
len=46 ip=206.18.98.180 ttl=51 DF id=0 sport=3724 flags=SA seq=5184 win=5840 rtt=99.2 ms
len=46 ip=206.18.98.180 ttl=51 DF id=0 sport=3724 flags=SA seq=5185 win=5840 rtt=99.0 ms
DUP! len=46 ip=206.18.98.180 ttl=51 DF id=0 sport=3724 flags=SA seq=5183 win=5840 rtt=3098.0 ms
len=46 ip=206.18.98.180 ttl=51 DF id=0 sport=3724 flags=SA seq=5186 win=5840 rtt=99.3 ms
len=46 ip=206.18.98.180 ttl=51 DF id=0 sport=3724 flags=SA seq=5187 win=5840 rtt=99.3 ms

--- 206.18.98.180 hping statistic ---
13174 packets transmitted, 13106 packets received, 1% packet loss
round-trip min/avg/max = 92.8/547.7/10695.2 ms

There are a number of reasons one would come across a DUP, but seeing a DUP is generally a bad sign something is wrong either with layer 1 or layer 2, bad nic etc etc
97 Pandaren Monk
16115
Im in CT with comcast....I play on Burning Blade and i've never had any lag issues for hte most part but today my ping shots up to 700 (normally around 100) and i pretty much an unable to do anything. Alt F4 and relogging seems to help temporarily but it comes back... this is pretty terrible, not entirely sure what's going on but this definitely needs to be fixed...

we died many times last night because ^Waraila kept dcing :( well that wasn't the only reason but still :P
90 Blood Elf Priest
12985
Yup, we pretty much just 9m raided since I just stood in the background and spammed PoH (which as a Disc still was pretty OP), and they BRed me a lot.
100 Tauren Druid
21875
we died many times last night because ^Waraila kept dcing :( well that wasn't the only reason but still :P


<3 you too rama... but yeah... run a traceroute and you'll see where the issue is.
90 Pandaren Monk
10150
Had to give up my raid spot due to these issues. I hope it gets fixed soon.
(checking in from Tucson as well)
Edited by Yatta on 1/11/2013 10:41 AM PST
90 Orc Hunter
11410
i have the latency problem as well, and for me atleast, its only when connecting to chicago and new york data centers, with LA and phoenix im fine. this started for me roughly 6 weeks ago, when going to new york or chicago servers i get routed through Cogentco ips and when through LA and phoenix i dont, so im wondering if thats perhaps the cause of the lag.
Tucson AZ same !@#$ here cox cable is my ips
90 Blood Elf Death Knight
13290
Also having this issue; tried calling COX and getting no help at all. Also ran a tracert and getting multiple atlas.cogentco.com addresses along the way. High latency started a few days ago. Not sure what else to do; can't raid on the Chicago based servers while this happens.
19 Draenei Shaman
3295
Okay so it's quite clear that there is a problem for all who have Cox internet, but is blizzard going to do anything about this issue to try to resolve the problem? I feel like it would be easier for blizzard to manage this change since it affects only their customer base. My latency for other games and online applications is unaffected.

A blue post would be nice...
Edited by Talea on 1/11/2013 10:17 AM PST
90 Blood Elf Priest
12985
Okay so it's quite clear that there is a problem for all who have Cox internet, but is blizzard going to do anything about this issue to try to resolve the problem? I feel like it would be easier for blizzard to manage this change since it affects only their customer base. My latency for other games and online applications is unaffected.

A blue post would be nice...


^ This.

Also it doesn't seem to be just Cox. Whereas that's what has mostly been posted here, there are many threads reporting high latency. It seems to be an issue with some ISPs connection to Blizzard's servers.
Edited by Aisllyn on 1/11/2013 10:33 AM PST
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]