Re: Lag, Disconnecting in World of Warcraft in OptimumOnline

Re: Lag, Disconnecting in World of Warcraft

Thu, 26 Jun 2008 14:46:55 EDT

km278 : I'm having a lot of trouble staying connected today.

Tracing route to worldofwarcraft.com [12.129.242.22]

over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1

2 8 ms 6 ms 7 ms xx.xx.xxx.x

3 7 ms 5 ms 6 ms dstswr2-vlan2.rh.rndhnj.cv.net [67.83.249.162]

4 * * * Request timed out.

5 * * * Request timed out.

6 * * * Request timed out.

7 * * * Request timed out.

8 10 ms 9 ms 9 ms ae-13-69.car3.NewYork1.Level3.net [4.68.16.5]

9 8 ms 9 ms 9 ms 192.205.33.93

10 81 ms 81 ms 82 ms tbr2.n54ny.ip.att.net [12.123.0.94]

11 81 ms 82 ms 81 ms cr2.n54ny.ip.att.net [12.122.16.205]

12 82 ms 81 ms 85 ms cr2.wswdc.ip.att.net [12.122.3.38]

13 87 ms 81 ms 81 ms cr1.attga.ip.att.net [12.122.1.173]

14 83 ms 80 ms 80 ms cr2.dlstx.ip.att.net [12.122.28.174]

15 83 ms 81 ms 84 ms cr2.la2ca.ip.att.net [12.122.28.178]

16 81 ms 81 ms 82 ms tbr2.la2ca.ip.att.net [12.122.19.198]

17 84 ms 84 ms 84 ms 12.127.3.189

18 81 ms 81 ms 81 ms 12.122.255.74

19 81 ms 81 ms 82 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]

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.

Re: Lag, Disconnecting in World of Warcraft

Thu, 26 Jun 2008 12:55:49 EDT

mute11 : This issue just recurred, disconnect from WOW and unable to get back. The trace shows we're now once again being routed through Cogentco in some crazy new trace that takes 30 hops to hit the destination. It was rock solid perfect until this.

EDIT: Route is back to the new route (Level 3 to AT&T). Any idea why the route would change suddenly like that, and then revert back? Is this going to be a common occurrence?

EDIT: And doing it again. It's some issue with their new route, it eventually reverts back but the route continually changes to some permutation of the old Cogent one. In the past 10 minutes the route has changed probably a dozen times. Ignore the top two hops, the meat is in the trace.

Correct trace:
Trace to: N/A 63.241.255.49
Repeated every 15 seconds

Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.1.1 --------------
3 167.206.33.34 dstswr2-vlan2.rh.lybrny.cv.net
4 167.206.33.5 r4-ge9-2.mhe.hcvlny.cv.net
5 64.15.4.13 rtr3-tg11-3.wan.hcvlny.cv.net
6 -
7 -
8 4.68.16.197 ae-43-99.car3.NewYork1.Level3.net
9 4.68.127.150 att-level3-oc192.NewYork1.Level3.net
10 12.123.3.57 tbr1.n54ny.ip.att.net
11 12.122.16.141 cr2.n54ny.ip.att.net
12 12.122.3.38 cr2.wswdc.ip.att.net
13 12.122.1.173 cr1.attga.ip.att.net
14 12.122.28.174 cr2.dlstx.ip.att.net
15 12.122.18.198 tbr2.dlstx.ip.att.net
16 12.123.16.213 br2.dlstx.ip.att.net
17 12.122.255.226 --------------
18 63.241.193.10 mdf001c7613r0003-gig-10-1.dal1.attens.net

Route changed since last log (most recently, 6/26/2008 1:33:31 PM)

Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.1.1 --------------
3 167.206.33.34 dstswr2-vlan2.rh.lybrny.cv.net
4 167.206.33.5 r4-ge9-2.mhe.hcvlny.cv.net
5 64.15.4.37 rtr4-tg11-3.wan.hcvlny.cv.net
6 -
7 -
8 4.68.16.197 ae-43-99.car3.NewYork1.Level3.net
9 4.68.127.150 att-level3-oc192.NewYork1.Level3.net
10 130.117.1.205 te8-6.ccr01.ams03.atlas.cogentco.com
11 12.122.16.141 cr2.n54ny.ip.att.net
12 12.122.3.38 cr2.wswdc.ip.att.net
13 12.122.1.173 cr1.attga.ip.att.net
14 12.122.28.174 cr2.dlstx.ip.att.net
15 12.122.18.198 tbr2.dlstx.ip.att.net
16 12.123.16.213 br2.dlstx.ip.att.net
17 12.122.255.226 --------------
18 63.241.193.10 mdf001c7613r0003-gig-10-1.dal1.attens.net

Route changed since last log (most recently, 6/26/2008 1:33:46 PM)

Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.1.1 --------------
3 167.206.33.34 dstswr2-vlan2.rh.lybrny.cv.net
4 167.206.33.5 r4-ge9-2.mhe.hcvlny.cv.net
5 64.15.4.37 rtr4-tg11-3.wan.hcvlny.cv.net
6 -
7 -
8 130.117.0.53 te9-2.ccr04.jfk02.atlas.cogentco.com
9 4.68.127.150 att-level3-oc192.NewYork1.Level3.net
10 130.117.1.205 te8-6.ccr01.ams03.atlas.cogentco.com
11 130.117.14.102 verio.lon02.atlas.cogentco.com
12 129.250.3.254 as-0.r20.nycmny01.us.bb.gin.ntt.net
13 129.250.2.11 po-3.r03.nycmny01.us.bb.gin.ntt.net
14 129.250.8.42 xe-0.att.nycmny01.us.bb.gin.ntt.net
15 12.122.86.98 tbr1.n54ny.ip.att.net
16 -
17 12.122.3.38 cr2.wswdc.ip.att.net
18 12.122.1.173 cr1.attga.ip.att.net
19 12.122.28.174 cr2.dlstx.ip.att.net
20 12.122.18.198 tbr2.dlstx.ip.att.net
21 12.123.16.213 br2.dlstx.ip.att.net
22 12.122.255.226 --------------
23 63.241.193.10 mdf001c7613r0003-gig-10-1.dal1.attens.net

Route changed since last log (most recently, 6/26/2008 1:35:01 PM)

Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.1.1 --------------
3 167.206.33.34 dstswr2-vlan2.rh.lybrny.cv.net
4 167.206.33.5 r4-ge9-2.mhe.hcvlny.cv.net
5 64.15.4.37 rtr4-tg11-3.wan.hcvlny.cv.net
6 -
7 -
8 130.117.0.53 te9-2.ccr04.jfk02.atlas.cogentco.com
9 4.68.127.150 att-level3-oc192.NewYork1.Level3.net
10 130.117.1.205 te8-6.ccr01.ams03.atlas.cogentco.com
11 130.117.1.46 verio.par04.atlas.cogentco.com
12 129.250.2.144 as-0.r23.londen03.uk.bb.gin.ntt.net
13 -
14 129.250.8.42 xe-0.att.nycmny01.us.bb.gin.ntt.net
15 129.250.2.11 po-3.r03.nycmny01.us.bb.gin.ntt.net
16 -
17 12.122.86.98 tbr1.n54ny.ip.att.net
18 -
19 12.122.3.38 cr2.wswdc.ip.att.net
20 12.122.1.173 cr1.attga.ip.att.net
21 12.122.28.174 cr2.dlstx.ip.att.net
22 -
23 12.123.16.213 br2.dlstx.ip.att.net
24 12.122.255.226 --------------

