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

Technical Support
29

It’s actually kinda ridiculous cause it isnt. people have been reporting perfectly fine connections with other games. it’s literally only over watch that is having these issues. regardless of ISP. I’m with rogers and I can barely play

3 Likes
31

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

Host - % Sent Recv Best Avrg Wrst Last
mynetwork - 0 726 726 0 0 8 0
10.11.0.169 - 0 726 726 3 7 32 7
ngflon0522w_lo0_symp.net.bell.ca - 0 726 726 3 4 15 4
10.178.206.35 - 0 726 726 3 4 41 3
tcore3-stcatharines10_bundle-ether2.net.bell.ca - 0 726 726 5 8 19 9
tcore3-toronto47_hu2-3-0-1.net.bell.ca - 0 726 726 6 10 19 12
tcore3-toronto01_0-1-0-0.net.bell.ca - 0 726 726 6 10 20 10
bx2-toronto01_et5-1-0.net.bell.ca - 0 726 726 6 6 42 8
ae55.bar2.Toronto1.Level3.net - 1 722 721 16 17 36 17
4.69.216.226 - 23 380 294 23 25 37 26
BLIZZARD-EN.ear1.NewYork5.Level3.net - 0 726 726 24 27 57 29
ae1-br01-eqny8.as57976.net - 0 726 726 78 81 237 79
et-0-0-2-br02-eqch2.as57976.net - 3 644 630 30 135 4398 3079
et-0-0-3-br02-eqla1.as57976.net - 0 726 726 80 87 216 92
No response from host - 100 145 0 0 0 0 0
No response from host - 100 145 0 0 0 0 0
No response from host - 100 145 0 0 0 0 0
No response from host - 100 145 0 0 0 0 0
No response from host - 100 145 0 0 0 0 0
No response from host - 100 145 0 0 0 0 0
No response from host - 100 145 0 0 0 0 0
No response from host - 100 145 0 0 0 0 0
No response from host - 100 145 0 0 0 0 0
No response from host - 100 145 0 0 0 0 0
No response from host - 100 145 0 0 0 0 0
No response from host - 100 145 0 0 0 0 0
No response from host - 100 145 0 0 0 0 0
No response from host - 100 145 0 0 0 0 0
No response from host - 100 145 0 0 0 0 0
No response from host - 100 145 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______

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

1 Like
32

Your home equipment is showing major packet loss, which you’d have to address with the ISP.

33

So it’s a trend with others as well as myself and we are all experiencing it ONLY when playing Overwatch? That doesn’t make sense that it’s a packet loss issue with my ISP when other games run without lagging.

34

It’s likely you’re experiencing both problems. Networking equipment just doesn’t last forever. The issue we see in your test is hardware related or the line coming into your house. But you’re also experiencing the routing problem which is something Bell has to resolve.

35

As far as connections go, keep in mind that the route that your connection takes to get to one server may be different than another. Not all servers for all applications are in the same place and even if they’re in the same general location, the routing may differ. Can think of it like driving. If I were to go to the beach as opposed to the mountains, I’d likely take a different route. There may be traffic or some other delay on one route as opposed to another which would cause issues getting to the destination.

With that said, looking over the WinMTR results that have been posted, each one is showing packet loss when routing to the servers.

@Macster
The tests that you’ve provided have shown packet loss starting on the very first hop consistently:

mynetwork - 10	1071	973	0	1	43	1
mynetwork - 24	417	319	0	1	10	1
mynetwork - 7	1529	1431	0	1	43	1

This is generally the computer’s connection to the router\modem. If you are on wireless, we suggest switching to a wired connection. If you’re already on wired, then you’d want to contact the ISP for assistance clearing up the packet loss on that first hop.

For other tests we’re generally seeing packet loss starting as soon as the connection reaches the Level 3 network. Its possible that this may be due to shaping. With routing issues there’s two things that can be done as a workaround or at least to help confirm the issue. This would involve either testing on a different network such as a mobile connection or connecting through a VPN. But in general, for issues affecting a specific ISP\region, it would be best to contact the ISP.

1 Like
36

