Canadians are getting a huge spike in Latency

Technical Support
21

Currently having 250 ms + on all servers except for Brazil.

Bell Canada in Ottawa, Ontario.

Please kick Bell in the butt.

1 Like
22

Manitoba, Canada player here! I’ve logged in to two separate accounts, and both experienced the same 188ms to 202ms delay consistently. When asking in-game, I was told I’m on SA servers. Would really like this to be resolved ASAP, as I’d LOVE to be able to play more during this event period. Also really hope that blizzard may even extend the event period as a result of these server connection issues.

23

As I stated before, it is not our fault for getting a high latency, I hope it isn’t blizzards fault either, but hopefully the issue will be resolved by today? All Canadians are experiencing the same issue Sask - all the way east. All we can do is comment on this as Nicole told me, it’s pretty obvious something is wrong with our Canadian servers re-directing us to some South American servers, just wait and hope Blizzard can see the obvious, as we all have.

24

Its not blizz its Bell and I think this could be a while…

1 Like
25

It is not only bell, it is all other internet providers in Canada throughout Sask to the east.

26

This doesn’t explain someone in LA getting put into SA server though. Something got messed up since yesterday after patch and needs to be fixed.

27

welp, hopefully Blizzard/internet providers can fix the issue since none of us can. More people that comment on here the faster it will be fixed, as Nicole told me.

28

No way you would see wayyyyy more posts bro.

29

Hello,
From Quebec here, same issue. Had 50~ping average, got 300 in game now. Using Us server.
Internet provider: Bell
SpeedTest is good, (5ping, 300Mbps upload/download)

Tried going through the steps of Blizzard connection troubleshooting
us.battle.net /support/en/article/99037

Here is the tracert file

Summary

D‚termination de l’itin‚raire vers ec2-18-231-106-87.sa-east-1.compute.amazonaws. com [18.231.106.87]
avec un maximum de 30 sautsÿ:

1 <1 ms <1 ms <1 ms mynetwork [192.168.2.1]
2 2 ms 2 ms 2 ms 10.11.18.105
3 1 ms 2 ms 1 ms 10.178.206.164
4 2 ms 1 ms 1 ms 10.178.206.165
5 7 ms 7 ms 7 ms tcore4x-quebec14_0-4-0-2.net.bell. ca [64.230.87.106]
6 5 ms 7 ms 7 ms tcore3-montreal02_hundredgige2-12-0-1.net.bell. ca [64.230.40.172]
7 6 ms 7 ms 5 ms bx1-montreal02_hundredgige0-1-0-0.net.bell. ca [64.230.91.123]
8 6 ms 4 ms 5 ms ix-ae-10-0.tcore1.w6c-montreal.as6453. net [66.198.96.9]
9 17 ms 14 ms 13 ms if-ae-12-2.tcore1.mtt-montreal.as6453. net [64.86.31.26]
10 13 ms 13 ms 14 ms if-ae-0-2.tcore2.mtt-montreal.as6453. net [216.6.115.90]
11 13 ms 14 ms 14 ms if-ae-5-2.tcore2.n0v-new-york.as6453. net [64.86.226.58]
12 13 ms 13 ms 13 ms if-ae-2-2.tcore1.n0v-new-york.as6453. net [216.6.90.21]
13 13 ms 16 ms 17 ms if-ae-7-2.tcore1.nto-new-york.as6453. net [63.243.128.141]
14 14 ms 14 ms 13 ms if-ae-9-2.tcore1.n75-new-york.as6453. net [63.243.128.122]
15 14 ms 20 ms 17 ms 66.110.96.157
16 * * * D‚lai d’attente de la demande d‚pass‚.
17 * * * D‚lai d’attente de la demande d‚pass‚.
18 * * * D‚lai d’attente de la demande d‚pass‚.
19 * * * D‚lai d’attente de la demande d‚pass‚.
20 * * * D‚lai d’attente de la demande d‚pass‚.
21 * * * D‚lai d’attente de la demande d‚pass‚.
22 * * * D‚lai d’attente de la demande d‚pass‚.
23 * * * D‚lai d’attente de la demande d‚pass‚.
24 * * * D‚lai d’attente de la demande d‚pass‚.
25 146 ms 146 ms 146 ms 177.72.240.116
26 171 ms 186 ms 156 ms 54.240.244.164
27 148 ms 146 ms 145 ms 54.240.244.169
28 147 ms 145 ms 145 ms 54.240.244.72
29 * * * D‚lai d’attente de la demande d‚pass‚.
30 * * * D‚lai d’attente de la demande d‚pass‚.

Itin‚raire d‚termin‚.

Here is the Looking Glass file:

Summary

