Problem with traffic to Blizzard servers (World of Warcraft) via Cogentco

I am having the exact same problem here in Georgia. I have been in contact with all THREE parties (Blizzard, Cogent, and Cox). Blizzard acknowledges the issue but is unable to do anything because the issue is with the Cogent servers. Cogent says contact your ISP. Cox won't acknowledge the issue. All Cox needs to do is stop routing traffic to these Cogent servers. I am very displeased with Cox's customer service through this. I hope Cox realizes this certainly is not worth losing a customers over and simply stops routing traffic to cogent.

Ive contacted Cox through their FB page, you might try that too.  I so far had been the only one to post a comment there but there have been a few others who have commented on my post. 

Dont know if this will help you any since its from AZ, but you can probably find your local Cox page on FB,

https://www.facebook.com/CoxArizona/posts/10151331014126220?comment_id=24350477&ref=notif&notif_t=feed_comment

The trace route data posted in those threads all seemed to suggest a problem within the AT&T network as commonly seen before in the past.  If you have any additional trace route data suggesting otherwise please post and I'll take a look.

Im very much aware of this being a problem with the Cogent/ATT connection.  The problem I have with it being decidedly not a Cox Comm problem is that folks from around the neighborhood who connect to the internet from other providers are not being routed through the Cogent connection.   You guys ultimately control how my data is routed, even off your network.  None of us are getting anything but the run around when we try to discuss this issue with the providers that our data is being routed through.  We are told that you must open dialogue with them because you are the ones routing data through them. 

Chris, thanks for the reply. Its good to hear from a moderator. But can you deny the fact Cox began routing us through the Cogent servers on 8 Jan? The same day the problems began? 

That may be the most favorable route to Blizzard in terms of metrics which is usually a good thing.  I seem to remember somebody metnioning that Blizzard was aware of the issue however that it was only a problem during periods of peak demand.

Its a consistent problem through out the day with service being most problematic during peak hours.  Ive spoken with Blizzard, they cant do much because of the way my ISP (that would be Cox Comm) is routing our traffic.  Ive attempted to speak to Cogentco and ATT but because I am not their customer they wont do anything and we are told to talk to our ISPs to have you guys address the problem.  So am I supposed to be stuck in limbo between the whole lot of you guys forever?  If it were a problem on the ATT side of the house, you would think that everyone who connects to that ATT server would have the same issue, but as of right now its mostly the folks who have the cogentco connection who are having the issues.  I have 3 other Tracerts from people who are not being routed through Cogentco who have great numbers at the ATT connection.  I can post them here if needed. 

Just called and talked to a Cogentco rep (finally got someone who didnt give me the no customer no help run around).  They are seeing a 99% saturation at the connection with ATT due to a peerage problem.  Their advice, wait for it, is to talk to you guys and find out of you guys can reroute the traffic either temporarily until this peerage issue is settled or permanently. 

Exactly, if the problem were Blizzard, all Blizzard customers would be experiencing this issue. But it so happens that only Cox users are experiencing the issue. It is not a fault of Cox's hardware or infrastructure, just the way they are routing us. 

Chris, you're saying that its not Cox routing us to Cogent but Blizzard? I didn't know that the destination server could chose the route... 

This isn't really a routing issue.  The route to Blizzard is correct and the most favorable route.  The issue is with a segment off of our network on that route, we have no control over that portion of the issue.

Thank you Chris. I understand and I will take this information to Blizzard. However, the only thing that still makes me believe that it is an issue with Cox is the fact only Cox customers are experiencing this issue.

There's an old saying that coalation doesn't imply causality which I think is very applicable in this sitaution.  The most favorable path from Cox to Blizzard just happens to take it over a part of the Cogento/AT&T connection that isn't necessarily used by all other Internet providers.

Ok, Ive spoken to Blizzard (they tell me to talk to you guys because its in how YOUR COMPANY routes MY traffic).  Ive talked to Cogentco, they are aware there is a peering problem between themselves and ATT, their advice, again talk to you guys because its in how YOUR COMPANY routes MY traffic.  Ill be speaking to ATT momentarily.  Im sure that its going to come down to, "talk to YOUR ISP, they can reroute OUR data.