on 11-10-2024 09:40
Hi
Looks like my line latency issues are back with a vengeance. Used to have a similar issue back in 2021 but things improved eventually.
Lately, I've noticed that even my Teams would warn me about poor connection quality. Decided to setup BQM again and... surprise!
Even simple ping to Google shows the issue:
Reply from 142.250.187.196: bytes=32 time=18ms TTL=116
Reply from 142.250.187.196: bytes=32 time=16ms TTL=116
Reply from 142.250.187.196: bytes=32 time=16ms TTL=116
Reply from 142.250.187.196: bytes=32 time=12ms TTL=116
Reply from 142.250.187.196: bytes=32 time=17ms TTL=116
Reply from 142.250.187.196: bytes=32 time=259ms TTL=116
Reply from 142.250.187.196: bytes=32 time=118ms TTL=116
Reply from 142.250.187.196: bytes=32 time=81ms TTL=116
Reply from 142.250.187.196: bytes=32 time=121ms TTL=116
Reply from 142.250.187.196: bytes=32 time=96ms TTL=116
Reply from 142.250.187.196: bytes=32 time=125ms TTL=116
Reply from 142.250.187.196: bytes=32 time=81ms TTL=116
Reply from 142.250.187.196: bytes=32 time=111ms TTL=116
Reply from 142.250.187.196: bytes=32 time=141ms TTL=116
Reply from 142.250.187.196: bytes=32 time=129ms TTL=116
Reply from 142.250.187.196: bytes=32 time=86ms TTL=116
Reply from 142.250.187.196: bytes=32 time=84ms TTL=116
Reply from 142.250.187.196: bytes=32 time=143ms TTL=116
Reply from 142.250.187.196: bytes=32 time=142ms TTL=116
Reply from 142.250.187.196: bytes=32 time=129ms TTL=116
Reply from 142.250.187.196: bytes=32 time=18ms TTL=116
Reply from 142.250.187.196: bytes=32 time=17ms TTL=116
Reply from 142.250.187.196: bytes=32 time=13ms TTL=116
Reply from 142.250.187.196: bytes=32 time=17ms TTL=116
Reply from 142.250.187.196: bytes=32 time=19ms TTL=116
Reply from 142.250.187.196: bytes=32 time=17ms TTL=116
Reply from 142.250.187.196: bytes=32 time=18ms TTL=116
Reply from 142.250.187.196: bytes=32 time=18ms TTL=116
Reply from 142.250.187.196: bytes=32 time=20ms TTL=116
Reply from 142.250.187.196: bytes=32 time=18ms TTL=116
Reply from 142.250.187.196: bytes=32 time=23ms TTL=116
Reply from 142.250.187.196: bytes=32 time=17ms TTL=116
This is as bad as it gets.
Logs:
3.0 Downstream channels
1 | 330000000 | 7.4 | 42 | QAM 256 | 25 |
2 | 138000000 | 9.2 | 42 | QAM 256 | 1 |
3 | 162000000 | 8.6 | 42 | QAM 256 | 4 |
4 | 170000000 | 8.6 | 42 | QAM 256 | 5 |
5 | 194000000 | 9 | 42 | QAM 256 | 8 |
6 | 202000000 | 8.9 | 42 | QAM 256 | 9 |
7 | 226000000 | 8.7 | 42 | QAM 256 | 12 |
8 | 234000000 | 8.5 | 42 | QAM 256 | 13 |
9 | 258000000 | 7.9 | 42 | QAM 256 | 16 |
10 | 266000000 | 7.8 | 42 | QAM 256 | 17 |
11 | 290000000 | 7.7 | 42 | QAM 256 | 20 |
12 | 298000000 | 7.5 | 42 | QAM 256 | 21 |
13 | 322000000 | 7.3 | 42 | QAM 256 | 24 |
14 | 354000000 | 7.7 | 42 | QAM 256 | 28 |
15 | 362000000 | 7.7 | 42 | QAM 256 | 29 |
16 | 386000000 | 7.3 | 42 | QAM 256 | 32 |
17 | 394000000 | 7.2 | 42 | QAM 256 | 33 |
18 | 402000000 | 7.1 | 42 | QAM 256 | 34 |
19 | 410000000 | 7.2 | 42 | QAM 256 | 35 |
20 | 418000000 | 7 | 42 | QAM 256 | 36 |
21 | 426000000 | 6.9 | 42 | QAM 256 | 37 |
22 | 434000000 | 6.4 | 42 | QAM 256 | 38 |
23 | 442000000 | 6 | 42 | QAM 256 | 39 |
24 | 450000000 | 5.9 | 42 | QAM 256 | 40 |
25 | 458000000 | 5.6 | 42 | QAM 256 | 41 |
26 | 466000000 | 5.5 | 42 | QAM 256 | 42 |
27 | 474000000 | 5.5 | 42 | QAM 256 | 43 |
28 | 482000000 | 5.6 | 42 | QAM 256 | 44 |
29 | 490000000 | 5.6 | 42 | QAM 256 | 45 |
30 | 498000000 | 5.4 | 42 | QAM 256 | 46 |
31 | 506000000 | 5.3 | 42 | QAM 256 | 47 |
32 | 514000000 | 5.1 | 42 | QAM 256 | 48 |
3.0 Downstream channels
1 | Locked | 42 | 1 | 0 |
2 | Locked | 42 | 1 | 0 |
3 | Locked | 42 | 2 | 0 |
4 | Locked | 42 | 3 | 0 |
5 | Locked | 42 | 3 | 0 |
6 | Locked | 42 | 0 | 0 |
7 | Locked | 42 | 1 | 0 |
8 | Locked | 42 | 1 | 0 |
9 | Locked | 42 | 1 | 0 |
10 | Locked | 42 | 2 | 0 |
11 | Locked | 42 | 2 | 0 |
12 | Locked | 42 | 3 | 0 |
13 | Locked | 42 | 2 | 0 |
14 | Locked | 42 | 1 | 0 |
15 | Locked | 42 | 0 | 0 |
16 | Locked | 42 | 2 | 0 |
17 | Locked | 42 | 1 | 0 |
18 | Locked | 42 | 1 | 0 |
19 | Locked | 42 | 3 | 0 |
20 | Locked | 42 | 1 | 0 |
21 | Locked | 42 | 1 | 0 |
22 | Locked | 42 | 4 | 0 |
23 | Locked | 42 | 2 | 0 |
24 | Locked | 42 | 2 | 0 |
25 | Locked | 42 | 4 | 0 |
26 | Locked | 42 | 3 | 0 |
27 | Locked | 42 | 4 | 0 |
28 | Locked | 42 | 2 | 0 |
29 | Locked | 42 | 6 | 0 |
30 | Locked | 42 | 3 | 0 |
31 | Locked | 42 | 6 | 0 |
32 | Locked | 42 | 3 | 0 |
3.1 Downstream channels
159 | 94 | 4K | 1840 | QAM 4096 | 1108 |
3.1 Downstream channels
159 | Locked | 42 | 3.4 | 743079917 | 17374 |
3.0 Upstream channels
0 | 49600000 | 47.5 | 5120 | QAM 64 | 9 |
1 | 43100000 | 47 | 5120 | QAM 64 | 10 |
2 | 36600000 | 46.5 | 5120 | QAM 64 | 11 |
3 | 30100000 | 46.3 | 5120 | QAM 64 | 12 |
4 | 23600000 | 46 | 5120 | QAM 64 | 13 |
3.0 Upstream channels
0 | ATDMA | 0 | 0 | 0 | 0 |
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
3.1 Upstream channels
14 | 10 | 41.2 | 2K | QAM 256 |
3.1 Upstream channels
14 | OFDMA | 200 | 74000000 | 0 | 0 |
I renewed my contract just over two weeks ago so the irony of the fact I'm now out of my cooling off period is not lost on me.
Answered! Go to Answer
on 11-10-2024 10:11
More then likely its upstream might be DoS by others in your area or you have something uploading you don't know about.
on 11-10-2024 09:55
This is the concern...
3.1 Downstream channels
159 | Locked | 42 | 3.4 | 743079917 | 17374 |
on 11-10-2024 10:11
More then likely its upstream might be DoS by others in your area or you have something uploading you don't know about.
on 11-10-2024 10:55
on 11-10-2024 12:05
Thank you. Traffic analyser on my router says my connection is practically idle. Just flashed it with the latest firmware though. Let's see if that helps.
11-10-2024 14:39 - edited 11-10-2024 14:40
It likely was something bad got on your router to be used as a DoS and a flash fixed it