High Latency / Lag Spikes. Comcast East Coast

90 Human Death Knight
SnP
15660
Have you tried uninstalling and re-installing the router software and starting from scratch?

Even with powering down, and resetting the router, I would get constant disconnects / lag.
There was a problem with my download/upload speed.
The router should be as fast as the modem.

Re-installing my router software fixed my problem. Good luck.
Edited by Babana on 5/8/2013 6:43 AM PDT
Reply Quote
90 Dwarf Paladin
15400
My download/upload speed is fine. I don't get disconnected either, nor do I have constant high latency. Just lag spikes which freezes all action on my screen for a few seconds then speed up to get caught up.
Reply Quote
90 Dwarf Paladin
15400
Bump.
Reply Quote
Support Forum Agent
Do you have more recent traces? Were you able to change up some factors, like testing on a different Internet connection?
________________________________________________
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
Reply Quote
90 Human Warrior
12565
I have one...you should totally check out my thread. Since no one else is.
Reply Quote
90 Dwarf Paladin
15400
Do you have more recent traces? Were you able to change up some factors, like testing on a different Internet connection?

I haven't tested on a different internet connection, to do that I'd have to take my almost 50 pound machine including all the accessories across 3 counties to a friend's house and hope I get results.
I'll do some more traces tonight, do you want any pathping test results too?
Edited by Fiddlesnarf on 5/9/2013 5:18 PM PDT
Reply Quote
90 Dwarf Paladin
15400
I did a lot of traces tonight, I'll post some in a little bit.
Unfortunitely a trace was not running when I experienced my biggest lag spike of the night, game "froze" for 6-7 seconds and my Home latency shot up to nearly 800ms, World latency stayed normal.

