ansky08
join:2005-07-11
New Milford, NJ
| Lag, Disconnecting in World of Warcraft
For the past few days, I have been getting recurring lag spikes and/or disconnects while in World of Warcraft. For the most part, it seems that WoW is the issue, because I stay connected to Ventrilo. There's 2 other guildmates that I have who also get lag spikes/disconnect at the same time as I do - they are also using Optimum Online.
I am in the Northern Jersey area. Is there anything I can do to resolve this issue? |
|
frdrizzt
join:2008-05-03
Farmingville, NY
 ·Optimum Online
1 edit | Can you connect to the www.worldofwarcraft.com when the game goes down? If you can't, I'd go:
start > run > cmd
On the next screen, write:
tracert www.worldofwarcraft.com
If it is not able to make it to the destination, there is a problem. (note: it is perfectly fine for some steps to not complete, as long as it makes it to the end).
I've seen people who had trouble with access to the game and the website simultaneously (not for many months though), where it was an issue with the OOL. There are many possibilities, but if you can't get to that website either, I'd definitely call OOL tech support (and have your friends try the same). |
|
ooltech
join:2001-04-04
Woodbury, NY
| Hi,
We've been getting some volume with regards to WoW users and intermittent lags. We have been looking at the AT&T network and believe that is where the issue is. We have been collecting Tracerouts on this. You can post on the Direct Forum so we can escalate it further or post on this thread in the World of Warcraft forum.
»forums.worldofwarcraft.com/threa···20&sid=1
Thanks,
**OOLTECH** |
|
MLGTWISTED
join:2007-01-19
Melville, NY | I also have been getting alot of lag and disconnect problems specifically with wow, I hope the problem smooths out soon. |
|
ooltech
join:2001-04-04
Woodbury, NY
| Hello all,
Optimum Online is trying to collect example trace routes so that our engineers can work on this problem. If you are experiencing WOW latency/disconnects, please post your account information (mac address/acct #) and a full trace route, including source and destination, in the private OOL forum.
Thanks very much. The more information we can obtain, the faster a solution can be implemented.
ooltech ec |
|
Pls Fix
@optonline.net | reply to ansky08
Having the same problem in Long Island, NY. Especially last night. Large lag spikes only seen in WoW. All other internet connections did not have an issue so I'm willing to bite its a connection issue between OOL & ATT (WoW's ISP). |
|
Fix it please
@cv.net | reply to ansky08
Large lag spikes last night between 10pm and 1am, WOW only. Ventrilo stayed connected, web speeds seemed normal. Pings spiked to 900-1k for several minutes at a time, then normalized. |
|
for petes sake
@optonline.net | reply to ansky08
Optimum Online engineers pls look into this problem with better tools than a tracert. 4000 latency makes it impossible to stay connected!!!!!!!!! |
|
Star64
@optonline.net | reply to ansky08
same issues here. getting really annoying. using OOL on long island. high latency during certain times of the day, random freeze ups, and sometimes disconnects. there's quite a few posts on the WoW forums about this as well. |
|
StreetSpirit
Premium
join:2002-08-13
Roslyn, NY
·Optimum Online
 ·Verizon Online DSL
