Packet loss / connectivity issues

Meteora-21621 · January 12, 2022, 10:06am

Hi, got a brand new gaming laptop last week and with it I have severe packet losses and connectivity issues. No matter what time of day or how much other bandwith is used at home…
Never had any issues with this with my old laptop(s)!

This came from looking glass:

TRACEROUTE:
traceroute to 141.135.188.119 (141.135.188.119), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.300 ms 0.308 ms 0.308 ms
2 37.244.25.2 (37.244.25.2) 1.136 ms 1.164 ms 1.164 ms
3 Blizzard Blizzard 0.973 ms 0.984 ms 0.985 ms
4 137.221.66.38 (137.221.66.38) 1.128 ms 1.130 ms 1.129 ms
5 * * *
6 137.221.65.19 (137.221.65.19) 7.537 ms 7.587 ms 7.564 ms
7 137.221.79.34 (137.221.79.34) 8.533 ms 8.542 ms 8.537 ms
8 uk-lon03a-ri2-ae-4-0.aorta. net (213.46.175.137) 8.153 ms 8.312 ms 8.253 ms
9 * * *
10 uk-lon01c-ri2-ae-4-0.aorta. net (84.116.135.50) 8.454 ms 8.450 ms 8.422 ms
11 213.46.174.102 (213.46.174.102) 12.719 ms 12.744 ms 12.747 ms
12 * * *
13 dD5E0C8E4.access.telenet.be (213.224.200.228) 17.215 ms 16.884 ms 16.875 ms
14 d8D87BC77.access.telenet.be (141.135.188.119) 26.721 ms 28.790 ms 28.761 ms

12/01/2022 09:59:02 UTC

PING:
PING 141.135.188.119 (141.135.188.119) 56(84) bytes of data.
64 bytes from 141.135.188.119: icmp_seq=1 ttl=52 time=19.3 ms
64 bytes from 141.135.188.119: icmp_seq=2 ttl=52 time=18.2 ms
64 bytes from 141.135.188.119: icmp_seq=3 ttl=52 time=19.2 ms
64 bytes from 141.135.188.119: icmp_seq=4 ttl=52 time=20.2 ms

— 141.135.188.119 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 18.212/19.256/20.221/0.719 ms

12/01/2022 09:59:02 UTC

PING:
PING 141.135.188.119 (141.135.188.119) 56(84) bytes of data.
64 bytes from 141.135.188.119: icmp_seq=1 ttl=52 time=26.7 ms
64 bytes from 141.135.188.119: icmp_seq=2 ttl=52 time=23.7 ms
64 bytes from 141.135.188.119: icmp_seq=3 ttl=52 time=24.5 ms
64 bytes from 141.135.188.119: icmp_seq=4 ttl=52 time=24.6 ms

— 141.135.188.119 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 23.778/24.921/26.730/1.113 ms

12/01/2022 09:59:02 UTC

TRACEROUTE:
traceroute to 141.135.188.119 (141.135.188.119), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.286 ms 0.293 ms 0.292 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 d8d87bc77.access.telenet.be (141.135.188.119) 17.266 ms 24.642 ms 24.677 ms

12/01/2022 09:59:02 UTC

MTR:
Start: Wed Jan 12 09:59:02 2022 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0

12/01/2022 09:59:02 UTC

MTR:
Start: Wed Jan 12 09:59:02 2022 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 37.244.25.2 0.0% 10 0.6 0.8 0.6 1.7 0.0
3.|-- Blizzard 0.0% 10 0.9 0.9 0.7 1.1 0.0
4.|-- 137.221.66.38 0.0% 10 0.6 0.6 0.5 0.8 0.0
5.|-- 137.221.77.52 0.0% 10 3767. 5699. 3767. 7402. 1127.8
6.|-- 137.221.65.19 0.0% 10 7.4 25.8 7.4 189.5 57.5
7.|-- 137.221.79.34 0.0% 10 7.7 10.8 7.5 39.3 10.0
8.|-- uk-lon03a-ri2-ae-4-0.aorta. net 0.0% 10 8.0 8.1 7.9 8.5 0.0
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- uk-lon01c-ri2-ae-4-0.aorta. net 0.0% 10 8.2 10.1 8.2 18.2 3.8
11.|-- 213.46.174.102 0.0% 10 12.7 12.8 12.6 13.1 0.0
12.|-- dD5E0FA78.access.telenet.be 70.0% 10 15.0 15.5 15.0 16.4 0.0
13.|-- dD5E0C8E4.access.telenet.be 0.0% 10 17.2 17.1 16.7 17.7 0.0
14.|-- d8d87bc77.access.telenet.be 0.0% 10 25.2 28.4 24.1 35.4 3.7

12/01/2022 09:59:02 UTC

I have no idea how to interpret this, someone please help?

Mosinathus · January 13, 2022, 6:57pm

Sorry to hear you’ve been having connection issues. The tests you’ve provided do show a clean connection from ourselves towards your machine. However, the looking glass reports only shows it in this direction.

Based on what you described, it seems likely that this would be an issue with your wireless card. Swapping to a cabled connection could help confirm this. Along with this, try turning off your router/modem combination and restarting.

If you still see the same issues, a winmtr report could show where the issue lies. If you have any difficulties reading it, please include the results in a reply to this. ^^

Meteora-21621 · January 15, 2022, 12:21pm

Hi @Mosinathus!
Thank you for your reply. Unfortunately Wi-fi is all I’ve got to play on.
As stated, never had any issues with that untill this new laptop.
I’ve added a report from winmtr from a games that had a lot of issues:

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.0.1 - 15 | 259 | 222 | 3 | 40 | 570 | 15 |

| d8D87B001.access.telenet.be - 18 | 239 | 196 | 8 | 25 | 262 | 17 |

| dD5E0C8E1.access.telenet.be - 0 | 405 | 405 | 8 | 34 | 348 | 19 |

| dD5E0FA79.access.telenet.be - 0 | 405 | 405 | 10 | 34 | 559 | 18 |

| dD5E07D0F.access.telenet.be - 0 | 405 | 405 | 11 | 42 | 533 | 22 |

| ae-1-3104.edge7.Amsterdam1.Level3. net - 1 | 401 | 400 | 0 | 42 | 343 | 24 |

| BLIZZARD-EN.edge7.Amsterdam1.Level3. net - 1 | 401 | 400 | 0 | 50 | 529 | 32 |

| ae1-br02-eqam1.as57976. net - 6 | 315 | 298 | 0 | 312 | 4620 | 229 |

| 137.221.65.77 - 14 | 260 | 225 | 0 | 207 | 4310 | 3521 |

| 137.221.78.55 - 1 | 401 | 400 | 0 | 43 | 343 | 25 |

| No response from host - 100 | 82 | 0 | 0 | 0 | 0 | 0 |

|____________|||||||

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

I look forward to hearing from you. Thanks!