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

Technical Support
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

50

It’s funny how I was told it’s packet loss and to contact my ISP and now that people are posting their Mtr’s it seems everyone is having the same issue where we all need to contact our ISP’s? I contacted Bell and like a few other users I have seen, they said they can’t do anything about it and it is on Blizzards end.

51

It’s been weeks now, Bell says there is nothing they can do about it, my internet is working perfectly aside from this one thing. Game is pretty much unplayable, please escalate this issue and get it fixed ASAP.

1 Like
52

It’s because they’re cherry picking certain cases in this thread. They aren’t looking at the people who are all reporting the same problem.

2 Likes
53

Definitely on Blizzard’s end, only losing packets on the receiving end, but 0% loss on sending.

3 Likes
54

Started Today.
Mediacom
Central US
ORD1
| ae1-br01-eqch2.as57976.net - 7 | 235 | 220 | 10 | 36 | 181 | 24 |

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.0.1 -    0 |  294 |  294 |    0 |    0 |    3 |    0 |
|           173-26-112-1.client.mchsi.com -    0 |  294 |  294 |    3 |   12 |   66 |   13 |
|                            172.30.9.165 -    0 |  294 |  294 |    4 |   13 |   33 |   18 |
|            68-66-73-70.client.mchsi.com -    0 |  294 |  294 |    8 |   14 |   33 |   15 |
|              po10.chgil001er1.mchsi.com -    0 |  294 |  294 |    6 |   15 |   42 |   16 |
|be-123-pe01.350ecermak.il.ibone.comcast.net -    0 |  294 |  294 |    7 |   14 |   29 |   11 |
|173-167-56-238-static.hfc.comcastbusiness.net -    0 |  294 |  294 |    6 |   15 |   47 |   47 |
|              ae1-br01-eqch2.as57976.net -    7 |  235 |  220 |   10 |   36 |  181 |   24 |
|                   No response from host -  100 |   59 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   59 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   59 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   59 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   59 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   59 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   59 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   59 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   59 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   59 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   59 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   59 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   59 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   59 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   59 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   59 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   59 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   59 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   59 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   59 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   59 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   59 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
55

Overwatch is LITERALLY unplayable the way this latency bug is right now. You get into a match and spend the next 3-15mins trying to hit anything and spending the majority dead. thank god im not doing comp untill this is resolved. Not going to ruin my SR cause of some stupid server problems

3 Likes
56

Please fix this . Problem is just before Blizz server.

Ip : 4.69.216.226

40% packet loss there.

1 Like
57
WinMTR Statistics

WinMTR statistics

Host % Sent Recv Best Avrg Wrst Last
mynetwork 0 167 167 0 0 3 0
10.11.0.137 0 167 167 3 6 19 4
No response from host 100 33 0 0 0 0 0
tcore1-kitchener06_ae5.net.bell.ca 0 167 167 6 7 12 8
dis18-kitchener06_2-0-0.net.bell.ca 0 167 167 4 4 18 4
tcore4-kitchener06_0-9-0-0.net.bell.ca 0 167 167 7 7 13 7
tcore4-toronto63_bundle-ether30.net.bell.ca 0 167 167 6 10 17 11
tcore4-toronto01_hundredgige0-8-0-0.net.bell.ca 0 167 167 6 8 13 9
bx2-toronto01_et7-1-0.net.bell.ca 0 167 167 7 7 30 7
ae55.bar2.Toronto1.Level3.net 0 167 167 19 19 37 19
4.69.216.226 31 76 53 0 21 23 21
BLIZZARD-EN.ear1.NewYork5.Level3.net 0 167 167 25 28 59 26
ae1-br01-eqny8.as57976.net 0 167 167 26 33 234 27
et-0-0-2-br02-eqch2.as57976.net 7 127 119 283 451 3822 2192
No response from host 100 33 0 0 0 0 0
No response from host 100 33 0 0 0 0 0
No response from host 100 33 0 0 0 0 0
No response from host 100 33 0 0 0 0 0
No response from host 100 33 0 0 0 0 0
No response from host 100 33 0 0 0 0 0
No response from host 100 33 0 0 0 0 0
No response from host 100 33 0 0 0 0 0
No response from host 100 33 0 0 0 0 0
No response from host 100 33 0 0 0 0 0
No response from host 100 33 0 0 0 0 0
No response from host 100 33 0 0 0 0 0
No response from host 100 33 0 0 0 0 0
No response from host 100 33 0 0 0 0 0
No response from host 100 33 0 0 0 0 0
No response from host 100 33 0 0 0 0 0
1 Like
58

Blizz, please post what ever resolved this once you are back operational, everytime we call our ISP for this stuff they have no clue, and magically a day later everything is resolved. Everything usually works perfectly so am not gonna go on a rant, but forwarding people to their ISP sounds like a waste of time when it’s a peer having issues.

1 Like
59

Not Blizzard staff, but can offer some explanation:
You’re paying your ISP to route your traffic, Blizzard isn’t. So when it’s a routing partner that your ISP uses to reach Blizzard, your ISP is the only one who can resolve it. Blizzard can request they look into it, which they usually report back that they are doing so, but they can’t force an ISP or their partners to fix anything.

It does suck that whomever you end up speaking to at an ISP has no idea what you’re trying to convey, and usually you have to be escalated 4-5 times before you reach someone who understands. But that’s an issue of your ISP not training employees for that type of report from a customer :frowning: All you can really do is keep bothering them to work it out with the companies they buy routing capability from and hope they resolve it.

60

But why are we being routed through Kansas in order to reach the NewYork server?

61

The only US server locations for Overwatch are Chicago and LA, if that’s the server you’re referring to. Aside from that, routing mistakes happen all the time, as well as hub maintenance. If a certain area is under maintenance (or [natural] disaster happens), the traffic will be routed around it. Not always done the most efficient way, that’s for sure. But having a bunch of customers call into their ISP and say they are unhappy with the speed they are reaching servers helps them diagnose and get on fixing the problem.

62

My connection to LA was fine. It sent me to LAX1 during a skirmish. It’s the Chicago one causing me issues. (last night) I can update later in edit if it’s still happening tonight.

It’s perfectly fine tonight.

63

Hey Blizz,

Ya’ll plan on doing something about this any time soon? I question the feasibility of having individual customers call a giant ISP versus a big company like you working with them on behalf of all of us.

EDIT: Took their advice and called Bell. They said it’s definitely not an issue with them. So what gives?

1 Like
64

Yeah, it’s not their network issue, it’s the routing partner they use to reach Blizzard. But basically, they are the only company that can put pressure on them to fix it.

65

Seems unlikely that Blizzard can do less to solve this problem than their individual customer, given the issue effect most of Canada and not a single ISP but multiple ISPs.

As well this problem ONLY exists with Blizzard games and not other games.

But I guess if a couple hundred thousand stop playing their games, maybe they will wake up and do something.

1 Like