Route changed since last log (most recently, 6/26/2008 1:35:16 PM)

Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.1.1 --------------
3 167.206.33.34 dstswr2-vlan2.rh.lybrny.cv.net
4 167.206.33.5 r4-ge9-2.mhe.hcvlny.cv.net
5 64.15.4.37 rtr4-tg11-3.wan.hcvlny.cv.net
6 -
7 -
8 130.117.0.53 te9-2.ccr04.jfk02.atlas.cogentco.com
9 154.54.1.22 te4-2.ccr01.par01.atlas.cogentco.com
10 130.117.1.205 te8-6.ccr01.ams03.atlas.cogentco.com
11 130.117.1.46 verio.par04.atlas.cogentco.com
12 129.250.2.144 as-0.r23.londen03.uk.bb.gin.ntt.net
13 -
14 129.250.8.42 xe-0.att.nycmny01.us.bb.gin.ntt.net
15 129.250.2.11 po-3.r03.nycmny01.us.bb.gin.ntt.net
16 -
17 12.122.86.98 tbr1.n54ny.ip.att.net
18 -
19 12.122.3.38 cr2.wswdc.ip.att.net
20 12.122.1.173 cr1.attga.ip.att.net
21 12.122.28.174 cr2.dlstx.ip.att.net
22 -
23 12.123.16.213 br2.dlstx.ip.att.net
24 12.122.255.226 --------------

Route changed since last log (most recently, 6/26/2008 1:36:16 PM)

Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.1.1 --------------
3 167.206.33.34 dstswr2-vlan2.rh.lybrny.cv.net
4 167.206.33.5 r4-ge9-2.mhe.hcvlny.cv.net
5 64.15.4.37 rtr4-tg11-3.wan.hcvlny.cv.net
6 -
7 -
8 130.117.0.53 te9-2.ccr04.jfk02.atlas.cogentco.com
9 154.54.1.22 te4-2.ccr01.par01.atlas.cogentco.com
10 130.117.1.205 te8-6.ccr01.ams03.atlas.cogentco.com
11 130.117.1.46 verio.par04.atlas.cogentco.com
12 129.250.2.144 as-0.r23.londen03.uk.bb.gin.ntt.net
13 154.54.12.82 verio.ord03.atlas.cogentco.com
14 129.250.2.250 xe-4-1.r00.chcgil09.us.bb.gin.ntt.net
15 192.205.35.77
16 -
17 12.122.17.237 cr2.cgcil.ip.att.net
18 12.122.2.22
19 12.122.3.38 cr2.wswdc.ip.att.net
20 12.122.3.221 cr2.dlstx.ip.att.net
21 12.122.28.174 cr2.dlstx.ip.att.net
22 12.123.16.213 br2.dlstx.ip.att.net
23 12.123.16.213 br2.dlstx.ip.att.net
24 63.241.193.10 mdf001c7613r0003-gig-10-1.dal1.attens.net

Route changed since last log (most recently, 6/26/2008 1:36:31 PM)

Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.1.1 --------------
3 167.206.33.34 dstswr2-vlan2.rh.lybrny.cv.net
4 167.206.33.5 r4-ge9-2.mhe.hcvlny.cv.net
5 64.15.4.37 rtr4-tg11-3.wan.hcvlny.cv.net
6 -
7 -
8 130.117.0.53 te9-2.ccr04.jfk02.atlas.cogentco.com
9 154.54.5.249 te2-4.mpd01.bos01.atlas.cogentco.com
10 154.54.6.18 te2-2.mpd01.ord01.atlas.cogentco.com
11 154.54.5.26 vl3488.mpd01.ord03.atlas.cogentco.com
12 154.54.12.82 verio.ord03.atlas.cogentco.com
13 129.250.2.250 xe-4-1.r00.chcgil09.us.bb.gin.ntt.net
14 192.205.35.77
15 12.122.88.18 tbr2.cgcil.ip.att.net
16 12.122.17.237 cr2.cgcil.ip.att.net
17 12.122.2.22 cr2.sl9mo.ip.att.net
18 12.122.2.217 cr1.sl9mo.ip.att.net
19 12.122.3.221 cr2.dlstx.ip.att.net
20 12.122.18.198 tbr2.dlstx.ip.att.net
21 12.123.16.213 br2.dlstx.ip.att.net
22 12.122.255.226 --------------
23 63.241.193.10 mdf001c7613r0003-gig-10-1.dal1.attens.net

Route changed since last log (most recently, 6/26/2008 1:37:16 PM)

Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.1.1 --------------
3 167.206.33.34 dstswr2-vlan2.rh.lybrny.cv.net
4 167.206.33.5 r4-ge9-2.mhe.hcvlny.cv.net
5 64.15.4.37 rtr4-tg11-3.wan.hcvlny.cv.net
6 -
7 -
8 154.54.5.209 te9-2.mpd03.jfk02.atlas.cogentco.com
9 154.54.5.249 te2-4.mpd01.bos01.atlas.cogentco.com
10 154.54.6.18 te2-2.mpd01.ord01.atlas.cogentco.com
11 154.54.5.26 vl3488.mpd01.ord03.atlas.cogentco.com
12 154.54.12.82 verio.ord03.atlas.cogentco.com
13 129.250.2.250 xe-4-1.r00.chcgil09.us.bb.gin.ntt.net
14 192.205.35.77 --------------
15 12.122.88.18 tbr2.cgcil.ip.att.net
16 12.122.17.237 cr2.cgcil.ip.att.net
17 12.122.2.22 cr2.sl9mo.ip.att.net
18 12.122.2.217 cr1.sl9mo.ip.att.net
19 12.122.3.221 cr2.dlstx.ip.att.net
20 12.122.18.198 tbr2.dlstx.ip.att.net
21 12.123.16.213 br2.dlstx.ip.att.net
22 12.122.255.226 --------------
23 63.241.193.10 mdf001c7613r0003-gig-10-1.dal1.attens.net

Route changed since last log (most recently, 6/26/2008 1:37:46 PM)

Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.1.1 --------------
3 167.206.33.34 dstswr2-vlan2.rh.lybrny.cv.net
4 167.206.33.5 r4-ge9-2.mhe.hcvlny.cv.net
5 64.15.4.37 rtr4-tg11-3.wan.hcvlny.cv.net
6 -
7 -
8 130.117.0.53 te9-2.ccr04.jfk02.atlas.cogentco.com
9 154.54.5.249 te2-4.mpd01.bos01.atlas.cogentco.com
10 154.54.6.18 te2-2.mpd01.ord01.atlas.cogentco.com
11 154.54.5.26 vl3488.mpd01.ord03.atlas.cogentco.com
12 154.54.12.82 verio.ord03.atlas.cogentco.com
13 154.54.5.42 vl3494.mpd01.iad01.atlas.cogentco.com
14 192.205.35.77 --------------
15 12.122.88.18 tbr2.cgcil.ip.att.net
16 12.122.17.237 cr2.cgcil.ip.att.net
17 12.122.2.22 cr2.sl9mo.ip.att.net
18 12.122.2.217 cr1.sl9mo.ip.att.net
19 12.122.3.221 cr2.dlstx.ip.att.net
20 12.122.18.198 tbr2.dlstx.ip.att.net
21 12.123.16.213 br2.dlstx.ip.att.net
22 12.122.255.226 --------------
23 63.241.193.10 mdf001c7613r0003-gig-10-1.dal1.attens.net
24 -
25 -
26 -
27 154.54.5.42 vl3494.mpd01.iad01.atlas.cogentco.com

Route changed since last log (most recently, 6/26/2008 1:38:01 PM)

Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.1.1 --------------
3 167.206.33.34 dstswr2-vlan2.rh.lybrny.cv.net
4 167.206.33.5 r4-ge9-2.mhe.hcvlny.cv.net
5 64.15.4.37 rtr4-tg11-3.wan.hcvlny.cv.net
6 -
7 -
8 130.117.0.53 te9-2.ccr04.jfk02.atlas.cogentco.com
9 154.54.5.242 te2-2.ccr02.bos01.atlas.cogentco.com
10 154.54.6.22 te2-2.ccr02.ord01.atlas.cogentco.com
11 154.54.5.10 vl3499.ccr02.ord03.atlas.cogentco.com
12 154.54.3.237 gi9-0-0.core01.ord03.atlas.cogentco.com
13 154.54.5.42 vl3494.mpd01.iad01.atlas.cogentco.com
14 12.123.4.246 tbr1.cgcil.ip.att.net
15 12.122.17.149 cr2.cgcil.ip.att.net
16 12.122.2.22 cr2.sl9mo.ip.att.net
17 12.122.2.217 cr1.sl9mo.ip.att.net
18 12.122.3.221 cr2.dlstx.ip.att.net
19 12.122.18.198 tbr2.dlstx.ip.att.net
20 12.123.16.213 br2.dlstx.ip.att.net
21 12.122.255.226 --------------
22 63.241.193.10 mdf001c7613r0003-gig-10-1.dal1.attens.net
23 -
24 -
25 -
26 154.54.5.42 vl3494.mpd01.iad01.atlas.cogentco.com

