High Latency / Lag Spikes. Comcast East Coast

Technical Support
Prev 1 2 3 7 Next
F9K1001v3
Under the router setup I see the Wireless > Channel and SSID options page, and see where I could change wireless modes, but do not see a "B" option.

What other wireless modes have you tried?
________________________________________________
Monday - Friday, 8 am - 5 pm PST

'Look at flesh. See only potential. Strands, sequences, twisting, separating, joining. See how it could be better. Eat flesh, splinter bone. Inside me, can touch it. Weave it. Spin it... Make it great.'

Rate me! https://www.surveymonkey.com/s/Velnrak
05/02/2013 07:22 AMPosted by Annasoul
Well now my latency seems to fluctuate much more now. Normally it would stay between 50-55ms, now its bouncing between 55-88ms. No noticeable lag spikes yet though, doing a LFR, will see if it lags in there.


Oh jeez I have never ever ever had a latency lower than 230 MS playing wow, ever. Anything consistently under 350ms is a good connection for me, tbh I am amazed you could even notice the difference between 55ms amd 85ms. We really must be in the dark ages in australia.

I hope you get it all sorted tho :-)
I don't notice latency until i reaches around 150 or so, I was just stating that 80+ latency is not usual for me and therefore proves there is a problem with my connection.

@Velnrak
" 6. The router may be set to auto for the channel selection. As surrounding networks are added, the initial channel may become crowded. Use the drop-down list and select a new channel for your router.

Note: Channels 1, 6, or 11 are the best selections."

As the site has recommended I have tried channels 11 and then 6. Channel 1 was what it was on by default.

Also I should add, there is a Wireless Mode option in the router settings, but the modes it has listed are
1) Off
2) 802.11g only
3) 802.11n only
4) 802.11n & 802.11g & 802.11b

I have no idea what these are.
2) 802.11g only
3) 802.11n only
4) 802.11n & 802.11g & 802.11b

I have no idea what these are.

These are different speeds, and I would try each one, in turn.
________________________________________________
Monday - Friday, 8 am - 5 pm PST

'Look at flesh. See only potential. Strands, sequences, twisting, separating, joining. See how it could be better. Eat flesh, splinter bone. Inside me, can touch it. Weave it. Spin it... Make it great.'

Rate me! https://www.surveymonkey.com/s/Velnrak
2) 802.11g only
3) 802.11n only
4) 802.11n & 802.11g & 802.11b

I have no idea what these are.

http://en.wikipedia.org/wiki/IEEE_802.11" class="bml-link-url2">These are different speeds</a>, and I would try each one, in turn.
________________________________________________
Monday - Friday, 8 am - 5 pm PST

'Look at flesh. See only potential. Strands, sequences, twisting, separating, joining. See how it could be better. Eat flesh, splinter bone. Inside me, can touch it. Weave it. Spin it... Make it great.'

Rate me! <a href="https://www.surveymonkey.com/s/Velnrak

Ok, I changed it to the 3rd option, we'll see how it work in raid tonight.
Nope, still lag spikes. Definitely not exclusive to raids, happens everywhere. Odd thing is, my ingame latency meter doesn't seem to spike very much when I get the lag spikes, it still reads normal latency.

This is getting tiring, router/modem resets do nothing, Comcast is less than useless, says there is no issue on their end. I've tried every configuration there is in my router settings. What else can I do??
I took another trace tonight, during it I experienced 2 small lag spikes, froze for no more than 2 seconds.

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 63.240.161.189
2 37 ms 27 ms 30 ms 107.4.182.1
3 11 ms 12 ms 11 ms te-8-2-ur01.culpeper.va.richmond.comcast.net [68.85.70.149]
4 13 ms 13 ms 13 ms xe-5-1-3-0-ar02.staplesmllrd.va.richmond.comcast.net [68.86.173.109]
5 27 ms 26 ms 26 ms pos-0-9-0-0-cr01.charlotte.nc.ibone.comcast.net [68.86.95.65]
6 * 29 ms 31 ms pos-3-8-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.89.21]
7 48 ms 28 ms 30 ms pos-0-9-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.88.178]
8 30 ms 31 ms 31 ms as7018-pe01.56marietta.ga.ibone.comcast.net [75.149.228.86]
9 241 ms 51 ms 54 ms cr2.attga.ip.att.net [12.122.117.98]
10 148 ms 55 ms 51 ms cr1.nsvtn.ip.att.net [12.122.28.106]
11 56 ms 51 ms 55 ms cr1.sl9mo.ip.att.net [12.122.28.62]
12 51 ms 51 ms 51 ms cr2.sl9mo.ip.att.net [12.122.2.218]
13 54 ms 52 ms 67 ms cr2.cgcil.ip.att.net [12.122.2.21]
14 120 ms 68 ms 51 ms gar3.cgcil.ip.att.net [12.122.132.213]
15 53 ms 53 ms 52 ms 12.122.251.50
16 52 ms 53 ms 50 ms 63.240.130.214
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.
Tracing route to 63.240.161.189 over a maximum of 30 hops

