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

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.

Can we get an ETA on this?

I haven’t been able to play properly for atleast a week… I understand that it’s not an easy fix, but it’s very frustrating.

So I contacted Bell for the 3rd time and they still didn’t understand what I was trying to say. It’s very frustrating.

4.69.216.226

This IP seems to be a reoccuring issue with everyone here.

2 Likes

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

Host - % Sent Recv Best Avrg Wrst Last
mynetwork - 0 475 475 0 0 17 0
10.11.19.129 - 0 475 475 1 4 30 30
No response from host - 100 95 0 0 0 0 0
10.178.206.165 - 0 475 475 1 2 24 2
tcore4x-quebec14_0-4-0-2.net.bell.ca - 0 475 475 4 9 23 10
tcore3-montreal02_hundredgige2-12-0-1.net.bell.ca - 0 475 475 5 9 37 10
bx7-montreal02_ae4.net.bell.ca - 0 475 475 4 5 24 5
lag-107.bear2.Montreal2.Level3.net - 15 298 254 4 6 33 6
4.69.216.226 - 17 284 236 14 16 37 15
BLIZZARD-EN.ear1.NewYork5.Level3.net - 0 475 475 19 22 49 26
ae1-br01-eqny8.as57976.net - 1 466 464 299 350 462 350
et-0-0-2-br02-eqch2.as57976.net - 1 462 459 298 370 1326 340
be2-pe01-eqch2.as57976.net - 1 467 465 301 350 462 352
24.105.62.129 - 2 455 450 300 349 462 366
________________________________________________ ______ ______ ______ ______ ______ ______

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

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

Host - % Sent Recv Best Avrg Wrst Last
mynetwork - 0 632 632 0 0 7 1
10.11.18.105 - 0 632 632 1 4 24 2
10.178.206.164 - 0 632 632 0 1 3 1
10.178.206.165 - 0 632 632 0 1 41 2
tcore4x-quebec14_0-4-0-2.net.bell.ca - 0 632 632 5 9 16 6
tcore3-montreal02_hundredgige2-12-0-1.net.bell.ca - 0 632 632 4 8 14 12
bx7-montreal02_ae4.net.bell.ca - 0 632 632 4 5 25 5
lag-107.bear2.Montreal2.Level3.net - 19 365 298 0 5 11 5
4.69.216.226 - 26 314 235 0 24 40 40
BLIZZARD-EN.ear1.NewYork5.Level3.net - 0 632 632 19 22 58 20
ae1-br01-eqny8.as57976.net - 1 628 627 218 317 475 332
et-0-0-2-br02-eqch2.as57976.net - 1 628 627 218 322 1016 329
be2-pe02-eqch2.as57976.net - 1 628 627 218 315 372 329
24.105.62.129 - 0 632 632 219 316 372 340
________________________________________________ ______ ______ ______ ______ ______ ______

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

Same issue windsor ontario bell

40-70 ping near bell Toronto. I thought it was blizzards fault for randomly disconnecting me from the server for a short-term ping spike but lo and behold, its bell yet again.

I still don’t understand how these haven’t been purged yet. I feel your pain guys.

Lets hope it gets solved during this weekend atleast.

1 Like

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

Host - % Sent Recv Best Avrg Wrst Last
mynetwork - 0 485 485 0 0 2 1
10.11.19.129 - 0 485 485 1 4 36 2
No response from host - 100 97 0 0 0 0 0
10.178.206.165 - 0 485 485 1 2 22 1
tcore4x-quebec14_0-4-0-2.net.bell.ca - 1 481 480 5 9 15 13
tcore3-montreal02_hundredgige2-12-0-1.net.bell.ca - 0 485 485 4 8 13 9
bx7-montreal02_ae4.net.bell.ca - 0 485 485 4 5 26 5
lag-107.bear2.Montreal2.Level3.net - 17 291 243 5 5 11 6
4.69.216.226 - 22 262 206 0 17 33 16
BLIZZARD-EN.ear1.NewYork5.Level3.net - 0 485 485 19 22 62 20
ae1-br01-eqny8.as57976.net - 0 485 485 174 313 450 174
et-0-0-2-br02-eqch2.as57976.net - 1 466 462 169 327 3289 169
be2-pe01-eqch2.as57976.net - 0 485 485 176 313 361 176
24.105.62.129 - 0 485 485 171 312 360 171
________________________________________________ ______ ______ ______ ______ ______ ______

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

4.69.216.226

This IP is still a problem. The lag is STILL a problem.

The times I don’t have lag are the times I am not routed through that IP.

I get what you’re saying, however, I find it oddly coincidental that all of these issues began when the servers went kaput last Sunday. Prior to that, there were no issues.

1 Like

First time being matched on East Coast in a little over a week, still getting bad ping as if i were still on West Coast (~85-120ms) compared to my normal on East Coast (40-65ms).
NOTE: For 4 links i had to add (dot) where a . would be because i cant post links! Sorry.

Shaw Communications
Winnipeg, Manitoba
|------------------------------------------------------------------------------------------|
| WinMTR statistics |

