For the past week or two, I've been experience terrible lags at certain times that would at times disconnect me from play. By bad, I'm talking about 250ms at BEST, but usually ~300ms and spikes upward to ~3000ms, then dropping back down to ~1300ms for a while before dropping again to 200-300ms.

In this situation, I've lost arena games that we could've won, and my team is afraid to queue me up for games.
In addition, after queuing for AV which is a ridiculous 2-hour queue, I disconnect after a sudden lag spike and for some reason when i load back on, the load screen is very slow and when I enter I am outside AV back at the battle master.

In essence, this ridiculous lag is really started to inhibit my wow play performance. I have friends who are on this ISP as well who experience the same thing at times (a lot of times when I am too).




Here is my tracert results (Jan 09, 2008, Illidan US, 10:20EST, ~1300ms when tracert started):

Tracing route to 63.241.255.110 over a maximum of 30 hops



1 <1 ms <1 ms <1 ms 192.168.1.1

2 7 ms 6 ms 10 ms 10.224.192.1

3 7 ms * 8 ms vl-201.gw03.bloor.phub.net.cable.rogers.com [66.185.90.1]

4 14 ms 7 ms 10 ms te-6-1-0.gw01.bloor.phub.net.cable.rogers.com [24.153.5.45]

5 8 ms 13 ms 7 ms so-2-2-0.gw02.bloor.phub.net.cable.rogers.com [24.153.7.181]

6 10 ms 17 ms 22 ms so-1-0-0.gw02.wlfdle.phub.net.cable.rogers.com [66.185.80.45]

7 23 ms 23 ms 24 ms pos-1-0-0.igw01.vaash.phub.net.cable.rogers.com [66.185.80.190]

8 37 ms 38 ms 37 ms POS2-1.ar2.DCA3.gblx.net [208.51.239.201]

9 27 ms 27 ms 36 ms 192.205.33.33

10 64 ms 65 ms 61 ms tbr1.wswdc.ip.att.net [12.122.80.46]

11 69 ms 59 ms 61 ms tbr1.sl9mo.ip.att.net [12.122.10.30]

12 60 ms 65 ms 59 ms tbr2.dlstx.ip.att.net [12.122.10.90]

13 58 ms 60 ms 60 ms br2.dlstx.ip.att.net [12.123.16.213]

14 60 ms 59 ms 59 ms 12.122.255.226

15 61 ms 61 ms 73 ms mdf001c7613r0003-gig-10-1.dal1.attens.net [63.241.193.10]

16 * * * Request timed out.

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.

Bump

Bump again.

Similar problem happening to me for the last week or so on the Burning Blade server...I'm just worried about it cause I had the same problem about 2 months ago and it took like 3 -4 weeks to get fixed.

If this lasts longer than 1 week , I;m really gonna think about switching to Bell.

I also use ROgers and live in Toronto.

Same thing. Rogers, Toronto, ON.

Dar

what happens when you do a trace route and you get 30 "request timed out"s?...lol

Bump!

---

Q u o t e:
3 7 ms * 8 ms vl-201.gw03.bloor.phub.net.cable.rogers.com [66.185.90.1]

---

you seem to have some packet loss at hop 3, ask rogers to take a look at it

De mortuis nihil nisi bonum

---

Q u o t e:



you seem to have some packet loss at hop 3, ask rogers to take a look at it

---

What does that mean?

I've been noticing a similar problem recently, seeing pings on average of 600+, with the worst being around 1000ms. I'm using Rogers, from Toronto, ON, and am on the Farstriders server.

Here's my traceroute:

Tracing route to 72.5.213.101 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 51 ms 12 ms 25 ms 10.222.64.1
3 * 7 ms * vl-201.gw03.bloor.phub.net.cable.rogers.com [66.185.90.1]
4 10 ms 9 ms 12 ms te-6-1-0.gw01.bloor.phub.net.cable.rogers.com [24.153.5.45]
5 * 23 ms 11 ms so-3-2-0.gw02.wlfdle.phub.net.cable.rogers.com [66.185.80.174]
6 26 ms 25 ms 28 ms 24.153.5.234
7 28 ms 28 ms 35 ms cr1-eqix-peer.wdc003.internap.net [206.223.115.129]
8 31 ms 30 ms 32 ms cr2-cr1.wdc005.internap.net [66.79.146.202]
9 108 ms 109 ms 131 ms cr1.sea002.inappnet.cr2.wdc005.internap.net [66.79.146.221]
10 110 ms 111 ms 104 ms core6.inappnet-497.sef.internap.net [66.79.144.38]
11 185 ms 210 ms 120 ms border9.t8-1-bbnet2.sef.pnap.net [63.251.160.83]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
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.

here is a trace from Sunday night..latency would shoot up to 500-600 which would create a pause in the game.