Route changed since last log (most recently, 6/26/2008 1:38:16 PM)

Hop IPAddress DNSName
1 192.168.1.1 --------------
2 192.168.1.1 --------------
3 167.206.33.34 dstswr2-vlan2.rh.lybrny.cv.net
4 167.206.33.5 r4-ge9-2.mhe.hcvlny.cv.net
5 64.15.4.13 rtr3-tg11-3.wan.hcvlny.cv.net
6 -
7 -
8 4.68.16.197 ae-43-99.car3.NewYork1.Level3.net
9 4.68.127.150 att-level3-oc192.NewYork1.Level3.net
10 12.123.3.57 tbr1.n54ny.ip.att.net
11 12.122.16.141 cr2.n54ny.ip.att.net
12 12.122.3.38 cr2.wswdc.ip.att.net
13 12.122.1.173 cr1.attga.ip.att.net
14 12.122.28.174 cr2.dlstx.ip.att.net
15 12.122.18.198 tbr2.dlstx.ip.att.net
16 12.123.16.213 br2.dlstx.ip.att.net
17 12.122.255.226 --------------
18 63.241.193.10 mdf001c7613r0003-gig-10-1.dal1.attens.net
19 -
20 -
21 -
22 154.54.5.42 vl3494.mpd01.iad01.atlas.cogentco.com

Re: Lag, Disconnecting in World of Warcraft

Mon, 23 Jun 2008 12:39:58 EDT

ansky08 : I had pretty insanely high ping this weekend. Don't know if it was attributable to bad weather or to the same issue. There haven't been many replies here nor @ the wow forums, I am wondering if the issue is resolved for others.

Re: Lag, Disconnecting in World of Warcraft

Fri, 20 Jun 2008 13:21:42 EDT

ooltech :
Hi All,

This issue is supposedly resolved. Please let us know how it goes this weekend. Thanks.

Re: Lag, Disconnecting in World of Warcraft

Wed, 18 Jun 2008 11:00:04 EDT

anon : If you have lag in the game (and there was quite a bit last night 10:30pm-2am), please:

a.) call OOL tech support, as called-in identical issues will increase visibility of the scope of the problem for OOL and/or
b.) post to the OOLDirect forum (»/forum/ooldirect)

There seem to be WAY too few posts matching that Subject in the OOLDirect forum (I count about 20 posts since May 25th), vastly lower than the number of posts in THIS thread.

What you will be asked for is essentially the same what Blizzard asked for on the relevant forum thread:

- exact start/end time of the lag/disconnects
- if available: your in-game displayed latency (which is WAY off, and has been observed to be minutes behind the actual lagtime :)
- provide OOL IP (go to »whatsmyip.org/) and WoW game server IP
- provide traceroute data at the time of the lag, and if you happen to be the attentive kind that is constantly tracerouting around: a traceroute before and after the lag occurred might be useful.

