on 27-05-2022 10:54
Hey all,
Nearly a week ago now (22nd it started), I've been getting some weird inconsistent packet loss. I tried all the usual fixes such as restarting the router (multiple times), running the usual tests from the router and none have seemed to fix the issue. Decided to start tracking it so you can see what I mean:
This is from when it first started, Midnight 22nd. Mostly consistent 10% packet loss but then the issue seemed to randomly go away, besides some very low background packet loss which I guess could be seen as normal. Compared to yesterday as of this post however:
Seems to have randomly come back, albeit much stronger now around 20% consistently. Then just randomly stops at midnight, no idea why. Did not do anything that should affect the router. Then it came back even heavier this morning. The singular big spike was just me attempting to restart the internet, albeit to no avail.
Im currently WFH and its also making online gaming a near impossible task, I have no idea what I can do now. The router has been playing up a bit recently, but doesn't seem to be any reported area problem? Not too happy with this so hopefully I can get a swift solution.
Many thanks
on 27-05-2022 15:00
on 27-05-2022 16:11
Thanks for the reply,
Waited a bit to see if this change has made a difference and so far sadly it has not.
In the meantime, tried to see if its an area issue but nothing seems to be reported..
on 27-05-2022 16:50
on 27-05-2022 17:19
Hi @Weeblefaice
Your BQM pictures were rejected by the system as they contain your ip address.
Can you either redact the ip address and repost them, or do the following instead whic will post a live BQM please?
On Think Broadband go to your BQM and under the options you will see
Today | Previous Days | Edit | Delete | Share
Click on the Share option and on the screen that opens click on Share
On the next screen click on Share Live Graph
Copy the text in the Direct Link box (beware there may be more text than you can see so make sure yuo highlight it all)
On here when creating your post click the Link icon (2 links chain to the left of the camera icon)
In the URL box paste the link you copied and then click OK.
It would be useful if you could also post your hub stats.
In your browser’s URL box type in http://192.168.0.1 (or http://192.168.100.1 - if in modem mode) and hit return.
Don't login, instead below there click on Check Router Status
From the Router Status page copy/paste 3 FULL sets of data as text (not pictures) onto here – from the Downstream, Upstream, & Network Logs pages.
When you come to posting the info from the Network Logs tab you will get an error message, ignore the error and press post again and it will go through.
on 27-05-2022 18:09
Hey there,
Did not realize the images didn't show - apologies. Attached are the following images:
This is todays
https://www.thinkbroadband.com/broadband/monitoring/quality/share/9d95bb576a3cf7e330e497785eb19529a3...
and this was Yesterday's when it started up again:
https://www.thinkbroadband.com/broadband/monitoring/quality/share/9d95bb576a3cf7e330e497785eb19529a3...
on 27-05-2022 18:13
And the router data as asked
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 418750000 | -5 | 38 | 256 qam | 36 |
2 | 234750000 | 0.7 | 38 | 256 qam | 13 |
3 | 242750000 | 0.5 | 38 | 256 qam | 14 |
4 | 250750000 | 0.5 | 40 | 256 qam | 15 |
5 | 258750000 | 0.4 | 38 | 256 qam | 16 |
6 | 266750000 | 0 | 40 | 256 qam | 17 |
7 | 274750000 | -0.4 | 38 | 256 qam | 18 |
8 | 282750000 | -0.4 | 38 | 256 qam | 19 |
9 | 290750000 | -0.5 | 38 | 256 qam | 20 |
10 | 298750000 | -0.7 | 38 | 256 qam | 21 |
11 | 306750000 | -1.5 | 38 | 256 qam | 22 |
12 | 314750000 | -2 | 38 | 256 qam | 23 |
13 | 322750000 | -1.9 | 38 | 256 qam | 24 |
14 | 330750000 | -2.2 | 38 | 256 qam | 25 |
15 | 338750000 | -2.7 | 38 | 256 qam | 26 |
16 | 346750000 | -2.7 | 38 | 256 qam | 27 |
17 | 354750000 | -3 | 38 | 256 qam | 28 |
18 | 362750000 | -3.4 | 38 | 256 qam | 29 |
19 | 370750000 | -3.5 | 38 | 256 qam | 30 |
20 | 378750000 | -3.7 | 38 | 256 qam | 31 |
21 | 386750000 | -4 | 38 | 256 qam | 32 |
22 | 394750000 | -4.4 | 38 | 256 qam | 33 |
23 | 402750000 | -4.7 | 38 | 256 qam | 34 |
24 | 410750000 | -4.7 | 38 | 256 qam | 35 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.6 | 7 | 0 |
2 | Locked | 38.9 | 6 | 0 |
3 | Locked | 38.9 | 6 | 0 |
4 | Locked | 40.3 | 7 | 0 |
5 | Locked | 38.9 | 7 | 0 |
6 | Locked | 40.3 | 9 | 0 |
7 | Locked | 38.9 | 5 | 0 |
8 | Locked | 38.9 | 12 | 0 |
9 | Locked | 38.6 | 6 | 0 |
10 | Locked | 38.9 | 8 | 0 |
11 | Locked | 38.9 | 11 | 0 |
12 | Locked | 38.9 | 10 | 0 |
13 | Locked | 38.9 | 5 | 0 |
14 | Locked | 38.9 | 6 | 0 |
15 | Locked | 38.9 | 13 | 0 |
16 | Locked | 38.9 | 12 | 0 |
17 | Locked | 38.9 | 11 | 0 |
18 | Locked | 38.9 | 6 | 0 |
19 | Locked | 38.9 | 14 | 0 |
20 | Locked | 38.9 | 2 | 0 |
21 | Locked | 38.6 | 6 | 0 |
22 | Locked | 38.9 | 14 | 0 |
23 | Locked | 38.6 | 20 | 0 |
24 | Locked | 38.6 | 13 | 0 |
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 32600000 | 31.8 | 5120 | 64 qam | 13 |
2 | 39400000 | 32.8 | 5120 | 64 qam | 12 |
3 | 46200000 | 34.3 | 5120 | 64 qam | 11 |
4 | 53700000 | 34.3 | 5120 | 64 qam | 10 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
Time Priority Description
27/05/2022 09:32:13 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/05/2022 23:12:8 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/05/2022 21:03:23 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/05/2022 05:32:6 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/05/2022 03:40:29 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/05/2022 03:40:29 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/05/2022 22:50:0 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/05/2022 22:46:30 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/05/2022 09:16:30 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/05/2022 08:06:56 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/05/2022 08:06:56 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/05/2022 04:51:47 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/05/2022 20:06:56 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/05/2022 20:06:56 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/05/2022 14:19:41 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/05/2022 08:06:56 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/05/2022 08:06:56 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/05/2022 20:55:1 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/05/2022 00:22:51 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/05/2022 07:12:56 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 27-05-2022 18:18
on 27-05-2022 20:37
Test you linked didn't seem to run for me, so tried a similar one:
on 27-05-2022 21:53
Got it to run eventually