aree
join:2008-05-26
Bronx, NY
1 edit | reply to MLGTWISTED
Re: Whats With The World Of Warcraft Lag?
I been having this problem for about 3 months already; whenever I start to raid BlackTemple or Sunwell. My latency starts from 200ms to 20k ms then i just DC and lose all internet connection with my phone too which is VoIP. I first though it was my addon/UI or my computer; well I deleted all my addons/ WTF folder and that didn't work; so i reinstalled Wow and that didn't work. Then I though it could be my computer; so I rebuilded it again and that didn't work. At that point I call my ISP and told them my problem, I have had 6 Optimum Online techs come different times to my house and they couldn't find the problem with my internet. Until one of the higher level tech referred my problem to the engineers. They came 4 different times over to fix the problem; but I yet to see any improvements. After reading some of the other Wow players DC's problems on the forums, it looks like WoW doesn't like Motorola SBV5120, so every time I login I lose all internet and phone connection because of Wow. I already told my ISP about the game and what I found out about Motorola SBV5120 not liking WoW; said they are going to look in to it and contact blizz. This is just getting out of hand, blizz and Optimum Online needs together and fix this problem. Theirs alot of players with this problem, not only with type of modem but with DC'ing since the last few patchs.
ISP - Optimum Online/Cablevision
DSL/Cable Modem (and firmware if available) -Motorola SBV5120-2.10.1.7-SCM04-SHSF
Router (and firmware if available) - Dlink DGL-4100, but I don't use it since the dc'ing started
Any other intermediate network devices (hubs, switches, Power over Ethernet, etc) - No
Connection type - wired
Operating System -XP
Geographical Location - Bronx, NY
Tracert -
Tracing route to 206.16.23.128 over a maximum of 30 hops
1 6 ms 5 ms 6 ms 10.240.184.73
2 7 ms 5 ms 5 ms ool-4353e322.dyn.optonline.net [67.83.227.34]
3 * * * Request timed out.
4 8 ms 7 ms 8 ms rtr4-tg10-2.wan.whplny.cv.net [64.15.8.29]
5 * * * Request timed out.
6 * * * Request timed out.
7 10 ms 7 ms 7 ms po9-1.core01.jfk02.atlas.cogentco.com [154.54.2.129]
8 7 ms 8 ms 8 ms te3-2.mpd03.jfk02.atlas.cogentco.com [154.54.5.238]
9 15 ms 16 ms 14 ms te2-1.mpd01.dca01.atlas.cogentco.com [154.54.6.5]
10 16 ms 15 ms 15 ms vl3492.mpd01.dca02.atlas.cogentco.com [66.28.4.86]
11 16 ms 15 ms 15 ms vl3496.mpd01.iad01.atlas.cogentco.com [154.54.5.46]
12 16 ms 16 ms 15 ms 192.205.35.105
13 58 ms 57 ms 58 ms tbr1.wswdc.ip.att.net [12.123.8.130]
14 57 ms 57 ms 58 ms cr2.wswdc.ip.att.net [12.122.16.45]
15 65 ms 57 ms 57 ms cr1.attga.ip.att.net [12.122.1.173]
16 58 ms 57 ms 57 ms cr2.dlstx.ip.att.net [12.122.28.174]
17 58 ms 59 ms 57 ms tbr2.dlstx.ip.att.net [12.122.18.230]
18 59 ms 60 ms 59 ms br2.dlstx.ip.att.net [12.123.16.213]
19 58 ms 57 ms 57 ms mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
20 58 ms 57 ms 57 ms mdf002fbi8ks0001-eth-1-4.dal1.attens.net [63.241.192.126]
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. |
