[Oct 22] High Latency - Bell Canada

Located in Halifax, NS, Canada.

Started having ping times at 100ms today. Normally they are around 48ms/52ms.

Server IP connecting to in game: 24.105.43.225

I’ve added “_” in the .net parts to overcome not being able to share links in the post.

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

Host - % Sent Recv Best Avrg Wrst Last
192.168.1.51 - 0 340 340 0 0 1 0
192.168.1.1 - 0 340 340 0 0 2 0
loop0.52w.ba06.drmo.ns.aliant.ne_t - 1 336 335 0 4 19 3
ae17-84.cr02.drmo.ns.aliant.ne_t - 1 336 335 0 3 30 5
ae4.cr02.stjh.nb.aliant.ne_t - 1 336 335 0 6 35 5
ae0.bx01.toro.on.aliant.ne_t - 1 336 335 0 23 47 25
ae52.edge1.Toronto2.Level3.ne_t - 1 336 335 0 24 50 22
No response from host - 100 69 0 0 0 0 0
BLIZZARD-EN.ear3.LosAngeles1.Level3.ne_t - 1 336 335 0 92 150 88
ae1-br01-eqla1.as57976.ne_t - 1 336 335 0 93 202 88
et-0-0-2-br01-swlv10.as57976.ne_t - 1 335 334 0 109 1601 94
137.221.65.133 - 1 336 335 0 100 438 92
No response from host - 100 69 0 0 0 0 0
No response from host - 100 69 0 0 0 0 0
No response from host - 100 69 0 0 0 0 0
No response from host - 100 69 0 0 0 0 0
No response from host - 100 69 0 0 0 0 0
No response from host - 100 69 0 0 0 0 0
No response from host - 100 69 0 0 0 0 0
No response from host - 100 69 0 0 0 0 0
No response from host - 100 69 0 0 0 0 0
No response from host - 100 69 0 0 0 0 0
No response from host - 100 69 0 0 0 0 0
No response from host - 100 69 0 0 0 0 0
No response from host - 100 69 0 0 0 0 0
No response from host - 100 69 0 0 0 0 0
No response from host - 100 69 0 0 0 0 0
No response from host - 100 69 0 0 0 0 0
No response from host - 100 69 0 0 0 0 0
No response from host - 100 69 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______

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

Hey, Abarth! I moved you over to a new thread since the other one was specifically for Century Link.

Thanks for including the WinMTR test! The primary concern with the increase in latency would be the 1% packet loss here.

Packet loss can cause increase in latency. This is starting on the Alient peering network, which will be best addressed by the Internet Service Provider.

I am a bit curious to the server location. Would you happen to know if you’re normally on US Central (ORD1) servers? Could we also have a US Central (IP Address: 24.105.62.129) test to compare?

I’m getting the same issue in Fredericton/NB/Canada

I usually get around 45 ping in ord1 but now I’m getting 100ms ping.

When I ping servers chicago I get an decent response of around 33ms and when I connect to the EU servers (cdg1) I get the usual 120 ping (I get 112ms when I ping servers in paris).

I’m not sure if my ping to LAX1 was affected, I get 120 now but I don’t remember what it used to be. I “think” that’s what I used to get.

Anyway, my ping isn’t affected in any other game. It seems to only be specifically when connecting to the ORD1 server through the overwatch client.

In the past I remember connecting to the Chicago/Central server. I don’t think I’ve ever been auto connected to a west coast server.

Is there anyway to force the game to connect to a specific server? I’ve relaunched it a few times and it connects to west coast every single time.

I did it by joining a custom game in that server. If you hit ctrl+shift+N you can see what server youre on on the top left. LAX1 is west, ORD1 is central.

As for packet losses, if the ctrl+shift+N tool is accurate I get no packet losses after a full game.

There is no way to force a specific server, but if we can try comparing a new test to the US Central servers, it may give us some clues to what may be happening.

You both are close enough in the same area and the same ISP. It seems like there’s definitely an issue with Bell Canada at the moment and it’s connection route to the Overwatch Servers. Could you, bruh, also include a WinMTR test?

I’ll run through some diagnostics to see what’s happening with the average latency as well. Thank you both for your reports :slight_smile:

Thanks.

Here’s a WINMTR of that IP: 24.105.62.129

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