To find the game server IP:
Start->Run->cmd.exe
run `netstat -n`
Find the line where the "Foreign IP" is x.x.x.x:3724 (that's the WoW TCP game port).
run `tracert x.x.x.x` for that IP

Copy&paste (command shell pulldown menu: Edit->Copy) the result for posting/emailing to support - a tad easier than redirecting it to a file and then looking for it (the way Blizzard suggested to do it)

The standard Windows traceroutes will never complete, because Blizzard's game servers are not replying to tracert's packets - once you see more than 3 hops that show "* * *" (unreachable), you can hit CTRL-C to abort. You can't ping them with a standard Windows ping either - a 'security' choice on Blizzard's part.

You can safely ignore, and stop feeling paniccy about a few routers on OOL's network not responding during the traceroute at all. They are busy forwarding more important packets, and generally don't want to disclose certain interface IPs - move along, nothing to see here :
if interested, google for the traceroute(8) man page, editions 1996 or later, for an explanation that has been unchanged before the majority of today's WoW players were born.

Re: Lag, Disconnecting in World of Warcraft

Tue, 17 Jun 2008 23:47:45 EDT

MLGTWISTED : Tuesday 11:46 pm, June 17th, Huge, huge lag night, disconnects all night. Just got completely cut off, when is it going to end?

Re: Lag, Disconnecting in World of Warcraft

Tue, 17 Jun 2008 22:28:14 EDT

anon : More of the same tonight. Consistent 550ms latency, which spikes to up to 1600ms and can boot me.

Re: Lag, Disconnecting in World of Warcraft

Mon, 16 Jun 2008 16:50:05 EDT

BLUNTED 1 : MLGTWISTED I am getting this on Halo 2 and 3 with OOL also.\

If you got a friend request from I Vyrax I that is a 1 month trial I made so accept if you want

Re: Lag, Disconnecting in World of Warcraft

Sun, 15 Jun 2008 22:32:47 EDT

MLGTWISTED : Im getting strange drop outs when hosting now which I've never had before. World of warcraft is getting up to around 8 disconnects per day, its not fun.

Re: Lag, Disconnecting in World of Warcraft

Sun, 15 Jun 2008 16:06:16 EDT

anon : i think it's them, if you are hosting you get a bunch of requests and they must have something in place to stop the p2p.

Re: Lag, Disconnecting in World of Warcraft

Sun, 15 Jun 2008 15:08:34 EDT

rebecca191 : I played all afternoon on one char, then I played for a few hours in the evening on a different char. No d/cs, and I didn't notice spikes either. My ping on one server has always been higher then the other but both were green pings all day.

Re: Lag, Disconnecting in World of Warcraft

Sun, 15 Jun 2008 09:21:40 EDT

AdamB2K3 : You must have just gotten lucky. How long did you play for and at what time? The problem is still pretty bad for me, every few minutes there is a huge lag spike. I'm not the only one-- this thread on the WoW tech support forum, the majority of replies from cablevision customers, is almost 50 pages long now: »forums.worldofwarcraft.com/threa···pageNo=1

Re: Lag, Disconnecting in World of Warcraft

Sat, 14 Jun 2008 01:17:55 EDT

rebecca191 : I haven't noticed any particular lag today, those thousand ping traceroutes look pretty horrible though :-O I hope mine doesn't come back :(

Re: Lag, Disconnecting in World of Warcraft

Fri, 13 Jun 2008 21:32:33 EDT

BLUNTED 1 : Its not just WOW I get horrible lag on Halo 2 and Halo 3 where my connection goes red bar and when I get host everyone gets red bar connections and the game goes to the reconnecting screen. 2 of my friends with OOL in Suffolk county and the Bronx get this same issue so I wonder WTF they are doing.

Re: Lag, Disconnecting in World of Warcraft

Fri, 13 Jun 2008 17:14:11 EDT

anon : are you in the NYC area? if so,then i believe its just OOL going through some BS. cause i've never had a problem this bad. this is just UN-RELIABLE right now. my pc works fine surfing and downloading,but when i play a GAME,theres a problem. whether i play a GAME on the PC or the PS2/3....the connection is just F'd up lately.

Re: Lag, Disconnecting in World of Warcraft

Fri, 13 Jun 2008 17:04:33 EDT

AdamB2K3 : This is getting ridiculous already.

46 pages and counting

»forums.worldofwarcraft.com/threa···ageNo=46

Re: Lag, Disconnecting in World of Warcraft

Fri, 13 Jun 2008 16:46:18 EDT

audious : Yet another week has come to an end, and we still haven't seen any progress.

Re: Lag, Disconnecting in World of Warcraft

Fri, 13 Jun 2008 02:36:31 EDT

BLUNTED 1 : I can't even do a trace route to all of those IP's you guys did on OOL but on Fios I can.

Re: Lag, Disconnecting in World of Warcraft

Fri, 13 Jun 2008 02:30:36 EDT

anon : Connecting to the server now (with traditional 250-ish ms) but still can't connect to the main website.

I've already established a credit on my account with OOL until they fix this issue or compel Cogent to fix it, I recommend you do the same. Call up billing and tell them you want to cancel your account or expect a full credit (and mean it, no bluffing here please) unless the problem is fixed.

Re: Lag, Disconnecting in World of Warcraft

Fri, 13 Jun 2008 02:19:36 EDT

Wolffstarr : Same issue - trace is pretty much identical to mine on this page. Seems to have cleared now, but the issue is definitely in Cogent Communications territory; I did a reverse from LA using their looking glass on their website and it was blowing up after Chicago and before Toledo, OH.

Re: Lag, Disconnecting in World of Warcraft

Fri, 13 Jun 2008 02:15:21 EDT

martin2x : Happening here as well.

Re: Lag, Disconnecting in World of Warcraft

Fri, 13 Jun 2008 02:14:40 EDT

anon : Same issue. This is getting to be unbelievable...

Re: Lag, Disconnecting in World of Warcraft

Fri, 13 Jun 2008 02:11:05 EDT

anon : yep i can get online but my name is "unknown" and i have 15000ms and the game is pretty much frozen.

as for the site i can't conntect forums, armory and the mainsite it is all a bust.

there are a couple of post on the wow forums about this , and i suggest when we all get decent acess to tell blizzard to get on AT@T/CogentCo about this. cause it freaking bs that we pay $15 a month to play a game whose routing support lags/dcs us.

Re: Lag, Disconnecting in World of Warcraft

Fri, 13 Jun 2008 02:03:06 EDT

Demonio : Same here, at approximately 1-2am EST on 6-13-08 my internet connection went out, but the funny part is when I try to log back into game, thinking everything will be fine, I can't get into WOW and the www.worldofwarcraft.com website or the forums .

This is what a tracert looks like to us.logon.worldofwarcraft.com

G:\>tracert us.logon.worldofwarcraft.com

Tracing route to us.logon.worldofwarcraft.com [12.129.232.111]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 5 ms 6 ms 5 ms 10.240.184.13
3 5 ms 5 ms 5 ms dstswr2-vlan2.rh.nbrgnj.cv.net [67.83.246.162]
4 * * * Request timed out.
5 * * * Request timed out.
6 11 ms 9 ms 9 ms 64.15.0.65
7 * * * Request timed out.
8 71 ms 102 ms 23 ms te9-2.ccr04.jfk02.atlas.cogentco.com [130.117.0.
53]
9 * * * Request timed out.
10 653 ms 658 ms 646 ms te9-2.ccr02.iah01.atlas.cogentco.com [154.54.24.
18]
11 677 ms 678 ms * te3-4.ccr02.lax01.atlas.cogentco.com [154.54.3.1
86]
12 850 ms * 812 ms vl3491.mpd01.lax05.atlas.cogentco.com [154.54.3.
142]
13 * * * Request timed out.
14 681 ms 677 ms 676 ms tbr2.la2ca.ip.att.net [12.123.222.30]
15 * * * Request timed out.
16 * 683 ms 679 ms 12.122.255.74
17 * 682 ms * mdf001c7613r0003-gig-10-1.lax1.attens.net [12.12
9.193.242]
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.

All other websites and online programs are working fine. I even scored 15mbps download and 1.8mbps upload speeds.

Re: Lag, Disconnecting in World of Warcraft

Fri, 13 Jun 2008 01:56:18 EDT

anon : My guild in Sunwell wasn't happy. Hope this log helps OOL fix the issue:
my Hostname: ool-44c11a99(.)dyn(.)optonline(.)net

Tracing route to worldofwarcraft.com [12.129.242.22]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 6 ms 17 ms 7 ms 10.63.64.1
3 7 ms 7 ms 6 ms dstswr1-vlan-2.rh.wmfdnj.cv.net [67.83.252.33]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 9 ms 9 ms 9 ms te9-2.ccr04.jfk02.atlas.cogentco.com [130.117.0.
53]
9 * * 15 ms te2-1.ccr02.dca01.atlas.cogentco.com [154.54.6.1
3]
10 * 642 ms 624 ms te9-2.ccr02.iah01.atlas.cogentco.com [154.54.24.
18]
11 * 659 ms * te4-4.ccr02.lax01.atlas.cogentco.com [66.28.4.23
8]
12 663 ms 663 ms * vl3491.mpd01.lax05.atlas.cogentco.com [154.54.3.
142]
13 * 673 ms 668 ms gr1-a350s3.sffca.ip.att.net [192.205.35.5]
14 675 ms 671 ms 667 ms tbr2.la2ca.ip.att.net [12.123.222.30]
15 666 ms * * 12.127.3.189
16 * 656 ms * 12.122.255.74
17 661 ms 661 ms 673 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.12
9.193.242]
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.

Re: Lag, Disconnecting in World of Warcraft

Fri, 13 Jun 2008 01:55:04 EDT

anon : same with me dude cant even log on or connect to there websight.

Re: Lag, Disconnecting in World of Warcraft

Fri, 13 Jun 2008 01:53:52 EDT

anon : Same here, I'm mad.

Re: Lag, Disconnecting in World of Warcraft

Fri, 13 Jun 2008 01:48:05 EDT

anon : As off about 20 minutes ago, all access has been lost. I briefly connected to a server, with 9000ms, and was booted. The worldofwarcraft.com site is also completely unavailable.

Re: Lag, Disconnecting in World of Warcraft

Fri, 13 Jun 2008 01:42:44 EDT

anon : Here's my traceroute at 1:40 est

Tracing route to us.logon.worldofwarcraft.com [12.129.224.112]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 8 ms 8 ms 9 ms 10.90.160.1
3 8 ms 12 ms 8 ms dstswr1-vlan2.rh.jcsnnj.cv.net [67.83.247.33]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 13 ms 11 ms 11 ms te9-2.mpd03.jfk02.atlas.cogentco.com [154.54.5.2
09]
9 18 ms 18 ms 17 ms te2-1.mpd01.dca01.atlas.cogentco.com [154.54.6.5
]
10 * 623 ms * te7-3.mpd01.iah01.atlas.cogentco.com [154.54.2.2
46]
11 * * * Request timed out.
12 649 ms * 642 ms te4-1.ccr01.phx02.atlas.cogentco.com [154.54.1.1
66]
13 663 ms 658 ms * te4-1.ccr01.san01.atlas.cogentco.com [154.54.7.8
6]
14 * 651 ms * te4-1.ccr01.sna02.atlas.cogentco.com [154.54.25.
125]
15 692 ms 679 ms 684 ms te3-4.mpd01.lax01.atlas.cogentco.com [154.54.3.3
8]
16 * 672 ms * vl3493.mpd01.lax05.atlas.cogentco.com [154.54.6.
230]
17 679 ms * * gr1-a350s3.sffca.ip.att.net [192.205.35.5]
18 685 ms * * tbr2.la2ca.ip.att.net [12.123.222.46]
19 671 ms 673 ms 676 ms 12.127.3.189
20 * 682 ms 682 ms 12.122.255.74
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.

Re: Lag, Disconnecting in World of Warcraft

Thu, 12 Jun 2008 18:09:06 EDT

Quba : you guys were right, and i was wrong. the problem SUPPOSEDLY was signal interference in my area. I received a call from a OOL supervisor and was informed that the cable lines in my area ALL needed to be balanced. i wait till tonight to find lag so i can kill a tech via phone. lol Best suggestion to you guys is getting in contact with a supervisor and stressing the situation, they will do what they can.

edit:

they didnt fix anything, i was decieved with 1 night of fine internet and a phone call the day after asking how my service was the night before. Talk about feeling bamboozled. WOW....

Re: Lag, Disconnecting in World of Warcraft

Thu, 12 Jun 2008 08:32:00 EDT

audious : The problem still hasn't been resolved.

/bump

Re: Lag, Disconnecting in World of Warcraft

Wed, 11 Jun 2008 19:47:03 EDT

Lightmgl : I felt my issue was relevant because it is the same physical location as the World of Warcraft servers. It is likely a problem with routing or connections to that area, not just Warcraft so I hoped maybe it would help bring light to it.

Re: Lag, Disconnecting in World of Warcraft

Wed, 11 Jun 2008 15:52:20 EDT

ansky08 : The difference is - when we have lag spikes in WoW, our ventrilo and web browsing are fine. In fact, when I spike in WoW, I and the 2 other people who use OOL in my guild all say "I'm lagging, this sucks. Ok now I'm back."

From what you say, I don't think you have the same symptoms

Re: Lag, Disconnecting in World of Warcraft

Wed, 11 Jun 2008 13:13:07 EDT

TheWiseGuy : No, they are not exactly the same. Most of the posters have a good connection except on certain routes outside the OOL network. You are showing what appears to be localized packet loss, though it is hard to tell from the inbound trace. Many of the posters can run traces which do not show latency but get intermittent lag.

You can simply say it is the same problem, but when their problem is fixed you may very well still have a problem. As suggested more diagnostic on your problem would be advantageous to make certain it is not simply a routing problem off the OOL network.
--
Warning, If you post nonsense and use misinformation and are here to argue based on those methods, you will be put on ignore.

Re: Lag, Disconnecting in World of Warcraft

Wed, 11 Jun 2008 13:09:23 EDT

frdrizzt : This topic is "Lag, Disconnecting in World of Warcraft". Your problem is "Lag, Disconnecting in general". I'm not marginalizing your issue, I'm telling you that if you want help with a general connection, this topic is not going to help you. (edit: Though it sounds like you may need a tech visit - just try with seperate devices connected to the modem & no router to be sure it's not a problem with your network card.)

Re: Lag, Disconnecting in World of Warcraft

Wed, 11 Jun 2008 12:59:13 EDT

Quba : Just because i have not been playing WOW does not mean the issue is irrelevant. The symptoms are exactly the same....

From the hours of 9pm-1am theres high packet loss of 1000-3000MS in which its only remedy is to wait. I've replaced everything possible on my end from removing splitters to replacing the modem. And the packet loss does not only refer to Games but to any web browsing, there is significant loss. If only FIOS was available in the area.

Re: Lag, Disconnecting in World of Warcraft

Wed, 11 Jun 2008 12:35:21 EDT

frdrizzt : Sounds like you're having problems unrelated to this topic. You may want to create your own or post to the direct forum if you're having packet loss problems.

Re: Lag, Disconnecting in World of Warcraft

Wed, 11 Jun 2008 11:27:20 EDT

Quba : incorrect, i was having huge disconnect problems with Ventrilo Chat as well as Counter-Strike. I live in Union County, NJ and after finding that i was still recieving packet loss and D/c.. i came to the conclusion of running a line quality test.

»/linequality/nil/2394630

It's nice to find out im 150ms to my FIRST hop.

its not OOLs fault? seems like a bunch of bullsnap to me.

Re: Lag, Disconnecting in World of Warcraft

Wed, 11 Jun 2008 09:49:18 EDT

audious : Yes, last night was fine.

Did we get rerouted?

Did they feed the hamster?

Re: Lag, Disconnecting in World of Warcraft

Wed, 11 Jun 2008 09:22:06 EDT

ansky08 : surprisingly, last night, I did not get the crazy latency and disconnects. knock on wood - hopefully things are wrapping up

Re: Lag, Disconnecting in World of Warcraft

Tue, 10 Jun 2008 23:45:19 EDT

anon : All,

If you read the official WoW forums you'll see that it is not just OOL that is having this issue.

OOL has investigates all provided trace routes, and will continue to, but still sees the issue with AT&T and Cogentco.

They're working on it, trust me.. lots of the people who you complain to also play WoW.

There has been an innormous amount of complains with this, as you all can understand, it's major. But it's not just OOL, it's also Verizon, Time Warner, Cox Cable. Do the research and you'll see.

Even though it might not be OOL's "fault", they are still trying to work for a resolution to solve atleast their customers.

I would stop being so "hostile" towards OOL, as if it was them who caused all ISP's to have the same issue.

Re: Lag, Disconnecting in World of Warcraft

Tue, 10 Jun 2008 22:44:15 EDT

Quba : yes unfortunately, this problem is not only with WOW, as it is happening with all of OOL's routing at this time. It appears CongestedCo lacks superior hardware and really stresses routers during peak hours. Im really glad that i came onto the forums because it's been a fight between me and OOL for the last 2 weeks. Lol, i've had more than 7 phone techs take logs of my intermittent lag and about 3 house visits, in which OOL keeps sending the SAME incompetent tech. I guess the best thing we can do is keep calling and pointing out that there is a routing issue. ALL I WANNA DO IS FRAG, WHY!

Re: Lag, Disconnecting in World of Warcraft

Tue, 10 Jun 2008 17:19:57 EDT

anon :
Tracing route to us.logon.worldofwarcraft.com [12.129.232.112]

over a maximum of 30 hops:

1 6 ms 5 ms 5 ms 10.103.32.1

2 5 ms 5 ms 6 ms dstswr1-vlan2.rh.prnynj.cv.net [67.83.242.33]

3 * * * Request timed out.

4 * * * Request timed out.

5 * * * Request timed out.

6 * * * Request timed out.

7 9 ms 7 ms 7 ms vl3496.mpd03.jfk02.atlas.cogentco.com [154.54.6.49]

8 15 ms 13 ms 13 ms te7-3.mpd01.dca01.atlas.cogentco.com [154.54.3.45]

9 44 ms 39 ms 39 ms te7-3.mpd01.iah01.atlas.cogentco.com [154.54.2.246]

10 74 ms 74 ms 73 ms te7-4.mpd01.lax01.atlas.cogentco.com [154.54.2.198]

11 76 ms 75 ms 74 ms vl3492.mpd01.lax05.atlas.cogentco.com [154.54.3.10]

12 76 ms 75 ms 74 ms gr1-a350s3.sffca.ip.att.net [192.205.35.5]

13 75 ms 75 ms 76 ms tbr2.la2ca.ip.att.net [12.123.222.46]

14 75 ms 75 ms 74 ms 12.127.3.189

15 74 ms 75 ms 76 ms 12.122.255.74

16 77 ms 75 ms 75 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]

17 * * * Request timed out.

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.

Re: Lag, Disconnecting in World of Warcraft

Tue, 10 Jun 2008 16:46:25 EDT

dantheman815 : Bump Heres my Tracert:

Tracing route to 206.16.23.106 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.1.1
2 7 ms 18 ms 15 ms 10.29.128.1
3 11 ms 7 ms 11 ms dstswr2-vlan2.rh.stjmny.cv.net [167.206.39.162]

4 10 ms 11 ms 13 ms rtr4-ge1-10.mhe.hcvlny.cv.net [167.206.39.137]
5 10 ms 9 ms 12 ms rtr4-tg11-3.wan.hcvlny.cv.net [64.15.4.37]
6 * * * Request timed out.
7 * * * Request timed out.
8 11 ms 14 ms 11 ms vl3491.ccr04.jfk02.atlas.cogentco.com [154.54.7.
9]
9 16 ms 31 ms 17 ms te8-2.ccr02.dca01.atlas.cogentco.com [66.28.4.12
6]
10 20 ms 29 ms 17 ms vl3493.mpd01.dca02.atlas.cogentco.com [154.54.7.
230]
11 17 ms 27 ms 17 ms vl3497.mpd01.iad01.atlas.cogentco.com [154.54.5.
66]
12 25 ms 18 ms 18 ms 192.205.35.105
13 60 ms 63 ms 58 ms tbr2.wswdc.ip.att.net [12.123.8.134]
14 63 ms 62 ms 61 ms cr2.wswdc.ip.att.net [12.122.16.93]
15 59 ms 62 ms 77 ms cr1.attga.ip.att.net [12.122.1.173]
16 59 ms 62 ms 60 ms cr2.dlstx.ip.att.net [12.122.28.174]
17 63 ms 64 ms 62 ms tbr2.dlstx.ip.att.net [12.122.18.238]
18 59 ms 57 ms 58 ms br2.dlstx.ip.att.net [12.123.16.213]
19 58 ms 60 ms 58 ms mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255
.78]
20 58 ms 58 ms 58 ms mdf002fbi8ks0001-eth-1-3.dal1.attens.net [63.241
.192.122]
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.