Ok here they are, I cut out after they timed out.

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 35 ms 30 ms 29 ms 107.4.182.1
3 14 ms 10 ms 12 ms te-8-2-ur01.culpeper.va.richmond.comcast.net [68.85.70.149]
4 12 ms 11 ms 12 ms te-1-1-ur01.ruckersville.va.richmond.comcast.net [68.86.172.205]
5 91 ms 12 ms 12 ms xe-5-1-3-0-ar02.charlvilleco.va.richmond.comcast.net [68.86.173.233]
6 16 ms 17 ms 14 ms pos-1-2-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.91.53]
7 15 ms 19 ms 15 ms pos-0-3-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.86.142]
8 19 ms 19 ms 19 ms 192.205.37.41
9 48 ms 47 ms 47 ms cr2.wswdc.ip.att.net [12.122.134.186]
10 44 ms 49 ms 47 ms cr1.cgcil.ip.att.net [12.122.18.21]
11 128 ms 144 ms 100 ms gar2.clboh.ip.att.net [12.122.133.197]
12 60 ms 48 ms 47 ms 12.122.251.22
13 50 ms 47 ms 45 ms 63.240.130.214
14 * * * Request timed out.


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 35 ms 39 ms 29 ms 107.4.182.1
3 14 ms 11 ms 11 ms te-8-2-ur01.culpeper.va.richmond.comcast.net [68.85.70.149]
4 13 ms 11 ms 14 ms te-1-1-ur01.ruckersville.va.richmond.comcast.net [68.86.172.205]
5 13 ms 11 ms 10 ms xe-5-1-3-0-ar02.charlvilleco.va.richmond.comcast.net [68.86.173.233]
6 16 ms 18 ms 31 ms pos-1-2-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.91.53]
7 318 ms 117 ms 125 ms pos-0-3-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.86.142]
8 16 ms 15 ms 17 ms 192.205.37.41
9 48 ms 48 ms 47 ms cr2.wswdc.ip.att.net [12.122.134.186]
10 50 ms 43 ms 43 ms cr1.cgcil.ip.att.net [12.122.18.21]
11 47 ms 46 ms 46 ms gar2.clboh.ip.att.net [12.122.133.197]
12 47 ms 64 ms * 12.122.251.50
13 46 ms 48 ms 47 ms 63.240.130.214
14 * * * Request timed out.
Edited by Velnrak on 5/13/2013 8:40 AM PDT
Reply Quote
90 Dwarf Paladin
15400
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 24 ms 29 ms 34 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 12 ms 13 ms 26 ms te-1-1-ur01.ruckersville.va.richmond.comcast.net [68.86.172.205]
5 206 ms 237 ms 19 ms xe-5-1-3-0-ar02.charlvilleco.va.richmond.comcast.net [68.86.173.233]
6 17 ms 16 ms 17 ms pos-1-2-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.91.53]
7 16 ms 16 ms 14 ms pos-0-3-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.86.142]
8 33 ms 19 ms 19 ms 192.205.37.41
9 47 ms 47 ms 48 ms cr2.wswdc.ip.att.net [12.122.134.186]
10 43 ms 44 ms 43 ms cr1.cgcil.ip.att.net [12.122.18.21]
11 43 ms 43 ms 44 ms gar2.clboh.ip.att.net [12.122.133.197]
12 45 ms 48 ms 47 ms 12.122.251.50
13 47 ms 49 ms 45 ms 63.240.130.214
14 * * * Request timed out.


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 38 ms 29 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 11 ms 13 ms 11 ms te-1-1-ur01.ruckersville.va.richmond.comcast.net [68.86.172.205]
5 11 ms 12 ms 13 ms xe-5-1-3-0-ar02.charlvilleco.va.richmond.comcast.net [68.86.173.233]
6 171 ms 16 ms 19 ms pos-1-2-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.91.53]
7 16 ms 16 ms 15 ms pos-0-3-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.86.142]
8 16 ms 19 ms 20 ms 192.205.37.41
9 47 ms 47 ms 47 ms cr2.wswdc.ip.att.net [12.122.134.186]
10 49 ms 45 ms 46 ms cr1.cgcil.ip.att.net [12.122.18.21]
11 42 ms 43 ms 176 ms gar2.clboh.ip.att.net [12.122.133.197]
12 45 ms 47 ms 48 ms 12.122.251.22
13 47 ms 60 ms 46 ms 63.240.130.214
14 * * * Request timed out.


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 43 ms 29 ms 29 ms 107.4.182.1
3 11 ms 11 ms 11 ms te-8-2-ur01.culpeper.va.richmond.comcast.net [68.85.70.149]
4 13 ms 12 ms 12 ms te-1-1-ur01.ruckersville.va.richmond.comcast.net [68.86.172.205]
5 87 ms 12 ms 12 ms xe-5-1-3-0-ar02.charlvilleco.va.richmond.comcast.net [68.86.173.233]
6 19 ms 15 ms 20 ms pos-1-3-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.91.57]
7 15 ms 16 ms 16 ms pos-0-3-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.86.142]
8 35 ms 18 ms 20 ms 192.205.37.41
9 51 ms 49 ms 47 ms cr2.wswdc.ip.att.net [12.122.134.186]
10 139 ms 290 ms 135 ms cr1.cgcil.ip.att.net [12.122.18.21]
11 54 ms 44 ms 57 ms gar2.clboh.ip.att.net [12.122.133.197]
12 52 ms 50 ms 48 ms 12.122.251.50
13 47 ms 50 ms 48 ms 63.240.130.214
14 * * * Request timed out.


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 26 ms 30 ms 27 ms 107.4.182.1
3 159 ms 187 ms 240 ms te-8-2-ur01.culpeper.va.richmond.comcast.net [68.85.70.149]
4 10 ms 11 ms 17 ms te-1-1-ur01.ruckersville.va.richmond.comcast.net [68.86.172.205]
5 12 ms 11 ms 11 ms xe-5-1-3-0-ar02.charlvilleco.va.richmond.comcast.net [68.86.173.233]
6 17 ms 18 ms 35 ms pos-1-3-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.91.57]
7 14 ms 15 ms 28 ms pos-0-3-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.86.142]
8 18 ms 19 ms 19 ms 192.205.37.41
9 45 ms 50 ms 44 ms cr2.wswdc.ip.att.net [12.122.134.186]
10 54 ms 63 ms 47 ms cr1.cgcil.ip.att.net [12.122.18.21]
11 43 ms 43 ms 42 ms gar2.clboh.ip.att.net [12.122.133.197]
12 49 ms 45 ms 54 ms 12.122.251.22
13 56 ms 47 ms 45 ms 63.240.130.214
14 * * * Request timed out.
Edited by Velnrak on 5/13/2013 8:40 AM PDT
Reply Quote
90 Blood Elf Paladin
6975
Without getting too specific for IRL security, where do you live currently? I live in a city using cable lines for my internet. Generally, your "share" a line, which is why I would love to switch to fiber. Basically the main line gets a set amount of bandwidth, which as you go down the line gets lower and lower. The first house does not get all of the bandwidth (it has a limit), but if this sounds like a similar setup to yours, your neighbors may be leaving their systems running overnight with updates. I occasionally slow down my neighbors by updating and downloading multiple things simultaneously, on multiple VM's.