Host - % Sent Recv Best Avrg Wrst Last
192.168.0.1 - 21 144 115 0 1 27 1
No response from host - 100 52 0 0 0 0 0
64.59.181.29 - 36 108 70 0 58 465 12
rc3sc-hge0-9-0-0.wp.shawcable(dot)net - 24 134 102 10 34 225 10
rc4ec-be25-1.il.shawcable(dot)net - 87 59 8 0 143 473 32
eqix-ix-ch1.blizzard(dot)com - 19 150 122 0 64 375 28
ae1-br02-eqch2.as57976(dot)net - 57 80 35 0 77 378 128
No response from host - 100 52 0 0 0 0 0
No response from host - 100 52 0 0 0 0 0
No response from host - 100 52 0 0 0 0 0
No response from host - 100 52 0 0 0 0 0
No response from host - 100 52 0 0 0 0 0
No response from host - 100 52 0 0 0 0 0
No response from host - 100 52 0 0 0 0 0
No response from host - 100 52 0 0 0 0 0
No response from host - 100 52 0 0 0 0 0
No response from host - 100 52 0 0 0 0 0
No response from host - 100 52 0 0 0 0 0
No response from host - 100 52 0 0 0 0 0
No response from host - 100 52 0 0 0 0 0
No response from host - 100 52 0 0 0 0 0
No response from host - 100 52 0 0 0 0 0
No response from host - 100 52 0 0 0 0 0
No response from host - 100 52 0 0 0 0 0
No response from host - 100 52 0 0 0 0 0
No response from host - 100 52 0 0 0 0 0
No response from host - 100 52 0 0 0 0 0
No response from host - 100 52 0 0 0 0 0
No response from host - 100 52 0 0 0 0 0
No response from host - 100 52 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______

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

Server: ORD1

WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
mynetwork 0 1231 1231 0 0 24 0
10.11.0.137 1 1201 1193 3 7 44 12
No response from host 100 246 0 0 0 0 0
tcore1-kitchener06_ae4.net.bell.ca 1 1223 1221 6 8 60 7
dis18-kitchener06_2-0-0.net.bell.ca 1 1220 1217 4 4 28 5
tcore4-kitchener06_0-9-0-0.net.bell.ca 1 1224 1222 6 8 34 8
tcore4-toronto63_bundle-ether30.net.bell.ca 1 1216 1212 7 11 41 15
tcore4-toronto01_hundredgige0-8-0-0.net.bell.ca 1 1224 1222 6 9 57 10
bx2-toronto01_et7-1-0.net.bell.ca 1 1216 1212 6 7 51 12
ae55.bar2.Toronto1.Level3.net 1 1223 1221 17 20 65 38
4.69.216.226 13 829 728 21 23 41 23
BLIZZARD-EN.ear1.NewYork5.Level3.net 1 1220 1217 25 28 58 27
ae1-br01-eqny8.as57976.net 1 1220 1217 26 28 150 26
et-0-0-2-br02-eqch2.as57976.net 1 1187 1178 97 346 4734 106
No response from host 100 246 0 0 0 0 0
No response from host 100 246 0 0 0 0 0
No response from host 100 246 0 0 0 0 0
No response from host 100 246 0 0 0 0 0
No response from host 100 246 0 0 0 0 0
No response from host 100 246 0 0 0 0 0
No response from host 100 246 0 0 0 0 0
No response from host 100 246 0 0 0 0 0
No response from host 100 246 0 0 0 0 0
No response from host 100 246 0 0 0 0 0
No response from host 100 246 0 0 0 0 0
No response from host 100 246 0 0 0 0 0
No response from host 100 246 0 0 0 0 0
No response from host 100 246 0 0 0 0 0
No response from host 100 246 0 0 0 0 0
No response from host 100 246 0 0 0 0 0

Same problem. Same IP is the Problem.

Ever a fix? Not an issue with other games Blizzard…

I just tried HOTS to check if it was Blizz games/servers as other games worked properly with normal latency (where Overwatch is randomly giving me 40,90,120,and 350-400ms latency).

HOTS latency was a stable 25ms…

Been having a slight ping increase not as worse as people on Bell my ping usually stays at 40 normally but recently it just played around 80 -100 ms same goes to another co-worker of mine who I party up with from time to time

Winnipeg
ISP: Shaw

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

Host - % Sent Recv Best Avrg Wrst Last
hitronhub.home - 1 417 416 3 25 187 27
50.70.224.1 - 1 417 416 9 25 190 18
rc3sc-be111-1.wp.shawcablenet - 1 417 416 10 26 194 10
rc4ec-be25-1.il.shawcablenet - 1 414 412 25 42 194 29
eqix-ix-ch1.blizzardcom - 1 417 416 24 42 167 26
ae1-br02-eqch2.as57976net - 1 417 416 25 60 415 44
No response from host - 100 85 0 0 0 0 0
No response from host - 100 85 0 0 0 0 0
No response from host - 100 85 0 0 0 0 0
No response from host - 100 85 0 0 0 0 0
No response from host - 100 85 0 0 0 0 0
No response from host - 100 85 0 0 0 0 0
No response from host - 100 85 0 0 0 0 0
No response from host - 100 85 0 0 0 0 0
No response from host - 100 85 0 0 0 0 0
No response from host - 100 85 0 0 0 0 0
No response from host - 100 85 0 0 0 0 0
No response from host - 100 85 0 0 0 0 0
No response from host - 100 85 0 0 0 0 0
No response from host - 100 85 0 0 0 0 0
No response from host - 100 85 0 0 0 0 0
No response from host - 100 85 0 0 0 0 0
No response from host - 100 85 0 0 0 0 0
No response from host - 100 85 0 0 0 0 0
No response from host - 100 85 0 0 0 0 0
No response from host - 100 85 0 0 0 0 0
No response from host - 100 85 0 0 0 0 0
No response from host - 100 85 0 0 0 0 0
No response from host - 100 85 0 0 0 0 0
No response from host - 100 85 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______

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

Same issues this month. Toronto, Rogers internet.

Still not fixed…

While we don’t have any updates yet, wanted to let y’all know that this is still on our radar. As with the previous post the spikes that we are seeing are generally occurring when going through Level 3 and so may affect any ISPs that route through there. The only workaround for the time being would likely be to alter the route using a VPN. Past that though, we’re looking into this and will be posting updates as we get them.