Thanks for the information Zhyxen; is there any way Blizzard can reach out to the ISP as well? Bell in particular is notoriously bad for being useful to individual customers.

1 Like
37

Ok I’ll give Bell a call and see if I can get this resolved. Thanks for the help.

Edit: I still don’t think they understand what the real issue is I was trying to come across so I’m not sure if Overwatch support is able to get in touch with the ISP to explain the issue that’s happening. All they did was adjust my internet speeds by adding +2MBps?

38

My ticket was elevated to their level 5 whatever the heck. The representative thought I was calling about an issue with my modem and didn’t understand the issue was related to their networks routing to Overwatch. Now they’re conferring with colleagues, but still doesn’t seem to be grasping my issue. Ugh, Bell.

39

enter the labyrinth…

40

Hello again Zhyxen;

Bell has informed me that since the packet loss happens once it reaches New York (or on wards) it’s out of their control and there is nothing they can do to support their customers.

Any ideas on your end?

41

Blizzard responded to me saying that they are working with Bell to figure out the issue once I put a technical support ticket in. They don’t have an ETA when it’s going to be fixed but they are looking at the issue.

42

I’d like to point out once again thats its not just Bell users having this issue. I’m on rogers and its only overwatch that has these “packet losses”. My freind is with Tekksavvy and hes reporting the same thing. it’s somewhere on blizzards end for sure

1 Like
43

What am i doing wrong? why can i not post my WinMTR txt file ?

44

What about me?

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

Host - % Sent Recv Best Avrg Wrst Last
router.dlink. com - 0 484 484 0 2 751 0
10.11.2.81 - 0 484 484 1 7 761 2
10.178.206.86 - 0 484 484 5 8 765 7
10.178.206.87 - 0 484 484 3 6 758 4
tcore4x-hamilton14_0-4-0-0.net.bell.ca - 0 484 484 4 11 754 10
tcore4-toronto12_bundle-ether19.net.bell.ca - 0 484 484 4 10 746 7
tcore3-toronto01_hundredgige0-8-0-0.net.bell.ca - 0 484 484 4 9 753 7
bx2-toronto01_et5-1-0.net.bell.ca - 0 484 484 4 7 759 5
ae55.bar2.Toronto1.Level3. net - 0 484 484 17 20 760 17
4.69.216.226 - 20 273 220 0 41 537 39
BLIZZARD-EN.ear1.NewYork5.Level3. net - 0 484 484 23 27 767 31
ae1-br01-eqny8.as57976. net - 0 484 484 23 29 774 24
et-0-0-2-br02-eqch2.as57976. net - 0 484 484 30 154 859 44
No response from host - 100 97 0 0 0 0 0
No response from host - 100 97 0 0 0 0 0
No response from host - 100 97 0 0 0 0 0
No response from host - 100 97 0 0 0 0 0
No response from host - 100 97 0 0 0 0 0
No response from host - 100 97 0 0 0 0 0
No response from host - 100 97 0 0 0 0 0
No response from host - 100 97 0 0 0 0 0
No response from host - 100 97 0 0 0 0 0
No response from host - 100 97 0 0 0 0 0
No response from host - 100 97 0 0 0 0 0
No response from host - 100 97 0 0 0 0 0
No response from host - 100 97 0 0 0 0 0
No response from host - 100 97 0 0 0 0 0
No response from host - 100 97 0 0 0 0 0
No response from host - 100 97 0 0 0 0 0
No response from host - 100 97 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______

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

45

look at all the responses here.

Mine is the same:

4.69.216.226 is the problem. Whatever that is, or wherever that is. It is the point just before Blizzard servers.

So it is likely in New York state and not something that Canadian ISPs can fix. But perhaps Blizzard can contact or figure out what is wrong at that IP address.

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