Basically, you may be too far down the line.
Reply Quote
90 Dwarf Paladin
15400
Without getting too specific for IRL security, where do you live currently?
Central Virginia, I have neighbors, but they aren't a stones throw away.
Reply Quote
90 Dwarf Paladin
15400
Bump.
Reply Quote
90 Worgen Hunter
8350
Having almost identical problems as Fiddlesnarf, starting on 5/5/13 I have been having horrible lag spikes in the evenings. I thought it was only in raids but it is happening in the open world too, primarily when I enter combat.

Chat will continue to function, I can still run around, but everything freezes in place for 5-10 secs, sometimes worse. This is followed by a huge spike in latency.

I talked to my ISP and they were unable to identify any problems. I've tried all the tricks I know, reinstall WoW, reset everything, virus scans, no addons, ect. nothing seems to work.

I have seen a lot of posts about this same type of issue but it seems to be a west coast thing, i live in North Carolina right on the border of VA.

Any help would be greatly appreciated, I have had to sit out on our heroic progression due to these lag spikes.

Here are some tracing from tonight:

1 <1 ms <1 ms <1 ms EVERHARTNETWORK [192.168.1.1]
2 <1 ms <1 ms <1 ms 69-77-158-1.skybest.com [69.77.158.1]
3 <1 ms <1 ms <1 ms XMR-1-BLDW-1-MLX.SKYBEST.COM [69.77.128.141]
4 50 ms 51 ms 55 ms 165.166.133.9
5 11 ms 11 ms 11 ms cha-b1-link.telia.net [213.248.68.1]
6 17 ms 17 ms 17 ms atl-bb1-link.telia.net [213.155.134.202]
7 32 ms 32 ms 32 ms 192.205.33.41
8 59 ms 87 ms 64 ms cr2.attga.ip.att.net [12.123.22.154]
9 59 ms 62 ms 71 ms cr1.nsvtn.ip.att.net [12.122.28.106]
10 71 ms 66 ms 66 ms cr2.nsvtn.ip.att.net [12.122.28.70]
11 54 ms 58 ms 55 ms cr1.cl2oh.ip.att.net [12.122.28.74]
12 66 ms 71 ms 72 ms cr1.cgcil.ip.att.net [12.122.2.205]
13 77 ms * 72 ms gar2.clboh.ip.att.net [12.122.133.197]
14 69 ms 65 ms 64 ms 12.122.251.50
15 82 ms 85 ms 85 ms 63.240.130.214

1 1 ms 4 ms <1 ms EVERHARTNETWORK [192.168.1.1]
2 <1 ms 3 ms <1 ms 69-77-158-1.skybest.com [69.77.158.1]
3 2 ms 3 ms 8 ms XMR-1-BLDW-1-MLX.SKYBEST.COM [69.77.128.141]
4 28 ms 22 ms 23 ms 165.166.133.9
5 11 ms 12 ms 11 ms cha-b1-link.telia.net [213.248.68.1]
6 26 ms 20 ms 19 ms atl-bb1-link.telia.net [213.155.134.202]
7 17 ms 17 ms 15 ms 192.205.33.41
8 44 ms 44 ms 42 ms cr2.attga.ip.att.net [12.123.22.154]
9 42 ms 45 ms 42 ms cr1.nsvtn.ip.att.net [12.122.28.106]
10 41 ms 40 ms 45 ms cr2.nsvtn.ip.att.net [12.122.28.70]
11 59 ms 48 ms 50 ms cr1.cl2oh.ip.att.net [12.122.28.74]
12 59 ms 59 ms 60 ms cr1.cgcil.ip.att.net [12.122.2.205]
13 47 ms 45 ms 44 ms gar2.clboh.ip.att.net [12.122.133.197]
14 42 ms 44 ms 44 ms 12.122.251.22
15 53 ms 52 ms 52 ms 63.240.130.214