Host - % Sent Recv Best Avrg Wrst Last
192.168.1.51 - 0 45 45 0 0 1 0
192.168.1.1 - 0 45 45 0 0 2 0
loop0.52w.ba06.drmo.ns.aliant.ne_t - 3 41 40 0 4 19 6
be12-83.cr01.drmo.ns.aliant.ne_t - 3 41 40 0 3 7 4
et-5-1-0-50.cr02.drmo.ns.aliant.ne_t - 3 41 40 0 3 15 2
ae4.cr02.stjh.nb.aliant.ne_t - 3 41 40 0 6 8 6
ae0.bx01.toro.on.aliant.ne_t - 3 41 40 0 24 47 23
ae52.edge1.Toronto2.Level3.ne_t - 3 41 40 0 23 32 23
No response from host - 100 9 0 0 0 0 0
BLIZZARD-EN.ear3.LosAngeles1.Level3.ne_t - 3 41 40 0 93 153 88
ae1-br01-eqla1.as57976.ne_t - 3 41 40 0 95 199 87
et-0-0-2-br01-swlv10.as57976.ne_t - 3 41 40 0 89 114 89
137.221.65.133 - 3 41 40 0 90 145 89
be1-pe1-eqch2.as57976.ne_t - 3 41 40 0 87 89 88
24.105.62.129 - 3 41 40 0 88 90 88
________________________________________________ ______ ______ ______ ______ ______ ______

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

I’ll try and connect to a game on the central server and see.

And you’re right. It seems to be only affecting Overwatch at this time. Other games and services seem to be fine.

Thanks so much, Abarth! I am seeing Bell Canada, Nova Scotia and New Brunswick, latency has definitely increased today.

There was some spiked up to 128ms today at around 1AM to 8AM CDT, then it permanently spiked around 12PM Central to around 90-120ms. Based on the test, both LAX1 and ORD1 are around the 90-120ms latency. Both tests are showing the packet loss at this peering network though:

This peering network is outside of our control. Contacting the Bell about the situation with both of the WinMTR tests may be the best route to take.

In the mean time, I went ahead and changed the title for this thread and getting tracking up, as well as checking if other regions are experiencing high latency spikes today. :slight_smile:

screenshot of the ctrl+shift+n
https://i.imgur.co_m/ob78sry.png

ip 24.105.40.203

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

Host - % Sent Recv Best Avrg Wrst Last
mynetwork - 0 7 7 0 0 0 0
loop0.38w.ba07.fctn.nb.aliant.ne_t - 0 7 7 2 6 9 2
be14-181.dr01.fctn.nb.aliant.ne_t - 0 7 7 1 3 8 2
ae3-50.dr02.fctn.nb.aliant.ne_t - 0 7 7 1 4 7 3
ae7.cr02.stjh.nb.aliant.ne_t - 0 7 7 2 5 8 4
ae0.bx01.toro.on.aliant.ne_t - 0 7 7 21 23 26 21
ae52.edge1.Toronto2.Level3.ne_t - 0 7 7 20 23 26 22
No response from host - 100 1 0 0 0 0 0
BLIZZARD-EN.ear3.LosAngeles1.Level3.ne_t - 0 7 7 89 91 95 90
ae1-br01-eqla1.as57976.ne_t - 0 7 7 84 96 156 86
et-0-0-2-br01-swlv10.as57976.ne_t - 0 7 7 93 98 111 111
137.221.65.133 - 0 7 7 85 98 146 96
No response from host - 100 1 0 0 0 0 0
No response from host - 100 1 0 0 0 0 0
No response from host - 100 1 0 0 0 0 0
No response from host - 100 1 0 0 0 0 0
No response from host - 100 1 0 0 0 0 0
No response from host - 100 1 0 0 0 0 0
No response from host - 100 1 0 0 0 0 0
No response from host - 100 1 0 0 0 0 0
No response from host - 100 1 0 0 0 0 0
No response from host - 100 1 0 0 0 0 0
No response from host - 100 1 0 0 0 0 0
No response from host - 100 1 0 0 0 0 0
No response from host - 100 1 0 0 0 0 0
No response from host - 100 1 0 0 0 0 0
No response from host - 100 1 0 0 0 0 0
No response from host - 100 1 0 0 0 0 0
No response from host - 100 1 0 0 0 0 0
No response from host - 100 1 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______

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

Thanks, bruh! Could you run the test a bit longer? around 5-10 minutes is ideal. It looks like this one was ran for around 7 seconds so there isn’t much data to work with.

