on 09-06-2024 16:26
A few days ago I started to have high packet loss, I have always noticed packet loss with Virgin Media, but lately it has become too high.
I'm using the Hub 5 in modem mode to which I connected a NanoPi R6S (8core@2.4GHz - 8GB RAM) to the 2.5Gbps port, configured to use SQM/fq_codel and DSCP packet (inbound and outbound), tested with Wireshark to double check and it works.
Obviously I have already tried restarting the modem and rouer.
The game packets are of UDP type, I'm playing Valorant which reports a high number of lost packets (2/3 packets every second), and I have the same problem with my multistream on Twitch and YouTube where I lose 40% of frames, packet loss is present even when I'm not streaming.
My upload speed test is lower than usual (90Mbps)
3.0 Downstream channels
1 | 331000000 | 6.5 | 41 | QAM 256 | 25 |
2 | 139000000 | 6.5 | 41 | QAM 256 | 1 |
3 | 147000000 | 6.3 | 41 | QAM 256 | 2 |
4 | 155000000 | 6.3 | 41 | QAM 256 | 3 |
5 | 163000000 | 6.3 | 41 | QAM 256 | 4 |
6 | 171000000 | 6.1 | 41 | QAM 256 | 5 |
7 | 179000000 | 6.3 | 41 | QAM 256 | 6 |
8 | 187000000 | 6.3 | 42 | QAM 256 | 7 |
9 | 195000000 | 6.5 | 41 | QAM 256 | 8 |
10 | 203000000 | 5.7 | 41 | QAM 256 | 9 |
11 | 211000000 | 3.7 | 40 | QAM 256 | 10 |
12 | 219000000 | 6 | 41 | QAM 256 | 11 |
13 | 227000000 | 6.2 | 41 | QAM 256 | 12 |
14 | 235000000 | 6.3 | 41 | QAM 256 | 13 |
15 | 243000000 | 6 | 41 | QAM 256 | 14 |
16 | 251000000 | 6.1 | 41 | QAM 256 | 15 |
17 | 259000000 | 6.1 | 41 | QAM 256 | 16 |
18 | 267000000 | 6.2 | 41 | QAM 256 | 17 |
19 | 275000000 | 6.3 | 41 | QAM 256 | 18 |
20 | 283000000 | 6.2 | 41 | QAM 256 | 19 |
21 | 291000000 | 6.5 | 41 | QAM 256 | 20 |
22 | 299000000 | 6.5 | 41 | QAM 256 | 21 |
23 | 307000000 | 6.7 | 41 | QAM 256 | 22 |
24 | 315000000 | 6.8 | 42 | QAM 256 | 23 |
25 | 323000000 | 6.6 | 41 | QAM 256 | 24 |
26 | 339000000 | 6.3 | 41 | QAM 256 | 26 |
27 | 347000000 | 6.4 | 41 | QAM 256 | 27 |
28 | 355000000 | 6.2 | 41 | QAM 256 | 28 |
29 | 363000000 | 6.5 | 41 | QAM 256 | 29 |
30 | 371000000 | 6.7 | 41 | QAM 256 | 30 |
31 | 379000000 | 6.7 | 41 | QAM 256 | 31 |
32 | 387000000 | 6.8 | 42 | QAM 256 | 32 |
3.0 Downstream channels
1 | Locked | 41 | 0 | 0 |
2 | Locked | 41 | 0 | 0 |
3 | Locked | 41 | 0 | 0 |
4 | Locked | 41 | 0 | 0 |
5 | Locked | 41 | 0 | 0 |
6 | Locked | 41 | 0 | 0 |
7 | Locked | 41 | 0 | 0 |
8 | Locked | 42 | 0 | 0 |
9 | Locked | 41 | 0 | 0 |
10 | Locked | 41 | 0 | 0 |
11 | Locked | 40 | 0 | 0 |
12 | Locked | 41 | 0 | 0 |
13 | Locked | 41 | 0 | 0 |
14 | Locked | 41 | 0 | 0 |
15 | Locked | 41 | 0 | 0 |
16 | Locked | 41 | 0 | 0 |
17 | Locked | 41 | 0 | 0 |
18 | Locked | 41 | 0 | 0 |
19 | Locked | 41 | 0 | 0 |
20 | Locked | 41 | 0 | 0 |
21 | Locked | 41 | 0 | 0 |
22 | Locked | 41 | 0 | 0 |
23 | Locked | 41 | 0 | 0 |
24 | Locked | 42 | 0 | 0 |
25 | Locked | 41 | 0 | 0 |
26 | Locked | 41 | 0 | 0 |
27 | Locked | 41 | 0 | 0 |
28 | Locked | 41 | 0 | 0 |
29 | Locked | 41 | 0 | 0 |
30 | Locked | 41 | 0 | 0 |
31 | Locked | 41 | 0 | 0 |
32 | Locked | 42 | 0 | 0 |
3.1 Downstream channels
159 | 94 | 4K | 1840 | QAM 4096 | 1108 |
3.1 Downstream channels
159 | Locked | 42 | 7.5 | 12693655 | 0 |
3.0 Upstream channels
0 | 49600000 | 37.3 | 5120 | QAM 64 | 9 |
1 | 43100000 | 37.3 | 5120 | QAM 64 | 10 |
2 | 36600000 | 36.8 | 5120 | QAM 64 | 11 |
3 | 30100000 | 36.3 | 5120 | QAM 64 | 12 |
4 | 23600000 | 37 | 5120 | QAM 64 | 13 |
3.0 Upstream channels
0 | ATDMA | 0 | 3 | 1 | 0 |
1 | ATDMA | 0 | 3 | 0 | 0 |
2 | ATDMA | 0 | 3 | 1 | 0 |
3 | ATDMA | 0 | 3 | 0 | 0 |
4 | ATDMA | 0 | 3 | 18 | 0 |
3.1 Upstream channels
14 | 10 | 31.0 | 2K | QAM 256 |
3.1 Upstream channels
14 | OFDMA | 200 | 74000000 | 0 | 0 |
Answered! Go to Answer
on 15-06-2024 14:29
Hi @parmi
Welcome back to the community forums
Sorry to hear you're having issues with your service at this time.
Checking the systems at our side, we can see that there is an outage raised for SNR (signal noise ratio) meaning there are disruptions and interferences which are affecting your services intermittently. Our apologies for the inconvenience this may cause. There is an estimated fix time of 17 June 2024 at 9:05am, these are estimated and can be resolved before or extended further if the issues needs time than previously estimated. Our teams are working to have this resolved as soon as possible for you.
on 09-06-2024 16:26
Network Log
09-06-2024 16:02:31 | notice | GUI Login Status - Login Success from LAN interface |
09-06-2024 15:45:56 | notice | GUI Login Status - Login Success from LAN interface |
09-06-2024 15:43:42 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=--:--:--:--:--:--;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
09-06-2024 15:36:04 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=--:--:--:--:--:--;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
09-06-2024 15:36:04 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 12 13; New Profile: 13.;CM-MAC=--:--:--:--:--:--;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
09-06-2024 15:35:40 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=--:--:--:--:--:--;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
09-06-2024 15:35:40 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=--:--:--:--:--:--;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
09-06-2024 15:34:56 | warning | TCS Partial Service;CM-MAC=--:--:--:--:--:--;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
09-06-2024 15:34:56 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=--:--:--:--:--:--;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
09-06-2024 15:34:39 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=--:--:--:--:--:--;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
09-06-2024 15:34:37 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=--:--:--:--:--:--;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
09-06-2024 15:34:37 | notice | US profile assignment change. US Chan ID: 14; Previous Profile: 13; New Profile: 11 13.;CM-MAC=--:--:--:--:--:74;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
09-06-2024 15:34:34 | warning | TCS Partial Service;CM-MAC=--:--:--:--:--:74;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
09-06-2024 15:34:34 | critical | No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=--:--:--:--:--:--;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
09-06-2024 15:34:34 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
09-06-2024 15:34:24 | warning | REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=--:--:--:--:--:--;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
09-06-2024 15:34:19 | notice | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=--:--:--:--:--:--;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
09-06-2024 15:34:15 | notice | TLV-11 - unrecognized OID;CM-MAC=--:--:--:--:--:--;CMTS-MAC=--:--:--:--:--:-;CM-QOS=1.1;CM-VER=3.1; |
09-06-2024 15:34:13 | warning | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=--:--:--:--:--:-;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
09-06-2024 15:34:11 | notice | Honoring MDD; IP provisioning mode = IPv4 |
09-06-2024 15:34:08 | critical | No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=--:--:--:--:--:--;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
09-06-2024 15:33:43 | critical | No Ranging Response received - T3 time-out;CM-MAC=--:--:--:--:--:--;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
09-06-2024 15:33:39 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=--:--:--:--:--:--;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
09-06-2024 15:33:38 | critical | Cable Modem Reboot because of - HW or Power-On Reset |
08-06-2024 23:09:33 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=--:--:--:--:--:--;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
08-06-2024 12:20:13 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=--:--:--:--:--:--;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
07-06-2024 08:05:58 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=--:--:--:--:--:--;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
06-06-2024 20:49:23 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=--:--:--:--:--:--;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
06-06-2024 04:52:15 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=--:--:--:--:--:--;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
01-06-2024 07:24:15 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=--:--:--:--:--:--;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
31-05-2024 23:44:24 | critical | No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=--:--:--:--:--:--;CMTS-MAC=--:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
31-05-2024 23:43:49 | critical | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=--:--:--:--:--:--;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
31-05-2024 23:43:48 | critical | Cable Modem Reboot because of - HW or Power-On Reset |
20-05-2024 19:46:27 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=--:---:--:--:--:--;CMTS-MAC=00:--:--:--:--:--;CM-QOS=1.1;CM-VER=3.1; |
on 11-06-2024 09:03
Anyone can help me?
on 11-06-2024 09:41
The stats in this thread don't cover packet loss on the video streaming applications in question.
on 11-06-2024 09:54
What do you mean? what stats do you need?
on 11-06-2024 10:14
https://www.thinkbroadband.com/broadband/monitoring/quality
Post a link here to the live display.
on 11-06-2024 11:24
I just created a new account on thinkbroadband, I'm already starting to see that there are packet losses.
on 12-06-2024 09:45
Anyone have any idea what's going on?
on 12-06-2024 11:20
That illustrates your reported problem pretty well. How do those red periods coincide with your heavy use? Are there other times that are OK for you when you are streaming?
on 12-06-2024 11:40
Basically from the tests I have done, I can conclude that during the red periods I notice the following things:
There is no one else in the house using the connection during the red periods.
During the non-red periods, none of the above problems occur.
This problem started happening a few days ago, I've never had any problems like this before.