tl;dr: Lag in WoW. Never had this before or in any other game. Tried a bunch of crap and it isn't working. Packets are lagging in traceroute to WoW server. Need suggestions.
I recently started playing WoW again about 1-2 months ago. I've been playing on and off now with the same ISP since closed beta and I've NEVER had a problem with lag. The last time I played was when TBC came out - I had the same router and same modem with no latency problems.
Now I'm sitting here with always 250ms up to ~600 (rare) just while questing. Occasionally it will lock up for 5-8 seconds and in dungeons the ping is much higher, usually around 400-500 constant and will increase to 1000+ and lag out. I've read a ton of similar threads on the WoW forums and can't find the problem.
I've tried the following with no success:
-tcpklatency(sp?) registry entry (posted on forums)
-latest motherboard ethernet drivers
-latest router firmware
-all WoW ports have always been opened (and opened in firewall)
-changing from static IP to DHCP
-Removing the router and connecting straight to modem
-Disabling ALL addons
Here's my traceroute to my server (The Forgotten Coast) - IP 72.5.213.59
Tracing route to 72.5.213.59 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 8 ms 10 ms c-69-251-72-1.hsd1.md.comcast.net [69.251.72.1]
3 6 ms 5 ms 9 ms ge-1-22-ur01.churchville.md.bad.comcast.net [68.87.132.249]
4 7 ms 7 ms 6 ms te-9-1-ur01.aberdeen.md.bad.comcast.net [68.87.128.121]
5 10 ms 6 ms 6 ms te-8-1-ur02.aberdeen.md.bad.comcast.net [68.85.209.146]
6 6 ms 14 ms 7 ms te-0-13-0-4-ar03.whitemarsh.md.bad.comcast.net [68.87.128.130]
7 12 ms 11 ms 11 ms pos-0-10-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.90.17]
8 12 ms 25 ms 13 ms te2-2.mpd01.jfk05.atlas.cogentco.com [154.54.11.209]
9 12 ms 12 ms 11 ms te2-4.ccr01.jfk02.atlas.cogentco.com [154.54.6.49]
10 21 ms 17 ms 17 ms te9-8.mpd01.bos01.atlas.cogentco.com [154.54.25.242]
11 43 ms 44 ms 45 ms te2-2.ccr01.ord01.atlas.cogentco.com [154.54.6.154]
12 57 ms 55 ms 54 ms te4-2.mpd01.mci01.atlas.cogentco.com [154.54.6.158]
13 66 ms 68 ms 67 ms te4-4.mpd01.den01.atlas.cogentco.com [154.54.24.81]
14 93 ms 93 ms 92 ms te4-2.ccr01.slc01.atlas.cogentco.com [154.54.0.42]
15 99 ms 93 ms 92 ms te4-2.ccr01.smf01.atlas.cogentco.com [154.54.1.101]
16 105 ms 106 ms 106 ms te4-1.ccr01.sea01.atlas.cogentco.com [154.54.27.25]
17 107 ms 108 ms 106 ms te4-4.ccr01.sea02.atlas.cogentco.com [154.54.3.146]
18 101 ms 102 ms 99 ms 38.104.126.70
19 100 ms 103 ms 101 ms border9.t8-1-bbnet2.sef.pnap.net [63.251.160.83]
20 * * * Request timed out.
I thought maybe it was my ISP or because the servers in the Seattle datacenter so I tried traceroutes to multiple servers in my closest datacenter (Boston) all with the same results - high ping in the last few hops.
I even had my girlfriend traceroute to my server from her house (lives 20miles away, Verizon FIOS ISP)
Tracing route to 72.5.213.59 over a maximum of 30 hops
1 1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 10 ms 6 ms 7 ms L100.VFTTP-07.BLTMMD.verizon-gni.net [71.179.4.1]
3 6 ms 8 ms 8 ms P3-3.LCR-02.BLTMMD.verizon-gni.net [130.81.39.154]
4 22 ms 13 ms 12 ms P14-2.LCR-02.NWRKNJ.verizon-gni.net [130.81.28.86]
5 13 ms 12 ms 11 ms 0.so-6-0-0.XL2.PHL6.ALTER.NET [152.63.3.81]
6 95 ms 94 ms 95 ms 0.so-2-0-0.XT2.SEA1.ALTER.NET [152.63.104.229]
7 93 ms 92 ms 92 ms POS7-0.GW7.SEA1.ALTER.NET [152.63.105.181]
8 91 ms 92 ms 92 ms internap-gw.customer.alter.net [208.214.103.138]
9 95 ms 94 ms 94 ms border9.t7-1-bbnet1.sef.pnap.net [63.251.160.19]
10 * * * Request timed out.
I'm not sure whether this is my problem or Blizzards. A ton of people are having issues right now. If 2 people with different ISPs have similar traceroutes, chances are this is not my problem? I can't think or any other solutions and I'm going to have to cancel my account because of how unplayable it is.
I recently started playing WoW again about 1-2 months ago. I've been playing on and off now with the same ISP since closed beta and I've NEVER had a problem with lag. The last time I played was when TBC came out - I had the same router and same modem with no latency problems.
Now I'm sitting here with always 250ms up to ~600 (rare) just while questing. Occasionally it will lock up for 5-8 seconds and in dungeons the ping is much higher, usually around 400-500 constant and will increase to 1000+ and lag out. I've read a ton of similar threads on the WoW forums and can't find the problem.
I've tried the following with no success:
-tcpklatency(sp?) registry entry (posted on forums)
-latest motherboard ethernet drivers
-latest router firmware
-all WoW ports have always been opened (and opened in firewall)
-changing from static IP to DHCP
-Removing the router and connecting straight to modem
-Disabling ALL addons
Here's my traceroute to my server (The Forgotten Coast) - IP 72.5.213.59
Tracing route to 72.5.213.59 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 8 ms 10 ms c-69-251-72-1.hsd1.md.comcast.net [69.251.72.1]
3 6 ms 5 ms 9 ms ge-1-22-ur01.churchville.md.bad.comcast.net [68.87.132.249]
4 7 ms 7 ms 6 ms te-9-1-ur01.aberdeen.md.bad.comcast.net [68.87.128.121]
5 10 ms 6 ms 6 ms te-8-1-ur02.aberdeen.md.bad.comcast.net [68.85.209.146]
6 6 ms 14 ms 7 ms te-0-13-0-4-ar03.whitemarsh.md.bad.comcast.net [68.87.128.130]
7 12 ms 11 ms 11 ms pos-0-10-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.90.17]
8 12 ms 25 ms 13 ms te2-2.mpd01.jfk05.atlas.cogentco.com [154.54.11.209]
9 12 ms 12 ms 11 ms te2-4.ccr01.jfk02.atlas.cogentco.com [154.54.6.49]
10 21 ms 17 ms 17 ms te9-8.mpd01.bos01.atlas.cogentco.com [154.54.25.242]
11 43 ms 44 ms 45 ms te2-2.ccr01.ord01.atlas.cogentco.com [154.54.6.154]
12 57 ms 55 ms 54 ms te4-2.mpd01.mci01.atlas.cogentco.com [154.54.6.158]
13 66 ms 68 ms 67 ms te4-4.mpd01.den01.atlas.cogentco.com [154.54.24.81]
14 93 ms 93 ms 92 ms te4-2.ccr01.slc01.atlas.cogentco.com [154.54.0.42]
15 99 ms 93 ms 92 ms te4-2.ccr01.smf01.atlas.cogentco.com [154.54.1.101]
16 105 ms 106 ms 106 ms te4-1.ccr01.sea01.atlas.cogentco.com [154.54.27.25]
17 107 ms 108 ms 106 ms te4-4.ccr01.sea02.atlas.cogentco.com [154.54.3.146]
18 101 ms 102 ms 99 ms 38.104.126.70
19 100 ms 103 ms 101 ms border9.t8-1-bbnet2.sef.pnap.net [63.251.160.83]
20 * * * Request timed out.
I thought maybe it was my ISP or because the servers in the Seattle datacenter so I tried traceroutes to multiple servers in my closest datacenter (Boston) all with the same results - high ping in the last few hops.
I even had my girlfriend traceroute to my server from her house (lives 20miles away, Verizon FIOS ISP)
Tracing route to 72.5.213.59 over a maximum of 30 hops
1 1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 10 ms 6 ms 7 ms L100.VFTTP-07.BLTMMD.verizon-gni.net [71.179.4.1]
3 6 ms 8 ms 8 ms P3-3.LCR-02.BLTMMD.verizon-gni.net [130.81.39.154]
4 22 ms 13 ms 12 ms P14-2.LCR-02.NWRKNJ.verizon-gni.net [130.81.28.86]
5 13 ms 12 ms 11 ms 0.so-6-0-0.XL2.PHL6.ALTER.NET [152.63.3.81]
6 95 ms 94 ms 95 ms 0.so-2-0-0.XT2.SEA1.ALTER.NET [152.63.104.229]
7 93 ms 92 ms 92 ms POS7-0.GW7.SEA1.ALTER.NET [152.63.105.181]
8 91 ms 92 ms 92 ms internap-gw.customer.alter.net [208.214.103.138]
9 95 ms 94 ms 94 ms border9.t7-1-bbnet1.sef.pnap.net [63.251.160.19]
10 * * * Request timed out.
I'm not sure whether this is my problem or Blizzards. A ton of people are having issues right now. If 2 people with different ISPs have similar traceroutes, chances are this is not my problem? I can't think or any other solutions and I'm going to have to cancel my account because of how unplayable it is.
Facebook
Twitter