TRACEROUTE:
traceroute to 174.89.77.78 (174.89.77.78), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.298 ms 0.283 ms 0.280 ms
2 37.244.22.2 (37.244.22.2) 1.300 ms 1.319 ms 1.318 ms
3 24.105.30.166 (24.105.30.166) 1.318 ms 1.317 ms 1.317 ms
4 137.221.66.0 (137.221.66.0) 1.487 ms 2.627 ms 2.635 ms
5 137.221.68.66 (137.221.68.66) 1.471 ms 1.472 ms 1.473 ms
6 137.221.68.32 (137.221.68.32) 2.626 ms 1.529 ms 1.510 ms
7 213.248.78.166 (213.248.78.166) 1.500 ms 1.555 ms 1.523 ms
8 dls-b21-link.telia. net (62.115.123.136) 33.064 ms 34.051 ms 34.224 ms
9 213.155.130.179 (213.155.130.179) 43.171 ms 43.209 ms 43.259 ms
10 213.155.130.176 (213.155.130.176) 53.874 ms 53.687 ms 53.724 ms
11 213.248.79.222 (213.248.79.222) 258.027 ms 257.994 ms 257.984 ms
12 * * *
13 * * *
14 * * *
15 * * *

24/10/2018 17:11:57 UTC

TRACEROUTE:
traceroute to 174.89.77.78 (174.89.77.78), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.300 ms 0.292 ms 0.292 ms
2 37.244.23.130 (37.244.23.130) 0.493 ms 0.589 ms 0.680 ms
3 24.105.62.146 (24.105.62.146) 1.050 ms 1.073 ms 2.502 ms
4 137.221.66.8 (137.221.66.8) 2.171 ms 2.182 ms 2.247 ms
5 137.221.69.70 (137.221.69.70) 13.762 ms 13.780 ms 13.782 ms
6 137.221.69.34 (137.221.69.34) 1.378 ms 1.169 ms 1.148 ms
7 213.248.78.162 (213.248.78.162) 3.221 ms 2.930 ms 3.001 ms
8 213.248.79.222 (213.248.79.222) 245.386 ms 245.324 ms 245.357 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 qubcpq0957w-lp130-01-174-89-76-1.dsl.bell. ca (174.89.76.1) 255.418 ms 255.459 ms 255.632 ms

24/10/2018 17:11:57 UTC

PING:
PING 174.89.77.78 (174.89.77.78) 56(84) bytes of data.

— 174.89.77.78 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3001ms

24/10/2018 17:11:57 UTC

PING:
PING 174.89.77.78 (174.89.77.78) 56(84) bytes of data.

— 174.89.77.78 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2999ms

24/10/2018 17:11:57 UTC

MTR:
Start: Wed Oct 24 17:11:57 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.3 0.4 0.0
2.|-- 37.244.23.130 0.0% 10 0.6 0.6 0.5 0.8 0.0
3.|-- 24.105.62.146 0.0% 10 2.3 1.1 0.8 2.3 0.3
4.|-- 137.221.66.8 0.0% 10 2.3 2.1 2.0 2.3 0.0
5.|-- 137.221.69.70 0.0% 10 3.6 10.7 1.8 75.9 23.2
6.|-- 137.221.69.34 0.0% 10 1.3 1.2 1.2 1.3 0.0
7.|-- 213.248.78.162 0.0% 10 1.9 2.1 1.9 3.3 0.0
8.|-- 213.248.79.222 0.0% 10 245.5 245.4 245.3 245.5 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15.|-- qubcpq0957w-lp130-01-174-89-76-1.dsl.bell. ca 0.0% 10 255.3 255.3 255.2 255.4 0.0
16.|-- ??? 0.0% 0 0.0 0.0 0.0 0.0 0.0

24/10/2018 17:11:57 UTC

MTR:
Start: Wed Oct 24 17:11:57 2018 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.3 0.0
2.|-- 37.244.22.130 0.0% 10 0.5 0.6 0.5 0.8 0.0
3.|-- 24.105.30.166 0.0% 10 0.9 1.3 0.7 2.9 0.3
4.|-- 137.221.66.0 0.0% 10 1.5 1.6 1.4 1.7 0.0
5.|-- 137.221.68.66 0.0% 10 1.5 1.7 1.3 4.3 0.7
6.|-- 137.221.68.32 0.0% 10 1.2 1.3 1.1 1.9 0.0
7.|-- 213.248.78.166 0.0% 10 1.5 1.6 1.4 3.3 0.3
8.|-- dls-b21-link.telia. net 0.0% 10 33.9 33.4 32.5 36.0 0.9
9.|-- 213.155.130.179 0.0% 10 43.0 43.1 42.8 43.4 0.0
10.|-- 213.155.130.176 0.0% 10 53.7 53.8 53.7 54.0 0.0
11.|-- 213.248.79.222 0.0% 10 258.7 258.7 258.7 258.9 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
15.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
16.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
17.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
18.|-- qubcpq0957w-lp130-01-174-89-76-1.dsl.bell. ca 0.0% 10 271.5 271.5 271.5 271.8 0.0
19.|-- ??? 0.0% 0 0.0 0.0 0.0 0.0 0.0

