Latency Issues - Phoenix, Arizona - Cox Cable

Technical Support
1 2 3 7 Next
I've been having this issue for a long time now. I've had traceroutes/pathpings posted multiple times. First I get the "Contact your ISP" response, the my ISP gives me the "Your connection looks exceptional, continue contacting your game's tech support" response.

I've ran literally dozens of internet connection tests. My ms hovers around 20-25 ms with 35 upload/60 download.

I have Cox Cable and play on Tichondrius. I have 7 level 90's and have played WoW for almost 10 years with thousands of dollars invested. My guild has dozens of people experiencing this same issue.

We ONLY have latency issues in INSTACED PVP. ie: Arena, Rated Battlegrounds, Random Battlegrounds.

Unfortunately, the issues occurs in the ONLY place high latency is the most detrimental.

Once again, I live in the northern part of Phoenix, Arizona. I have Cox Cable as my internet-service-provider. I only experience this lag in INSTANCED gameplay. My home/world MS are usually at 23-25 ms. They spike to upwards of 250-500 when I join an ARENA/RBG/Random BG.
I also live in Phoenix and use Cox. Since 3 days ago and today being the worst and making the game unplayable my latency is hitting over 1300 world. I had to stop playing completely as I couldn't do a thing whether in an instance or just talking to a vendor. This is frustrating and unacceptable. Everything was just fine 4 days ago.
Join the club, I've been having troubles for about a month now, Cox says it's Blizz's fault, Blizz says it's ISP's fault. Here is my link to the Cox thread.

http://forums.cox.com/forum_home/internet_forum/f/5/p/3159/13053.aspx#13053
It's happening again right now. I literally press disengage in an RBG, and 2 seconds later it happens after I run from 2 yards and it throws me the opposite way.

Such BS.
It's not Cox Communication's fault for this because I get great latency on other servers, but on Shu'halo it's 5x-10x that number. 20-30 on Windrunner, 150-300 on Shu'halo with spikes north of 1000 a regular occurrence in the evening. In the mornings with low traffic its 50-60 and it all started when they started doing their dreadfully managed, piss poor server merges. I talked to a GM and the arrogant twerp told me 200-300 latency isn't unplayable and I should deal with it. Actually its quite unplayable on a rogue and I shouldn't have to put up with it. I wish BLIZZ would own up to their problems and then FIX THEM.
It's not Cox Communication's fault for this because I get great latency on other servers, but on Shu'halo it's 5x-10x that number. 20-30 on Windrunner, 150-300 on Shu'halo with spikes north of 1000 a regular occurrence in the evening. In the mornings with low traffic its 50-60 and it all started when they started doing their dreadfully managed, piss poor server merges. I talked to a GM and the arrogant twerp told me 200-300 latency isn't unplayable and I should deal with it. Actually its quite unplayable on a rogue and I shouldn't have to put up with it. I wish BLIZZ would own up to their problems and then FIX THEM.


Yep, I had a GM try to convince me that it's "OKAY" that my MS more than quadruples when I'm in instanced pvp, or it's later in the day. Yet, I will literally press and ability and the keybind will light up and not actually happen until 3-4 seconds later. I'm pretty sure they mask the MS and it's actually even worse than it is.

There is NO excuse for this.

World of Warcraft, including EVERY SINGLE EXPANSION and Mists of Pandaria cost $15.

And on top of that, we pay what the game including every damn xpack costs EVERY MONTH just so we can play it and get this kind of service?

