New Contributor
•
10 Messages
Problem with traffic to Blizzard servers (World of Warcraft) via Cogentco
The traffic from my house in AZ is sent to Phoenix and then sent out to a Cogentco connection between Cox and ATT (Blizzards provider). At the Cogentco interface there appears to be a problem with saturation and our data is being slowed down considerably by this saturation. I am not the only one experiencing this issue. Below are the links to multiple threads showing many people with problems connecting from the AZ area and others (some on different ISPs but still routing through Cogentco).
http://us.battle.net/wow/en/forum/topic/7006347308
http://us.battle.net/wow/en/forum/topic/7593741008
http://us.battle.net/wow/en/forum/topic/7592401496
http://us.battle.net/wow/en/forum/topic/7593741878
http://us.battle.net/wow/en/forum/topic/6552145272
When I call and try to get some sort of help from customer service, they have no clue what Im talking about and cant give me any means of contacting someone who does. When I contacted someone from the home networking department (which I was told to do via the online customer chat) I was passed around to someone else after explaining what the problem was to one person, and then while trying to explain the issue to this person I was hung up on.
Im sure Im going to be told this isnt an ISP problem but rather a problem on Blizzards end. And it isnt exactly a Cox Comm problem but it is a problem with how you route our traffic. Everyone who is being routed through these Cogentco connections is having the same issue, regardless of who their ISP is. Cogentco wont do anything to address the issue because we arent their customers and have told us that we need to contact our ISPs so that the ISP can address the issue with Cogentco.
Please do something to fix this.
Related Content
Closed
8
0
Closed
9
0
Closed
19
0
Closed
2
0
Closed
2
0
ElgorKad
New Contributor
•
12 Messages
No ultimatums, I just happen to be fortunate to have choices about where I spend my money and shall exercise them !
Unless of course Chris (or other) posts that happy message...
"Dear Valued Cox Customers
We are please to report we have reverted/changed our routing of traffic to avoid problems caused by or service partners (Cogent/AT&T).
We apologize for the inconvenience the routing change we made has caused and believe this problem has been solved."
So Chris - what news? I suppose the alternate message is AT&T/Cogent has fixed the issue works as well! :)
Clocks ticking - status please!
Thanks
0
0
warhippy
New Contributor
•
15 Messages
I think what we're seeing here is a company that chose a third rate routing service, and either financially or legally can't reroute traffic. Sorta like us when we agree to a two year contract with Cox. We're liable for payment, regardless of the service, and have to depend on our provider to be fair about providing a good service. Cox is stuck using that routing service, and it doesn't matter how many customers are dissatisfied, it's still gonna be routed thru there. I don't know what century links prices are, but I know two people in phoenix who play wow on my server who are having absolutely no latency issues, while my latency is spiking sometimes at night to 2000 to 3000ms, and I'm paying for Cox Ultimate, almost $100 a month. I'm calling CenturyLink, I'm not going down with this ship!!
0
0
ElgorKad
New Contributor
•
12 Messages
Amen
Chris (or other moderator), will you kindly update this thread with status?
Thanks
0
0
texokwoodcarver
New Contributor
•
19 Messages
Ok again to night my latacncy shot up to 696 home and 612 world'
Here is the trace:
Tracing route to 12.129.209.68 over a maximum of 30 hops
1 8 ms 14 ms 8 ms 10.33.192.1
2 9 ms 7 ms 8 ms COX-68-12-9-76-static.coxinet.net [68.12.9.76]
3 20 ms 19 ms 9 ms COX-68-12-19-152-static.coxinet.net [68.12.19.152]
4 * 22 ms * 68.1.5.135
5 19 ms 19 ms 21 ms xe-11-0-0.edge4.Dallas3.Level3.net [4.71.122.21]
6 21 ms 24 ms 22 ms ae-1-60.edge10.Dallas1.Level3.net [4.69.145.18]
7 38 ms 39 ms 35 ms ATT [4.68.62.230]
8 69 ms 65 ms 63 ms cr2.dlstx.ip.att.net [12.123.16.110]
9 69 ms 67 ms 71 ms cr2.la2ca.ip.att.net [12.122.28.178]
10 70 ms 69 ms 69 ms gar29.la2ca.ip.att.net [12.122.129.241]
11 66 ms 62 ms 69 ms 12-122-254-238.attens.net [12.122.254.238]
12 64 ms 74 ms 66 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
13 * * * Request timed out.
14 * * * Request timed out.
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.
Everything starts with hop/node 4 as usual. I have talked until I am blue in the face with cox. Nobody can tell me who is owns that node, Cox, Levele3 or somebody else. All that I can find out is from the IP it is located somewhere in Kansas.
All that I know is Cox hands it off to it, and it in turn hands it off to level 3. Cox claims that they are just required to hand it off to them, even they don't know who it is.
0
0
texokwoodcarver
New Contributor
•
19 Messages
Well, Well, Well, One of the Blizzard mod was able to help me find out who the week link belongs to. COX
http://images.ip2location.com/26088967.png
0
0
ElgorKad
New Contributor
•
12 Messages
Cox Moderator - may we please have an update?
1 day to go!
0
0
Aroberts64
New Contributor
•
10 Messages
@Woodcarver: For future instances like that, I would suggest you try using something like this webpage.
http://aruljohn.com/track.pl
Thats what I use and its worked very well for me in the past.
As for the latency issue, its still here, hasnt gotten any better, and unless its fixed soon I will be leaving the Cox Network. This isnt just about video game traffic. I also have issues with other things that follow that route. I despise paying what I pay a month for internet and 2 games and having both games unplayable. The only way I can make them playable is to subscribe to a third party program that may well get me banned or at least a temporary suspension because of the suspicious nature of the third party software.
0
0
texokwoodcarver
New Contributor
•
19 Messages
Actually Since posting that I started my own thread on these forums, since my problem is a little different the the others in this tread. You might look at it you will find it very interesting. For one I found out the mystery node 4 actually belongs to Cox. When using pingplotter, that had a packet loss between 30 to 50%
Also I have been doing a lot more research on my routing using http://cqcounter.com/whois/ to better locate each node.
Node 1 is my house in Tulsa OK. From there it hops to node 2 - Cox in Bethany, OK, and on to node 3 - Cox in Oklahoma City. From there it goes almost a 1,000 miles southeast to node 3 Cox's problem child in Macon, GA.
From there it double back almost 900 miles West to nodes 5&6 belonging to level3 in Dallas Tx. Who in turn sends it north to ATT's backbone in Kansas, where it goes on to Blizzard.
It appears it is going over 2,000 miles in a circle!
If I don't get any good answers from Cox in the AM, I am filing a FCC complaint here is a link to the FCC's website and complaint form https://esupport.fcc.gov/ccmsforms/form2000.action?form_type=2000B
Also if you are goinf to use a tunneling service, you might want to look into WTFast. Unlike most of the others; it uses you own IP address to ID when connecting to WoW. So you are less likely to trigger any lockout/suspensions.
0
0
Aroberts64
New Contributor
•
10 Messages
Hmmm, does this WTFast have a trial period? Im still very much against paying to use a service just to make other services I already pay for work.
0
0
texokwoodcarver
New Contributor
•
19 Messages
I think they my I haven't really tried it yet. I just know about from Following markeedragon on Youtube for the last year http://www.youtube.com/results?search_query=wtfast&oq=wtfast&gs_l=youtube.12..0l10.12426.21677.0.31416.6.6.0.0.0.0.126.727.0j6.6.0...0.0...1ac.1.JbSVwCzhr08
0
0
Bluepoet
New Contributor
•
4 Messages
Still lagging, too...whether it's at 5am or at 6PM, although worse in prime time.
Cox people: Do you have any idea how many of your customers play WoW? I would suggest you fix this problem--sooner rather than later...
The word is getting out...
0
0
warhippy
New Contributor
•
15 Messages
I made a new macro to be used in a raid, when my lag causes the raid to wipe. Basically, it posts this in the raid warnings:" Please excuse my seeming incompetence, I'm a COX internet customer. PITY me, don't BOOT me :((". Time for some in-game free advertising for Cox, since they choose to ignore their customers.
0
0
warhippy
New Contributor
•
15 Messages
My last important macro was very efficient in stopping people crying in trade chat about the server, it went like this, "If you're unhappy with this server, but you're too stupid or cheap to transfer to another server, please feel free to whine in Trade Chat. There will be crying towels available at both exits". I actually got whispers asking where the exits were located.
0
0
sin66
New Contributor
•
1 Message
Im in AZ as well(Avondale). Ive been having the same problem since 1-15-13, before that i always had 60ms ping. Now my latency goes up to 4000ms ping fluctuations but averages 350ms. Wow's representative said to ask for my connection to be routed away from cogentco servers because they are my problem.
Tracing route to 63.240.161.189 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms www.asusnetwork.net [192.168.1.1]
2 40 ms 11 ms 42 ms 10.129.240.1
3 11 ms 9 ms 32 ms 172.21.0.240
4 14 ms 11 ms 14 ms 70.169.75.84
5 47 ms 53 ms 20 ms chnddsrj01-ae2.0.rd.ph.cox.net [70.169.76.229]
6 * * * Request timed out.
7 35 ms 23 ms 37 ms te0-0-0-21.ccr22.lax05.atlas.cogentco.com [38.104.84.13]
8 48 ms 31 ms 59 ms te0-2-0-2.ccr22.lax01.atlas.cogentco.com [154.54.29.201]
9 102 ms 69 ms 59 ms te0-2-0-5.mpd22.iah01.atlas.cogentco.com [154.54.0.250]
10 98 ms 66 ms 65 ms te0-4-0-1.ccr22.dfw01.atlas.cogentco.com [154.54.24.2]
11 77 ms 74 ms 75 ms te0-2-0-1.ccr22.mci01.atlas.cogentco.com [154.54.46.217]
12 99 ms 88 ms 94 ms te0-7-0-33.ccr22.ord01.atlas.cogentco.com [154.54.30.102]
13 96 ms 101 ms 86 ms te0-6-0-0.ccr22.ord03.atlas.cogentco.com [154.54.29.22]
14 110 ms * 101 ms 192.205.37.173
15 * * 116 ms cr2.cgcil.ip.att.net [12.122.84.94]
16 114 ms 152 ms 141 ms gar2.clboh.ip.att.net [12.122.133.197]
17 118 ms 182 ms 134 ms 12.122.251.22
18 121 ms 142 ms 111 ms 63.240.130.214
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.
0
0
littlesparkz
New Contributor
•
1 Message
This issue is also affecting my work and losing me money. I stream live media as part of my job and the packet loss is causing my stream to be degraded significantly. So it's not just gaming people being affected by this issue.
0
0