Toronto, Ontario
Use Rogers
Problem began about 1 week ago

Tracing route to 206.16.23.43 over a maximum of 30 hops


1 6 ms 7 ms 8 ms 10.222.192.1

2 11 ms 63 ms * vl-201.gw03.bloor.phub.net.cable.rogers.com [66.185.90.1]

3 9 ms 8 ms 5 ms te-15-1-0.gw01.bloor.phub.net.cable.rogers.com [24.153.5.29]

4 8 ms 18 ms 15 ms so-3-2-0.gw02.wlfdle.phub.net.cable.rogers.com [66.185.80.174]

5 29 ms 35 ms 28 ms pos-1-0-0.igw01.vaash.phub.net.cable.rogers.com [66.185.80.190]

6 239 ms 259 ms 258 ms POS2-1.ar2.DCA3.gblx.net [208.51.239.201]

7 45 ms 35 ms 51 ms 192.205.34.109

8 69 ms 80 ms 66 ms tbr1.wswdc.ip.att.net [12.122.84.158]

9 83 ms 66 ms 64 ms tbr1.sl9mo.ip.att.net [12.122.10.30]

10 63 ms 71 ms 59 ms tbr2.dlstx.ip.att.net [12.122.10.90]

11 64 ms 57 ms 61 ms br2.dlstx.ip.att.net [12.123.16.213]

12 62 ms 65 ms 66 ms mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]

13 91 ms 67 ms 67 ms mdf002fbi8ks0001-eth-1-4.dal1.attens.net [63.241.192.126]

14 * * * Request timed out.

15 * * * Request timed out.

16 * * * Request timed out.

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

20

---

Q u o t e:
here is a trace from Sunday night..latency would shoot up to 500-600 which would create a pause in the game.

Toronto, Ontario
Use Rogers
Problem began about 1 week ago

Tracing route to 206.16.23.43 over a maximum of 30 hops


1 6 ms 7 ms 8 ms 10.222.192.1

2 11 ms 63 ms * vl-201.gw03.bloor.phub.net.cable.rogers.com [66.185.90.1]


20

---

See your hop 2?

It is the same as the one above you on hop 3:

3 * 7 ms * vl-201.gw03.bloor.phub.net.cable.rogers.com [66.185.90.1]


You are both having the same issues, because you are both using the same router that is having issues.

What do you mean the router is causing the issue? I've been playing WoW since release and it has never caused any problems till recently.

I'm using Rogers High Speed Extreme!, and I use their Motorola SB5100 Cable Modem (the one they provided me).

I have tried to disconnect my router to see if it resolves the issue, but i still lag.
I use the Linksys WRT54G router.

This lag continues even after I shut off antivirus problems, chat applets, etc. It's pretty retarded.
I'm actually gearing up at the moment to play competitively in arenas, but I cant with this lag, it's just not possible.

I found this started to happen as of 2.3.2, it is spiky... i.e. fine for a while, then pause... then fine.

Normally this is indicative of network congestion. Coincidentally

- 2.3.2 disabled Nagle's algorithm
- Nagle's algorithm (ding ding ding) is a way to solve network congestion.

Disabling it may make latency slightly better for 1, but not for the many.

Rogers, Toronto, ON.

Located at Bay/College area.

I've called and @%@*#ed at Rogers tonight and am now getting credited for them not providing an acceptable service. You may wish to do the same.

1-888-ROGERS1

Technical Assistance -> High Speed Internet -> Technical Respresentative

Dar

Same - massive latency issues for the past week or so.

Toronto area, Rogers.

They never seem to be able to locate the problem when i call them. Pisses me off for all the money it costs for cable internet.

Just to be thorough, I spoke to Roger's Tech Support tonight and had them open a ticket. I relayed the information from the traceroutes posted here, i.e. that at least one other person seemed to be having loss at one of their primary hubs (66.185.90.1). While I am not overly optimistic that this will have any impact, it seemed the only thing to do at present.

Its not a Rogers issue in the sense of service.

Usually I would play in the 80-90ms ping area. The issue exists with the DPX2100 series WebStar router. It is incompatible with the disabling of the Nagle Algorithm. It is unfortunate, but after talking to a Tier 2 support tech at Rogers, I was told that the routers do not deal well with multiple packet sizes, and the speed at which the Nagle algorithm will saturate the network facing interface.

Its apparent as you play.. the latency climbs, climbs, climbs, and then you get disconnected as the modem implodes trying to handle all the small and varying in size packets causing your ENTIRE network to go down making it seem like its a Rogers issue. Sure your latency LOOKS awesome because hey those packets sure are quick... what you're not getting is how MANY of these packets there are, and as such, the increased SYN/ACK traffic for packets that are not delivered properly.

