Whats crazy is that its intermittent. One boss pull is fine the next is dog poo.
I am having the same issues. Ever since the last patch drop it is much worse than before. Any amount of spell tossing and multiple characters or npcs on the screen and I freeze up and disconnect. It’s getting so the game is not playable outside of wandering around on my own.
I have xfinity, which I do believe is affiliated with Cox cable. Can you do anything with them to smooth this out?
Cox here. Same thing happening. Sitting out of raid. (Cox has been utter garbage the past couple months in general)
Optimum online here, game has been 1k-3k all night long.
Same thing happening here. Do fine until pull and then spike up to 1500 MS or more. My guild-mates say they can see my corpse sliding around the floor after I die.
collecting data? need any more?
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| Destination network unreachable. - 1 | 870 | 864 | 0 | 0 | 10 | 0 |
| Destination network unreachable. - 5 | 755 | 720 | 6 | 12 | 194 | 63 |
| Destination network unreachable. - 5 | 759 | 725 | 7 | 17 | 207 | 14 |
| ae3—0.cor02.sttl.wafrontiernetnet - 5 | 755 | 721 | 7 | 10 | 77 | 9 |
| ae1—0.cbr01.sttl.wafrontiernetnet - 5 | 759 | 726 | 7 | 12 | 198 | 15 |
| eqix-se2.blizzardentertainmentcom - 5 | 755 | 721 | 7 | 11 | 197 | 13 |
| ae1-br01-eqse2.as57976net - 5 | 759 | 726 | 37 | 43 | 239 | 41 |
| xe-0-0-0-1-br01-eqsv5.as57976net - 5 | 759 | 726 | 37 | 43 | 229 | 39 |
| xe-0-0-1-1-br02-eqla1.as57976net - 5 | 755 | 721 | 37 | 45 | 227 | 46 |
| Destination network unreachable - 5 | 759 | 725 | 36 | 47 | 356 | 75 |
| Destination network unreachable - 6 | 766 | 724 | 37 | 48 | 1501 | 38 |
| et-0-0-31-pe01-swlv10.as57976net - 5 | 759 | 726 | 36 | 40 | 227 | 41 |
| las-swlv10-ia-bons-01.as57976net - 5 | 759 | 726 | 36 | 40 | 228 | 44 |
| Destination network unreachable. - 5 | 755 | 720 | 36 | 39 | 225 | 40 |
| No response from host - 100 | 179 | 0 | 0 | 0 | 0 | 0 |
| Destination network unreachable. - 100 | 179 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 179 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 179 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 179 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 179 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 179 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 179 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 179 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 179 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 179 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 179 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 179 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 179 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 179 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 179 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
So pretty much this, this ISP hates me and my only other option in my area is CenturyLink. For Gigabit Internet.
1 Like
Happening right now. I had to leave an instance cause the tank complained. I was not the only one affected. Warlock from Arizona having issues, me from Southern California.
I got Cox Communications here. Was seeing 1.3k World latency, where my net was looking just fine on my other PC. (I play multiple games).
Seems to only be an issue in WoW, after I joined Timewalking Stonecore, every minute, nothing moved for 6+ seconds. Cant satisfy the Tank with non-responsive spells like that. Instance chat worked fine tho.
I’ll do one of those number posting things in a little bit
Having the same issue. Only seems to happen in raid after the boss gets pulled. In San Diego with Cox.
Cox user in Rhode Island and I’m getting 2k+ latency at the moment.
To be more precise on my own location, I am also in San Diego with Cox Communications. I will need more time between RL and interent searching to figure out how to do the traceroute thing, or whatever it’s called.
Oof guess im not playing any blizz games tonight 
Dear Blizzard, I would really like to be able to play the game. Nothing like pulling a boss only then be frozen in place for 4 and a half mins until you relog just to see stuff move. Thank you in advance for not caring.
Also had this issue a few weeks ago, and am now getting them again. Same snag on the Win program with the way cox is interacting with blizzard servers. This time its less severe, not 10k world ms. but still going from 70 to 1300-2400 randomly and disconnecting.
Finally got around to getting the tracert thing…
I am in the middle of Tweeting at CoxHelp right now, to see if they know about the issue, and with all that this representative has said, he says “we are not aware of any known issues with our service causing packet loss or intermittent service to any server/game at this time.”
C:\WINDOWS\system32>tracert 137.221.105.2
Tracing route to 137.221.105.2 over a maximum of 30 hops
1 1 ms <1 ms <1 ms Linksys08630 (Removed Personal Data)
2 7 ms 8 ms 7 ms 10.142.0.1
3 8 ms 11 ms 8 ms 68.6.14.134
4 8 ms 8 ms 12 ms 100.120.108.14
5 13 ms 12 ms 12 ms 68.1.1.61
6 13 ms 16 ms 14 ms 68.105.30.130
7 20 ms 25 ms 28 ms ae1-br01-eqla1.as57976.net [137.221.68.33]
8 19 ms 18 ms 23 ms et-0-0-2-br01-swlv10.as57976.net [137.221.65.69]
9 17 ms 17 ms 17 ms et-0-0-31-pe01-swlv10.as57976.net [137.221.83.67]
10 18 ms 19 ms 17 ms las-swlv10-ia-bons-02.as57976.net [137.221.66.19]
11 21 ms 17 ms 16 ms 137.221.105.2
Trace complete.I am having the same as well
tracert 72.213.217.25
Tracing route to “ip72-213-217-25.pn. at .cox .net[72.213.217.25]”
over a maximum of 30 hops:1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms 10.155.0.1
3 9 ms 8 ms 8 ms 68.6.9.236
4 9 ms 9 ms 9 ms 100.120.108.18
5 55 ms 54 ms 58 ms “pnschdrj01 -ae4.0.rd.pn.cox.net [68.1.4.156]”
6 56 ms 56 ms 57 ms “ip68-1-11-85. at. at .cox.net [68.1.11.85]”
7 57 ms 57 ms 57 ms “ip68-1-11-85. at. at .cox.net [68.1.11.85]”
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
This is Pumbaz, for whatever reason, this forum thinks “Pumbaz” is a “new user” and wont let me post anymore replies…
I suggest you tweet @coxhelp … I dont seem to have enough to show that there is an issue right now.
I am a bit frustrated, and he wont look at this thread.
All of my Tweets with them have been good experiences. Just only so much they can do.
Traceroutes won’t tell you much. You need to run a MTR as it is basically an extended trace that keeps running and tracks ping spikes and packetloss.
h ttps://us.battle.net/support/en/article/27780
Any update today Blizzard? There is not much we as customers can do since it is a direct peering problem between COX and you at their handoffs to you at Equinix datacenters.
I’m experiencing immense lag spikes as well, reporting in from KS user of COX
1 Like
can confirm