My bad, thought it was done when the text appeared

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

Host - % Sent Recv Best Avrg Wrst Last
mynetwork - 0 330 330 0 0 5 0
loop0.38w.ba07.fctn.nb.aliant.ne_t - 0 330 330 0 4 27 3
be14-181.dr01.fctn.nb.aliant.ne_t - 0 330 330 0 4 9 7
ae3-50.dr02.fctn.nb.aliant.ne_t - 0 330 330 0 3 47 4
ae7.cr02.stjh.nb.aliant.ne_t - 1 326 325 2 5 25 6
ae0.bx01.toro.on.aliant.ne_t - 0 330 330 19 23 47 22
ae52.edge1.Toronto2.Level3.ne_t - 0 330 330 19 23 61 25
No response from host - 100 65 0 0 0 0 0
BLIZZARD-EN.ear3.LosAngeles1.Level3.ne_t - 0 330 330 88 96 267 91
ae1-br01-eqla1.as57976.ne_t - 0 330 330 83 96 289 90
et-0-0-2-br01-swlv10.as57976.ne_t - 1 326 325 93 99 216 96
137.221.65.133 - 0 329 329 84 117 1009 90
No response from host - 100 65 0 0 0 0 0
No response from host - 100 65 0 0 0 0 0
No response from host - 100 65 0 0 0 0 0
No response from host - 100 65 0 0 0 0 0
No response from host - 100 65 0 0 0 0 0
No response from host - 100 65 0 0 0 0 0
No response from host - 100 65 0 0 0 0 0
No response from host - 100 65 0 0 0 0 0
No response from host - 100 65 0 0 0 0 0
No response from host - 100 65 0 0 0 0 0
No response from host - 100 65 0 0 0 0 0
No response from host - 100 65 0 0 0 0 0
No response from host - 100 65 0 0 0 0 0
No response from host - 100 65 0 0 0 0 0
No response from host - 100 65 0 0 0 0 0
No response from host - 100 65 0 0 0 0 0
No response from host - 100 65 0 0 0 0 0
No response from host - 100 65 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______

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

1 Like

Thanks you, two! Really appreciate it. Still working on checking the other Providences. It looks like so far the latency has increased for those in NS, NB, NL, PE.

@bruh, this one looks pretty different, but the same latency spike happens on the Aliant peering network. There’s some spots of packet loss happening that doesn’t persist.

We still need more tests from other people to fully determine what’s happening on this node, but it’s looking like a configuration or throttling issue by the ISP or peering partner.

Trying to get some people to test on the other ISP here (Eastlink) to see if they’re running into the same problems or not. Will update if/when I get the results.

1 Hour later:

Unfortunately the people I asked seem to have no interest in assisting with testing and the one person that did want to help, WINMTR does not report any results when running it. (Likely PC issue, AntiVirus software, etc). So hopefully some others can chime in.

His ping was about 70 he said which is still high, on server 24.105.42.9, He’s on Bell Aliant (ISP).

My other friend which I have not got results from (and probably won’t) said his ping is 90ms on server 24.195.42.39. He is with Eastlink (ISP). This is a 100/10 connection I believe. 90ms still seems quite high even with that ISP.

Bell Aliant is Fiber to the home. Eastlink is fiber to the pole then coax to the home.

Without the WINMTR tests I know it’s kind of hard to troubleshoot. Hopefully someone else can chime in I guess.

I called Bell Aliant just now. That’s a waste of time. Spoke to two different people that have no comprehension of packet loss or anything like that. So… good luck everyone! lol

Latency is back to normal for me.

Same exact scenario in Rhode Island;

Typically get 45ms latency. Today OBD1 is at 84ms and LAX1 is at 90ms.

Right now it’s only LAX1, can’t get into OBD1 at all.

Edit: using fios fiber

Ping back down to 49ms now. So either it fixed itself or someone fixed it.

Howdy y’all,

I ran some reports on Bell Canada internally and noticed some abnormal packet loss. This was confirmed in several of the winMTR reports. So far the reporting for today looks much improved!!

If anyone is still having high latency and is using Bell Canada ISP please let us know.

Thanks!

Rogers Canada here, latency spikes constantly, unless it’s early morning 6am-11am. Seems like once West Coast is awake my png spikes. They only have servers in Chicago for us east coasters and they’re down most the time from what i’ve read. Please fix this it’s been over a year now sheesh and with overwatch 2 coming out.