World of Warcraft

1 . 2 . 3
Blizzard Entertainment
View All Posts by This User ignore-inactive
Nickjs
Blizzard Poster
  • 0. Ontario, Canada High Latency Issues (Rogers)   10/24/2007 03:23:20 PM PDT
quote locked
UPDATE 11/7 1:02pm Pacific Time

Hello everybody,

Since the last update, we still did not receive many reports and the few additional ones we did receive many of them were still incomplete. Due to the lack of reports we received and based on the investigation by our network team, It has been determined that these connection issues are either localized to specific users or ISP related. For those of you who are still experiencing these connection issues, we can assist with determining if it may be localized or an ISP issue. I would encourage you to create your own thread, contact us via phone or email us for further assistance with determining this. Our additional contact information can be found at the link below:
http://us.blizzard.com/support/article.xml?articleId=21049

Please keep in mind that it may be something beyond our control if it is indeed through your ISP but contacting us to confirm whether or not that's the case is suggested and we may have you try a few more steps with us in case it isn't with your ISP. If it's determined your issue is ISP related, we will suggest you contact them directly for further assistance.

________________________________________________________________________________


UPDATE 11/1 1:03pm Pacific Time

Hello everybody,

Since our update on Monday (10/29), we have only received 3 additional reports (one of them was incomplete). We strongly encourage any of you who are still experiencing these high latency issues in the Ontario, Canada area and who are also using Rogers Cable to provide the information requested so we can investigate this further. We need a substantial amount to work with but that is not the case right now, if only a few users are reporting this, various things could be causing it and it may not necessarily indicate an ISP or server issue. So for those who have yet to submit their information and those who submitted incomplete information, I strongly encourage you to read through the previous updates and make sure you submit all of the requested information, otherwise we will not be able to investigate this further.

NOTE: If the issue appears to be resolved for anybody, please let us know.

________________________________________________________________________________


UPDATE 10/29 5:33pm Pacific Time

Hello everybody,

The majority of the reports that we have received did not include all of the requested information. The amount of reports that we did receive were also very minimal. For any player who is experiencing issues with this, please be sure to submit the information requested. For those who have submitted their information, please make sure to resubmit your information and include everything that has been requested in this post, otherwise it will delay any progress while we investigate this further. We appreciate everybody's patience and assistance with this.

Some additional information our network team are now requesting include:

- In addition to the trace routes we request, please include the in-game latency number, time, and day. Make sure you run a trace route when you are experiencing high latency and when you are not.
- Your location & time zone.

________________________________________________________________________________


Hello everybody,

Our network team has requested that we gather some information regarding the high latency issues some of you are experiencing in the Ontario, Canada area and who are also using Rogers Cable. For players outside of this area or who have a different Internet Provider, please create your own thread for assistance. For those who are included in this, please email the following information to forumtech@blizzard.com. In the subject line be sure to enter "ATTN: NickJS - Ontario, Canada High Latency (Rogers)". Please DO NOT post your Public IP Address here on the forums:

