High Latency Cox Comm & South LA area

90 Blood Elf Priest
8890
Any help would be appreciated. Has been happening for the last week or so. This is from Malganis (NY server).

Normally am around 80-100ms tops now I am spiking into 1500+ every so often. It isn't all the time but definitely enough to hinder game play during raid time and random spurts throughout the day
_______________________________________
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Ruwon>tracert 199.107.6.164

Tracing route to 199.107.6.164 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 8 ms 8 ms 10.127.184.1
3 10 ms 7 ms 8 ms 68.11.13.45
4 8 ms 9 ms 7 ms 68.11.14.65
5 8 ms 9 ms 7 ms 68.11.14.82
6 21 ms 20 ms 31 ms 68.1.2.121
7 19 ms 23 ms 19 ms xe-11-2-0.edge4.Dallas3.Level3.net [4.59.32.1]
8 20 ms 21 ms 19 ms 4.69.145.82
9 39 ms 41 ms 39 ms ATT [4.68.62.230]
10 91 ms 92 ms 88 ms cr1.dlstx.ip.att.net [12.123.16.86]
11 86 ms 88 ms 87 ms cr2.nsvtn.ip.att.net [12.122.1.242]
12 79 ms 80 ms 83 ms cr1.cl2oh.ip.att.net [12.122.28.74]
13 74 ms 75 ms 76 ms cr2.cl2oh.ip.att.net [12.122.2.126]
14 82 ms 83 ms 82 ms cr2.phlpa.ip.att.net [12.122.2.210]
15 107 ms 77 ms 77 ms gar1.pitpa.ip.att.net [12.122.107.85]
16 205 ms 80 ms 80 ms 12-122-254-242.attens.net [12.122.254.242]
17 89 ms 89 ms 98 ms mdf001c7613r0004-gig-12-1.nyc3.attens.net [63.24
0.65.14]
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.
Edited by Zurri on 9/18/2012 6:57 PM PDT
Reply Quote
90 Draenei Paladin
13325
Just thought I would add I'm having the same issues with Cox HSI from Oklahoma. The latency always seems to spike at the connection from Level 3 in Dallas to AT&T or within the AT&T network. It seems to happen most often in the evenings. This is for Laughing Skull (Chicago datacenter).

C:\Users\Username>tracert 206.18.99.14

Tracing route to 206.18.99.14 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms HOME [192.168.2.1]
2 8 ms 12 ms 10 ms 10.33.64.1
3 12 ms 10 ms 9 ms COX-68-12-9-170-static.coxinet.net [68.12.9.170]

4 10 ms 23 ms 10 ms COX-68-12-19-68-static.coxinet.net [68.12.19.68]

5 19 ms 16 ms 18 ms 68.1.2.121
6 14 ms 13 ms 12 ms xe-10-1-0.edge4.Dallas3.Level3.net [4.59.32.85]

7 27 ms 24 ms 21 ms ae-3-80.edge10.Dallas1.Level3.net [4.69.145.146]

8 * 54 ms 54 ms ATT [4.68.62.230]
9 * * 76 ms cr2.dlstx.ip.att.net [12.123.16.110]
10 78 ms 86 ms 74 ms cr1.sl9mo.ip.att.net [12.122.3.222]
11 79 ms 82 ms 86 ms cr2.sl9mo.ip.att.net [12.122.2.218]
12 78 ms 81 ms 81 ms cr2.cgcil.ip.att.net [12.122.2.21]
13 * 73 ms 78 ms gar3.cgcil.ip.att.net [12.122.132.213]
14 * 75 ms 69 ms 12.122.251.22
15 92 ms * 78 ms 63.240.130.210
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.

Thanks for any assistance you might be able to provide.
Reply Quote
90 Draenei Paladin
13325
Still having issues on Cox HSI. Latest PingPlotter results are below. Once it hits the AT&T network there's about 10-40% packet loss. Would like to hear any kind of updates. Thanks!

Target Name: N/A
IP: 206.18.99.14
Date/Time: 9/19/2012 8:55:03 PM to 9/19/2012 8:57:19 PM

