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 | Re: Lag, Disconnecting in World of Warcraft 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
| Re: Lag, Disconnecting in World of Warcraft 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 | Re: Lag, Disconnecting in World of Warcraft 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
| Re: Lag, Disconnecting in World of Warcraft 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 | 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 | 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 | 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 | 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. | |
|
aree
join:2008-05-26
Bronx, NY
1 edit | 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
| 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. | |
|
| |
digi
@optonline.net
| Re: Lag, Disconnecting in World of Warcraft 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.
| |
|
| | |
digi
@optonline.net
| Re: Lag, Disconnecting in World of Warcraft 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. | |
|
One
@optonline.net
| My tracert, pretty horrible, when will this be fixed?! | |
|
Audious2
@precisionsigns.com
| 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
| 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
| Re: Lag, Disconnecting in World of Warcraft 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 | 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 | Re: Lag, Disconnecting in World of Warcraft -deleted post- | |
|
truu
@optonline.net
| 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 | 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. | |
|
Camanon
@optonline.net
| I'm getting the spikes (packetloss) between Long Island Optimum and two desinations: a Cogent datacenter in DC and Blizzard's AT&T in LA.
Cogent in Virginia:
tracert 38.100.11.1
Tracing route to gi9-12.mpd01.iad03.atlas.cogentco.com [38.100.11.1]
over a maximum of 30 hops:
1 11 ms 9 ms 12 ms 10.240.160.121
2 8 ms 9 ms 8 ms dstswr1-vlan2.rh.stjmny.cv.net [167.206.39.161]
3 * * * Request timed out.
4 21 ms 14 ms 11 ms rtr3-tg10-3.wan.hcvlny.cv.net [64.15.4.9]
5 * * * Request timed out.
6 * * * Request timed out.
7 10 ms 10 ms 9 ms te9-2.ccr04.jfk02.atlas.cogentco.com [130.117.0.53]
8 26 ms 14 ms 17 ms te2-1.ccr02.dca01.atlas.cogentco.com [154.54.6.13]
9 16 ms 31 ms 17 ms te4-1.mpd01.dca02.atlas.cogentco.com [154.54.2.182]
10 20 ms 18 ms 25 ms gi9-12.mpd01.iad03.atlas.cogentco.com [38.100.11.1]
Trace complete.
...
Reply from 38.100.11.1: bytes=32 time=17ms TTL=245
Reply from 38.100.11.1: bytes=32 time=16ms TTL=245
Reply from 38.100.11.1: bytes=32 time=17ms TTL=245
Reply from 38.100.11.1: bytes=32 time=19ms TTL=245
Request timed out.
Request timed out.
Reply from 38.100.11.1: bytes=32 time=19ms TTL=245
Reply from 38.100.11.1: bytes=32 time=22ms TTL=245
Reply from 38.100.11.1: bytes=32 time=25ms TTL=245
...
AT&T in LA:
tracert 12.129.193.246
Tracing route to mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]
over a maximum of 30 hops:
1 8 ms 7 ms 7 ms 10.240.160.121
2 10 ms 9 ms 16 ms dstswr1-vlan2.rh.stjmny.cv.net [167.206.39.161]
3 * * * Request timed out.
4 8 ms 9 ms 7 ms rtr4-tg10-3.wan.hcvlny.cv.net [64.15.4.33]
5 * * * Request timed out.
6 * * * Request timed out.
7 12 ms 11 ms 12 ms vl3492.mpd03.jfk02.atlas.cogentco.com [154.54.7.13]
8 161 ms 221 ms 219 ms te8-3.mpd01.dca01.atlas.cogentco.com [154.54.5.98]
9 43 ms 43 ms 50 ms te2-2.mpd01.iah01.atlas.cogentco.com [154.54.2.146]
10 77 ms 79 ms 153 ms te4-4.mpd01.lax01.atlas.cogentco.com [154.54.5.102]
11 77 ms 83 ms 83 ms vl3493.mpd01.lax05.atlas.cogentco.com [154.54.6.230]
12 78 ms 76 ms 81 ms gr1-a350s3.sffca.ip.att.net [192.205.35.5]
13 79 ms 78 ms 83 ms tbr2.la2ca.ip.att.net [12.123.222.30]
14 76 ms 78 ms 87 ms 12.127.3.189
15 78 ms 77 ms 77 ms 12.122.255.74
16 83 ms 78 ms 78 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]
Trace complete.
...
Reply from 12.129.193.246: bytes=32 time=77ms TTL=240
Reply from 12.129.193.246: bytes=32 time=78ms TTL=240
Reply from 12.129.193.246: bytes=32 time=78ms TTL=240
Reply from 12.129.193.246: bytes=32 time=83ms TTL=240
Reply from 12.129.193.246: bytes=32 time=78ms TTL=240
Reply from 12.129.193.246: bytes=32 time=77ms TTL=240
Request timed out.
Request timed out.
Reply from 12.129.193.246: bytes=32 time=78ms TTL=240
Reply from 12.129.193.246: bytes=32 time=79ms TTL=240
Reply from 12.129.193.246: bytes=32 time=91ms TTL=240
...
The two "Request timed out" are concurrent.
The tracert's don't show the actual problem, just the current routes. Both are currently exhibiting symptoms where they cause 5-8 seconds of packetloss every 5 minutes or so. This has been happening on and off, to greater and lesser degrees of severity, for the past 3 weeks.
Assuming CV and Cogent are peering in NY I'm not sure how AT&T is the problem, or at least the only problem. | |
|
| TheWiseGuy
Dog And Butterfly
Premium,MVM
join:2002-07-04
Yonkers, NY
| Re: Lag, Disconnecting in World of Warcraft You can use a more thorough tracert utility to help find where the problem is located. Here are 2 freeware utilities, that will allow you to configure them to run for more than 3 packets per hop and may help determine where the problem is for WoW. Given the size of the Internet I would not be surprised if at any point in time there was more then one problem occurring somewhere with a router. The final link is to the Internet traffic report which also gives some info on where problems are occurring.
»www.pingplotter.com/freeware.html
»www.foundstone.com/us/resources/···rout.htm
»www.internettrafficreport.com/namerica.htm
--
Warning, If you post nonsense and use misinformation and are here to argue based on those methods, you will be put on ignore. | |
|
rebecca191
join:2008-05-18
Fairfield, CT
1 edit | Camanon - I've seen it spike high at cablevisionm, cogentco, and attens, so there may be a problem with how all 3 are routing. Cogentco appears to dropping 10% of my packets ATM but everything's pinging lower then it was earlier today. | |
|
|
Camanon
@optonline.net
| Re: Lag, Disconnecting in World of WarcraftUsing PingPlotter:
Target Name: gi9-12.mpd01.iad03.atlas.cogentco.com
IP: 38.100.11.1
Date/Time: 6/5/2008 5:52:38 PM to 6/5/2008 5:57:39 PM
Hop Sent Err PL% Min Max Avg Host Name / [IP]
1 299 0 0.0 5 28 8 [10.240.160.121]
2 299 0 0.0 5 32 9 dstswr1-vlan2.rh.stjmny.cv.net [167.206.39.161]
3 299 299 100.0 0 0 0 [-]
4 299 0 0.0 6 216 15 rtr3-tg10-3.wan.hcvlny.cv.net [64.15.4.9]
5 299 299 100.0 0 0 0 [-]
6 299 299 100.0 0 0 0 [-]
7 299 10 3.3 8 217 14 te9-2.ccr04.jfk02.atlas.cogentco.com [130.117.0.53]
8 299 11 3.7 14 340 28 te2-1.ccr02.dca01.atlas.cogentco.com [154.54.6.13]
9 299 8 2.7 15 275 28 te4-1.mpd01.dca02.atlas.cogentco.com [154.54.2.182]
10 299 7 2.3 15 233 21 gi9-12.mpd01.iad03.atlas.cogentco.com [38.100.11.1]
I'm not sure what the hop before 130.117.0.53 (te9-2.ccr04.jfk02.atlas.cogentco.com) is, but it's clear that the issue is happening at or before that router - perhaps the CV/Cogent handoff?
Any Optimum tech able to further investigate, surely you'd have a better idea what the hops between 64.15.4.9 (trouble free) and 130.117.0.53 (problematic) are? If you need any further information please don't hesitate to ask, though given the trace I'd think that OOL has sufficient data to locate the issue.
rebecca191: your spikes on the later hops can be caused by problems occurring before you reach them. | |
|
| | rebecca191
join:2008-05-18
Fairfield, CT
1 edit | Re: Lag, Disconnecting in World of Warcraft Camanon - yeah, I'm thinking it's something with Cognetco that is causing the problem. Although ocasionally I'll see a spike before it gets there, 99% of the time the lag seems to start there. Please take a look at Cogentco connections if anyone from OOL is reading this thread.
Mainly the problems start from rtr4-tg11-2.wan.whplny.cv.net [64.15.8.25] to vl3495.ccr04.jfk02.atlas.cogentco.com [154.54.6.45]
Also seeing lag spikes then at the following congentco IPs as well:
te3-3.ccr02.dca01.atlas.cogentco.com [154.54.5.246]
te4-3.mpd01.dca02.atlas.cogentco.com [154.54.7.2]
vl3496.mpd01.iad01.atlas.cogentco.com [154.54.5.46]
Not sure if it's getting worse there or just continuing the problem from the initial packet loss/lag spike from 64.15.8.25 to 154.54.6.45 | |
|
rebecca191
join:2008-05-18
Fairfield, CT
1 edit | I just got off the phone with OOL. It's definitley happening at Cogentco. The tech watched my route for a few mins and then he found the phone number the offending IPs belong to but... he said he can't call. WTF? do I have to speak to a higher up at OOL to have them call this number? | |
|
|
digi
@optonline.net
| Re: Lag, Disconnecting in World of Warcraft I sent an e-mail to cogent which I'm sure will have all the effect of pissing into the wind, what with me being just some guy with a g-mail account. At least now they'll be aware of the problem, however, if their spam filter doesn't just trash it ;p | |
|
rebecca191
join:2008-05-18
Fairfield, CT | I have their phone number around here somewhere, I just don't see the point in calling them since I'm not their customer. | |
|
|
digi
@optonline.net | Re: Lag, Disconnecting in World of Warcraft Yes, any phone call to tech support would get as far as 'what's your account number'. | |
|
| | rebecca191
join:2008-05-18
Fairfield, CT | Re: Lag, Disconnecting in World of Warcraft I'm trying to get a tech at OOL who has the authority to open a ticket or report the problem to Cogentco. | |
|
| | |
digi
@optonline.net | Re: Lag, Disconnecting in World of Warcraft any luck? do you have the IP of the offending router or is it more than one? | |
|
| | | | rebecca191
join:2008-05-18
Fairfield, CT
1 edit | Re: Lag, Disconnecting in World of Warcraft Basically every Cogentco router was giving me high pings when a spike happened, but the tech I had spoken to initially wasn't sure if they were all having problems or it was just a continuation of the lag from the very first hop to Cogentco.
It starts at 154.54.6.45 on my traces.
The people on the phone I've tried talking to claim they have no responsibility and aren't routing me to Cogentco - then who is? Why is there no communication between the techs here and the people when you call OOL? Who is right - is it being worked on, or not? | |
|
| | | | |
digi
@optonline.net
| Re: Lag, Disconnecting in World of Warcraft I haven't gotten a response from my e-mail so I'm assuming cogent is going to ignore me. The dumb thing is that even if they acknowledge the packet loss, its probably too low to violate any kind of terms of service, so they likely wouldn't be under any obligation to fix it anyway.
I suppose if they say they're not routing you through cogent there might be another intermediary (one of those that doesn't respond to tracert and therefore doesn't show up). I can't imagine that they don't have any control over where their packets get routed -- after all, if that faulty router actually went down they would find a way to get the packets through.
Have you threatened to change service providers? That's what I'll ultimately have to do when I call them. | |
|
| | | | | | rebecca191
join:2008-05-18
Fairfield, CT | Re: Lag, Disconnecting in World of Warcraft Or they could just be dumb phone tech people. Hard to say. | |
|
NiZZ
@optonline.net
| Tracing route to 12.129.233.127 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 12.129.233.127
2 * * * Request timed out.
3 33 ms 45 ms 42 ms opti33-162.nassau.cv.net [167.206.33.162]
4 36 ms 34 ms 28 ms rtr4-ge1-11.mhe.hcvlny.cv.net [167.206.33.133]
5 32 ms 32 ms 34 ms rtr3-tg11-3.wan.hcvlny.cv.net [64.15.4.13]
6 * * * Request timed out.
7 * * * Request timed out.
8 37 ms 31 ms 33 ms vl3496.mpd03.jfk02.atlas.cogentco.com [154.54.6.49]
9 52 ms 49 ms 51 ms te7-3.mpd01.dca01.atlas.cogentco.com [154.54.3.45]
10 67 ms 89 ms 71 ms te7-3.mpd01.iah01.atlas.cogentco.com [154.54.2.246]
11 101 ms 98 ms 98 ms te7-4.mpd01.lax01.atlas.cogentco.com [154.54.2.198]
12 99 ms 126 ms 99 ms vl3492.mpd01.lax05.atlas.cogentco.com [154.54.3.10]
13 106 ms 99 ms 162 ms gr1-a350s3.sffca.ip.att.net [192.205.35.5]
14 111 ms 100 ms 122 ms tbr2.la2ca.ip.att.net [12.123.222.30]
15 105 ms 111 ms 99 ms 12.127.3.189
16 104 ms 122 ms 115 ms 12.122.255.74
17 101 ms 101 ms 122 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]
18 * * * Request timed out.
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.
The lag is really destroying any chance I have at playing. This is really stupid......... | |
|
| frdrizzt
join:2008-05-03
Farmingville, NY
·Optimum Online
| Re: Lag, Disconnecting in World of Warcraft Cablevision had done a lot of tests with the information given, and has confirmed by the networking team that the issue is off their network, and they advise you to contact Blizzard/World of Warcraft for further troubleshooting.
Just updating you on the info CV has provided for us. Don't shoot the messanger. | |
|
| |
digi
@optonline.net
| Re: Lag, Disconnecting in World of Warcraft On the other hand, this is the response I received just today from the trouble ticket I filed yesterday with OOL:
"Thank you for contacting Optimum Online regarding your question about online gaming. We apologize for any inconvenience this may have caused you and will be happy to assist.
Thank you for your email. I have attached the information to your account and escalated this over to our Communications Desk for further review."
Since I haven't received an update on this ticket I can only assume that it is still being worked on. This kind of highlights the worst part of this entire experience, which is that we're consistently getting two different answers from OOL. | |
|
| |
digi
@optonline.net
| For anyone else still concerned about this problem, OOL is in fact still looking into it despite their somewhat ominous sounding immediate response. They really are a pretty good service provider. Names have been changed to protect the innocent, and I apologize for the wall of text below, but I think it really clears the matter up of what they are and aren't doing.
---
OOL: I see, what would you like to add to the ticket?
digi: i'm just looking for a status update on it if available, is it still open and being investigated?
OOL: As of this time the issue is still open. It has been confirmed by our Networking team that the issue is with the World of War Craft site. Please contact World of Warcraft for further troubleshooting. That is the latest update that I have sir. I truly apologize for the inconvenience.Can I assist with anything else regarding Optimum Online?
digi: In my troubleshooting I have found that the problem is before the warcraft site, on an intermediary router owned by Cogent Communications
digi: obviously I have already contacted the owners of warcraft and they confirmed that the problem is not on their network
digi: i've heard a few different responses from friends who have filed trouble tickets with OOL ; some of them say that OOL has stopped working on the problem, can you confirm that an alternate routing solution is still being investigated by your engineers?
OOL: That is fine but we do not control the router owned by Cogent Communications. We can only comment on anything on the Cablevision network. You can contact the World of Warcraft site and they can contact Cogent Communications. Again I truly apologize for the inconvenience.Can I assist with anything else regarding Optimum Online?
digi: i'm sorry, but unfortunately I pay world of warcraft for gaming services and I pay you guys for network connectivity
OOL: We provide your Internet connection. Are you able to access the Internet?
digi: I understand that OOL has control over which intermediary routers my packets are routed through to reach an end destination, and if OOL is routing my packets through a router with a known defect then I feel it is your responsibility to rectify the situation if possible
digi: i haven't had any problems whatsoever with my service, and I understand it isn't your hardware that has the problem
OOL: Again I truly apologize for the inconvenience. Can I assist with anything else regarding Optimum Online?
digi: but if you guys can't help me rectify it i'll have to start looking for another service provider that will
digi: i'm sure you understand the situation
digi: do you have a supervisor that you can refer me to?
OOL: I understand and I truly apologize for the inconvenience. Would like like to speak to a Supervisior?
digi: yes, please -- thanks mario, I know this issue is a pain in the ass
OOL: Hello sir, my name is Mrs. X and I am a supervisor in Technical Support.
digi: hi there
OOL: Hello I understand you have a question about the connectivity of World of War Craft. Is that correct?
digi: that's right, i have an open ticket
OOL: I see that we have an outage posted for this issue and it was determined that the lack connectivity is on a network that does not belong to Cablevision.
OOL: The issue resides on the side of Blizzard.
digi: that's right, it seems to be a problem with an intermediate router owned by Cogent Communications
digi: i don't think that's entirely accurate, the problem seems to be before the packets hit blizzard's network
digi: cogent is the intermediary between OOL and ATT (blizzard's service provider)
OOL: Cogentco piggy backs to the ATT network and this is where the issue resides.
digi: right, in Cogent's hardware
digi: I don't believe Cogent is associated with Blizzard's service provider, are they?
OOL: I was just researching this just prior to this conversation and for any course of action that we can take to assist customers in this.
OOL: No,
digi: are you guys working on an alternate route to bypass the defective routers, or currently in communication with Cogent?
OOL: Blizzard uses ATT for the provider and the backbone for the connection is with Cogentco. Cogentco consistently has issues .
digi: right
digi: so I'm as right to contact you about this as Blizzard is to contact ATT
digi: since the problem is on a third party router not associated with either of our service providers
OOL: We have been working to get this resolved. The information that I am passing to you is from another supervisor that also plays WOW.
digi: okay, so you guys are still working on it?
OOL: I can promise you that we are working on this.
digi: that's really all I'm trying to find out
digi: hehe okay, good
digi: you don't have an estimated timeframe, do you?
OOL: There are currently around 150 people in this call center that all play and are being affected as well.
digi: it really is a pretty annoying problem
OOL: For the timeframe, unfortunately, I do not have an exact answer.
OOL: It is a very annoying problem and can sympathize with you in this matter.
digi: that's fine, like I said I was just trying to get to the bottom of the situation and make sure that something is still being done
OOL: I understand and I know that everyone here involved is working their hardest to come to a resolution.
digi: thank you for your time
OOL: You are more than welcome and I hope that this is resolved as quickly as possible for you and everyone else.
digi: yeah me too -- thanks again, and take care | |
|
| | | |
NiZZ
@optonline.net | So what do we have to do, to get someone to contact Crapogent?! | |
|
audious
join:2008-06-03
| At least now (after weeks of getting nowhere with tech support) there's some sort of acknowledgment on OOL's end.
Thankfully, we're past power cycling our modems, bypassing our routers and making sure our cables are all plugged in correctly.
I think we'd all like to see an official post, tracking the progress of this issue. | |
|
audious
join:2008-06-03
| Here is a transcript of a chat session:
> Your Optimum Online Tech Support Specialist has arrived.
Nedrick M: Good afternoon! Thank you for contacting Cablevision's Technical Support rated #1 by J.D. Power and Associates. My name is Nedrick, and I will be happy to assist you today. How are you today William? I understand you need assistance with your connection and service. Is this correct?
Vossner: Yes.
Vossner: And I'm doing fine, thanks. 
Vossner: How about yourself?
Nedrick M: I understand this issue and sincerely apologize for any inconvenience at all. I will be more then happy to assist you. Pretty much alive and well thank you.
Vossner: Sounds good.
Vossner: TGIF hah.
Nedrick M: Allow me a minute to see what the current update is on the WoW issue.
Vossner: I figured that you would know what I'm talking about.
Nedrick M: The issue is still ongoing from the last update I see posted.
Vossner: Alright.
Vossner: I was curious, and you don't need to answer this if it's personal for your comfort, if you were working for OOL approximately two years ago when a similar situation happened?
Vossner: too personal*
Nedrick M: Sorry about the delay in answering.
Vossner: No problem at all. I waited 8 hours to leave work today so I'm in no rush haha.
Nedrick M: I have been with Cablevision for 3 years now.
Nedrick M: But they did have a similar issue I believe last year almost around the same time I believe.
Vossner: Ah. Something similar happened about two years ago like I said. OOL / Cablevision simply routed us around the issue and it cleared right up. I assume this time it's not so simply?
Vossner: Maybe it was only just last year and my memory is off.
Vossner: it's not simple.
Vossner: **
Vossner: Brain is fried.
Nedrick M: I see, unfortunately the word from the top is that we are waiting until the issue is resolve of the networking and we are being directed to direct you to contact the technical support of wow.
Nedrick M: From the report it is network wide.
Vossner: Alright. Sounds reasonable, although I can honestly say it's not an issue of Blizzard's hardware. I've been online several times in the past few days with friends who belong to Comcast and when I and the other players in my house are lagging out, my friends are doing just dandy.
Vossner: Is there any chance that someone is looking into contacting CogentCo about their lackluster servers?
Vossner: I realize OOL isn't a CogentCo customer but then again, neither am I lol.
Nedrick M: I know what you are saying and we both know what causes network lags but as you know once the ball is dropped from the top we little guys cannot really state much.
Vossner: Aye I understand that.
Vossner: So other than running dead-ends into Blizzard's forums, is there anything else I can do to remedy the situation?
Vossner: Or is it just a waiting game until some technician figures out how to either get us around the congested node or clear up the congestion?
Nedrick M: If there was a way to route you connection then that would be the way to go as it all depends on how your connection is routed and what servers you take to get to the server that you utilize.
Vossner: Right.
Vossner: There's conflicting reports of what other customers are being told.
Vossner: Some are saying that both Blizzard and OOL are telling us to talk to the other.
Vossner: And then some people are saying that OOL is working on resolving the situation.
Vossner: Any chance you or a supervisor might be able to definitively answer that?
Nedrick M: Right now it is basically a waiting game, but once it is resolve you will know.
Nedrick M: The supervisor will more than likely state it in a more standard script that the issue is not on our end.
Vossner: Aye, we both know where the issue lies.
Vossner: I guess what I'm looking for is.
Vossner: Who is going to fix it?
Vossner: And what catalyst is going to be needed to get that person to fix it
Vossner: ?*
Nedrick M: At this point in time William, the verdict from the man upstairs is since the issue is not on our end or better yet our networkfrom the reports we cannot state when the issue will be resolved. We are only being directed that customers should reach out to Blizzard.
Nedrick M: As you know I cannot point fingers from where I sit.
Vossner: Aye I understand that.
Vossner: So is that more or less a nice way of putting "Neither OOL or Blizzard is fixing the situation so the customers are left to their own devices"?
Nedrick M: I can neither say nay or yea to that question.
Vossner: Is there a chance that a supervisor could answer it? 
Nedrick M: If you would like to speak to a supervisor regarding this issue you may reach us via phone at 1866-575-8000.
Vossner: Alright, thanks kindly.
Nedrick M: You're welcome William. Is there anything else I can do to provide you with excellent service regarding Optimum Online or Optimum Voice?
Vossner: Nope, that was all, thanks.
Nedrick M: Thank you for using Optimum Online's Live Technical Support. There will be a survey at the end of this chat session to rate my performance. In the quest to achieve excellence in customer support, we have added answers to most common questions and some other useful information on our homepage www.optimum.net/support, under the customer support tab. Please be aware chat support is available from 8am to midnight seven days a week. Have a wonderful day!
=
What I gathered from this is neither Blizzard nor OOL is going to put pressure on CogentCo (which is quite easy to mistype as Congested, ironic) and we're basically going to sit here and lag our brains out." | |
|
| rebecca191
join:2008-05-18
Fairfield, CT | Re: Lag, Disconnecting in World of Warcraft Stupid. My DSL modem can't get here fast enough. Even if it's a bit slower then cable, if it doesn't lag to hell and randomly d/c me it will be good enough for me. | |
|
|
Vossner
@optonline.net
| I'm the Vossner (William) in the above post.
Essentially what I gathered from Nedrick was that neither Blizzard nor OOL, despite being the ones with the resources to do so, are going to be putting pressure on CogentCo to fix their situation.
So your guess is as good as mine. And, if you noticed, he couldn't answer which reports were correct.
I firmly believe that anyone who is told OOL is doing something is essentially being told "Yes we're doing something: we're sitting here telling you to go elsewhere for help." | |
|
| | audious
join:2008-06-03
1 edit | Re: Lag, Disconnecting in World of Warcraft Posted twice. Apologies. | |
|
| | | AdamB2K3
join:2004-03-12
Grand Prairie, TX
| Re: Lag, Disconnecting in World of Warcraft
Tracing route to 63.241.255.119 over a maximum of 30 hops
1 1 ms 1 ms 1 ms ROUTER [192.168.1.1]
2 11 ms 7 ms 5 ms 10.240.160.177
3 8 ms 10 ms 6 ms dstswr2-vlan2.rh.lybrny.cv.net [167.206.33.34]
4 9 ms 10 ms 8 ms r4-ge9-2.mhe.hcvlny.cv.net [167.206.33.5]
5 12 ms 9 ms 11 ms rtr3-tg11-3.wan.hcvlny.cv.net [64.15.4.13]
6 * * * Request timed out.
7 * * * Request timed out.
8 10 ms 10 ms 9 ms vl3495.ccr04.jfk02.atlas.cogentco.com [154.54.6.45]
9 17 ms 16 ms 22 ms te2-2.ccr02.bos01.atlas.cogentco.com [154.54.5.242]
10 39 ms 41 ms 37 ms te9-4.ccr02.ord01.atlas.cogentco.com [154.54.7.169]
11 49 ms 49 ms 49 ms te9-4.ccr02.mci01.atlas.cogentco.com [154.54.6.214]
12 58 ms 57 ms 60 ms te2-2.ccr02.dfw01.atlas.cogentco.com [154.54.5.165]
13 61 ms 62 ms 61 ms te7-3.ccr02.dfw03.atlas.cogentco.com [154.54.6.62]
14 62 ms 59 ms 61 ms gi10-0-0.core01.dfw03.atlas.cogentco.com [154.54.25.1]
15 61 ms 64 ms 60 ms 192.205.32.253
16 60 ms 57 ms 58 ms tbr1.dlstx.ip.att.net [12.123.16.202]
17 61 ms 58 ms 62 ms gar5.dlstx.ip.att.net [12.123.16.209]
18 57 ms 57 ms 58 ms 12.122.255.226
19 60 ms 60 ms 59 ms mdf001c7613r0003-gig-10-1.dal1.attens.net [63.241.193.10]
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. | |
|
|
|
|
·
