Since 2months ago i have been getting high latency its always around 300ms (not a big problem), But at 6-7server time it always shoots up 700-1400MS. This seems to only be a problem on Scarlet Crusade, when i log onto other servers when its 700-1400ms. my ms is always under 250 (most of the time its 80-120.

Iv seen a sticky here before and i e-mailed the support but they just told me look at my Firewall, and some other BS.

Blizz how did you fix other players with high latency with rogers?

i saw the post as well and i'm searching for it now. i'm actually employed by rogers. i'm a field service tech though...i have nothing to do with the Rogers Routers. heh.

i made a post asking basically the very same question.

thanks, it has to do with only with Scarlet Crusade so i dont think it has anything to do with my router or internet settings.

bump!

Can you please try running a traceroute to the Realm that you are having issues with? Do you know how to access the IP for your server? If not please read the following"

While ingame on the Realm you are having issues with please alt+tab out of the game.

Go to Start
Run
type in cmd
Type in netstat -a ( need the space between the t and - )
Press enter

Now look for the line that has ":3724 ESTABLISHED" in it.
That will have your Realms IP address.

Write that number down EXACTLY.

Now in the command window type in tracert xxx.xx.xxx.xx >C:\tracert.txt The x's being the number you got from netstat.

An example:
(Dalaran)

tracert 206.17.111.94 >C:\tracert.txt

This will create a text file of your traceroute on your C Drive. It may take 2 or 3 minutes in some cases.

You can access that by double clicking the My Computer icon on your desktop, then double clicking C drive.

Double click the file and please copy and paste it to this thread.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Kyle>tracert 12.129.233.75:3724
Unable to resolve target system name 12.129.233.75:3724.

C:\Documents and Settings\Kyle>tracert 12.129.233.75

Tracing route to 12.129.233.75 over a maximum of 30 hops

1 18 ms 8 ms 8 ms 10.230.160.1
2 15 ms 7 ms 10 ms vl-201.gw03.wlfdle.phub.net.cable.rogers.com [66
.185.90.161]
3 10 ms 6 ms 10 ms te-6-1-0.gw01.wlfdle.phub.net.cable.rogers.com [
24.153.5.41]
4 17 ms 9 ms 8 ms so-2-3-0.gw02.bloor.phub.net.cable.rogers.com [6
4.71.240.106]
5 9 ms 11 ms 8 ms so-1-0-0.gw02.wlfdle.phub.net.cable.rogers.com [
66.185.80.45]
6 26 ms 24 ms 25 ms pos-1-0-0.igw01.vaash.phub.net.cable.rogers.com
[66.185.80.190]
7 38 ms 38 ms 38 ms POS2-1.ar2.DCA3.gblx.net [208.51.239.201]
8 25 ms 26 ms 25 ms 192.205.33.33
9 107 ms 101 ms 101 ms tbr1.wswdc.ip.att.net [12.122.80.46]
10 328 ms 328 ms 316 ms tbr1.sl9mo.ip.att.net [12.122.10.30]
11 96 ms 102 ms 102 ms tbr2.sl9mo.ip.att.net [12.122.9.142]
12 303 ms 295 ms 328 ms tbr2.la2ca.ip.att.net [12.122.10.14]
13 319 ms 321 ms 327 ms 12.127.3.189
14 102 ms 101 ms 85 ms 12.122.255.74
15 106 ms 85 ms 93 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.12
9.193.246]
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.

Using rogers, same problem on Ysera.

Same issue... ALWAYS the same issue... this is my 3rd-4th post on the subject.

1 <1 ms <1 ms <1 ms 192.168.2.1
2 9 ms 11 ms 7 ms 10.223.64.1
3 9 ms 11 ms * vl-201.gw03.bloor.phub.net.cable.rogers.com [66.
185.90.1]
4 9 ms 9 ms 9 ms te-15-1-0.gw01.bloor.phub.net.cable.rogers.com [
24.153.5.29]
5 9 ms 9 ms 19 ms so-2-2-0.gw02.bloor.phub.net.cable.rogers.com [2
4.153.7.181]
6 10 ms 11 ms 21 ms gw02.bloor.phub.net.cable.rogers.com [66.185.80.
5]
7 25 ms 25 ms 25 ms pos-0-0-0.igw01.vaash.phub.net.cable.rogers.com
[24.153.5.230]
8 40 ms 38 ms 43 ms POS2-1.ar2.DCA3.gblx.net [208.51.239.201]
9 369 ms 364 ms 368 ms 192.205.34.109
10 403 ms 399 ms 396 ms tbr1.wswdc.ip.att.net [12.122.80.46]
11 85 ms 86 ms 88 ms tbr1.sl9mo.ip.att.net [12.122.10.30]
12 440 ms 430 ms 432 ms tbr2.sl9mo.ip.att.net [12.122.9.142]
13 85 ms 87 ms 89 ms tbr2.la2ca.ip.att.net [12.122.10.14]
14 90 ms 84 ms 87 ms 12.127.3.189
15 401 ms 403 ms 409 ms 12.122.255.74
16 428 ms 430 ms 432 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.12
9.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.