1 <1 ms 7 ms <1 ms EVERHARTNETWORK [192.168.1.1]
2 9 ms <1 ms <1 ms 69-77-158-1.skybest.com [69.77.158.1]
3 2 ms <1 ms <1 ms XMR-1-BLDW-1-MLX.SKYBEST.COM [69.77.128.141]
4 29 ms 28 ms 26 ms 165.166.133.9
5 11 ms 11 ms 11 ms cha-b1-link.telia.net [213.248.68.1]
6 18 ms 33 ms 26 ms atl-bb1-link.telia.net [213.155.134.202]
7 19 ms 21 ms 21 ms 192.205.33.41
8 51 ms 51 ms 46 ms cr2.attga.ip.att.net [12.123.22.154]
9 44 ms 45 ms 46 ms cr1.nsvtn.ip.att.net [12.122.28.106]
10 43 ms 45 ms 49 ms cr2.nsvtn.ip.att.net [12.122.28.70]
11 53 ms 50 ms * cr1.cl2oh.ip.att.net [12.122.28.74]
12 * 34 ms 36 ms cr1.cgcil.ip.att.net [12.122.2.205]
13 35 ms 39 ms 37 ms gar2.clboh.ip.att.net [12.122.133.197]
14 38 ms 36 ms 37 ms 12.122.251.50
15 41 ms 39 ms 40 ms 63.240.130.214

1 <1 ms <1 ms <1 ms EVERHARTNETWORK [192.168.1.1]
2 2 ms <1 ms <1 ms 69-77-158-1.skybest.com [69.77.158.1]
3 1 ms <1 ms <1 ms XMR-1-BLDW-1-MLX.SKYBEST.COM [69.77.128.141]
4 31 ms 37 ms 27 ms 165.166.133.9
5 11 ms 11 ms 11 ms cha-b1-link.telia.net [213.248.68.1]
6 23 ms 19 ms 19 ms atl-bb1-link.telia.net [213.155.134.202]
7 23 ms 21 ms 19 ms 192.205.33.41
8 47 ms 47 ms 50 ms cr2.attga.ip.att.net [12.123.22.154]
9 50 ms 51 ms 49 ms cr1.nsvtn.ip.att.net [12.122.28.106]
10 54 ms 55 ms 51 ms cr2.nsvtn.ip.att.net [12.122.28.70]
11 52 ms 50 ms 50 ms cr1.cl2oh.ip.att.net [12.122.28.74]
12 51 ms 47 ms 49 ms cr1.cgcil.ip.att.net [12.122.2.205]
13 60 ms 56 ms 53 ms gar2.clboh.ip.att.net [12.122.133.197]
14 196 ms 51 ms 51 ms 12.122.251.50
15 55 ms 50 ms 50 ms 63.240.130.214
Reply Quote
90 Blood Elf Paladin
6975
Then this is certainly not your issue. Hopefully a blue helps you out.
Reply Quote
90 Dwarf Paladin
15400
Bump!
Reply Quote
90 Dwarf Paladin
15400
Bump. Sucks having a Blizz rep ask for traces then doesn't check back.
Edited by Fiddlesnarf on 5/13/2013 6:41 PM PDT
Reply Quote
90 Dwarf Paladin
15400
Ridiculous this is STILL an issue.
I have dug out my old router and am using it now, by raid time tonight I'll know if its my router that is the problem.
Edited by Fiddlesnarf on 5/14/2013 1:22 AM PDT
Reply Quote
35 Troll Druid
6190
05/02/2013 07:22 AMPosted by Annasoul
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.


Indeed. I'm an Aussie too, and 300-350 ms is my *good* latency. A lag spike is when world latency gets over 1000 ms, and recently I've been getting a lot higher than that (peaking at 7000 ms this evening). Of course, when that happens the game is barely playable.
Reply Quote
90 Dwarf Paladin
15400
Changed routers, still lagging.
Reply Quote
90 Undead Warlock
15150
Still getting this bad high lag ms for me also. Blizzard has been unhelpful in taking care of this. Last try for me is getting a Comcast tech guy out here this week *for the 2nd time*. If it does not work I feel I will be shutting WOW down tell Blizzard fixes this problem. Very shocked to see this many people still having a problem and Blizzard is not helping players with it.
Reply Quote
90 Dwarf Paladin
15400
I changed the title to better reflect the issue. Beachbum, are you on the East Coast?
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]