0 Colossus.Belkin [192.168.2.3]
1 63.240.161.189
2 107.4.182.1
3 te-8-2-ur01.culpeper.va.richmond.comcast.net [68.85.70.149]
4 xe-5-1-3-0-ar02.staplesmllrd.va.richmond.comcast.net [68.86.173.109]
5 pos-0-9-0-0-cr01.charlotte.nc.ibone.comcast.net [68.86.95.65]
6 pos-3-8-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.89.21]
7 pos-0-9-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.88.178]
8 as7018-pe01.56marietta.ga.ibone.comcast.net [75.149.228.86]
9 cr1.attga.ip.att.net [12.122.141.182]
10 cr2.wswdc.ip.att.net [12.122.1.174]
11 cr1.cgcil.ip.att.net [12.122.18.21]
12 gar2.clboh.ip.att.net [12.122.133.197]
13 12.122.251.22
14 63.240.130.214
15 * * *
Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Colossus.Belkin [192.168.2.3]
0/ 100 = 0% |
1 --- 100/ 100 =100% 100/ 100 =100% 63.240.161.189
0/ 100 = 0% |
2 15ms 1/ 100 = 1% 1/ 100 = 1% 107.4.182.1
0/ 100 = 0% |
3 61ms 0/ 100 = 0% 0/ 100 = 0% te-8-2-ur01.culpeper.va.richmond.comcast.net [68.85.70.149]
0/ 100 = 0% |
4 53ms 0/ 100 = 0% 0/ 100 = 0% xe-5-1-3-0-ar02.staplesmllrd.va.richmond.comcast.net [68.86.173.109]
0/ 100 = 0% |
5 61ms 1/ 100 = 1% 1/ 100 = 1% pos-0-9-0-0-cr01.charlotte.nc.ibone.comcast.net [68.86.95.65]
0/ 100 = 0% |
6 66ms 0/ 100 = 0% 0/ 100 = 0% pos-3-8-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.89.21]
0/ 100 = 0% |
7 57ms 1/ 100 = 1% 1/ 100 = 1% pos-0-9-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.88.178]
0/ 100 = 0% |
8 64ms 0/ 100 = 0% 0/ 100 = 0% as7018-pe01.56marietta.ga.ibone.comcast.net [75.149.228.86]
100/ 100 =100% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr1.attga.ip.att.net [12.122.141.182]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr2.wswdc.ip.att.net [12.122.1.174]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr1.cgcil.ip.att.net [12.122.18.21]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% gar2.clboh.ip.att.net [12.122.133.197]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.22
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.214

Trace complete.
Bump please.
These are the slight trouble spot to your last two traces:
6 * 29 ms 31 ms pos-3-8-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.89.21]

9 241 ms 51 ms 54 ms cr2.attga.ip.att.net [12.122.117.98]


2 15ms 1/ 100 = 1% 1/ 100 = 1% 107.4.182.1

5 61ms 1/ 100 = 1% 1/ 100 = 1% pos-0-9-0-0-cr01.charlotte.nc.ibone.comcast.net [68.86.95.65]

7 57ms 1/ 100 = 1% 1/ 100 = 1% pos-0-9-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.88.178]

There doesn't seem to be a pattern here, and these are even 2 different connection routes.

Do you know of anyone else in your area that is lagging in WoW? Do any of your guildmates or friends play in your area?

It may be worth it to have one of them bring their computer over to test playing on your network. Or it may be worth to move your computer over to where you can connect with an ethernet cable, and test playing, and see if there's a difference.
________________________________________________
Monday - Friday, 8 am - 5 pm PST

'Look at flesh. See only potential. Strands, sequences, twisting, separating, joining. See how it could be better. Eat flesh, splinter bone. Inside me, can touch it. Weave it. Spin it... Make it great.'