Guys

I work for rogers and I have the same issue

traceroute to 206.17.111.121 (206.17.111.121), 30 hops max, 40 byte packets
1 * * * Request timed out.
2 gw10.wlfdle.rnc.net.cable.rogers.com (66.185.91.65) 10.401 ms 18.386 ms 8.621 ms
3 24.153.7.37 (24.153.7.37) 13.950 ms 8.864 ms 8.061 ms
4 so-4-2-0.gw02.wlfdle.phub.net.cable.rogers.com (66.185.81.213) 11.150 ms 9.097 ms 8.465 ms
5 pos-1-0-0.igw01.vaash.phub.net.cable.rogers.com (66.185.80.190) 23.654 ms 27.513 ms 25.322 ms
6 POS2-1.ar2.DCA3.gblx.net (208.51.239.201) 44.617 ms 27.961 ms 26.455 ms
7 192.205.33.33 (192.205.33.33) 384.310 ms 382.003 ms 375.947 ms
8 tbr2.wswdc.ip.att.net (12.122.80.18) 397.008 ms 400.158 ms 408.248 ms
9 cr2.wswdc.ip.att.net (12.122.16.101) 35.487 ms 40.819 ms 36.753 ms
10 cr2.n54ny.ip.att.net (12.122.3.37) 49.505 ms 47.263 ms 49.361 ms
11 tbr2.n54ny.ip.att.net (12.122.16.222) 50.463 ms 41.586 ms 40.200 ms
12 tbr1.cb1ma.ip.att.net (12.122.10.21) 309.892 ms 312.973 ms 311.879 ms
13 12.127.5.109 (12.127.5.109) 48.927 ms 40.049 ms 37.639 ms
14 12-122-254-14.attens.net (12.122.254.14) 61.379 ms 48.875 ms 50.830 ms
15 mdf001c7613r0003-gig-10-1.bos1.attens.net (12.130.0.170) 75.710 ms 63.927 ms 43.823 ms
16 * * * Request timed out.
17 * * * Request timed out.
18



traceroute to 206.17.111.121 ( 206.17.111.121), 30 hops max, 40 byte packets
1 * * * Request timed out.
2 gw10.wlfdle.rnc.net.cable.rogers.com ( 66.185.91.65) 14.620 ms 10.234 ms 9.198 ms
3 24.153.7.37 (24.153.7.37) 18.585 ms 9.340 ms 8.187 ms
4 so-4-2-0.gw02.wlfdle.phub.net.cable.rogers.com (66.185.81.213) 7.851 ms 8.517 ms 8.545 ms
5 pos-1-0-0.igw01.vaash.phub.net.cable.rogers.com (66.185.80.190) 26.732 ms 24.952 ms 42.379 ms
6 POS2-1.ar2.DCA3.gblx.net (208.51.239.201) 81.297 ms 195.149 ms 222.222 ms
7 192.205.33.33 (192.205.33.33) 378.359 ms 383.248 ms 371.659 ms
8 tbr2.wswdc.ip.att.net (12.122.80.18) 372.109 ms 389.569 ms 383.262 ms
9 cr2.wswdc.ip.att.net (12.122.16.101 ) 37.080 ms 37.627 ms 39.105 ms
10 cr2.n54ny.ip.att.net (12.122.3.37) 44.816 ms 45.370 ms 43.085 ms
11 tbr2.n54ny.ip.att.net (12.122.16.222) 50.225 ms 51.554 ms 46.839 ms
12 tbr1.cb1ma.ip.att.net (12.122.10.21 ) 359.779 ms 350.646 ms 356.143 ms
13 12.127.5.109 (12.127.5.109) 36.253 ms 36.936 ms 40.221 ms
14 12-122-254-14.attens.net (12.122.254.14) 52.567 ms 54.105 ms 55.643 ms
15 mdf001c7613r0003-gig-10-1.bos1.attens.net (12.130.0.170) 45.390 ms 43.278 ms 43.538 ms
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.

There are two ways to handle this issue

Either you complain to Blizzard (as you see no results) or you complain to Rogers

In the end its a issue between AT&T and Rogers (AT&T is Blizzards ISP)

My suggestion is you call into Rogers and demand to speak to a supervisor.

Come armed with your trace routes to prove your issue. If they try to bring you to a speed test web site say "The issue is down stream and a local speed test will not prove anything"