1 1 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms 0 ms HOME [192.168.2.1]
2 5 ms 5 ms 8 ms 5 ms 5 ms 4 ms 4 ms 8 ms 6 ms 7 ms [10.33.64.1]
3 9 ms 5 ms 8 ms 12 ms 5 ms 5 ms 4 ms 8 ms 9 ms 7 ms COX-68-12-9-170-static.coxinet.net [68.12.9.170]
4 11 ms 7 ms 14 ms 7 ms 7 ms 6 ms 14 ms 9 ms 6 ms 8 ms COX-68-12-19-68-static.coxinet.net [68.12.19.68]
5 48 ms 35 ms 23 ms 21 ms 23 ms 20 ms 19 ms 37 ms 16 ms 15 ms [68.1.2.121]
6 20 ms 18 ms 56 ms 50 ms 51 ms 48 ms 47 ms 54 ms 47 ms 69 ms xe-7-1-0.edge4.Dallas3.Level3.net [4.59.32.93]
7 23 ms 18 ms 51 ms 54 ms 50 ms 47 ms 48 ms 47 ms * 51 ms [4.69.145.82]
8 * 67 ms 98 ms * 95 ms 98 ms 92 ms * * 95 ms ATT [4.68.62.230]
9 * * * 82 ms 92 ms 93 ms * 87 ms 91 ms 89 ms cr2.dlstx.ip.att.net [12.123.16.110]
10 98 ms * 90 ms 89 ms 99 ms * 89 ms 91 ms * 98 ms cr1.sl9mo.ip.att.net [12.122.3.222]
11 96 ms 100 ms 85 ms 88 ms * 101 ms 94 ms 91 ms 98 ms 96 ms cr2.sl9mo.ip.att.net [12.122.2.218]
12 91 ms * 79 ms 84 ms 94 ms 96 ms 88 ms 88 ms 93 ms 92 ms cr2.cgcil.ip.att.net [12.122.2.21]
13 100 ms * 95 ms 116 ms 88 ms * * * 93 ms * gar3.cgcil.ip.att.net [12.122.132.213]
14 * * 83 ms N/A N/A N/A N/A N/A 92 ms * [12.122.251.50]
15 94 ms * 85 ms 89 ms * 103 ms 91 ms * 95 ms 155 ms [63.240.130.210]
16 * * * * * * * * * * [-]
17 * * * * * * * * * * [-]
18 * * * * * * * * * * [-]
19 * * * * * * * * * * [-]
20 * * * * * * * * * * [-]
21 * * * * * * * * * * [-]
22 * * * * * * * * * * [-]
23 * * * * * * * * * * [-]
24 * * * * * * * * * * [-]
25 * * * * * * * * * * [-]
26 * * * * * * * * * * [-]
27 * * * * * * * * * * [-]
28 * * * * * * * * * * [-]
29 * * * * * * * * * * [-]
30 * * * * * * * * * * [-]
31 * * * * * * * * * * [-]
32 * * * * * * * * * * [-]
33 * * * * * * * * * * [-]
34 * * * * * * * * * * [-]
35 * * * * * * * * * * [-]

Destination not reached in 35 hops
Edited by Kataani on 9/19/2012 6:59 PM PDT
Reply Quote
90 Orc Shaman
13480
Having the same issues. Before doing the tracer I disabled all add-ons, reset my router, checked for router updates and I still have major lag. The lag is ok in cities, but once I hit an instance server and start combat my latency in-game goes to about 3k. This also happens at night during the peak hours of play.

Cox Communications, Louisiana

C:\Users\User>tracert 199.107.24.244

Tracing route to 199.107.24.244 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 20 ms 9 ms 21 ms 10.127.152.1
3 11 ms 8 ms 11 ms 68.11.13.37
4 11 ms 8 ms 9 ms 68.11.14.65
5 20 ms 21 ms 10 ms 68.11.14.82
6 21 ms 30 ms 21 ms 68.1.2.121
7 21 ms 21 ms 20 ms xe-4-2-0.edge4.Dallas3.Level3.net [4.59.32.73]
8 21 ms 22 ms 21 ms ae-1-60.edge10.Dallas1.Level3.net [4.69.145.18]

