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
New Contributor II
•
Warcraft disconnect issues the minute I subscribed to COX in Henderson, NV
I have been a Cox customer for about 2 weeks (since moving to Henderson). Since then, World of Warcraft is unplayable for me. I cannot go 15 consecutive minutes without a disconnect or a lag spike of more than 5-15 seconds. Is anyone else having problems with WoW?
It's not my computer--WoW still works perfectly fine with no issues when I drive back to Glendale, CA and use my brother's ISP, nor does it have disconnect or lag issues using my Mom's old DSL connection. It's only here in Henderson, using Cox. For example (and this is not an extreme case, but about the average experience for me): This evening, Tuesday August 13, from 9:00 pm-9:40 pm, I disconnected 4 times from WoW. I also had 4 bouts of lag/latency that had me running in place onscreen for more than 10 seconds each time. And it doesn't matter what time of day I try to play. Morning, mid-day, evenings, weekdays or weekends, it's all the same.
I am a "Preferred" bundle customer, which is up to 25mbps download speeds. Should I pay extra and upgrade to 50 mbps? I wouldn't mind doing so, but the product I'm paying for now is so horrendous, I don't trust that paying extra would solve anything. Especially since my old DSL connection never had any problems like the ones I've experienced since the cable guy installed my internet and router and I plugged in two weeks ago. Everything else I do online, I can do from my smartphone--so if I can't play online, then there really is no reason to keep paying for Cox internet.
Trikein
Contributor III
•
First, its never a good idea to throw money at a problem. Especially since online gaming doesn't actually take as much bandwidth like downloading a game off Steam or streaming a HD movie off Netflix.
As for what is causing your "lag", its very hard to say. I would suggest this site, where it shows how to do a tracert to the WoW server you happen to be using. Try to do one when your having the problem, and one when your not having a problem. This may show us where the lag is occurring. There can be other things outside your specific connection to Cox that effects your quality of connection to WoW, but it gets pretty complex so I will only go into that depending on your traces.
0
0
Squidman
New Contributor II
•
Thanks for the advice. I ran the trace. I'll do it a few times when the lag/dc issues get bad (like between the hours of 7:00 am-10:00 pm in my experience so far). Thanks again!
0
0
Squidman
New Contributor II
•
Here is the trace route (if I did it correctly). The instructions from Blizzard were unclear--I installed the program, but didn't bother trying to play WoW again--what would be the point except more disconnects, lag, and frustration. Should I have logged back on to WoW for the trace to work? Anyway, here it is. I also e-mailed it to coxhelp@cox.com.
Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]
over a maximum of 30 hops:
1 10 ms 11 ms 11 ms 10.74.128.1
2 12 ms 19 ms 10 ms 24-234-16-137.ptp.lvcm.net [24.234.16.137]
3 13 ms 18 ms 11 ms 24-234-6-189.ptp.lvcm.net [24.234.6.189]
4 10 ms 9 ms 14 ms 24-234-6-254.ptp.lvcm.net [24.234.6.254]
5 35 ms 40 ms 37 ms langbprj01-ae1.rd.la.cox.net [68.1.1.13]
6 24 ms 24 ms 23 ms xe-8-0-0.edge2.LosAngeles9.Level3.net [4.53.230.1]
7 26 ms 27 ms 26 ms vlan70.csw2.LosAngeles1.Level3.net [4.69.144.126]
8 30 ms 29 ms 25 ms ae-73-73.ebr3.LosAngeles1.Level3.net [4.69.137.37]
9 31 ms 32 ms 33 ms ae-7-7.ebr2.Tustin1.Level3.net [4.69.153.226]
10 31 ms 33 ms 36 ms ae-208-3608.bar21.Tustin1.Level3.net [4.69.158.126]
11 34 ms 41 ms 34 ms 192.205.37.145
12 47 ms 47 ms 47 ms cr1.la2ca.ip.att.net [12.122.128.102]
13 49 ms 50 ms 49 ms cr2.phmaz.ip.att.net [12.122.31.190]
14 39 ms 38 ms 37 ms 12.122.108.105
15 46 ms 46 ms 43 ms 12-122-254-218.attens.net [12.122.254.218]
16 45 ms 44 ms 46 ms mdf002c7613r0001-gig-10-1.phx1.attens.net [63.241.130.198]
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.
0
0
Trikein
Contributor III
•
How were they unclear? What part did you not understand? Also, what did you mean by "program". A trace is done through your computers command prompt. Its nothing you have to download. Do you mean you uninstalled WoW? The whole point of the trace is to do it when things are "good" and do it again when things are "bad" and when you compare the two, it shows you where the "bad" is happening. If your not playing the game when doing the trace, how do we know if the problem was occurring?
0
0
Accepted Solution
Squidman
New Contributor II
•
Here is the link for the Blizzard trace route directions:
https://us.battle.net/support/en/article/performing-a-traceroute
There is nowhere on that page where it is printed to run the "program" (the trace route) during a good time/bad time/once/more than once. I followed the only explicit instructions given. If I was supposed to run it again at specific times and under specific conditions, then THAT should have been listed in the instructions, hence making it more clear. If I was supposed to assume that I should run the trace more than once or at specific times, then I suppose I would already have the knowledge or experience to not need forum help to begin with.
0
0