[Nov/Dec 2018] Canada - Mid Match Latency Spikes

They could still route us through a different peering partner (Bell that is). I see two Level3 nodes with over 25% packet loss.

Connecting with a VPN and using either GTT or Cogent seems to fix the problem. At this point this is just complete laziness by Bell. Not surprised.

For what it’s worth, add me as another person having this issue. Going from 40-45 to 300-400 latency.

Toronto, On
Bell
Don’t know what winmtr is or how to use it :neutral_face:

They might be able to, I have no idea what their entire network looks like. But ultimately, Blizzard has no say in how they route your data since they aren’t their customer and do not pay for use of any of their hubs. So customers have to call and encourage them to work with their routing peer for a fix.

Also want to add that connecting to vpn keeps my latency at about 50

1 Like

Hi friends,

I wanted to stop in here to let you know we are still gathering data on this. If you are still having issues and are on Bell Canada, please post back with a WinMTR.

We want to help out here and keeping us informed is the best way we have of knowing when something is fixed.

/Nathardrick

1 Like

A Bell CSR just replied to me with this :

just got off the phone with our NOC, they tell me the traffic is clean up until it gets off level 3. 14 hours ago the Blizzard CSR was still gathering reports so hopefully things move today.

How many reports do you guys actually need to do something ?

1 Like

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

Host - % Sent Recv Best Avrg Wrst Last
mynetwork - 0 3974 3974 0 0 11 0
10.11.19.129 - 0 3973 3973 0 4 71 2
No response from host - 100 795 0 0 0 0 0
10.178.206.165 - 0 3973 3973 1 2 25 2
tcore4x-quebec14_0-4-0-2.net.bell.ca - 0 3973 3973 4 9 19 9
tcore3-montreal02_hundredgige2-12-0-1.net.bell.ca - 0 3973 3973 4 9 71 7
bx7-montreal02_ae4.net.bell.ca - 0 3973 3973 4 5 32 5
lag-107.bear2.Montreal2.Level3.net - 10 2842 2558 0 5 76 6
4.69.216.226 - 26 1954 1448 0 15 79 15
BLIZZARD-EN.ear1.NewYork5.Level3.net - 0 3973 3973 19 22 52 28
ae1-br01-eqny8.as57976.net - 0 3972 3972 27 89 614 230
et-0-0-2-br02-eqch2.as57976.net - 2 3753 3709 27 114 4603 219
be2-pe01-eqch2.as57976.net - 0 3973 3973 29 88 264 231
24.105.62.129 - 0 3973 3973 28 87 264 230
________________________________________________ ______ ______ ______ ______ ______ ______

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

Its NOT just bell users though. I’ve had reports from friends who are with different service providers telling me the exact same thing. I myself am in Toronto with rogers and have the exact same issues.

  1. Colbanet (Videotron and Bell Canada subprovider)
  2. Montreal, East Canada
  3. ORD1

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

| WinMTR statistics |

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

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

| Linksys12513 - 0 | 450 | 450 | 0 | 0 | 6 | 0 |

| 17-81-252-216-dsl.colba. net - 15 | 287 | 246 | 7 | 97 | 518 | 21 |

| 10.170.192.58 - 15 | 283 | 241 | 8 | 94 | 524 | 21 |

| 97-83-252-216-static.colba. net - 13 | 303 | 266 | 7 | 100 | 703 | 21 |

| 50.21.165.233 - 13 | 299 | 261 | 7 | 99 | 524 | 15 |

| eth3-4.r1.mad1.es.as5580. net - 11 | 315 | 281 | 7 | 108 | 569 | 13 |

| et-0-0-71.cr5-nyc2.ip4.gtt. net - 14 | 291 | 251 | 15 | 102 | 527 | 29 |

| ip4.gtt. net - 10 | 327 | 296 | 0 | 129 | 632 | 15 |

| ae1-br01-eqny8.as57976. net - 14 | 291 | 251 | 0 | 104 | 526 | 29 |

| et-0-0-2-br02-eqch2.as57976. net - 16 | 279 | 236 | 0 | 122 | 547 | 45 |

| No response from host - 100 | 91 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 91 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 91 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 91 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 91 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 91 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 91 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 91 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 91 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 91 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 91 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 91 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 91 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 91 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 91 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 91 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 91 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 91 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 91 | 0 | 0 | 0 | 0 | 0 |

| No response from host - 100 | 91 | 0 | 0 | 0 | 0 | 0 |

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

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

  1. I didn’t find any place to attach a file? I also had to put a space after the dot of any internet address. (Behind every net in the text)

I’ve got 3 of them posted on this thread since earlier this week. Uninstalled the game today. Games are actually unplayable because of this issue, and given the speed at which this is being fixed, I’ll check back next week and see if any progress has been made.

3 Likes

Well it’s back … and more packet loss. :frowning:

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

Host - % Sent Recv Best Avrg Wrst Last
mynetwork - 0 303 303 0 0 7 0
10.11.19.129 - 0 303 303 0 4 22 2
No response from host - 100 60 0 0 0 0 0
10.178.206.165 - 0 303 303 1 2 24 2
tcore4x-quebec14_0-4-0-2.net.bell.ca - 0 303 303 4 9 15 7
tcore3-montreal02_hundredgige2-12-0-1.net.bell.ca - 0 303 303 4 8 14 6
bx7-montreal02_ae4.net.bell.ca - 0 303 303 4 5 27 5
lag-107.bear2.Montreal2.Level3.net - 20 171 138 4 5 8 5
4.69.216.226 - 24 154 118 15 25 41 20
BLIZZARD-EN.ear1.NewYork5.Level3.net - 0 303 303 19 22 54 42
ae1-br01-eqny8.as57976.net - 10 219 198 320 360 403 360
et-0-0-2-br02-eqch2.as57976.net - 11 213 191 320 361 490 369
be2-pe01-eqch2.as57976.net - 8 231 213 322 360 393 350
24.105.62.129 - 10 219 198 321 359 393 352
________________________________________________ ______ ______ ______ ______ ______ ______

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