In the end unless they get alot of complaints and escalations or cancellations

Blizzard or Rogers will not fix the issue.


If this is not fixed with in two weeks I am going to Bell. Employee discount or not this lag is not worth it to me and I know Blizard will not get this resolved as they have to many customers to care about people in Ontario who have Rogers, this is despite the fact that their ISP is provide lag as shown in the attached.

Blue I would love you to reply and try to tell me how this is not your issue.

I've sent this in a few times to Blizzard and they've done FACK ALL. The guy that had a stickied thread(blue) that was collecting information, has removed the sticked thread, and has went SILENT.

Blizzard is brushing it off, time to go to the better business bureau... as they don't give a rats fking azz... they are getting our money, and have pushed it off as not being their issue...

Fackin brutal for the amount of money they are making...

---

Q u o t e:
Guys

I work for rogers and I have the same issue

traceroute to 206.17.111.121 (206.17.111.121), 30 hops max, 40 byte packets
1 * * * Request timed out.
2 gw10.wlfdle.rnc.net.cable.rogers.com (66.185.91.65) 10.401 ms 18.386 ms 8.621 ms
3 24.153.7.37 (24.153.7.37) 13.950 ms 8.864 ms 8.061 ms
4 so-4-2-0.gw02.wlfdle.phub.net.cable.rogers.com (66.185.81.213) 11.150 ms 9.097 ms 8.465 ms
5 pos-1-0-0.igw01.vaash.phub.net.cable.rogers.com (66.185.80.190) 23.654 ms 27.513 ms 25.322 ms
6 POS2-1.ar2.DCA3.gblx.net (208.51.239.201) 44.617 ms 27.961 ms 26.455 ms
7 192.205.33.33 (192.205.33.33) 384.310 ms 382.003 ms 375.947 ms
8 tbr2.wswdc.ip.att.net (12.122.80.18) 397.008 ms 400.158 ms 408.248 ms
9 cr2.wswdc.ip.att.net (12.122.16.101) 35.487 ms 40.819 ms 36.753 ms
10 cr2.n54ny.ip.att.net (12.122.3.37) 49.505 ms 47.263 ms 49.361 ms
11 tbr2.n54ny.ip.att.net (12.122.16.222) 50.463 ms 41.586 ms 40.200 ms
12 tbr1.cb1ma.ip.att.net (12.122.10.21) 309.892 ms 312.973 ms 311.879 ms
13 12.127.5.109 (12.127.5.109) 48.927 ms 40.049 ms 37.639 ms
14 12-122-254-14.attens.net (12.122.254.14) 61.379 ms 48.875 ms 50.830 ms
15 mdf001c7613r0003-gig-10-1.bos1.attens.net (12.130.0.170) 75.710 ms 63.927 ms 43.823 ms
16 * * * Request timed out.
17 * * * Request timed out.
18



traceroute to 206.17.111.121 ( 206.17.111.121), 30 hops max, 40 byte packets
1 * * * Request timed out.
2 gw10.wlfdle.rnc.net.cable.rogers.com ( 66.185.91.65) 14.620 ms 10.234 ms 9.198 ms
3 24.153.7.37 (24.153.7.37) 18.585 ms 9.340 ms 8.187 ms
4 so-4-2-0.gw02.wlfdle.phub.net.cable.rogers.com (66.185.81.213) 7.851 ms 8.517 ms 8.545 ms
5 pos-1-0-0.igw01.vaash.phub.net.cable.rogers.com (66.185.80.190) 26.732 ms 24.952 ms 42.379 ms
6 POS2-1.ar2.DCA3.gblx.net (208.51.239.201) 81.297 ms 195.149 ms 222.222 ms
7 192.205.33.33 (192.205.33.33) 378.359 ms 383.248 ms 371.659 ms
8 tbr2.wswdc.ip.att.net (12.122.80.18) 372.109 ms 389.569 ms 383.262 ms
9 cr2.wswdc.ip.att.net (12.122.16.101 ) 37.080 ms 37.627 ms 39.105 ms
10 cr2.n54ny.ip.att.net (12.122.3.37) 44.816 ms 45.370 ms 43.085 ms
11 tbr2.n54ny.ip.att.net (12.122.16.222) 50.225 ms 51.554 ms 46.839 ms
12 tbr1.cb1ma.ip.att.net (12.122.10.21 ) 359.779 ms 350.646 ms 356.143 ms
13 12.127.5.109 (12.127.5.109) 36.253 ms 36.936 ms 40.221 ms
14 12-122-254-14.attens.net (12.122.254.14) 52.567 ms 54.105 ms 55.643 ms
15 mdf001c7613r0003-gig-10-1.bos1.attens.net (12.130.0.170) 45.390 ms 43.278 ms 43.538 ms
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.