9 62 ms 69 ms 60 ms ATT [4.68.62.230]
10 153 ms 149 ms 151 ms cr1.dlstx.ip.att.net [12.123.16.86]
11 172 ms 161 ms 168 ms cr2.nsvtn.ip.att.net [12.122.1.242]
12 156 ms 161 ms 141 ms cr1.cl2oh.ip.att.net [12.122.28.74]
13 144 ms 147 ms 155 ms cr2.cl2oh.ip.att.net [12.122.2.126]
14 161 ms 160 ms 159 ms cr2.phlpa.ip.att.net [12.122.2.210]
15 144 ms 135 ms 136 ms gar1.pitpa.ip.att.net [12.122.107.85]
16 149 ms 150 ms 166 ms 12-122-254-242.attens.net [12.122.254.242]
17 152 ms 153 ms 155 ms mdf001c7613r0003-gig-10-1.nyc3.attens.net [63.24
0.65.10]
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.
Edited by Zurotal on 9/19/2012 7:46 PM PDT
Reply Quote
90 Worgen Rogue
9885
What servers are we all playing on? I'm curious because other threads have shown issues with servers in the Northeast data centers, which my servers are hosted on. Mine always times out right when it hits, or attempts to hit, one specific server. Same one every day since last week. Hell, I can't even ping my server anymore. It seems like it's gotten even worse since then. If this isn't fixed by launch, people are going to be in for a rude awakening...
Reply Quote
85 Draenei Priest
9475
I'm also having World MS issues with Cox in Louisiana. Used to be 50-60 not that long ago, now it spikes to over 2k.

Edit: I'm on Emerald Dream. I don't know where the server is located, but the server time is CST. Of the people I've asked on the server, I seem to be the only one with this problem.
Edited by Syntech on 9/19/2012 8:36 PM PDT
Reply Quote
85 Orc Death Knight
13140
Like many of you guys, I'm having the same issue and also a Cox Comm. user from Las Vegas, NV.
Reply Quote
90 Night Elf Druid
5970
From Panama Having a super high latency as well
Reply Quote
89 Night Elf Druid
10610
Starting to have major Latency problems. I consistently get upwards of 400ms when normally I get 80-90 on my main server. The strange thing is that I get 25ms on a Pacific based server while my main server is Central/Eastern based. Just started happening a few hours ago. Its almost unplayable the latency is so bad.

I have Cox Comm located in Pheonix.
Reply Quote
85 Human Death Knight
8100
From Arizona and using Cox Comm having very high latency on Zuluhed, hope this gets fixed soon or I am not going to be playing with friends in MoP. :(
Edited by Dualîty on 9/19/2012 9:40 PM PDT
Reply Quote
90 Worgen Rogue
9885
09/19/2012 09:33 PMPosted by Nidaly
The strange thing is that I get 25ms on a Pacific based server while my main server is Central/Eastern based. Just started happening a few hours ago. Its almost unplayable the latency is so bad.


Exact same issue with me. My "other" server is located in Pacific, the usual no issues there. On my "main" server, located in Eastern, it's been titanic issues since 5.0 essentially. It started off a little higher than usual but gradually has gone up to being completely unplayable. It might taper off, going down around 100-200ms late around this hour but at peak play times, it's completely unplayable with latency in the high 1-2000 range.

I'm not sure what, if anything, Blizzard is doing about this but having (from what I've seen) a good amount of their paying customers UNABLE to play the game they pay for through no fault of their own.... I dunno, I don't see this ending too well, especially with a new expansion less than a week away.

We've provided all the traceroutes we can to them. The issue SHOWS it's on their end. It's the SAME server timing out every time I run a trace, which these days is multiple times a day. I really fail to understand why they seem to just... not acknowledge it.
Edited by Eccah on 9/19/2012 10:02 PM PDT
Reply Quote
90 Gnome Warlock
2990
Im just geting back i to the game after 8 months, my home latency is good 32ms-49ms. now my world ms it loads then freeze up and 5 min later it will free up then freeze again. so i did a trace well 5 traces.

what do i do? i cant play like this.

Tracing route to 206.18.98.184.tms-idc.com [206.18.98.184]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 23 ms 29 ms 28 ms c-76-123-48-1.hsd1.va.comcast.net [76.123.48.1]
3 12 ms 8 ms 12 ms te-1-4-ur01.warrenton.va.richmond.comcast.net [68.85.226.245]
4 33 ms 15 ms 12 ms xe-5-1-2-0-ar02.charlvilleco.va.richmond.comcast.net [68.86.173.13]
5 18 ms 21 ms 16 ms pos-1-2-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.91.53]
6 15 ms 15 ms 16 ms pos-0-5-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.87.14]
7 19 ms 20 ms 17 ms 192.205.37.41
8 46 ms 48 ms 45 ms cr2.wswdc.ip.att.net [12.122.134.186]
9 48 ms 50 ms 45 ms cr1.cgcil.ip.att.net [12.122.18.21]
10 111 ms 98 ms 45 ms gar2.clboh.ip.att.net [12.122.133.197]
11 45 ms 44 ms 44 ms 12.122.251.22
12 69 ms 48 ms 43 ms 63.240.130.214
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.
Reply Quote
85 Human Death Knight
8100
Im just geting back i to the game after 8 months, my home latency is good 32ms-49ms. now my world ms it loads then freeze up and 5 min later it will free up then freeze again. so i did a trace well 5 traces.

