High Latency - Bell Canada - Ontario

Support Technical Support
22

Theres another thread about Sasktel issues as well. Looks like people are starting to call and complain.

23

Hey there Drakuloth. I was in contact with sasktel support last night. The issue is definitely with sasktel nodes. I was the one who suggested cloudflare DNS, and even this was not fixing it. Upon doing MTR tests there were three sasktel nodes which had large packet loss. I have a ticket in to sasktel right now. I’ll update when they get back to me.

24

Also side note, for those of you with access to VPNs, linking out of province will avoid the nodes causing issues. 135ms is better than 2300ms for now!

25

Thanks for the updates! Don’t have too much in terms of updates however this is something that we’re currently tracking. Be sure to provide the info previously requested by Drakuloth here. As with previous posts, the only workaround for the time being would be to try setting up a different DNS or using a VPN to bypass the problem nodes.

26

On Sasktel as well. And me and my room-mate are on the same network and are ONLY experiencing problems with WoW. Got lagged out of dungeons, couldn’t use abilities, etc.
Glassdoor:

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

— 204.83.205.190 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

08/01/2019 18:23:12 UTC

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

— 204.83.205.190 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 2998ms

08/01/2019 18:23:12 UTC

TRACEROUTE:
traceroute to 204.83.205.190 (204.83.205.190), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.300 ms 0.290 ms 0.290 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

08/01/2019 18:23:12 UTC

TRACEROUTE:
traceroute to 204.83.205.190 (204.83.205.190), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.466 ms 0.478 ms 0.498 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

08/01/2019 18:23:12 UTC

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

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

08/01/2019 18:23:18 UTC

TRACEROUTE:
traceroute to 204.83.205.190 (204.83.205.190), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.232 ms 0.233 ms 0.241 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

08/01/2019 18:23:18 UTC

MTR:
Start: Tue Jan 8 18:23:12 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

08/01/2019 18:23:12 UTC

MTR:
Start: Tue Jan 8 18:23:12 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.2 0.6 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

08/01/2019 18:23:12 UTC

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

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

08/01/2019 18:23:24 UTC

TRACEROUTE:
traceroute to 204.83.205.190 (204.83.205.190), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.257 ms 0.246 ms 0.255 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

08/01/2019 18:23:24 UTC

MTR:
Start: Tue Jan 8 18:23:17 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.3 0.7 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

08/01/2019 18:23:17 UTC

MTR:
Start: Tue Jan 8 18:23:19 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.5 0.4 0.3 0.6 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

08/01/2019 18:23:19 UTC

winMTR:

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| homeportal - 0 | 379 | 379 | 0 | 1 | 4 | 1 |

|________________________________________________|______|______|______|______|______|______|

27

Doing a tracert to both US Central and US West seems to be working well now (Sasktel ISP):

Tracing route to 24.105.62.129 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms homeportal [172.16.1.254]
2 * * * Request timed out.
3 11 ms 7 ms 7 ms 207.47.190.137
4 39 ms 39 ms 43 ms 142.165.0.114
5 56 ms 59 ms 59 ms nyiix.eqny8.blizzardonline. net [198.32.160.141]
6 102 ms 102 ms 84 ms ae1-br01-eqny8.as57976. net [137.221.71.33]
7 68 ms 67 ms 67 ms et-0-0-2-br02-eqch2.as57976. net [137.221.65.8]
8 86 ms 85 ms 84 ms be2-pe02-eqch2.as57976. net [137.221.69.73]
9 87 ms 84 ms 85 ms chi-eqch2-ia-bons-04.as57976. net [137.221.66.15]
10 85 ms 84 ms 85 ms 24.105.62.129
Trace complete.

Tracing route to 137.221.105.2 over a maximum of 30 hops
1 1 ms <1 ms <1 ms homeportal [172.16.1.254]
2 * * * Request timed out.
3 4 ms 7 ms 7 ms 207.47.190.137
4 44 ms 39 ms 43 ms 142.165.0.114
5 65 ms 56 ms 76 ms nyiix.eqny8.blizzardonline. net [198.32.160.141]
6 91 ms 93 ms 93 ms ae1-br01-eqny8.as57976. net [137.221.71.33]
7 93 ms 97 ms 93 ms et-0-0-3-br01-eqdc2.as57976. net [137.221.65.14]
8 95 ms 93 ms 93 ms xe-0-0-1-1-br01-eqat2.as57976. net [137.221.65.45]
9 95 ms 93 ms 93 ms xe-0-0-0-0-br01-eqda6.as57976. net [137.221.65.48]
10 102 ms 94 ms 93 ms et-0-0-2-br02-swlv10.as57976. net [137.221.65.67]
11 93 ms 93 ms 93 ms et-0-0-67-pe02-swlv10.as57976. net [137.221.83.73]
12 96 ms 93 ms 93 ms 137.221.105.2