I can't deal with this horse crap anymore
Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 6 ms 7 ms 10.134.0.1
3 7 ms 8 ms 20 ms 172.21.1.70
4 12 ms 12 ms 9 ms 72.215.229.22
5 8 ms 8 ms 9 ms mcdlcorc03-te-0-3-0-0.ph.ph.cox.net [70.169.72.205]
6 29 ms 34 ms 28 ms langbprj02-ae2.rd.la.cox.net [68.1.1.19]
7 23 ms 29 ms 21 ms 216.156.65.25.ptr.us.xo.net [216.156.65.25]
8 24 ms 21 ms 21 ms 207.88.15.94.ptr.us.xo.net [207.88.15.94]
9 29 ms 27 ms 31 ms 205.158.79.242.ptr.us.xo.net [205.158.79.242]
10 31 ms 25 ms 29 ms cr1.la2ca.ip.att.net [12.122.128.102]
11 37 ms 35 ms 38 ms gar20.la2ca.ip.att.net [12.122.128.181]
12 25 ms 25 ms 25 ms 12-122-254-238.attens.net [12.122.254.238]
13 28 ms 29 ms 30 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
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.
Guys, it's all of our ISPs, it's not Blizzards backbones that are the problems (ATT/Cognetco). Children come from storks dropping babies at doorsteps, too.
Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 7 ms 8 ms 10.134.0.1
3 7 ms 13 ms 7 ms 172.21.1.70
4 10 ms 10 ms 13 ms 72.215.229.22
5 9 ms 9 ms 12 ms mcdlcorc03-te-0-3-0-0.ph.ph.cox.net [70.169.72.205]
6 * * * Request timed out.
7 22 ms 48 ms 23 ms 216.156.65.25.ptr.us.xo.net [216.156.65.25]
8 25 ms 22 ms 21 ms 207.88.15.94.ptr.us.xo.net [207.88.15.94]
9 26 ms 27 ms 28 ms 205.158.79.242.ptr.us.xo.net [205.158.79.242]
10 29 ms 28 ms 30 ms cr1.la2ca.ip.att.net [12.122.128.102]
11 62 ms 59 ms 55 ms gar20.la2ca.ip.att.net [12.122.128.181]
12 28 ms 30 ms 25 ms 12-122-254-238.attens.net [12.122.254.238]
13 25 ms 25 ms 34 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
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.
Still waiting for some "Technical Support".'

Oh, all you were gonna do is ask me to post a traceroute then disappear so you are completely avoiding me. Go figure
Bump again.
Crickets
I have Cox in San Diego and for the last month or two the game has been pretty much unplayable for me to the point where everytime i go to raid i have to disconnect my cox connection and plug in my iphone to raid off my verizon 3G connection. It's the only way the game becomes playable.
Bump.
Tracing route to 63.240.161.189 over a maximum of 30 hops

1 10 ms 7 ms 7 ms 10.112.96.1
2 12 ms 10 ms 9 ms 172.21.0.46
3 12 ms 11 ms 15 ms 70.169.73.64
4 11 ms 8 ms 17 ms 70.169.75.157
5 39 ms 23 ms 24 ms 68.1.5.139
6 22 ms 23 ms 22 ms te0-3-0-20.ccr23.lax05.atlas.cogentco.com [38.104.84.69]
7 22 ms 24 ms 25 ms be2179.ccr22.lax01.atlas.cogentco.com [154.54.41.81]
8 56 ms 62 ms 66 ms be2066.ccr22.iah01.atlas.cogentco.com [154.54.7.53]
9 70 ms 61 ms 64 ms be2147.ccr22.dfw01.atlas.cogentco.com [154.54.27.18]
10 77 ms 73 ms 76 ms be2012.ccr21.mci01.atlas.cogentco.com [154.54.2.113]
11 87 ms 86 ms 84 ms be2156.ccr21.ord01.atlas.cogentco.com [154.54.6.86]
12 98 ms 87 ms 84 ms be2003.ccr21.ord03.atlas.cogentco.com [154.54.29.22]
13 124 ms 129 ms 124 ms att.ord03.atlas.cogentco.com [154.54.12.86]
14 111 ms 116 ms 121 ms cr1.cgcil.ip.att.net [12.122.81.18]
15 133 ms 207 ms 185 ms gar18.cgcil.ip.att.net [12.122.99.21]
16 117 ms 116 ms 119 ms 12.122.251.18
17 112 ms 117 ms 119 ms 63.240.130.206
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.
Been noticing connection issues with cox during game but also from time to time out of game too. In my case modem keeps resetting and have discovered that the Docsis 3.0 modems have a tendency to drop when the system looks for a better signal. From what I've seen on the Cox forums it may be a case of having to have Cox lock it into a single signal. Keeping a log of the resets so I can give Cox the info a frequency of resets . I recommend others keep a log too
Same issues here, started over a week ago and hasn't gone away. Have had multiple techs come to my house before I figured out it was this. They fixed some random issues anyway but I really want to move to Century Link, even if it's slower, it has to be more stable...

So after doing some research this happened a long time ago and somehow it got fixed? Does anyone recall what someone did for this problem to go away? I just started WoW a couple of weeks ago and would hate to stop now =/
Yup I am from the Phoenix Area but 40 minutes away I am having the same issues with lag the past few days.... Great... When will this ever be resolved? lol
Let's get some pathpings so they have more to go on other than "I'm lagging!"

Bump.


Don't do that. They hate when you do that.
Bump

Join the Conversation

Return to Forum