- Public IP Address (http://whatismyip.com/):
- Traceroute during performance trouble (please include timestamp and timezone):
- Traceroute during normal performance (please include timestamp and timezone)
- If possible, try playing on other realms that are outside of your Battlegroup, the Battlegroup list can be found at (http://www.worldofwarcraft.com/pvp/battlegrounds/battlegroups/ ). Let us know how the game performance is.
- Time of day (including timezone) when performance is good or bad, if applicable:

Trace Route Instructions can be found below. Enter your Realm IP where the xxx.xxx.xxx.xxx should be. The Realm IP list can be found at the bottom of this post.

For Windows XP

- Click Start and then Run.
- Type in command or "cmd" and press Enter.
- In the command window, type "tracert xxx.xxx.xxx.xxx > C:\tracert.txt" and press the Enter key.

A file will be created on your C: drive called tracert.txt that contains your Trace Route information. Copy/Paste the results in your reply.

For Windows Vista:

- Click Start and in the Start Search field type "command" or "cmd".
- The search should find the cmd.exe program. Please right click on that program and select Run as Administrator to load up the command window.
- In the command window, type "tracert xxx.xxx.xxx.xxx > C:\tracert.txt" and press the Enter key.

A file will be created on your C: drive called tracert.txt that contains your Trace Route information. Copy/Paste the results in your reply.

Realm IP’s:

Aegwynn - 12.129.225.125
Aerie Peak - 206.17.111.82
Agamaggan - 63.241.255.14
Aggramar - 206.16.23.42
Akama - 12.129.225.27
Alexstrasza - 63.241.255.82
Alleria - 63.241.255.77
Altar of Storms - 206.17.111.35
Alterac Mountains - 206.17.111.103
Aman’Thul - 12.129.225.8
Andorhal - 206.17.111.4
Anetheron - 206.17.111.49
Antonidas - 72.5.213.61
Anub’arak - 72.5.213.113
Anvilmar - 206.17.111.126
Arathor - 12.129.233.37
Archimonde - 206.17.111.7
Area 52 - 206.16.147.46
Argent Dawn 206.16.23.51
Arthas - 206.16.23.71
Arygos - 206.17.111.81
Auchindoun - 206.16.147.59
Azgalor - 206.16.23.72
Azjol-Nerub - 12.129.233.103
Azshara - 63.241.255.98
Azuremyst - 206.16.147.49
Baelgun - 63.241.255.5
Balnazzar - 63.241.255.13
Barthilas - 12.129.225.72
Black Dragonflight - 206.17.111.21
Blackhand - 63.241.255.8
Blackrock - 12.129.225.21
Blackwater Raiders - 72.5.213.94
Blackwing Lair - 206.17.111.115
Blade’s Edge - 206.16.147.69
Bladefist - 72.5.213.95
Bleeding Hollow - 206.16.23.113
Blood Furnace - 206.16.147.65
Bloodhoof - 206.16.23.73
Bloodscalp - 12.129.233.7
Bonechewer - 12.129.233.13
Boulderfist - 12.129.233.47
Bronzebeard - 12.129.233.46
Burning Blade - 206.16.23.125
Burning Legion - 206.16.23.109
Cenarion Circle - 72.5.213.115
Cenarius - 72.5.213.52
Cho’gall - 63.241.255.101
Chromaggus - 12.129.225.22
Coilfang - 206.16.147.56
Crushridge - 12.129.233.52
Daggerspine - 12.129.233.88
Dalaran - 206.17.111.111
Dalvengyr - 206.17.111.36
Dark Iron - 63.241.255.67
Darkspear - 12.129.233.12
Darrowmere - 72.5.213.114
Dath’Remar - 12.129.225.73
Deathwing - 206.17.111.83
Demon Soul - 206.17.111.127
Dentarg - 206.17.111.125
Destromath - 63.241.255.102
Dethecus - 63.241.255.97
Detheroc - 63.241.255.66
Doomhammer - 206.17.111.90
Draenor - 12.129.233.33
Dragonblight - 12.129.233.17
Dragonmaw - 12.129.233.94
Drak’thul - 12.129.225.105
Draka - 12.129.225.19
Drenden - 72.5.213.100
Dunemaul - 12.129.233.23
Durotan - 206.16.23.87
Duskwood - 206.17.111.59
Earthen Ring - 206.16.23.117
Echo Isles - 72.5.213.125
Eitrigg - 12.129.225.126
Eldre’Thalas - 12.129.233.48
Elune - 206.16.23.92
Emerald Dream - 63.241.255.83
Eonar - 206.16.23.106
Eredar - 206.16.23.121
Executus - 206.17.111.121
Exodar - 206.16.147.100
Farstriders - 72.5.213.101
Feathermoon - 12.129.233.96
Fenris - 72.5.213.120
Firetree - 12.129.233.25
Frostmane - 12.129.233.53
Frostmourne - 12.129.225.107
Frostwolf - 12.129.225.127
Garithos - 12.129.225.14
Garona - 63.241.255.12
Gilneas - 206.16.23.110
Gnomeregan - 206.17.111.32
Gorefiend - 206.16.23.101
Gorgonnash - 63.241.255.84
Greymane - 63.241.255.56
Gul’dan - 63.241.255.120
Gurubashi - 12.129.233.24
Hakkar - 12.129.225.15
Haomarush - 206.17.111.37
Hellscream - 63.241.255.55
Hydraxis - 72.5.213.43
Hyjal - 72.5.213.8
Icecrown - 206.17.111.120
Illidan - 63.241.255.110
Jaedenar - 206.17.111.114
Jubei’Thos - 12.129.225.103
Kael’thas - 63.241.255.113
Kalecgos - 63.241.255.81
Kargath - 206.16.23.120
Kel’Thuzad - 206.17.111.41
Khadgar - 206.17.111.13
Khaz Modan - 12.129.225.13
Khaz’goroth - 12.129.225.123
Kil’jaeden - 12.129.225.112
Kilrogg - 12.129.225.26
Kirin Tor - 63.241.255.27
Korgath - 12.129.225.11
Korialstrasz - 72.5.213.97
Kul Tiras - 12.129.225.9
Laughing Skull - 206.16.23.98
Lethon - 206.17.111.99
Lightbringer - 72.5.213.58
Lightning’s Blade - 206.16.23.111
Lightninghoof - 63.241.255.100
Llane - 206.16.23.105
Lothar - 206.16.23.80
Madoran -206.16.23.77
Maelstrom - 63.241.255.88
Magtheridon - 206.16.23.76
Maiev - 72.5.213.98
Mal’Ganis - 206.17.111.43
Malfurion - 63.241.255.45
Malorne - 12.129.225.2
Malygos - 206.16.23.119
Mannoroth - 206.16.23.36
Medivh - 206.16.23.5
Misha - 72.5.213.9
Mok’Nathal - 72.5.213.117
Moon Guard - 72.5.213.62
Moonrunner - 63.241.255.9
Mug’thol - 12.129.225.6
Muradin - 12.129.225.3
Nagrand - 12.129.225.43
Nathrezim - 12.129.233.51
Nazgrel - 72.5.213.118
Nazjatar - 63.241.255.10
Ner’zhul - 12.129.225.16
Nordrassil - 72.5.213.54
Norgannon - 206.17.111.88
Onyxia - 206.17.111.1
Perenolde - 12.129.233.42
Proudmoore - 12.129.225.18
Quel’dorei - 72.5.213.99
Ravencrest - 63.241.255.23
Ravenholdt - 72.5.213.96
Rexxar - 12.129.225.58
Rivendare - 72.5.213.55
Runetotem - 12.129.225.1
Sargeras - 63.241.255.89
Scarlet Crusade - 12.129.233.72
Scilla - 206.17.111.22
Sen’jin - 12.129.225.80
Sentinels - 206.17.111.10
Shadow Council - 12.129.233.20
Shadowmoon - 206.16.23.128
Shadowsong - 12.129.233.97
Shandris - 72.5.213.69
Shattered Halls - 206.16.147.109
Shattered Hand - 206.16.23.37
Shu’halo - 72.5.213.83
Silver Hand - 12.129.225.114
Silvermoon - 12.129.233.40
Sisters of Elune - 72.5.213.102
Skullcrusher - 206.16.23.95
Skywall - 12.129.233.128
Smolderthorn - 12.129.233.21
Spinebreaker - 63.241.255.52
Spirestone - 12.129.233.4:
Staghelm - 63.241.255.48
Steamwheedle Cartel - 206.17.111.42
Stonemaul - 12.129.233.22
Stormrage - 206.16.23.74
Stormreaver - 63.241.255.90
Stormscale - 12.129.233.90
Suramar - 12.129.233.2
Tanaris - 206.17.111.3
Terenas - 12.129.233.89
Terokkar - 206.16.147.70
Thaurissan - 12.129.225.82
The Forgotten Coast - 72.5.213.127
The Scryers - 206.16.147.76
The Underbog - 206.16.147.43
The Venture Co - 206.17.111.39
Thorium Brotherhood - 12.129.225.4
Thrall - 206.17.111.100
Thunderhorn - 206.16.23.94
Thunderlord - 206.16.23.107
Tichondrius - 12.129.225.5
Tortheldrin - 72.5.213.36
Trollbane - 206.16.23.78
Turalyon - 206.17.111.87
Twisting Nether - 63.241.255.7
Uldaman - 206.17.111.48
Uldum - 12.129.233.6
Undermine - 206.17.111.124
Ursin - 63.241.255.80
Uther - 72.5.213.44
Vashj - 72.5.213.85
Vek’nilash - 12.129.225.10
Velen - 206.16.147.98
Warsong - 206.16.23.103
Whisperwind - 63.241.255.87
Wildhammer - 63.241.255.128
Windrunner - 12.129.233.11
Ysera - 206.17.111.8
Ysondre - 206.17.111.56
Zangarmarsh - 206.16.147.74
Zul’jin - 206.16.23.115
Zuluhed - 206.17.111.128

[ Post edited by Nickjs ]


Blizzard Entertainment Technical Support

"I remember I took away the chocolate bars [on the way home] and the players were singing ‘we want our chocolate back’". - AW
70
View All Posts by This User Toggle Ignore / Unignore This User
  • 2. Re: Ontario, Canada High Latency Issues (Rogers)   10/26/2007 09:04:19 AM PDT
quote locked
any news on this? we had a 6 page topic on it before

i'm still getting 300-500ms latency in the late evening hours. ive emailed some traces to the above address but would appreciate an update from blue
80
View All Posts by This User Toggle Ignore / Unignore This User
  • 3. Re: Ontario, Canada High Latency Issues (Roge   10/26/2007 10:14:02 AM PDT
quote locked
Get Shaw imo!

YOUR OFFER PLEASES TECHNOVIKING
Cryfire/Crylla
80
View All Posts by This User Toggle Ignore / Unignore This User
  • 4. Re: Ontario, Canada High Latency Issues (Rogers)   10/26/2007 12:10:27 PM PDT
quote locked
i dont know about any one else, but im with rogers and im getting around 100-200 lat
oh and 3rd post!
80
View All Posts by This User Toggle Ignore / Unignore This User
  • Destromath
  • 5. Re: Ontario, Canada High Latency Issues (Roge   10/26/2007 02:47:09 PM PDT
quote locked
This is still very much an issue. I bloody well wish I had have stayed with bell
17
View All Posts by This User Toggle Ignore / Unignore This User
  • Aegwynn
  • 6. Re: Ontario, Canada High Latency Issues (Roge   10/26/2007 04:01:15 PM PDT
quote locked
Can you guys stop blaming Rogers. It is not their fault, the problem is with the connections after you leave the Rogers network, so STOP BLAMING ROGERS!.

See:

Tracing route to 12-129-225-125.attens.net [12.129.225.125]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.45.33
2 8 ms 7 ms 7 ms 10.234.96.1
3 9 ms 9 ms 7 ms vl-201.gw03.wlfdle.phub.net.cable.rogers.com [66.185.90.161]
4 9 ms 10 ms 8 ms te-15-1-0.gw01.wlfdle.phub.net.cable.rogers.com[24.153.5.25]
5 9 ms 8 ms 9 ms so-3-0-0.gw02.wlfdle.phub.net.cable.rogers.com [66.185.80.130]

End of rogers network with mild latency increase.


6 23 ms 24 ms 24 ms 24.153.5.234
7 40 ms 39 ms 39 ms POS2-1.ar2.DCA3.gblx.net [208.51.239.201]
8 25 ms 28 ms 25 ms 192.205.33.33

Entry into AT&T with big latency increase.

9 88 ms 89 ms 90 ms tbr1.wswdc.ip.att.net [12.122.84.158]
10 93 ms 87 ms 85 ms tbr1.sl9mo.ip.att.net [12.122.10.30]
11 86 ms 86 ms 84 ms tbr2.sl9mo.ip.att.net [12.122.9.142]
12 92 ms 93 ms 91 ms tbr2.la2ca.ip.att.net [12.122.10.14]
13 85 ms 83 ms 83 ms 12.127.3.189
14 85 ms 85 ms 84 ms 12.122.255.74
15 113 ms 104 ms 93 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]

Now, Blizzard can you please update us with any details that you get. Thank you.
7
View All Posts by This User Toggle Ignore / Unignore This User
  • Thrall
  • 9. Re: Ontario, Canada High Latency Issues (Roge   10/27/2007 05:51:37 PM PDT
quote locked
Ok.

"What do you mean you forgot the chicken nuggets..?"
22
View All Posts by This User Toggle Ignore / Unignore This User
  • 10. Re: Ontario, Canada High Latency Issues (Roge   10/27/2007 09:30:25 PM PDT
quote locked
15 113 ms 104 ms 93 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]

I live in San Marcos, CA near San Diego and my ISP is Time/Warner Cable. When I run the trace to my realm's IP address, that is the same line that I lose connection at as well. I haven't even been able to log into the game for almost 2 months now. I connect, everyone's nameplate is unknown, and 10 seconds or so later I get disconnected. I'm not sure what blizzard can really do if it is an ISP issue, but I've tried calling them and it's impossible to get anywhere there, so hopefully this gets resolved somehow.
70
View All Posts by This User Toggle Ignore / Unignore This User
Lau
  • Dalaran
  • 11. Re: Ontario, Canada High Latency Issues (Roge   10/28/2007 04:25:56 AM PDT
quote locked

Q u o t e:
Can you guys stop blaming Rogers. It is not their fault, the problem is with the connections after you leave the Rogers network, so STOP BLAMING ROGERS!.

See:

Tracing route to 12-129-225-125.attens.net [12.129.225.125]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.45.33
2 8 ms 7 ms 7 ms 10.234.96.1
3 9 ms 9 ms 7 ms vl-201.gw03.wlfdle.phub.net.cable.rogers.com [66.185.90.161]
4 9 ms 10 ms 8 ms te-15-1-0.gw01.wlfdle.phub.net.cable.rogers.com[24.153.5.25]
5 9 ms 8 ms 9 ms so-3-0-0.gw02.wlfdle.phub.net.cable.rogers.com [66.185.80.130]

End of rogers network with mild latency increase.


6 23 ms 24 ms 24 ms 24.153.5.234
7 40 ms 39 ms 39 ms POS2-1.ar2.DCA3.gblx.net [208.51.239.201]
8 25 ms 28 ms 25 ms 192.205.33.33

Entry into AT&T with big latency increase.

9 88 ms 89 ms 90 ms tbr1.wswdc.ip.att.net [12.122.84.158]
10 93 ms 87 ms 85 ms tbr1.sl9mo.ip.att.net [12.122.10.30]
11 86 ms 86 ms 84 ms tbr2.sl9mo.ip.att.net [12.122.9.142]
12 92 ms 93 ms 91 ms tbr2.la2ca.ip.att.net [12.122.10.14]
13 85 ms 83 ms 83 ms 12.127.3.189
14 85 ms 85 ms 84 ms 12.122.255.74
15 113 ms 104 ms 93 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.129.193.246]

Now, Blizzard can you please update us with any details that you get. Thank you.


here's how it works, when you leave the rogers network they pay the next carrier for the bandwidth, so although it's not directly rogers they still have to forward the ticket, blizzard are a receiver of the service

De mortuis nihil nisi bonum
17
View All Posts by This User Toggle Ignore / Unignore This User
  • Aegwynn
  • 12. Re: Ontario, Canada High Latency Issues (Roge   10/28/2007 06:38:20 AM PDT
quote locked
I realize that, and that is why I am saying stop blaming Rogers. If you do a little research you will find out that the problem is actually politics between Global Crossing and AT&T. AT&T refuses to cooperate 100% with Global Crossing to fix the problem because of Global Crossing's bankruptcy protected status. The problem occurs every few months because of high network traffic at a major link between the two carrier networks. They squabble with each other for 3-4 days until their customers voices finally drown out the squabbling and then things get fixed.

I just hope it gets fixed as WoW is unplayable for many of us taking the glbx-AT&T route. You are right though it is up to Rogers to pass on the information and also up to Blizzard to flex its muscle, unless they are not interested in keeping a few customers out of 8 million.
70
View All Posts by This User Toggle Ignore / Unignore This User
Lau
  • Dalaran
  • 13. Re: Ontario, Canada High Latency Issues (Roge   10/28/2007 08:54:30 AM PDT
quote locked
Because blizzard are not direcly a customer it is quite difficult for them to take up the issue, in all honesty they have very little influence over the outcome

De mortuis nihil nisi bonum
70
View All Posts by This User Toggle Ignore / Unignore This User
  • Kirin Tor
  • 14. Re: Ontario, Canada High Latency Issues (Roge   10/28/2007 02:02:04 PM PDT
quote locked
No one is forcing Rogers to route through Global Crossing. AT&T have plenty of peering points elsewhere.
70
View All Posts by This User Toggle Ignore / Unignore This User
  • 15. Re: Ontario, Canada High Latency Issues (Roge   10/28/2007 02:56:54 PM PDT
quote locked
I'm on shaw and am getting high lag as well.. looks like at&t

Tracing route to 63.241.255.89 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 31 ms 120 ms 40 ms rd1bb-ge5-0-0-1.vc.shawcable.net [64.59.159.2]
4 28 ms 44 ms 69 ms rc1bb-ge5-0-0.vc.shawcable.net [66.163.69.105]
5 127 ms 64 ms 43 ms rc1wt-pos4-0-0.wa.shawcable.net [66.163.76.126]

6 250 ms 61 ms 44 ms sl-gw12-sea-1-0.sprintlink.net [144.228.93.149]

7 39 ms 30 ms 45 ms sl-bb21-sea-4-0-0.sprintlink.net [144.232.6.123]

8 117 ms 70 ms 40 ms sprint-gw.st6wa.ip.att.net [192.205.32.173]
9 139 ms 121 ms 110 ms 12.127.6.62
10 534 ms 99 ms 143 ms tbr2.cgcil.ip.att.net [12.122.10.61]
11 145 ms 101 ms 165 ms tbr2.sl9mo.ip.att.net [12.122.10.46]
12 336 ms 100 ms 163 ms tbr1.sl9mo.ip.att.net [12.122.9.141]
13 116 ms 115 ms 110 ms tbr2.dlstx.ip.att.net [12.122.10.90]
14 272 ms 139 ms 144 ms br2.dlstx.ip.att.net [12.123.16.213]
15 165 ms 98 ms 175 ms 12.122.255.226
16 107 ms 116 ms 93 ms mdf001c7613r0003-gig-10-1.dal1.attens.net [63.24
1.193.10]
70
View All Posts by This User Toggle Ignore / Unignore This User
  • Exodar
  • 16. Re: Ontario, Canada High Latency Issues (Roge   10/29/2007 09:29:54 AM PDT
quote locked
I don't care whos fault it is, I just want this fixed so I can raid :(


Q u o t e:
Yes, I want to see mages throw fireballs OUT OF THEIR ASS.
Blizzard Entertainment
View All Posts by This User ignore-inactive
Nickjs
Blizzard Poster
  • 17. Re: Ontario, Canada High Latency Issues (Roge   10/29/2007 05:33:44 PM PDT
quote locked
UPDATE 5:33pm Pacific Time

Hello everybody,

The majority of the reports that we have received did not include all of the requested information. The amount of reports that we did receive were also very minimal. For any player who is experiencing issues with this, please be sure to submit the information requested. For those who have submitted their information, please make sure to resubmit your information and include everything that has been requested in this post, otherwise it will delay any progress while we investigate this further. We appreciate everybody's patience and assistance with this.

Some additional information our network team are now requesting include:

- In addition to the trace routes we request, please include the in-game latency number, time, and day. Make sure you run a trace route when you are experiencing high latency and when you are not.
- Your location & time zone.

[ Post edited by Nickjs ]


Blizzard Entertainment Technical Support

"I remember I took away the chocolate bars [on the way home] and the players were singing ‘we want our chocolate back’". - AW
70
View All Posts by This User Toggle Ignore / Unignore This User
  • 18. Re: Ontario, Canada High Latency Issues (Roge   10/30/2007 06:51:22 AM PDT
quote locked
Well I've been attempting to catch a spike on a tracert for a couple of days now and I seem to not be having much luck catching it. I do however have some information related to this and a question.

A while ago while experiencing the same problem, before this post went up and before I realized it wasn't just my connection having the problem, I ran a tracert during lag. There were 2 odd things I noted about the tracert information.

1. The very first 'bounce' recorded, which I am assuming was to my router, or possibly a local hub (not sure), had a massive latency of around ">1000000ms" and after that there were a few bounces with fairly normal ping and then another one with massive latency at the 5th or 6th bounce with the same amount or so. I will try to trace another and record it in a .txt and email it.

2. The in game latency seemed to spike back and fourth erratically between a normal ping of ~100 and a very high one of around ~10000. After a few seconds at the high end, I would get dropped and lose connection for a couple of seconds up to several minutes. I am wondering if this may be why only some of the bounces in my tracert are extremely high and the rest are normal? Could it be some sort of large network spiking happening on the Rogers Network? They own the cable lines in the area of Canada that's having the problem.

As I said I'm trying to catch another tracert to send to you guys for a bit better information to be interpreted. Hopefully sometime this week I'll have one to send in.

Thanks for the effort on your end.

Popsicles are for summertime.
70
View All Posts by This User Toggle Ignore / Unignore This User
  • 19. Re: Ontario, Canada High Latency Issues (Roge   10/30/2007 11:50:01 AM PDT
quote locked
Nice... Wellcome to South America problem... I like see blizzard helping someone in crisis with 300-450 when that is a good latency for us...
1 . 2 . 3
Forum Nav : Jump To This Forum
Blizzard Entertainment