There are two ways to handle this issue

Either you complain to Blizzard (as you see no results) or you complain to Rogers

In the end its a issue between AT&T and Rogers (AT&T is Blizzards ISP)

My suggestion is you call into Rogers and demand to speak to a supervisor.

Come armed with your trace routes to prove your issue. If they try to bring you to a speed test web site say "The issue is down stream and a local speed test will not prove anything"

In the end unless they get alot of complaints and escalations or cancellations

Blizzard or Rogers will not fix the issue.


If this is not fixed with in two weeks I am going to Bell. Employee discount or not this lag is not worth it to me and I know Blizard will not get this resolved as they have to many customers to care about people in Ontario who have Rogers, this is despite the fact that their ISP is provide lag as shown in the attached.

Blue I would love you to reply and try to tell me how this is not your issue.

---

I just spent 30 mins trying to figure out what causes this latency. I'm in Toronto, and also using Rogers. This latency came with last patch, and only gets worse. Nothing I tried worked. I'm still on the same server, using the same hardware and router, only now instead of 200 ping I have 800 ping, and the game is unplayable in PvP.

Immediate fix is required Blizz, a very large percentage of Canada's population is within Ontario, and a very large portion of that uses Rogers. They are my internet and cable provider, so when it comes down to a choice between them and you, I'll choose them, and you can say bye bye to my monthly payments.

Same issue... also Rogers... :(


Tracing route to 206.17.111.11 over a maximum of 30 hops



1 <1 ms <1 ms <1 ms 192.168.0.1

2 8 ms 10 ms 12 ms 10.234.0.1

3 29 ms 17 ms 15 ms vl-201.gw03.wlfdle.phub.net.cable.rogers.com [66.185.90.161]

4 9 ms 9 ms 12 ms te-15-1-0.gw01.wlfdle.phub.net.cable.rogers.com [24.153.5.25]

5 12 ms 8 ms 10 ms so-3-0-0.gw02.wlfdle.phub.net.cable.rogers.com [66.185.80.130]

6 32 ms 27 ms 23 ms pos-0-0-0.igw01.vaash.phub.net.cable.rogers.com [24.153.5.230]

7 41 ms 48 ms 37 ms POS2-1.ar2.DCA3.gblx.net [208.51.239.201]

8 43 ms 29 ms 29 ms 192.205.33.33

9 39 ms 42 ms 60 ms tbr1.wswdc.ip.att.net [12.122.84.158]

10 313 ms 311 ms 330 ms cr2.wswdc.ip.att.net [12.122.16.45]

11 38 ms 37 ms 35 ms cr2.n54ny.ip.att.net [12.122.3.37]

12 36 ms 47 ms 37 ms tbr2.n54ny.ip.att.net [12.122.16.214]

13 40 ms 39 ms 38 ms tbr1.cb1ma.ip.att.net [12.122.10.21]

14 38 ms 41 ms 37 ms 12.127.5.109

15 327 ms 325 ms 390 ms 12-122-254-14.attens.net [12.122.254.14]

16 37 ms 39 ms 35 ms mdf001c7613r0004-gig-12-1.bos1.attens.net [12.130.0.174]

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.

Strange thing is that its only effected by this game the other games run fine.

---

Q u o t e:
Strange thing is that its only effected by this game the other games run fine.

---

Roger that. Tabula Rasa right this minute is at 290 ping, and EVE Online 265 ping. WoW 729 ping. And I used to get 200 ping steady with the same hardware prior to 2.3.

---

Q u o t e:


Roger that. Tabula Rasa right this minute is at 290 ping, and EVE Online 265 ping. WoW 729 ping. And I used to get 200 ping steady with the same hardware prior to 2.3.

---

well lets hope for the best and they fix it.

Im getting aprox 800-1k latency on frostwolf.. i live in toronto, ont, using rogers.. i know 2 people using rogers who 1 is in toronto, 1 is 45 minutes from toronto and arnt having the problem on the same realm.

Tell them to post on the forums, maybe if there's enough people posting they will actually do something to help :(

I just recently have the same problem... with Shaw (former rogers here)... in BC as in the province, not the game lol

Going to keep this thread bumped so other people having the problem can post some info here, like one poster said. Phone rogers and ask to talk to a supervisor about this, with enough complaints and potential cancellations they might just do something, if we don't do anything we wont see anything done about it.

My problem with phoning Rogers is, what am I gonna tell them? Everything runs fine, download speeds are fantastic, upload speeds are fantastic, no connection downtime that I know of, all online games (both MMO and just multiplayer ones) run just fine, except WOW which started to misbehave after Blizzard released the patch. I mean, what can they do?