Yeah this is ridiculous. I have Tespa coming up. D:

I do not play overwatch but I got redirected to this thread after trying to find information about this issue. My problem seems to be the same as everyone else despite the fact that I play World of Warcraft and also gets worse while raiding (I have seen world ms go as high as 2000). As others stated above, I had Fortnite and WoW opened side by side and no problems whatsoever on Fortnite (20-30ms).

ISP: Bell Canada
Region : Montreal, Eastern Canada
Server : Illidan US (in case it matters)

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

Host - % Sent Recv Best Avrg Wrst Last
mynetwork - 0 162 162 0 0 2 1
10.11.16.145 - 0 162 162 11 14 31 12
No response from host - 100 33 0 0 0 0 0
tcore4-montreal01_hundredgige1-6-0-3.net.bell.ca - 0 162 162 13 16 23 17
dis3-montreal01_0-6-0.net.bell.ca - 0 162 162 12 13 21 12
tcore3-montreal01_1-10-0-1.net.bell.ca - 0 162 162 13 18 26 13
bx2-montreal01_bundle-ether1.net.bell.ca - 0 162 162 12 13 21 14
lag-105.bear1.Montreal2.Level3. net - 0 162 162 12 12 20 12
4.69.216.226 - 20 91 73 22 25 71 71
BLIZZARD-EN.ear1.NewYork5.Level3. net - 0 162 162 24 27 57 31
ae1-br01-eqny8.as57976. net - 0 162 162 37 40 84 38
et-0-0-2-br02-eqch2.as57976. net - 0 162 162 36 38 100 36
be2-pe01-eqch2.as57976. net - 0 162 162 36 36 42 36
24.105.62.129 - 0 162 162 36 37 46 36
________________________________________________ ______ ______ ______ ______ ______ ______

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

Host - % Sent Recv Best Avrg Wrst Last
mynetwork - 1 349 348 0 4 223 6
10.11.5.233 - 1 341 338 0 22 379 25
10.178.206.86 - 1 340 338 7 17 374 7
10.178.206.87 - 1 349 348 0 16 381 13
tcore3x-hamilton14_0-4-0-0.net.bell. ca - 1 344 343 9 21 381 15
tcore3-toronto47_bundle-ether23.net.bell. ca - 1 340 338 10 26 377 17
tcore3-toronto01_0-1-0-0.net.bell. ca - 1 340 338 10 24 381 16
bx2-toronto01_et5-1-0.net.bell. ca - 1 341 338 0 22 380 9
ae55.bar2.Toronto1.Level3. net - 1 340 338 19 33 380 23
4.69.216.226 - 19 200 162 0 46 260 28
BLIZZARD-EN.ear1.NewYork5.Level3. net - 0 348 348 27 41 682 28
ae1-br01-eqny8.as57976. net - 0 348 348 28 41 378 30
et-0-0-2-br02-eqch2.as57976. net - 8 265 245 336 403 3170 374
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 70 0 0 0 0 0
No response from host - 100 70 0 0 0 0 0
No response from host - 100 70 0 0 0 0 0
No response from host - 100 69 0 0 0 0 0
No response from host - 100 70 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

Better but still lagging.

Happens on the west coast too,
Shaw ISP
British Columbia, Canada

Ping spike on the match loading screen, game is unplayable because i just get kicked for inactivity

That address in bold is the one you should mention to your ISP. It is definitely a routing partner that is used to reach Blizzard, but doesn’t appear to be one of their hubs (I’m concluding this from the addresses I normally see). Just tell them

“I am having trouble connecting to Blizzard games. I used a traceroute application to look at my connection, and it is timing out at 4.69.216.226”

That’s all the information they need to investigate (I have dealt with this type of issue more than 5 times with my ISP).

1 Like

I too am reaching between 300 and 500 ms latency in game. ISP Bell near Toronto. Latency is reasonable 50 early morning and later in the evening, but all day, Overwatch is unplayable. First couple of hops are fine, is the ones after Blizzard New York that get bottlenecked. How can I fix this? No point in playing this game if that can’t be rectified.

Howdy!

I wanted to add an update to this thread. Thanks again for helping us gather data around this issue, please keep it up. As Zhyxen reported and explained Here This appears to be a routing issue so the path the connection is taking to our server is why it’s occurring. We are getting this data to the right people to help reach out and look for resolutions!

@ Aurléan Your issue appears to not be fully related to the routing problem issue as it starts at the first ISP hop, you may wish to contact your ISP and show them:
Linksys12513 - 0 | 450 | 450 | 0 | 0 | 6 | 0 |

| 17-81-252-216-dsl.colba. net - 15 | 287 | 246 | 7 | 97 | 518 | 21 |

| 10.170.192.58 - 15 | 283 | 241 | 8 | 94 | 524 | 21 |

| 97-83-252-216-static.colba. net - 13 | 303 | 266 | 7 | 100 | 703 | 21 |

Thank you!

1 Like

Make your own thread.