05-10-2023 10:02 - edited 05-10-2023 10:33
My connection has been absolutely shocking for latency and lag spikes recently. For over a month.
I have tried unplugging everything off the network and leaving it for a few hours and everything.
I include the BQM for my router for the last 24 hours. The packet loss was where I rebooted the router after unplugging all devices. I left everything unplugged for an hour after the reboot then plugged everything back in again.
As it stands I can barely get through a voice call without getting 3 or 4 seconds of dropped connection every minute or two.
on 05-10-2023 15:35
See this...
Post up your Hub/network connection details and someone will check to see if there is a problem there. In your browser’s URL box type in http://192.168.0.1 (or http://192.168.100.1 - if in modem mode) (DONT click these links) - and hit return. No need to log in - just click on the “Router Status” icon/text at bottom-middle (Hub3/4/5) or top/right (SH’s) - of the Login page.
Then… Navigate to these “data pages” and just copy/paste the normal “Formatted Text” (not images) 3 FULL sets of data onto here – 2 tables from the Downstream, 2 from the Upstream, & the Network Logs pages. Don't worry too much about the formatting it can be easily read & DON’T include personal data or MAC addresses - blank them out - if you copy/paste the data, the board software will do this for you (you may need to click the "submit" button again). If character limits are “exceeded” - just do two posts
on 06-10-2023 10:04
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 203000000 | 1.4 | 40 | 256 qam | 9 |
2 | 139000000 | 1.2 | 38 | 256 qam | 1 |
3 | 147000000 | 1.4 | 38 | 256 qam | 2 |
4 | 155000000 | 1.2 | 40 | 256 qam | 3 |
5 | 163000000 | 1.2 | 40 | 256 qam | 4 |
6 | 171000000 | 1.5 | 40 | 256 qam | 5 |
7 | 179000000 | 1.7 | 40 | 256 qam | 6 |
8 | 187000000 | 1.7 | 40 | 256 qam | 7 |
9 | 195000000 | 1.5 | 40 | 256 qam | 8 |
10 | 211000000 | 1.4 | 38 | 256 qam | 10 |
11 | 219000000 | 1.4 | 40 | 256 qam | 11 |
12 | 227000000 | 1.5 | 40 | 256 qam | 12 |
13 | 235000000 | 1.5 | 40 | 256 qam | 13 |
14 | 243000000 | 1.4 | 38 | 256 qam | 14 |
15 | 251000000 | 1.4 | 40 | 256 qam | 15 |
16 | 259000000 | 1.7 | 40 | 256 qam | 16 |
17 | 267000000 | 1.7 | 40 | 256 qam | 17 |
18 | 275000000 | 1.9 | 40 | 256 qam | 18 |
19 | 283000000 | 2 | 40 | 256 qam | 19 |
20 | 291000000 | 1.9 | 40 | 256 qam | 20 |
21 | 299000000 | 2 | 40 | 256 qam | 21 |
22 | 307000000 | 1.5 | 40 | 256 qam | 22 |
23 | 315000000 | 1.9 | 38 | 256 qam | 23 |
24 | 323000000 | 1.9 | 38 | 256 qam | 24 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 40.3 | 100 | 0 |
2 | Locked | 38.9 | 82 | 0 |
3 | Locked | 38.9 | 102 | 0 |
4 | Locked | 40.3 | 36 | 0 |
5 | Locked | 40.3 | 104 | 0 |
6 | Locked | 40.3 | 197 | 0 |
7 | Locked | 40.9 | 101 | 0 |
8 | Locked | 40.3 | 38 | 0 |
9 | Locked | 40.3 | 51 | 0 |
10 | Locked | 38.9 | 47 | 0 |
11 | Locked | 40.3 | 16 | 0 |
12 | Locked | 40.3 | 34 | 0 |
13 | Locked | 40.3 | 27 | 0 |
14 | Locked | 38.9 | 36 | 0 |
15 | Locked | 40.3 | 48 | 0 |
16 | Locked | 40.9 | 32 | 0 |
17 | Locked | 40.3 | 32 | 0 |
18 | Locked | 40.3 | 25 | 0 |
19 | Locked | 40.3 | 193 | 0 |
20 | Locked | 40.3 | 234 | 0 |
21 | Locked | 40.3 | 197 | 0 |
22 | Locked | 40.3 | 217 | 0 |
23 | Locked | 38.9 | 203 | 0 |
24 | Locked | 38.9 | 145 | 0 |
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 43100000 | 50 | 5120 | 64 qam | 6 |
2 | 30100030 | 51 | 5120 | 64 qam | 8 |
3 | 36600000 | 50.3 | 5120 | 64 qam | 7 |
4 | 49600000 | 50 | 5120 | 64 qam | 5 |
5 | 23600000 | 51 | 5120 | 64 qam | 11 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 2 | 0 |
2 | ATDMA | 0 | 0 | 1 | 0 |
3 | ATDMA | 0 | 0 | 3 | 0 |
4 | ATDMA | 0 | 0 | 1 | 0 |
5 | ATDMA | 0 | 0 | 0 | 0 |
on 06-10-2023 10:04
Time Priority Description
06/10/2023 10:00:58 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/10/2023 23:03:39 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/10/2023 22:32:11 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/10/2023 07:03:53 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/09/2023 20:13:59 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/09/2023 23:47:25 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/09/2023 17:54:41 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
27/09/2023 14:03:35 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/09/2023 21:39:41 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/09/2023 21:39:39 | Error | DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/09/2023 08:25:12 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/09/2023 17:49:3 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/09/2023 02:09:41 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/09/2023 17:52:41 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/09/2023 14:29:22 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/09/2023 14:09:41 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/09/2023 10:18:53 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/09/2023 02:09:41 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/09/2023 08:43:7 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/09/2023 17:01:9 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 06-10-2023 10:42
Is the voice call problem with an analogue telephone plugged into the VM Hub socket TEL 1 ?
Or is this a VOIP / SIP Phone call or a perhaps Zoom / Skype etc type of voice call ?
on 06-10-2023 11:51
on 08-10-2023 12:17
Hi @kayrah87,
Thank you for your posts and welcome back to our community forums. We're here to help.
I'm so sorry to hear that you're having some trouble with your connection recently. I've just checked over things on our systems and I'm unable to detect any faults currently. Is this problem ongoing for you today? If it is, are you able to share a live BQM with us so we can see your connection quality in real-time?
Thanks,
on 08-10-2023 15:32
Hi Zach, this is a continuous thing. I am struggling to participate in the daily standup at work because I miss every other sentence that someone is saying.
My live BQM is here:
https://www.thinkbroadband.com/broadband/monitoring/quality/share/9748ca5a917ed8cbb7619f57f2102b1300...
on 08-10-2023 17:22
test with hub in modem mode
on 10-10-2023 20:34
Thank you for that information. As legacy1 has recommend we would advise to test this in modem mode to see if any difference is made.
^Martin