Re: Lag, Disconnecting in World of Warcraft

Tue, 10 Jun 2008 14:17:29 EDT

Pizz : can you try running a tracert to www.everquest.com and post the results, im curious how you're routed. Their servers are on the west coast as well.

Re: Lag, Disconnecting in World of Warcraft

Tue, 10 Jun 2008 11:10:29 EDT

Lightmgl : Just wanted to add into this that it is not only World of Warcraft. I have been experiencing the exact same symptoms, generally during peak hours (6pm to 11pm est) on all of Nexon's games. Nexon is based in Los Angeles, and while I don't have traceroutes on hand at the moment, the ones I have done in the past showed massive packetloss and 3000-5000 pings on Internap and ATT Los Angeles nodes when the packetloss occurs.

Dunno if its directly related to the WoW issue or just similar, but this could be an issue with lag and packetloss to the entire Los Angeles region? I know alot of the Blizzard servers used to route through Internap along with ATT. There were issues back in January like this and supposedly Blizzard took care of it on their end somehow. It seems now both ATT and Internap are giving people trouble through a couple of ISPS (Time Warner, Optimum, and Roadrunner) as there have been threads on the WoW forums the last few days about it. I wonder if Blizzard's "fix" in January was to remove Internap from the equation as I go through Cogentco now and I did not used to. The whole system out there has something wrong.

