on 05-01-2023 20:54
Hi!
Can someone help? I have 1Gb connection and generally get good speeds but I do get random packet loss, seems to be always when on a work zoom/webex etc. Have tried a reboot and factory restet but nothing seems to fix it. On my scan using the app I do see incredibly high latency (15k +) and Jitter (1000ms) to the hub, this is not to the device, just to the hub. Speeds seem to be fin Av around 500Mbps. I also notice poor performance on streaming sometimes even with wired connections. Will attach BQM graphs and network status reports below:-
Time Priority Description
Thu 01/01/1970 00:01:25 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:02:32 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xxxxxxxxx;CMTS-MAC=00:01:xxxxxxCM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:02:32 | 3 | No Ranging Response received - T3 time-out;CM-MAC=axxxxxxxx;CMTS-MAC=00:01:xxxxxxx;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:02:54 | 4 | Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=axxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:04:22 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:04:22 | 3 | No Ranging Response received - T3 time-out;CM-MAC=xxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:04:51 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=axxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:04:51 | 3 | No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 28/12/2022 16:20:33 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 29/12/2022 00:06:26 | 3 | No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 31/12/2022 05:43:35 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 31/12/2022 10:28:47 | 3 | No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun 01/01/2023 16:40:55 | 6 | US profile assignment change. US Chan ID: 10; Previous Profile: 12; New Profile: 11.;CM-MAC=xxxxxxxxxxCMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon 02/01/2023 00:22:45 | 3 | No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 03/01/2023 08:07:04 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=xxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 03/01/2023 13:08:45 | 3 | No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 03/01/2023 15:11:57 | 6 | US profile assignment change. US Chan ID: 10; Previous Profile: 11; New Profile: 12.;CM-MAC=xxxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue 03/01/2023 16:13:20 | 3 | No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 04/01/2023 11:08:48 | 6 | US profile assignment change. US Chan ID: 10; Previous Profile: 11; New Profile: 12.;CM-MAC=xxxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:02:43 | 3 | DHCP FAILED - Discover sent, no offer received;CM-MAC=xxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:03:08 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:03:09 | 3 | No Ranging Response received - T3 time-out;CM-MAC=axxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:03:30 | 4 | Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=xxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:05:00 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:05:00 | 3 | No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:05:32 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:05:32 | 3 | No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:06:04 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=xxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:06:04 | 3 | No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 04/01/2023 12:19:13 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xxxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed 04/01/2023 16:05:05 | 3 | No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/01/2023 10:23:19 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=xxxxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/01/2023 10:23:23 | 5 | Lost MDD Timeout;CM-MAC=xxxxxxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/01/2023 10:23:23 | 6 | CM-STATUS message sent. Event Type Code: 21; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/01/2023 10:23:24 | 5 | Lost MDD Timeout;CM-MAC=xxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/01/2023 10:23:47 | 3 | No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/01/2023 10:24:02 | 6 | CM-STATUS message sent. Event Type Code: 23; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxxxxx;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/01/2023 10:24:06 | 3 | No Ranging Response received - T3 time-out;CM-MAC=xxxxxxx;CMTS-MAC=00:01:xxxxx;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/01/2023 10:24:11 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=xxxxxx;CMTS-MAC=00:01:x;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/01/2023 10:24:29 | 6 | US profile assignment change. US Chan ID: 10; Previous Profile: 12; New Profile: 11.;CM-MAC=xxxxxxxx;CMTS-MAC=0xxxx:da;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/01/2023 13:47:05 | 3 | No Ranging Response received - T3 time-out;CM-MAC=axxxxxxxx;CMTS-MAC=xxxxxx;CM-QOS=1.1;CM-VER=3.1; |
on 05-01-2023 20:54
on 05-01-2023 20:56
<a title="Broadband Ping" href="https://www.thinkbroadband.com/broadband/monitoring/quality/share/83f0a72516c4cd810c549b842aa5f9baeffcadc5-03-01-2023"><img alt="My Broadband Ping - Home" src="https://www.thinkbroadband.com/broadband/monitoring/quality/share/83f0a72516c4cd810c549b842aa5f9baeffcadc5-03-01-2023.png" /></a>
on 05-01-2023 20:57
on 05-01-2023 20:58
on 05-01-2023 20:59
https://www.thinkbroadband.com/broadband/monitoring/quality/share/8a6f55a0e51c2ee10464f565186f5bade7b13c9b
on 09-01-2023 13:25
Hi @djgeurn thanks for your post although I'm sorry to hear of your concerns raised.
I've ran some checks here and there doesn't appear to be any issues on the line, have things stabilised for you over the weekend?
When you run speed tests when connected to a device via ethernet, what speeds are you receiving?
Many thanks
on 09-01-2023 14:09
Hi Tom, speed tests are fine, but the experience isn’t great. Buffering, dropped calls on webex etc.
even streaming internally isn’t great. My tv and NAS are both hardwired and get buffering?
also looking at the latency to the router, 15k and 1000 jitter? Is that normal?
Thanks for looking in to this for me
on 09-01-2023 19:26
@tom_W please see the graph from today, few spikes in latency and few bits of packet loss. It's really frustrating because we are getting fantastic speeds, but if we have latency and packet loss the experience is poor. 😞
on 09-01-2023 19:36
The stats you posted on 5/1 show all upstream channels on 16QAM when they should be 64QAM. Can you power cycle the hub and after a few hours post a new full set of stats. If the upstream remains at 16QAM you will certainly need a technician’s visit to fix.