| reply to aree
Re: Lag, Disconnecting in World of Warcraft I have the same issue, im playing normaly and all of a sudden my latency just shots up and i get disconected from wow (all my other stuff works fine... like teamspeak and browsing... it's just WoW)
Anyway here is my trace route
Tracing route to 63.241.255.47 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.1.1
2 9 ms 8 ms 10 ms 10.82.64.1
3 10 ms 9 ms 22 ms dstswr1-vlan2.rh.cftnnj.cv.net [67.83.244.33]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 13 ms 12 ms 22 ms vl3491.ccr04.jfk02.atlas.cogentco.com [154.54.7.9]
9 40 ms 44 ms 39 ms te4-3.ccr02.ord01.atlas.cogentco.com [154.54.1.190]
10 51 ms 56 ms 52 ms te4-2.ccr02.mci01.atlas.cogentco.com [154.54.6.253]
11 58 ms 57 ms 61 ms te8-4.ccr02.dfw01.atlas.cogentco.com [154.54.5.169]
12 61 ms 60 ms 65 ms vl3490.ccr02.dfw03.atlas.cogentco.com [154.54.6.98]
13 69 ms 73 ms 61 ms gi2-0-0.core01.dfw03.atlas.cogentco.com [154.54.7.34]
14 63 ms 61 ms 62 ms 192.205.32.253
15 63 ms 60 ms 64 ms tbr2.dlstx.ip.att.net [12.123.16.206]
16 60 ms 61 ms 60 ms br2.dlstx.ip.att.net [12.123.16.213]
17 65 ms 61 ms 62 ms 12.122.255.226
18 62 ms 68 ms 65 ms mdf001c7613r0003-gig-10-1.dal1.attens.net [63.241.193.10]
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. |
|
| Unfortunately, this problem is still a problem. The threads on blizzard's wow forums still have people reporting problems by the hour.
Tracert below, also please keep in mind that the problem is highly intermittent (in between lag events my in-game server latency is 150ms) and it's pretty unlikely that this tracert is illustrating any packet loss.
Tracing route to 206.17.111.123 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.1.1
2 11 ms 9 ms 8 ms 10.95.192.1
3 7 ms 9 ms 7 ms dstswr2-vlan2.rh.wrrnnj.cv.net [67.83.251.162]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 11 ms 13 ms 13 ms vl3491.ccr04.jfk02.atlas.cogentco.com [154.54.7.
9]
9 17 ms 21 ms 17 ms te8-2.ccr02.dca01.atlas.cogentco.com [66.28.4.12
6]
10 17 ms 17 ms 16 ms te7-3.mpd01.dca02.atlas.cogentco.com [154.54.6.2
6]
11 18 ms 15 ms 18 ms vl3497.mpd01.iad01.atlas.cogentco.com [154.54.5.
66]
12 19 ms 17 ms 19 ms 192.205.35.105
13 30 ms 32 ms 31 ms tbr1.wswdc.ip.att.net [12.122.80.58]
14 29 ms 28 ms 30 ms cr2.wswdc.ip.att.net [12.122.16.61]
15 31 ms 31 ms 30 ms cr2.n54ny.ip.att.net [12.122.3.37]
16 29 ms 32 ms 28 ms cr1.cb1ma.ip.att.net [12.122.31.126]
17 29 ms 30 ms 30 ms tbr1.cb1ma.ip.att.net [12.122.20.130]
18 30 ms 47 ms 34 ms 12.127.5.93
19 30 ms 31 ms 29 ms 12-122-254-14.attens.net [12.122.254.14]
20 176 ms 203 ms 200 ms mdf001c7613r0003-gig-10-1.bos1.attens.net [12.13
0.0.170]
21 * * * Request timed out.
|
|
| I ran two simultaneous pings to two different destinations along my tracert above until I found a spot where packets continue to pass normally on one and are lost downstream on another. As you can (hopefully) see in the attachment, the packets are lost between 67.83.251.162 (hop 3) and 192.205.35.105 (hop 12). Unfortunately none of the intermediate hops (cogent's routers) respond to pings, so I can't run the same test to narrow it down. However, its obvious from this that the problem occurs *before* att and after ool. As you can see, the period of dropped packets is very short (3-4 seconds max) and the occurrence of these 'lag events' is few and far between (every 5 or 10 minutes), so it will be difficult to pick up on many diagnostic tools. |
|
|
|