These issues started appoximatly 1 month ago, prior to then there were no issues.

Re: Lag, Disconnecting in World of Warcraft

Mon, 09 Jun 2008 13:37:36 EDT

audious : So who isn't paying their bills on time? Blizzard? Optimum? The fact is WE ARE, to both companies.

We want answers.

Re: Lag, Disconnecting in World of Warcraft

Mon, 09 Jun 2008 12:40:09 EDT

mute11 : I wouldn't expect this to be the latter situation, unless a contract just expired, as this is a new issue dating back only about a month. Hell, if this had been the case from day one I doubt anyone would still be playing from the affected areas.

Re: Lag, Disconnecting in World of Warcraft

Mon, 09 Jun 2008 12:37:23 EDT

Pizz : This is from a ATT Tech who works at the LA Noc. It showed the problem, and blizzard *gasp* actually looked into the issue, and my latency is fine again.

Do a end to end ping with the port of the server being used - 3724 - if the ping comes back fine, than its not their server's problem. But if it comes back with very high latency, its a problem on their end. Usually it's a peering problem with Cogent and their ISP ATT.

Also, certain peers incoming on a backbone that isnt 'paid', will get lowest priority during peak-times. So if cogent doesnt have a good relationship with ATT (I.E. Mutual peering or paid) latency like this will occur.

Re: Lag, Disconnecting in World of Warcraft

Mon, 09 Jun 2008 12:30:46 EDT

mute11 : I'd suggest joining this yahoo group and getting the issue noticed there, as well. It's a support group frequented by some very high level Cablevision employees, like the CTO.

»finance.groups.yahoo.com/group/lioptonline/

Re: Lag, Disconnecting in World of Warcraft

Mon, 09 Jun 2008 12:24:35 EDT

JDCMAN : Look, complain to Cablevision, complain to WoW, and it couldn't hurt to write a nasty email to level3 (or wherever the hop goes bad). The squeaky wheel gets the oil, you know.

Re: Lag, Disconnecting in World of Warcraft

Mon, 09 Jun 2008 12:15:04 EDT

ansky08 : if Verizon is reliable once it arrives, I'm cancelling OOL and not looking back. You'd think in this day and age, with hundreds of complaints, something would get done in a reasonable amount of time. Companies pointing fingers at each other doesn't solve the problem.

Re: Lag, Disconnecting in World of Warcraft

Mon, 09 Jun 2008 11:29:11 EDT

audious : Here is a thread from LAST YEAR. Seems this isn't the first time this nonsense is happening.

»forums.worldofwarcraft.com/threa···19&sid=1

I'm furious.

Re: Lag, Disconnecting in World of Warcraft

Mon, 09 Jun 2008 11:01:33 EDT

audious : Time Warner Clients are getting the same bad hop.

Tracing route to us.logon.worldofwarcraft.com [12.129.232.116]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 86 ms 38 ms 68 ms gig-5-1-nycmnyw-rtr2.nyc.rr.com [24.29.97.77]
4 47 ms 39 ms 64 ms pos-0-0-nycmnyw-rtr1.nyc.rr.com [24.29.101.241]

5 77 ms 94 ms 97 ms pos-6-2-nycmnyrdc-rtr1.nyc.rr.com [24.29.119.29]

6 80 ms 77 ms 97 ms gig1-0-0-nwrknjmd-rtr1.nyc.rr.com [24.29.130.182
]
7 57 ms 36 ms 86 ms te-4-3.car1.Newark1.Level3.net [4.79.188.113]
8 63 ms 106 ms 105 ms ae-31-55.ebr1.Newark1.Level3.net [4.68.99.158]
9 95 ms 86 ms 71 ms ae-2.ebr1.NewYork1.Level3.net [4.69.132.97]
10 39 ms 54 ms 37 ms ae-81-81.csw3.NewYork1.Level3.net [4.69.134.74]

11 57 ms 81 ms 49 ms ae-33-89.car3.NewYork1.Level3.net [4.68.16.133]

12 * * * Request timed out.
13 113 ms 115 ms 115 ms tbr1.n54ny.ip.att.net [12.123.0.90]
14 113 ms 114 ms 113 ms cr2.n54ny.ip.att.net [12.122.16.149]
15 119 ms 120 ms 129 ms cr2.wswdc.ip.att.net [12.122.3.38]
16 137 ms 153 ms 135 ms cr1.attga.ip.att.net [12.122.1.173]
17 171 ms 141 ms 163 ms cr2.dlstx.ip.att.net [12.122.28.174]
18 148 ms 141 ms 149 ms cr2.la2ca.ip.att.net [12.122.28.178]
19 154 ms 154 ms 154 ms tbr2.la2ca.ip.att.net [12.122.19.206]
20 154 ms 160 ms 190 ms 12.127.3.189
21 124 ms 144 ms 134 ms 12.122.255.74
22 135 ms 141 ms 135 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.12
9.193.242]
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.

---------------------------------------------------------------------------------- ----------------------------------------------
Tracing route to us.logon.worldofwarcraft.com [12.129.224.110]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 26 ms 11 ms 19 ms gig-5-1-nycmnyw-rtr2.nyc.rr.com [24.29.97.77]
4 24 ms 26 ms 20 ms pos-5-0-nycmnyrdc-rtr2.nyc.rr.com [24.29.119.26]

5 22 ms 29 ms 20 ms tenge-0-0-0-nycsnyoo-rtr1.nyc.rr.com [24.29.119.
102]
6 36 ms 10 ms 14 ms te-4-1.car3.NewYork1.Level3.net [4.78.182.45]
7 38 ms 43 ms 42 ms ggr2-p360.n54ny.ip.att.net [192.205.33.93]
8 149 ms 142 ms 140 ms tbr1.n54ny.ip.att.net [12.123.0.90]
9 145 ms 139 ms 131 ms cr2.n54ny.ip.att.net [12.122.16.149]
10 147 ms 135 ms 144 ms cr2.wswdc.ip.att.net [12.122.3.38]
11 159 ms 155 ms 151 ms cr1.attga.ip.att.net [12.122.1.173]
12 173 ms 163 ms 160 ms cr2.dlstx.ip.att.net [12.122.28.174]
13 155 ms 179 ms 164 ms cr2.la2ca.ip.att.net [12.122.28.178]
14 148 ms 162 ms 157 ms tbr2.la2ca.ip.att.net [12.122.19.214]
15 160 ms 157 ms 159 ms 12.127.3.189
16 135 ms 120 ms 126 ms 12.122.255.74
17 118 ms 123 ms 121 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.12
9.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.

Re: Lag, Disconnecting in World of Warcraft

Mon, 09 Jun 2008 10:03:03 EDT

ansky08 : been having lag spike issues for about 3 weeks now. some nights are OK, some nights are just downright terrible.

