Not exactly sure when this started happening, but I am getting these short 1 second freezes that happen every few seconds during a match. I looked through the forums and I guess they sometimes ask for a WinMTR, so I did that while in a game for around 5 minutes.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % |
Sent |
Recv |
Best |
Avrg |
Wrst |
Last |
mynetwork - 0 |
481 |
481 |
1 |
7 |
798 |
1 |
10.11.4.33 - 1 |
477 |
476 |
14 |
26 |
856 |
29 |
10.178.206.30 - 0 |
481 |
481 |
14 |
21 |
830 |
17 |
10.178.206.31 - 1 |
477 |
476 |
15 |
30 |
851 |
17 |
tcore4x-london14_0/4/0/2.net.bell.ca - 1 |
478 |
477 |
28 |
34 |
339 |
29 |
tcore4-toronto47_hundredgige2-8-0-1.net.bell.ca - 1 |
478 |
477 |
29 |
37 |
358 |
32 |
tcore4-chicagocp_hundredgige0-3-0-0.net.bell.ca - 1 |
478 |
477 |
28 |
38 |
346 |
32 |
bx6-chicagodt_0-7-0-0.net.bell.ca - 0 |
481 |
481 |
29 |
44 |
827 |
33 |
blizzard_bx6-chicagodt.net.bell.ca - 1 |
478 |
477 |
30 |
36 |
366 |
30 |
ae1-br02-eqch2.as57976 net - 1 |
478 |
477 |
31 |
50 |
357 |
36 |
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 |
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
I also get this big latency spike that shows up on the net graph that appears like the yellow line spiking up and blocked off in color.
And just to be thorough, I ran a traceroute on the same server…
Tracing route to 24.105.41.41 over a maximum of 30 hops
1 1 ms 1 ms 1 ms mynetwork [192.168.2.1]
2 27 ms 99 ms 16 ms 10.11.4.33
3 16 ms 15 ms 16 ms 10.178.206.30
4 15 ms 15 ms 15 ms 10.178.206.31
5 31 ms 29 ms 28 ms tcore4x-london14_0/4/0/2.net.bell.ca [64.230.112.106]
6 31 ms 31 ms 31 ms tcore4-toronto47_hundredgige2-8-0-1.net.bell.ca [64.230.50.244]
7 38 ms 30 ms 31 ms tcore4-chicagocp_hundredgige0-3-0-0.net.bell.ca [64.230.79.159]
8 29 ms 30 ms 32 ms bx6-chicagodt_0-7-0-0.net.bell.ca [64.230.79.87]
9 31 ms 33 ms 30 ms blizzard_bx6-chicagodt.net.bell.ca [184.150.181.57]
10 37 ms 33 ms 38 ms ae1-br02-eqch2.as57976 net [137.221.69.35]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
The connection to your router or modem looks a bit unstable, as it’s shooting up to 798ms ping occasionally. Are you wireless? It might be worth trying a cable, or switching cables and ports on the device.
Looking down the list, your Bell connection is losing packets starting at the neighborhood level and further on. This could be a temporary issue with your ISP, or it could be something you need to call them to address. You could check it later or tomorrow, but if the issue is still there, you might want to call.
As for the freezes, they could be related to your packet loss, but that generally appears as a sort of wobbly/rubberbanding behavior in game rather than a freeze. Are you still playing on the same hardware as before? Wondering about those temps again.
I’m on the same hardware as before, but temp hasn’t been an issue. I’ve since cleaned it out and have a cooling pad under the laptop. This issue only recently started happening, I was able to play just fine before. I’ve noticed it happening for a few days now, so it’s not an issue that just popped up today. I will contact my ISP and ask them if they see anything since I have had issues with them in the past and the line out here, but I was sure that was resolved.
Happy to hear about your temps and cooling pad situation With the ISP stuff could be that whatever caused the issue on the line before, like environmental stuff, could be happening again. One time, some plants were resting on the my lines and making them wet all the time, which degraded the signal. So even if they don’t see anything on their end immediately (they usually run a quick caption and not a long test like the Winmtr), it might be worth forwarding these results to them, and possibly scheduling an appointment.
Ok, so my ISP didn’t see anything on their end, so before I decide to have them send a tech out, I did a little bit of digging on my own. I had noticed in the task manager that there were some processes that were spiking from time to time and that I didn’t recognize. I traced them back to anti-spyware software installed on my system. I went in, uninstalled the software and rebooted my laptop. Once that was done, I ran another WinMTR on the same server and these are my new results…
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
Host - % |
Sent |
Recv |
Best |
Avrg |
Wrst |
Last |
mynetwork - 0 |
1821 |
1821 |
0 |
1 |
9 |
1 |
10.11.4.33 - 0 |
1821 |
1821 |
14 |
18 |
51 |
15 |
10.178.206.30 - 0 |
1821 |
1821 |
14 |
15 |
49 |
15 |
10.178.206.31 - 0 |
1821 |
1821 |
15 |
16 |
43 |
15 |
tcore4x-london14_0/4/0/2.net.bell.ca - 1 |
1817 |
1816 |
28 |
30 |
50 |
29 |
tcore4-toronto47_hundredgige2-8-0-1.net.bell.ca - 0 |
1821 |
1821 |
29 |
33 |
59 |
30 |
tcore4-chicagocp_hundredgige0-3-0-0.net.bell.ca - 0 |
1821 |
1821 |
28 |
33 |
57 |
32 |
bx6-chicagodt_0-7-0-0.net.bell.ca - 0 |
1821 |
1821 |
28 |
30 |
57 |
30 |
blizzard_bx6-chicagodt.net.bell.ca - 0 |
1821 |
1821 |
30 |
31 |
66 |
31 |
ae1-br02-eqch2.as57976 net - 0 |
1821 |
1821 |
30 |
40 |
206 |
33 |
No response from host - 100 |
364 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
364 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
364 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
364 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
364 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
364 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
364 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
364 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
364 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
364 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
364 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
364 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
364 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
364 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
364 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
364 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
364 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
364 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
364 |
0 |
0 |
0 |
0 |
0 |
No response from host - 100 |
364 |
0 |
0 |
0 |
0 |
0 |
________________________________________________ |
______ |
______ |
______ |
______ |
______ |
______ |
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
The numbers don’t seem that bad now, so maybe it was just one of those programs constantly interrupting my signal and packets from getting through. Either way, tell me if these results look better.
Yeah, they do look better now.