The only solution is to pack up your router, call Rogers, and go to the nearest center and drop it off in exchange with one of the newer Motorola SB5100 routers which does not experience this issue. This is the immediate fix. More then likely you have a DPX 2100 Series made by WebStar.. much like mine, or another one of the 4 routers they hand out to people. I haven't been able to confirm anyone else uses another router other then the WebStar or Motorola, but its confirmed that the Motorola modem does work.

The next fix is to see if a blue will confirm that they will be re enabling the algorithm in the next patch on Tuesday, or if this is here to stay. If its here to stay... this is your only solution, go get a new modem.

Blizzards solution of contacting vendors and having them create firmware, then getting them to tell ISP's there is an immediate need to update the firmware so people can play WoW is almost as laughable as my attempts to stay connected.

From a Rogers standpoint, the network is fine, everything else I'm doing is fast, XBL, Tabula Rasa, Starcraft, everything is fine and without issue, and as such, the issue is not with them.

You can send your tracert to the forum as many times as you want, but its not going to give Blizzard anything to work with given you can't recreate the same type of data saturation with a tracert that removing an algorithm will create. Its the equivalent of telling someone to defrag a computer because the network is down. Its the modem / internal network that is unable to handle the sudden onslaught of network traffic that WoW spews out without the algorithm in place.

Can a blue confirm that this is here to stay, or are you looking at re-instating the algorithm? You've been using it for 3 years now, the superficial change of latency times is not worth the switch for a lot of your users.

I am currently using a program called "PingPlotter" and am finding that I am losing about 60% packet loss at the third hop into the network:

vl-201.gw03.bloor.phub.net.cable.rogers.com

I've called Rogers, complained about not getting adequate service, and am now getting compensated. Again, I urge any of you who are experiencing the same problem to call: 1-888-ROGERS1.


My traceroute to www.rogers.com (lol!) is as follows:

Tracing route to www.rogers.com [207.245.252.27]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 7 ms 7 ms 10.224.32.1
3 7 ms 10 ms * vl-201.gw03.bloor.phub.net.cable.rogers.com [66.
185.90.1]
4 9 ms 8 ms 7 ms te-6-1-0.gw01.bloor.phub.net.cable.rogers.com [2
4.153.5.45]
5 8 ms 7 ms 9 ms so-2-2-0.gw02.bloor.phub.net.cable.rogers.com [2
4.153.7.181]
6 10 ms 10 ms 9 ms pos-3-0.igw01.front.phub.net.cable.rogers.com [6
4.71.240.29]
7 8 ms 18 ms 9 ms ge10-0.gwy2-tor.bb.allstream.net [216.191.65.121
]
8 9 ms 9 ms 10 ms ge-wan7-1.hcap4-tor.bb.allstream.net [199.212.16
8.194]
9 10 ms 10 ms 15 ms 216.191.187.82
10 * * *

As you can see, I'm lagging out on the third hop. Everything else seems fine.

Dar

Tracing route to 206.17.111.58 over a maximum of 30 hops

1 9 ms 11 ms 12 ms 10.222.224.1
2 28 ms 10 ms 9 ms vl-201.gw03.bloor.phub.net.cable.rogers.com [66.
185.90.1]
3 47 ms 10 ms 9 ms te-6-1-0.gw01.bloor.phub.net.cable.rogers.com [2
4.153.5.45]
4 14 ms 11 ms 14 ms so-2-2-0.gw02.bloor.phub.net.cable.rogers.com [2
4.153.7.181]
5 32 ms 18 ms 23 ms gw02.bloor.phub.net.cable.rogers.com [66.185.80.
5]
6 64 ms 60 ms 62 ms pos-1-0-0.igw01.vaash.phub.net.cable.rogers.com
[66.185.80.190]
7 37 ms 51 ms 42 ms POS2-1.ar2.DCA3.gblx.net [208.51.239.201]
8 58 ms 55 ms 56 ms 192.205.34.109
9 82 ms 78 ms 84 ms tbr2.wswdc.ip.att.net [12.122.80.18]
10 80 ms 88 ms 86 ms cr2.wswdc.ip.att.net [12.122.16.109]
11 58 ms 56 ms 57 ms cr2.n54ny.ip.att.net [12.122.3.37]
12 86 ms 79 ms 88 ms tbr2.n54ny.ip.att.net [12.122.16.214]
13 85 ms 74 ms 73 ms tbr1.cb1ma.ip.att.net [12.122.10.21]
14 63 ms * 63 ms 12.127.5.93
15 96 ms 63 ms 65 ms 12-122-254-14.attens.net [12.122.254.14]
16 74 ms 62 ms 62 ms mdf001c7613r0003-gig-10-1.bos1.attens.net [12.13
0.0.170]
17 * * * Request timed out.
18 * * ^C

same problem as before, crappy at&t routers