Welcome to the Cox Community
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
Messages
Selected Messages
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
New Contributor
•
2 Messages
Closed
http://forums.cox.com/forum_home/internet_forum/f/5/t/1146.aspx
Here is a link to a thread about an issue that occurred in January where many players were experiencing high latency on World of Warcraft servers mainly due to the Cogentco connection between Cox and AT&T. The issue disappeared awhile ago and now it is happening again where I am getting 100-300 MS on servers where I would usually be at around 20 MS. I'm not sure what was fixed last time in order to solve this problem but I would like some feedback on this issue.
I would say the issue started about 3-4 days ago and based on this forum post:
http://us.battle.net/wow/en/forum/topic/9793019207
many other Cox Digital Cable users in AZ are experiencing similar issues with high ping due to the Cogentco routing.
Discussions
•
Updated
6.2K
8
0
0
They don’t care
Discussions
1
0
Internet outage 24 hrs
Discussions
1
0
Outages
Discussions
2
Daily outages
Discussions
2
0
SSID & Password
Discussions
1
0
Internet outage 24 hrs
Discussions
1
0
Wifi 7
Discussions
1
0
Frequent Outages
Discussions
2
Outages
Discussions
2
ShaneB
New Contributor
•
same exact issues here, had the same problem a couple months ago and it stayed this way for at least 2 weeks, hopefully this gets fixed alot quicker this time because it is pretty annoying
0
0
ShaneB
New Contributor
•
seems like the latency gets worse and worse every day, my ping in blizzard games has gone up by a consistent 40 every day since saturday, please fix this
0
0
Starbuck
New Contributor
•
I've also been experiencing this, I've made a support ticket with Blizzard hoping they can some how help resolve this issue, although the problem lies with Cox and AT&T, the issue is especially frustrating given that i've recently forked over money to blizzard to transfer my characters from a Dallas server group, to an LA one, only for me to be routed right back to Dallas then to LA.
0
0
faust
New Contributor
•
I too have been noticing this issue for the past week or so. Hope this gets fixed soon.
0
0
Trikein
Contributor III
•
From the data in the thread mentioned, it looks like a peering issue. Last time Cognito fixed it, but took a week or two. It is outside Cox's network. Have you tried calling Cognito?
0
0
Torrey
New Contributor
•
I have the same issues, and I am getting really sick and tired of it. I am freezing up during combat in dungeons, scenerios, and LFRs. All of those are pretty much unplayable. I sent this to Cox email support and they didn't read what I wrote and just stated to power cycle the modem. Cox techs have been to my house twice, and I purchased a new modem and wireless network adapter. I have the same problem when I play wired, so it is not the router. I have this issue with a fresh install of WoW with no addons. PingPlotter shows packet loss over numerous hops along the route to the WoW server. As you can see below, there are also issues going to the google server. I have been having this terrible latency and packet loss since February 2013!
TRACERT TO WoW SERVER:
Tracing route to 12.129.209.68 over a maximum of 30 hops
1 1 ms <1 ms <1 ms READYSHARE [192.168.1.1]
2 9 ms 13 ms 9 ms 10.175.24.1
3 13 ms * * fed1sysc01-gex0918.sd.sd.cox.net [68.6.11.98]
4 * * * Request timed out.
5 11 ms 10 ms 12 ms fed1sysc01-gex0901.sd.sd.cox.net [68.6.8.100]
6 35 ms 30 ms 29 ms sanjbprj01-ae0.0.rd.sj.cox.net [68.1.5.184]
7 44 ms 40 ms 38 ms xe-7-0-2.edge1.SanJose3.Level3.net [4.53.208.201]
8 30 ms 32 ms 33 ms ae-1-60.edge2.SanJose1.Level3.net [4.69.152.15]
9 46 ms 43 ms 43 ms 192.205.32.209
10 56 ms 58 ms 58 ms cr1.sffca.ip.att.net [12.122.114.6]
11 58 ms 59 ms 62 ms cr1.la2ca.ip.att.net [12.122.3.122]
12 52 ms 54 ms 54 ms gar20.la2ca.ip.att.net [12.122.128.181]
13 * * * Request timed out.
14 53 ms 52 ms 52 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
15 * * * Request timed out.
TRACERT TO GOOGLE:
Tracing route to iad23s06-in-f8.1e100.net [74.125.228.40]
over a maximum of 30 hops:
1 1 ms 1 ms <1 ms READYSHARE [192.168.1.1]
2 9 ms 9 ms 10 ms 10.175.24.1
3 10 ms 17 ms 9 ms 68.6.11.96
4 * * * Request timed out.
5 10 ms 15 ms * fed1dsrj01-xe130.0.rd.sd.cox.net [68.6.8.0]
6 * 33 ms * 68.1.5.137
7 15 ms 17 ms 19 ms langbbrj01-ge050000804.r2.la.cox.net [68.105.30.181]
8 19 ms 23 ms 25 ms 64.233.174.238
9 14 ms 15 ms 69 ms 64.233.174.188
10 71 ms 70 ms 69 ms 72.14.239.80
11 78 ms 76 ms 79 ms 216.239.48.41
12 86 ms 82 ms 81 ms 72.14.235.11
13 82 ms 82 ms 84 ms 72.14.236.153
14 82 ms 82 ms 83 ms 72.14.238.175
15 82 ms 82 ms 86 ms iad23s06-in-f8.1e100.net [74.125.228.40]
RESULTS TO GOOGLE:
Target Name: www.google.com
Date/Time: 8/25/2013 9:12:19 PM to 8/25/2013 9:37:04 PM
Hop Sent Err PL% Min Max Avg Host Name /
1 100 0 0.0 0 4 0 READYSHARE [192.168.1.1]
2 100 6 6.0 7 26 9 [10.175.24.1]
3 100 5 5.0 8 30 10 [68.6.11.96]
4 100 100 100.0 0 0 0 [-]
5 100 8 8.0 9 61 14 fed1dsrj01-xe130.0.rd.sd.cox.net [68.6.8.0]
6 100 35 35.0 13 73 20 [68.1.5.137]
7 100 24 24.0 13 50 16 langbbrj01-ge050000804.r2.la.cox.net [68.105.30.181]
8 100 5 5.0 14 117 22 [64.233.174.238]
9 100 3 3.0 14 44 17 [209.85.250.245]
10 100 3 3.0 13 35 17 lax02s19-in-f17.1e100.net [74.125.224.113]
0
0
cdeeinaz
New Contributor
•
I'm noticing the issue...have been for several months.
0
0
faust
New Contributor
•
I noticed it got better for a day or two last week or so but then it went back to the way it was and today was in particular brutal. I got frequent lag spikes up into the 300'ish ms range. Usually when I'm lagging it hovers at about 150'ish ms.
0
0