Rate me! https://www.surveymonkey.com/s/Velnrak
I am having the exact same issues since Saturday 26th. I can play fine for a few hours but as soon as I attempt LFR I am disconnected within five minutes and my latency is ruined for the rest of the night no matter what I try to do after that.

No other internet issues, speed tests are fine and I am the only one using the router when this happens. I have done a test with an ethernet, checked the up and downstream signals and made sure my router is using an uncluttered channel.
I play from the UK and 120-130 is pretty normal for me.


Tracing route to 63.240.161.189 over a maximum of 30 hops

1 10 ms 11 ms 11 ms cpc1-broo7-2-0-gw.14-2.cable.virginmedia.com [82.25.172.1]
2 10 ms 12 ms 10 ms renf-core-2b-ae4-2890.network.virginmedia.net [62.252.70.61]
3 14 ms 15 ms 15 ms leed-bb-1c-ae2-0.network.virginmedia.net [62.253.174.41]
4 21 ms 19 ms 18 ms 213.152.245.53
5 20 ms 43 ms 35 ms 64.125.24.121.available.above.net [64.125.24.121]
6 94 ms 95 ms 103 ms xe-4-3-0.cr2.dca2.us.above.net [64.125.24.41]
7 94 ms 119 ms 122 ms xe-7-2-0.cr1.dca2.us.above.net [64.125.26.41]
8 93 ms 91 ms 96 ms xe-1-0-1.er1.iad10.us.above.net [64.125.26.238]
9 96 ms 95 ms 95 ms 192.205.36.125
10 125 ms 131 ms 131 ms cr2.wswdc.ip.att.net [12.122.81.250]
11 121 ms 125 ms 120 ms cr1.cgcil.ip.att.net [12.122.18.21]
12 120 ms 214 ms 127 ms gar2.clboh.ip.att.net [12.122.133.197]
13 134 ms 122 ms 123 ms 12.122.251.50
14 161 ms 123 ms 120 ms 63.240.130.214
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
These are the slight trouble spot to your last two traces:
6 * 29 ms 31 ms pos-3-8-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.89.21]

9 241 ms 51 ms 54 ms cr2.attga.ip.att.net [12.122.117.98]


2 15ms 1/ 100 = 1% 1/ 100 = 1% 107.4.182.1

5 61ms 1/ 100 = 1% 1/ 100 = 1% pos-0-9-0-0-cr01.charlotte.nc.ibone.comcast.net [68.86.95.65]

7 57ms 1/ 100 = 1% 1/ 100 = 1% pos-0-9-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.88.178]

There doesn't seem to be a pattern here, and these are even 2 different connection routes.

Do you know of anyone else in your area that is lagging in WoW? Do any of your guildmates or friends play in your area?

It may be worth it to have one of them bring their computer over to test playing on your network. Or it may be worth to move your computer over to where you can connect with an ethernet cable, and test playing, and see if there's a difference.
None of my guildies live near me.

05/03/2013 03:05 PMPosted by Velnrak
these are even 2 different connection routes.
What does this mean exactly?
Bump.
Bump.
Bump.
Problem here too, exactly as described...East Coast perhaps?
Problem here too, exactly as described...East Coast perhaps?

East Coast. Comcast?
I am East Coast Comcast also and I had all the problem since 5.2 came out. Game is unplayable right now
Same problems also on my side.

It seems there is an issue but isn't being acknowledged since they can't find a solution to it. They might contact you to answer any ticket you have raised, but answer with the same thing over and over, citing the same "solutions" w/c does not work. Or worst case scenario, contact you and will just say "You are AFK, so i will just send an e-mail wrt your concern", even though you are answering his inquiry real time. (i know it happened to me)

This was just like the MoP launch where there were lots and lots of latency/lag issues w/c were not being addressed and then "magically" went away.
Been sending all my info to a gm support ticket for days now and this is what I have found. Look like problem is beyond the power and know how of blue on the from. The gm I talked with had to send the info to a tech specialist. The problem could be coming from a backone server issue. Make sure you trace and send all info of what battle group you are on so they can check out the info

Wow Ip info
https://us.battle.net/support/en/article/running-a-pathping-test

Last night I was spiking 400-1400ms now I am back at 37 37 ms without fixing anything. This show me the problem is more on Blizzard's end. Hope this will be fixed before 5.3.

Join the Conversation

Return to Forum