ordered Verizon DSL - huge step down in speed, but if it's reliable, it is the clear winner.

kind of stinks to disconnect during Kil'jaeden multiple times

Re: Lag, Disconnecting in World of Warcraft

Mon, 09 Jun 2008 09:55:51 EDT

audious : Perhaps we're not informing the right people of this ongoing issue. I intend on calling customer support and contacting supervisors when I get home. We've provided more than enough trace routes to blizzard and OOL, and no one seems to be any closer to a solution.

Re: Lag, Disconnecting in World of Warcraft

Mon, 09 Jun 2008 08:08:54 EDT

AdamB2K3 : I am still having the same problem with lag spikes, and I am not seeing any extra hops on my way to the same server as previously. There is a 35 page thread on the World of Warcraft forums here: »forums.worldofwarcraft.com/threa···ageNo=35 regarding this problem. As long as that thread keeps growing every day, the problem is not resolved.

Re: Lag, Disconnecting in World of Warcraft

Mon, 09 Jun 2008 06:40:37 EDT

audious : I got dc'd 5 times in BT last night. The problem is definitely not gone.

Re: Lag, Disconnecting in World of Warcraft

Mon, 09 Jun 2008 01:19:52 EDT

rebecca191 : I had no problems at all during a full BT clear except for 350 ping for a grand total of one minute.... no spikes, nothing. I did check a trace and I'm seeing an extra hop so maybe routing in my area got changed, I don't know.

Re: Lag, Disconnecting in World of Warcraft

Sun, 08 Jun 2008 22:19:38 EDT

JDCMAN : Any issues on other sites (like Youtube)? I had tons of problems for two weeks with Youtube and Xbox Live, then performance came back better than before. Maybe it has something to do with network routes & the new expresslink they're talking about?

EDIT: Tracerts to Youtube servers show it ends with Cogentco, back when I was having YT issues it died in cogent territory too.

Re: Lag, Disconnecting in World of Warcraft

Sun, 08 Jun 2008 21:57:06 EDT

audious : It's back tonight. Just DC'd twice. Still no official response or recognition on a large scale.

Re: Lag, Disconnecting in World of Warcraft

Sun, 08 Jun 2008 01:22:22 EDT

anon : I just started experiencing this problem on 6/3 in Morris County, NJ. While playing alone, I often get large lag spikes but I can continue playing. While in 5 man groups, I get spikes sometimes followed by a disconnect. And while in 25-man content, I always disconnect after a spike.

I was doing some testing with 3d traceroute and while the game told me I was at 1200ms latency, the traceroute program picked up no latency changes in the path to the server. Like others, hops 4,5,6, and 7 don't respond.

I'm not buying the "It's AT&T or CogentCo's problem" considering I have yet to find any other post about other ISPs having this problem. I can't help but think this is some packet shaping initiative screw up.

Re: Lag, Disconnecting in World of Warcraft

Sun, 08 Jun 2008 01:18:01 EDT

anon : I’ve been experiencing lag and service interruptions all last week and very bad today and especially this evening. I can’t even play poker on line never mind WOW. I’m in North Western NJ. Like most big companies don’t expect the truth when you contact them. I can’t be bothered with calling them. That is what competition is for,

Eddie

Re: Lag, Disconnecting in World of Warcraft

Sun, 08 Jun 2008 00:50:34 EDT

BLUNTED 1 : I am also having issues in Halo 2 and Halo 3 in Nassau county NY which is right next to Franklin Square when using OOL but My Fios seems to be fine on the same games.

Re: Lag, Disconnecting in World of Warcraft

Sun, 08 Jun 2008 00:29:52 EDT

audious : Bump.

Any chance we could get an update on the situation?

Re: Lag, Disconnecting in World of Warcraft

Sat, 07 Jun 2008 06:46:22 EDT

anon : This is not specific to WOW my friends. I am also experiencing lag spikes in COD 1, 2, and 4 here in Woodmere, NY. My nephew is having the same issue in Final fantasy 11 on a different UBR in Franklin Square, NY. Same exact issues, different games and UBR's. It seems every 10 minutes or so of gameplay, their is a spike, where your ping goes to 999 as if you are disconnecting, then it eventuslly restores itself after a few seconds back to normal ping times between 40 to 50ms. I know the server I connect to with COD is located in Toronto, CAN. This has been happening for about 2 weeks or so now.

We do not notice any isue when just browsing the internet, but it is very noticeable in gaming. So I doubt this is related to a specific server or servers that are hosting, but most definately a routing issue as you mention. I am sure OOL tech support are receiving plenty of calls in relation to this issue and I am surprised they are not aware of any issue, but then again, the techs are usually left in the dark with matters such as this with experience to similar issues in the past. If it is occurring outside the network, their is not much they can do. I will run a tracert as well to see where the affected router is located as well and post back later.....hope this is resolved sometime soon.

Re: Lag, Disconnecting in World of Warcraft

Fri, 06 Jun 2008 19:37:22 EDT

anon : Here's my conversation audios,

"Good evening,

I was told by my ISP as well as my game manufacturer (Blizzard) to contact the other in order to resolve some situation currently being experienced by every customer of Cablevision's Optimum Online that is attempting to play the Blizzard game World of Warcraft. However, each seems to feel that neither is at fault because, according to the tracerts of everyone responding to the topics located

Lag, Disconnecting in World of Warcraft

and

forums.worldofwarcraft.com/threa···pageNo=1

we seem to be running into our problem at one of your servers. For reference, I am attaching my tracert as a .txt document, but I will also take a snippet from it where the "lag" appears to be occurring.

3 12 ms 9 ms 11 ms dstswr1-vlan2.rh.rndhnj.cv.net [67.83.249.161]

4 * * * Request timed out.

5 * * * Request timed out.

6 * * * Request timed out.

7 * * * Request timed out.

8 17 ms 11 ms 11 ms vl3492.mpd03.jfk02.atlas.cogentco.com [154.54.7.13]

I'm quite sorry that I'm contacting you as I'm not currently a paying customer of yours, however any information that can be shared on this situation by you or your people would be greatly appreciated. As it stands right now, World of Warcraft is nearly unplayable for most of the East Coast using Optimum Online as we are being routed through your servers.

Thank you and I appreciate any and all replies."

Re: Lag, Disconnecting in World of Warcraft

Fri, 06 Jun 2008 19:27:41 EDT

AdamB2K3 :

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.

Re: Lag, Disconnecting in World of Warcraft

Fri, 06 Jun 2008 19:04:49 EDT

audious : Posted twice. Apologies.

Re: Lag, Disconnecting in World of Warcraft

Fri, 06 Jun 2008 18:56:51 EDT

audious : I did. After speaking to a tech at Cogentco, I was told to forward the traceroute. I encourage everyone on these boards to the same.

1-877-875-4432
Ask to speak to tech support or Customer Service. They will most likely give you an email address, which is:
support@cogentco.com

Here was my email to them.

We are being told by our ISP that the lag/latency/disconnects we're experiencing is being cause on Cogentco. The tech that I spoke to at Cogent was not aware of any issues.
Any help would be greatly appreciated. I'm sure I speak for thousands of people on the eastern seaboard. :P

Here is the OOL tech support thread :

»Lag, Disconnecting in World of Warcraft

Here is the official wow forums tech support thread (one of many)

»forums.worldofwarcraft.com/threa···pageNo=1

Here is a trace route.

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.

Re: Lag, Disconnecting in World of Warcraft

Fri, 06 Jun 2008 18:27:24 EDT

anon : 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."

Re: Lag, Disconnecting in World of Warcraft

Fri, 06 Jun 2008 18:17:51 EDT

rebecca191 : 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.

Re: Lag, Disconnecting in World of Warcraft

Fri, 06 Jun 2008 18:09:58 EDT

audious : 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? :D
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. :D
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."

Re: Lag, Disconnecting in World of Warcraft

Fri, 06 Jun 2008 15:18:05 EDT

audious : 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.

Re: Lag, Disconnecting in World of Warcraft

Fri, 06 Jun 2008 14:13:41 EDT

anon : So what do we have to do, to get someone to contact Crapogent?!