24/10/2018 17:11:57 UTC

And finally here is the WinMTR file, run over 10mins:

Summary

|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
mynetwork - 0 587 587 0 0 28 0
10.11.18.105 - 1 568 565 0 23 4430 5
10.178.206.164 - 0 587 587 0 1 33 1
10.178.206.165 - 0 587 587 0 1 30 1
tcore4x-quebec14_0-4-0-2.net.bell. ca - 0 587 587 4 8 33 12
tcore3-montreal02_hundredgige2-12-0-1.net.bell. ca - 0 587 587 4 8 31 11
bx1-montreal02_hundredgige0-1-0-0.net.bell. ca - 0 587 587 4 5 28 5
ix-ae-10-0.tcore1.w6c-montreal.as6453. net - 0 587 587 4 5 37 5
if-ae-12-2.tcore1.mtt-montreal.as6453. net - 0 587 587 12 13 43 13
if-ae-0-2.tcore2.mtt-montreal.as6453. net - 0 587 587 12 13 42 13
if-ae-5-2.tcore2.n0v-new-york.as6453. net - 0 587 587 12 13 38 14
if-ae-2-2.tcore1.n0v-new-york.as6453. net - 0 587 587 12 13 41 14
if-ae-7-2.tcore1.nto-new-york.as6453. net - 0 587 587 12 13 38 13
if-ae-9-2.tcore1.n75-new-york.as6453. net - 0 587 587 12 13 44 13
66.110.96.157 - 0 587 587 11 13 43 13
No response from host - 100 118 0 0 0 0 0
No response from host - 100 118 0 0 0 0 0
No response from host - 100 118 0 0 0 0 0
No response from host - 100 118 0 0 0 0 0
No response from host - 100 118 0 0 0 0 0
No response from host - 100 118 0 0 0 0 0
No response from host - 100 118 0 0 0 0 0
No response from host - 100 118 0 0 0 0 0
No response from host - 100 118 0 0 0 0 0
54.240.244.42 - 0 587 587 141 142 167 142
54.240.244.214 - 0 587 587 141 147 210 199
54.240.244.217 - 0 587 587 143 144 170 144
177.72.240.253 - 0 587 587 142 144 215 143
No response from host - 100 118 0 0 0 0 0
No response from host - 100 118 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Hope this can help.
Good luck resolving the issue,
Have a nice day.

31

I’m having this problem as well. I live in Ontario and use Bell Canada. On IsTheServiceDown.ca, it says Bell has been having problems since 10:00 AM EST today. So this might be part of MY problem, but I’m not sure about everyone else.

I was matched with other Canadians in QP who said they were also experiencing high latency. I also noticed one player typing exclusively in Spanish, so it was at this point I assumed I was connected to SA or Mexican servers. I’m not certain that this was the case. The problem might be a combination of Bell connection issues and wrong servers?

EDIT: The players were actually speaking Portuguese. I asked the players I was playing with if there were any fellow Canadians and there were maybe one or two others. They said they were experiencing high latency. A different person spoke and said that we are on Brazilian servers. I guess that explains the high latency! lol

32

From the Greater Toronto Area, using Bell, also having the same issues

1 Like
33

Same issues as everyone else. Please blizz I need to PWN

34

Game is currently not playable. The delay is so annoying… Malganis Q already has a built-in mini delay on cast animation so add THAT to the actual DELAY and game = unplayable. FIX THIS !!!

35

Same issues as above, Toronto with Bell ISP

36

In the GTA on Bell having the same latency issue. Would love some type of eta as to when this problem will be solved

37

EVERYBODY POSTING HERE/READING THIS HAVING THIS PROBLEM GO ON TWITTER AND TWEET @BELL @BLIZZARDCS and demand a resolution time or bare minimum that they acknowledge this as being an active issue they have dedicated major ressources to due to the impact (Canada Nationwide with Bell and MORE!) Bell is a MAJOR ISP! Many Affected!

The game is NOT playable at the moment. BROKEN!

Also post on reddit here to get more notice to the issue:

inb4 this is related to the democrats and their OCTOBER SURPRISE from qanon.pub HMMMMM

38

Toronto here, I just played 2 comp matches with chilean players and all the english speaking players are also experiencing high ping, im getting 180+

1 Like
39

I’m out in LA and i’m having a bad latency spike to the server I normally connect too (LAX1), it went from a stable 70-80ms to 230ms. I don’t connect to other servers, but when I join the Asia Servers, (PSE1) had a better latency than (LAX1).

40

Using Bell here in Toronto, getting around 165-170 ms in games since yesterday. Not playable. Traceroute shows a very long and elongated route.

1 Like
41

Same here. I’m in Manitoba using Bell and I’ve been connecting to the sael server all day. 200+ ping and no english speakers in game. It’s pretty frustrating to be honest.

1 Like