what do i do? i cant play like this.

Tracing route to 206.18.98.184.tms-idc.com [206.18.98.184]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 23 ms 29 ms 28 ms c-76-123-48-1.hsd1.va.comcast.net [76.123.48.1]
3 12 ms 8 ms 12 ms te-1-4-ur01.warrenton.va.richmond.comcast.net [68.85.226.245]
4 33 ms 15 ms 12 ms xe-5-1-2-0-ar02.charlvilleco.va.richmond.comcast.net [68.86.173.13]
5 18 ms 21 ms 16 ms pos-1-2-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.91.53]
6 15 ms 15 ms 16 ms pos-0-5-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.87.14]
7 19 ms 20 ms 17 ms 192.205.37.41
8 46 ms 48 ms 45 ms cr2.wswdc.ip.att.net [12.122.134.186]
9 48 ms 50 ms 45 ms cr1.cgcil.ip.att.net [12.122.18.21]
10 111 ms 98 ms 45 ms gar2.clboh.ip.att.net [12.122.133.197]
11 45 ms 44 ms 44 ms 12.122.251.22
12 69 ms 48 ms 43 ms 63.240.130.214
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.


We really can do nothing but wait for bliz to give us a update, i just hope this gets fixed before my guild starts raiding and doing rated bgs/arena or else i will have a problem on my hands.
Reply Quote
90 Worgen Rogue
9885
12 69 ms 48 ms 43 ms 63.240.130.214
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.


BINGO. That's the exact IP that I start getting timed out on.
Reply Quote
90 Night Elf Druid
13380
I'm still encountering this as well, even in the new Scenario. I was under the impression that this issue had been resolved in the last patch.
Reply Quote
85 Human Hunter
4290
New Orleans, Louisiana
I have Cox also and speedtest.net
I have 5ms, 40mb download, 30mb upload.
I get on WoW before 5.0.4 patch and i run
from 30-70ms, now i cant play as it randomly jumps
From 60ms-500-1k.. thank god i didn't buy mop
because I've called and posted on forums and there is
nothing they can do. I play xbox online cod,bf3,halo etc and have no lag
Or delay also i play guild wars with absolutely 0 lag, so blizz will not
bull!@#$ me anymore about my internet. This latency problem "Never"
happen to me until the 5.0.4 patch, and latency jumps on both my g.f and my pc
randomly about 20 minutes into playing.
Reply Quote
90 Draenei Paladin
13325
09/19/2012 11:11 PMPosted by Eccah
BINGO. That's the exact IP that I start getting timed out on.

That's the border router at Blizzard. You're supposed to time out on that one.
Reply Quote
90 Worgen Rogue
9885
Well I'm an idiot :\

Still doesn't explain the latency randomly jumping around.
Reply Quote
90 Blood Elf Paladin
10280
oh! new orleans people! i live in nola too, glad i found some info on this. although it seems like there really ISN'T any info. most i've been able to gather is it's something to do with at&t, and blizzard has been extremely silent on this one. no one has found a blue post anywhere? btw- i'm on duskwood, an EST server.
Edited by Kizi on 9/20/2012 6:31 PM PDT
Reply Quote
90 Night Elf Hunter
17945
I'm also in New Orleans with Cox. I can usually play during the day (latency usually around 65 to 68) but since the patch WoW is unplayable for several hours in the evenings. Usually home and world are both high latency, although sometimes it has been just one (sometimes just home or just world). If I get a green bar with latency around 120 for both, it soon goes either yellow or red with latency between 1500 to over 5000. I've tried all the fixes they've suggested but so far nothing has helped. I'm on Gnomeregon, which I think is a west coast server.
Reply Quote

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)
Submit Cancel

Reported!

[Close]