Re: Lag, Disconnecting in World of Warcraft

Fri, 06 Jun 2008 14:05:35 EDT

DownLow : Heh...

"There are currently around 150 people in this call center that all play and are being affected as well."

I assume they are all playing during work hours..might explain the wonderful Cablevision customer service!!!

:D :D :D :D :D :D :D
--
Cleverly Disguised As A Responsible Adult!

Re: Lag, Disconnecting in World of Warcraft

Fri, 06 Jun 2008 13:48:13 EDT

anon : 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

Re: Lag, Disconnecting in World of Warcraft

Fri, 06 Jun 2008 12:56:00 EDT

anon : 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.

Re: Lag, Disconnecting in World of Warcraft

Fri, 06 Jun 2008 12:13:48 EDT

frdrizzt : 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.

Re: Lag, Disconnecting in World of Warcraft

Thu, 05 Jun 2008 22:06:31 EDT

anon : 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.........

Re: Lag, Disconnecting in World of Warcraft

Thu, 05 Jun 2008 21:55:29 EDT

rebecca191 : Or they could just be dumb phone tech people. Hard to say.

Re: Lag, Disconnecting in World of Warcraft

Thu, 05 Jun 2008 21:52:52 EDT

anon : 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.

Re: Lag, Disconnecting in World of Warcraft

Thu, 05 Jun 2008 21:39:36 EDT

rebecca191 : 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?

Re: Lag, Disconnecting in World of Warcraft

Thu, 05 Jun 2008 21:33:49 EDT

anon : any luck? do you have the IP of the offending router or is it more than one?

Re: Lag, Disconnecting in World of Warcraft

Thu, 05 Jun 2008 20:50:19 EDT

rebecca191 : I'm trying to get a tech at OOL who has the authority to open a ticket or report the problem to Cogentco.

Re: Lag, Disconnecting in World of Warcraft

Thu, 05 Jun 2008 20:48:12 EDT

anon : Yes, any phone call to tech support would get as far as 'what's your account number'.

Re: Lag, Disconnecting in World of Warcraft

Thu, 05 Jun 2008 20:45:50 EDT

rebecca191 : I have their phone number around here somewhere, I just don't see the point in calling them since I'm not their customer.

Re: Lag, Disconnecting in World of Warcraft

Thu, 05 Jun 2008 20:40:33 EDT

anon : 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

Re: Lag, Disconnecting in World of Warcraft

Thu, 05 Jun 2008 20:05:00 EDT

rebecca191 : 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?

Re: Lag, Disconnecting in World of Warcraft

Thu, 05 Jun 2008 19:59:07 EDT

anon : 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.

Re: Lag, Disconnecting in World of Warcraft

Thu, 05 Jun 2008 18:13:43 EDT

rebecca191 : 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

Re: Lag, Disconnecting in World of Warcraft

Thu, 05 Jun 2008 18:09:34 EDT

anon : Using 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.

Re: Lag, Disconnecting in World of Warcraft

Thu, 05 Jun 2008 18:07:44 EDT

anon : 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.

Re: Lag, Disconnecting in World of Warcraft

Thu, 05 Jun 2008 17:51:32 EDT

rebecca191 : 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.

Re: Lag, Disconnecting in World of Warcraft

Thu, 05 Jun 2008 17:33:56 EDT

TheWiseGuy : 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.

Re: Lag, Disconnecting in World of Warcraft

Thu, 05 Jun 2008 17:17:35 EDT

anon : 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.

Re: Lag, Disconnecting in World of Warcraft

Thu, 05 Jun 2008 14:44:39 EDT

rebecca191 : 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.

Re: Lag, Disconnecting in World of Warcraft

Wed, 04 Jun 2008 21:56:55 EDT

anon : 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

Re: Lag, Disconnecting in World of Warcraft

Wed, 04 Jun 2008 19:03:40 EDT

ansky08 : -deleted post-

Re: Lag, Disconnecting in World of Warcraft

Wed, 04 Jun 2008 18:01:22 EDT

DownLow : 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!

Re: Lag, Disconnecting in World of Warcraft

Wed, 04 Jun 2008 17:27:25 EDT

TheWiseGuy :

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.

Re: Lag, Disconnecting in World of Warcraft

Wed, 04 Jun 2008 16:53:25 EDT

anon : 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.

Re: Lag, Disconnecting in World of Warcraft

Wed, 04 Jun 2008 16:21:58 EDT

anon : 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.

Re: Lag, Disconnecting in World of Warcraft

Tue, 03 Jun 2008 22:40:30 EDT

anon : My tracert, pretty horrible, when will this be fixed?!

Re: Lag, Disconnecting in World of Warcraft

Tue, 03 Jun 2008 22:15:48 EDT

anon : 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.

Re: Lag, Disconnecting in World of Warcraft

Sun, 01 Jun 2008 22:57:10 EDT

aree : 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.

Re: Lag, Disconnecting in World of Warcraft

Sun, 01 Jun 2008 21:47:02 EDT

StreetSpirit : 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. :)

Tracing route to worldofwarcraft.com [12.129.242.22]over a maximum of 30 hops:   1    <1 ms    <1 ms    <1 ms  192.168.1.1  2     7 ms     6 ms     7 ms  10.27.64.1  3     8 ms    19 ms    10 ms  dstswr2-vlan2.rh.nyk2ny.cv.net [67.83.220.162]  4     8 ms    11 ms     8 ms  ool-4353dc8d.dyn.optonline.net [67.83.220.141]  5    10 ms     9 ms     7 ms  rtr4-tg11-3.wan.hcvlny.cv.net [64.15.4.37]  6     *        *        *     Request timed out.  7     *        *        *     Request timed out.  8    10 ms    13 ms    27 ms  te9-2.mpd03.jfk02.atlas.cogentco.com [154.54.5.209]  9    18 ms    17 ms    17 ms  te2-1.mpd01.dca01.atlas.cogentco.com [154.54.6.5] 10    45 ms    42 ms    44 ms  te7-3.mpd01.iah01.atlas.cogentco.com [154.54.2.246] 11    77 ms    81 ms    81 ms  te7-4.mpd01.lax01.atlas.cogentco.com [154.54.2.198] 12    81 ms    77 ms    78 ms  vl3493.mpd01.lax05.atlas.cogentco.com [154.54.6.230] 13    78 ms    77 ms    77 ms  gr1-a350s3.sffca.ip.att.net [192.205.35.5] 14    79 ms    87 ms    81 ms  tbr2.la2ca.ip.att.net [12.123.222.38] 15    79 ms    78 ms    78 ms  12.127.3.189 16    77 ms    77 ms    78 ms  12.122.255.74 17   255 ms   208 ms   236 ms  mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]  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.

Look at hop #17 - AT&T's shines through once again. :)

Re: Lag, Disconnecting in World of Warcraft

Sun, 01 Jun 2008 21:34:07 EDT

anon : 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.

Re: Lag, Disconnecting in World of Warcraft

Sun, 01 Jun 2008 21:14:29 EDT

anon : Optimum Online engineers pls look into this problem with better tools than a tracert. 4000 latency makes it impossible to stay connected!!!!!!!!!

Re: Lag, Disconnecting in World of Warcraft

Thu, 29 May 2008 14:26:20 EDT

anon : 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.

Re: Lag, Disconnecting in World of Warcraft

Wed, 28 May 2008 19:00:29 EDT

anon : 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).

Re: Lag, Disconnecting in World of Warcraft

Wed, 28 May 2008 16:31:54 EDT

ooltech : 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

Re: Lag, Disconnecting in World of Warcraft

Wed, 28 May 2008 14:19:18 EDT

MLGTWISTED : I also have been getting alot of lag and disconnect problems specifically with wow, I hope the problem smooths out soon.

Re: Lag, Disconnecting in World of Warcraft

Wed, 28 May 2008 13:01:54 EDT

ooltech : 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**

Re: Lag, Disconnecting in World of Warcraft

Wed, 28 May 2008 12:44:28 EDT

frdrizzt : 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).

Lag, Disconnecting in World of Warcraft

Tue, 27 May 2008 17:00:25 EDT

ansky08 : 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?