Trace complete.

Using the looking glass tool, it’s still failing at hop 14. Here is the trace back to me and MTR for Area 52:

09/01/2019 01:19:50 UTC

TRACEROUTE:
traceroute to 204.83.120.86 (204.83.120.86), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.283 ms 0.289 ms 0.294 ms Blizzard(24.105.18.2) 1.114 ms 1.159 ms 1.165 ms
3 137.221.105.14 (137.221.105.14) 1.173 ms 1.179 ms 1.223 ms
4 137.221.66.22 (137.221.66.22) 1.178 ms 1.183 ms 1.188 ms
5 137.221.83.68 (137.221.83.68) 30.286 ms 30.289 ms 30.309 ms
6 137.221.65.68 (137.221.65.68) 30.040 ms 30.321 ms 30.314 ms
7 137.221.65.1 (137.221.65.1) 30.125 ms 30.132 ms 30.122 ms
8 137.221.65.7 (137.221.65.7) 30.211 ms 30.118 ms 30.114 ms
9 137.221.65.41 (137.221.65.41) 30.289 ms 30.337 ms 30.339 ms
10 137.221.73.32 (137.221.73.32) 29.975 ms 29.818 ms 29.914 ms
11 six2.sasktel. com (206.81.81.188) 34.451 ms 37.832 ms 36.946 ms
12 142.165.0.117 (142.165.0.117) 57.680 ms 57.100 ms 57.058 ms
13 142.165.60.190 (142.165.60.190) 61.270 ms 60.545 ms 60.524 ms
14 * * *
15 207-47-191-61.ngai.static.sasknet.sk.ca (207.47.191.61) 92.107 ms 92.236 ms 92.152 ms

09/01/2019 01:19:53 UTC

MTR:
Start: Wed Jan 9 01:19:50 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.4 0.3 0.6 0.0 Blizzard 0.0% 10 0.7 0.9 0.5 2.0 0.3
3.|-- 137.221.105.14 0.0% 10 0.7 0.7 0.6 1.0 0.0
4.|-- 137.221.66.22 0.0% 10 0.7 0.7 0.6 0.8 0.0
5.|-- 137.221.83.68 0.0% 10 30.4 30.5 30.1 31.5 0.3
6.|-- 137.221.65.68 0.0% 10 223.7 50.2 30.1 223.7 61.0
7.|-- 137.221.65.1 0.0% 10 378.1 65.1 30.1 378.1 110.0
8.|-- 137.221.65.7 0.0% 10 30.3 30.7 30.3 33.2 0.8
9.|-- 137.221.65.41 0.0% 10 30.3 32.8 30.3 54.8 7.7
10.|-- 137.221.73.32 0.0% 10 30.0 30.1 29.9 30.8 0.0
11.|-- six2.sasktel. com 0.0% 10 36.3 36.0 34.7 37.9 0.9
12.|-- 142.165.0.117 0.0% 10 56.1 55.8 54.0 58.2 1.4
13.|-- 142.165.60.190 0.0% 10 55.1 58.7 55.1 62.2 2.3
14.|-- 207-47-190-154.ngai.static.sasknet.sk.ca 20.0% 10 7335. 7304. 7240. 7351. 51.9
15.|-- 207-47-191-61.ngai.static.sasknet.sk.ca 20.0% 10 92.9 92.5 92.3 92.9 0.0
16.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

28

To everyone still experiencing issues, This issue has now been escalated to Sasktel’s Network team after providing them with the problem nodes. They are aware of the specific problem and are looking into a fix

MAJOR UPDATE*****************************************
So apparently the issue was with a major data center in Seattle. Sasktel has confirmed that at 4pm CST this data center was worked on and the issue should be resolved. If anyone still has issues please post here so i can pass along any info.

1 Like
29

Thanks for helping escalate this. Been busy IRL, so I appreciate the persistence.

30

It’s not just you. My ISP is Cogeco and the lag has been pretty bad at times. It might start at 32 or so but then slowly climbs into the 400s and worse at times. It affects my FPS as well as would be expected. The strange part is that at times it will be around 34 but will have a delay of 2 or 3 seconds when I click on an action such as a melee move.

31

I don’t think this is limited to Bell Canada. I’m in Seattle and am having the same issue.

Random spikes in ping anywhere from 700 to 5k.

33

Hey you two,

This issue is long since resolved. If you’re still having problems, they are unrelated. Please check out this thread and follow the instructions to start your own thread if it’s not helpful.