Another 1016 ffs

Technical Support
1

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

Host - % Sent Recv Best Avrg Wrst Last
192.168.0.250 - 0 1178 1178 0 0 3 0
10.13.8.254 - 0 1177 1177 2 20 118 3
10.79.1.254 - 0 1177 1177 1 19 149 35
10.83.3.254 - 0 1176 1176 2 20 122 21
10.83.2.254 - 0 1176 1176 2 20 140 23
10.10.26.254 - 1 1165 1162 3 26 143 39
10.11.1.251 - 0 1175 1175 3 25 195 15
10.11.3.1 - 0 1175 1175 4 27 142 6
105.233.39.161 - 0 1176 1176 4 26 136 8
105.233.39.156 - 1 1173 1172 4 26 210 33
105.233.13.254 - 1 1172 1171 12 38 236 56
105.233.31.25 - 0 1175 1175 12 35 148 27
105.233.31.45 - 1 1164 1161 152 176 280 169
195.66.226.234 - 1 1167 1165 153 183 317 171
ae1-br01-eqld5.as57976*net - 3 1076 1052 0 276 3084 313
No response from host - 100 238 0 0 0 0 0
137.221.65.77 - 8 821 756 0 638 4540 324
bond0-vs01-eqam1.as57976*net - 0 1175 1175 159 185 309 175
185.60.112.158 - 1 1167 1165 159 183 334 161
________________________________________________ ______ ______ ______ ______ ______ ______

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

So here is AGAIN for the 99 time ANOTHER WinMTR. from packet 0 to 1167 i had 7 error 1016.

BLIZZARD FIX THIS DAMMIT

2

What is this? Can u eleborate?

3

This is like a network “path” from the user’s end to Blizzard’s servers. Commonly used to prove that it’s Blizzard’s fault instead of user’s, like if Blizzard really cared about it.