Host - % Sent Recv Best Avrg Wrst Last
mynetwork - 0 881 881 0 0 9 0
10.11.0.137 - 0 881 881 3 6 23 3
No response from host - 100 176 0 0 0 0 0
tcore2-kitchener06_ae5.net.bell.ca - 0 881 881 6 7 20 9
dis17-kitchener06_10-0-0.net.bell.ca - 0 881 881 3 4 15 4
tcore4-kitchener06_0-8-0-0.net.bell.ca - 0 881 881 6 7 21 8
tcore4-toronto63_bundle-ether30.net.bell.ca - 0 881 881 6 10 22 9
tcore4-toronto01_hundredgige0-8-0-0.net.bell.ca - 0 881 881 6 8 17 8
bx2-toronto01_et7-1-0.net.bell.ca - 0 881 881 6 7 31 7
ae55.bar2.Toronto1.Level3.net - 0 881 881 18 19 45 19
4.69.216.226 - 19 502 407 28 42 55 39
BLIZZARD-EN.ear1.NewYork5.Level3.net - 0 881 881 25 27 57 35
ae1-br01-eqny8.as57976.net - 0 881 881 25 27 97 26
et-0-0-2-br02-eqch2.as57976.net - 1 840 832 32 136 4355 69
No response from host - 100 176 0 0 0 0 0
No response from host - 100 176 0 0 0 0 0
No response from host - 100 176 0 0 0 0 0
No response from host - 100 176 0 0 0 0 0
No response from host - 100 176 0 0 0 0 0
No response from host - 100 176 0 0 0 0 0
No response from host - 100 176 0 0 0 0 0
No response from host - 100 176 0 0 0 0 0
No response from host - 100 176 0 0 0 0 0
No response from host - 100 176 0 0 0 0 0
No response from host - 100 176 0 0 0 0 0
No response from host - 100 176 0 0 0 0 0
No response from host - 100 176 0 0 0 0 0
No response from host - 100 176 0 0 0 0 0
No response from host - 100 176 0 0 0 0 0
No response from host - 100 176 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______

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

46

Turns out that ip is Kansas
…

So something 8s wrong.

47

Call our ISP tho :joy:

1 Like
48

My ISP isn’t in Kansas :thinking:

49

We’re not in Kansas anymore

I’ve posted my WinMTR twice in this thread, once in another. Here’s another time:

The game is really not fun to play at 300 ms latency. What is going on?

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

Host - % Sent Recv Best Avrg Wrst Last
router.dlink. com - 0 509 509 0 0 5 0
10.11.2.81 - 0 509 509 0 6 1103 2
10.178.206.86 - 0 509 509 5 6 13 5
10.178.206.87 - 0 509 509 3 4 25 3
tcore4x-hamilton14_0-4-0-0.net.bell.ca - 0 509 509 4 9 15 9
tcore4-toronto12_bundle-ether19.net.bell.ca - 0 509 509 5 9 13 9
tcore3-toronto01_hundredgige0-8-0-0.net.bell.ca - 0 509 509 4 6 10 8
bx2-toronto01_et5-1-0.net.bell.ca - 0 509 509 4 5 37 12
ae55.bar2.Toronto1.Level3. net - 0 509 509 17 17 35 18
4.69.216.226 - 22 273 213 37 43 47 45
BLIZZARD-EN.ear1.NewYork5.Level3. net - 0 509 509 23 25 46 24
ae1-br01-eqny8.as57976. net - 0 509 509 23 26 136 24
et-0-0-2-br02-eqch2.as57976. net - 3 456 445 275 384 2967 406
No response from host - 100 102 0 0 0 0 0
No response from host - 100 102 0 0 0 0 0
No response from host - 100 102 0 0 0 0 0
No response from host - 100 102 0 0 0 0 0
No response from host - 100 102 0 0 0 0 0
No response from host - 100 102 0 0 0 0 0
No response from host - 100 102 0 0 0 0 0
No response from host - 100 102 0 0 0 0 0
No response from host - 100 102 0 0 0 0 0
No response from host - 100 102 0 0 0 0 0
No response from host - 100 102 0 0 0 0 0
No response from host - 100 102 0 0 0 0 0
No response from host - 100 102 0 0 0 0 0
No response from host - 100 102 0 0 0 0 0
No response from host - 100 102 0 0 0 0 0
No response from host - 100 102 0 0 0 0 0
No response from host - 100 102 0 0 0 0 0
________________________________________________ ______ ______ ______ ______ ______ ______

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