2 edits | reply to ooltech
Same Warcraft problem here.
My nephew loves our fast Inet but he says Warcraft is unplayable because of the lag and disconnections.
I even tried to remove my router thinking maybe that was causing it-- modem straight to PC same thing.
I don't play the game (or many PC based games at all) but I imagine if I was a gamer, this would drive me batty.
Also this seems unlikely to be an OOL problem. It looks like many have reported this hop as causing latency. »www.google.com/search?source=ig&···e+Search
Now let's all hand in our traceroutes like good little children, the teacher looks annoyed as is. :)
Look at hop #17 - AT&T's shines through once again. :) |
|
aree
join:2008-05-26
Bronx, NY
1 edit | reply to ansky08
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 didnt 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. |
|
Akka
@optonline.net
| 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. |
|
One
@optonline.net
| reply to ansky08
My tracert, pretty horrible, when will this be fixed?! |
|
Audious2
@precisionsigns.com
| reply to ansky08
Bump. Having the same issue the last few weeks. Several folks in my area are having the same problem.
Tracing route to 206.17.111.29 over a maximum of 30 hops
1 1 ms 2 ms 1 ms 192.168.1.1
2 11 ms 11 ms 27 ms 10.240.160.161
3 10 ms 8 ms 17 ms opti33-162.nassau.cv.net [167.206.33.162]
4 10 ms 11 ms 9 ms opti33-141.nassau.cv.net [167.206.33.141]
5 12 ms 22 ms 12 ms rtr4-tg11-3.wan.hcvlny.cv.net [64.15.4.37]
6 * * * Request timed out.
7 * * * Request timed out.
8 13 ms 16 ms 12 ms vl3495.ccr04.jfk02.atlas.cogentco.com [154.54.6.45]
9 39 ms 19 ms 17 ms te3-3.ccr02.dca01.atlas.cogentco.com [154.54.5.246]
10 26 ms 24 ms 38 ms te7-3.mpd01.dca02.atlas.cogentco.com [154.54.6.26]
11 32 ms 19 ms 20 ms vl3496.mpd01.iad01.atlas.cogentco.com [154.54.5.46]
12 21 ms 19 ms 19 ms 192.205.35.105
13 51 ms 32 ms 34 ms tbr1.wswdc.ip.att.net [12.122.80.58]
14 30 ms 31 ms 33 ms cr2.wswdc.ip.att.net [12.122.16.5]
15 30 ms 29 ms 30 ms cr2.n54ny.ip.att.net [12.122.3.37]
16 43 ms 33 ms 33 ms cr1.cb1ma.ip.att.net [12.122.31.126]
17 39 ms 33 ms 34 ms tbr1.cb1ma.ip.att.net [12.122.20.130]
18 35 ms 30 ms 41 ms 12.127.5.93
19 32 ms 34 ms 34 ms 12-122-254-14.attens.net [12.122.254.14]
20 41 ms 33 ms 31 ms mdf001c7613r0004-gig-12-1.bos1.attens.net [12.130.0.174]
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. |
|
Del0718
@optonline.net
| reply to ansky08
In Long Island, having the same problems as posted above, getting the same info when running a trace with hops 3, 5, & 6 timing out. Contacted Optimum directly and was told it was my router......it's not. Please try to resolve this, or give an answer that doesn't imply all of us just got very unlucky with bad routers. |
|
TheWiseGuy
Dog And Butterfly
Premium,MVM
join:2002-07-04
Yonkers, NY
| said by Del0718 :
getting the same info when running a trace with hops 3, 5, & 6 timing out.
Caveat- I am not saying there is not a problem somewhere.
If there are hops that always time out and the trace continues with the following hops and they have a low latency, those routers are simple set up to not reply to a trace. It is unlikely they are the problem if the following hops have low latency. You need to look for hops with high latency or that sometimes lose packets and sometimes do not lose packets. For a good writeup on how to use tracerts see
»homepage.ntlworld.com/robin.d.h.···tracemis
--
Warning, If you post nonsense and use misinformation and are here to argue based on those methods, you will be put on ignore. |
|
DownLow
Nope...I Got Nothing
Premium
join:2001-04-25
Long Island | reply to ansky08
Wow, I am glad I am not the only one getting this for the past week or so (last night I had a ping of over 2000).
--
Cleverly Disguised As A Responsible Adult! |
|
ansky08
join:2005-07-11
New Milford, NJ
2 edits | -deleted post- |
|
truu
@optonline.net
| reply to ansky08
Server: Arthas
Location: Brooklyn, NY
Tracing route to 206.16.23.50 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.1.103
2 14 ms 13 ms 10 ms 10.38.0.1
3 21 ms 10 ms 15 ms dstswr1-vlan2.rh.nyk1ny.cv.net [67.83.220.33]
4 * * * Request timed out.
5 28 ms 10 ms 10 ms rtr4-tg11-2.wan.hcvlny.cv.net [64.15.4.25]
6 * * * Request timed out.
7 * * * Request timed out.
8 170 ms 215 ms 204 ms vl3491.ccr04.jfk02.atlas.cogentco.com [154.54.7.
9]
9 48 ms 217 ms 232 ms te8-2.ccr02.dca01.atlas.cogentco.com [66.28.4.12
6]
10 239 ms 19 ms 205 ms te4-3.mpd01.dca02.atlas.cogentco.com [154.54.7.2
]
11 118 ms 205 ms 204 ms vl3497.mpd01.iad01.atlas.cogentco.com [154.54.5.
66]
12 20 ms 20 ms 34 ms 192.205.35.105
13 81 ms 62 ms 65 ms tbr1.wswdc.ip.att.net [12.123.8.186]
14 63 ms 59 ms 65 ms cr2.wswdc.ip.att.net [12.122.16.53]
15 58 ms 60 ms 58 ms cr1.attga.ip.att.net [12.122.1.173]
16 66 ms 60 ms 63 ms cr2.dlstx.ip.att.net [12.122.28.174]
17 61 ms 69 ms 60 ms tbr2.dlstx.ip.att.net [12.122.18.206]
18 62 ms 77 ms 66 ms br2.dlstx.ip.att.net [12.123.16.213]
19 76 ms 60 ms 61 ms mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255
.78]
20 66 ms 73 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 |
|
rebecca191
join:2008-05-18
Fairfield, CT
2 edits | reply to ansky08
Was good last night but now lag is back today, so annoyed I can't switch ISPs but the only other option here is slow AT&T dsl  although I'm wondering if at this point that would be a better option, or the fact it's DSL would leave me with a bad ping anyway
Edited to add new trace route, it's lagging out both at Cablevision and then again near the end:
Tracing route to 206.17.111.56 over a maximum of 30 hops
1 11 ms 8 ms 5 ms 10.119.224.1
2 10 ms 7 ms 7 ms dstswr1-vlan2.rh.brptct.cv.net [67.83.224.161]
3 * * * Request timed out.
4 210 ms 9 ms 104 ms rtr4-tg11-2.wan.whplny.cv.net [64.15.8.25]
5 * * * Request timed out.
6 * * * Request timed out.
7 10 ms 12 ms 10 ms vl3495.ccr04.jfk02.atlas.cogentco.com [154.54.6.45]
8 33 ms 18 ms 16 ms te3-3.ccr02.dca01.atlas.cogentco.com [154.54.5.246]
9 17 ms 17 ms 20 ms te4-3.mpd01.dca02.atlas.cogentco.com [154.54.7.2]
10 17 ms 40 ms 18 ms vl3496.mpd01.iad01.atlas.cogentco.com [154.54.5.46]
11 18 ms 17 ms 22 ms 192.205.35.105
12 69 ms 30 ms 30 ms tbr1.wswdc.ip.att.net [12.123.8.130]
13 32 ms 30 ms 34 ms cr2.wswdc.ip.att.net [12.122.16.5]
14 29 ms 34 ms 36 ms cr2.n54ny.ip.att.net [12.122.3.37]
15 27 ms 30 ms 30 ms cr1.cb1ma.ip.att.net [12.122.31.126]
16 29 ms 30 ms 32 ms tbr1.cb1ma.ip.att.net [12.122.20.146]
17 28 ms 27 ms 29 ms 12.127.5.93
18 196 ms 203 ms 204 ms 12-122-254-14.attens.net [12.122.254.14]
19 39 ms 35 ms 30 ms mdf001c7613r0004-gig-12-1.bos1.attens.net [12.130.0.174]
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. |
|
