on 14-11-2023 08:57
Hello,
I've been having issues with low upload speeds for a few months, usually in the evening. I should have 100mbit upload, but it's sometimes around 30mbit.
The main problem is that during this period of slow upload, any attempt to upload something results in massive latency spikes or a complete disconnect. The only fix I've found for this is to limit my upload speed.
We called support and an engineer was sent out, but they just replaced my modem with a Hub 5 in the hopes that would resolve the issues. The issue is intermittent, so there is a chance he would not have seen the problem when troubleshooting. It does seem to be mostly in the evenings, but I've had the issue at all hours.
Here are my modem stats for the past 12 hours:
Here is my BQM:
Last night I was attempting to upload something and I disconnected three times. Restarting the modem did not help. I use a third-party router and had to limit my upload speed to 10mbit before I could upload without disconnecting.
I have tried using the Hub 5 in router mode while on the phone with support, but my upload speed was just as slow with massive latency spikes. I've been having large amounts of errors on my modem for a few years now but this is the first time I've started having connection/bandwidth issues.
Could someone from Virgin Media please look into this?
Thank you
on 15-11-2023 08:59
We had the same issues last night, multiple disconnects while attempting to upload. I had to cap my upload to 5mbit to stop the modem going offline.
No upstream timeouts this time, but tens of thousands of downstream errors.
16-11-2023 17:23 - edited 16-11-2023 18:06
After rebooting the modem, here are the stats for the past 5 hours:
A current speed test:
This was my latency during the speed test:
64 bytes from 1.1.1.1: icmp_seq=1 ttl=57 time=11.0 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=57 time=16.0 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=57 time=33.5 ms
64 bytes from 1.1.1.1: icmp_seq=4 ttl=57 time=26.7 ms
64 bytes from 1.1.1.1: icmp_seq=5 ttl=57 time=9.34 ms
64 bytes from 1.1.1.1: icmp_seq=6 ttl=57 time=28.4 ms
64 bytes from 1.1.1.1: icmp_seq=7 ttl=57 time=12.3 ms
64 bytes from 1.1.1.1: icmp_seq=8 ttl=57 time=8.81 ms
64 bytes from 1.1.1.1: icmp_seq=9 ttl=57 time=9.35 ms
64 bytes from 1.1.1.1: icmp_seq=10 ttl=57 time=33.5 ms
64 bytes from 1.1.1.1: icmp_seq=11 ttl=57 time=35.2 ms
64 bytes from 1.1.1.1: icmp_seq=12 ttl=57 time=11.2 ms
64 bytes from 1.1.1.1: icmp_seq=13 ttl=57 time=13.6 ms
64 bytes from 1.1.1.1: icmp_seq=14 ttl=57 time=9.70 ms
64 bytes from 1.1.1.1: icmp_seq=15 ttl=57 time=12.2 ms
64 bytes from 1.1.1.1: icmp_seq=16 ttl=57 time=18.8 ms
64 bytes from 1.1.1.1: icmp_seq=17 ttl=57 time=31.3 ms
64 bytes from 1.1.1.1: icmp_seq=18 ttl=57 time=11.6 ms
64 bytes from 1.1.1.1: icmp_seq=19 ttl=57 time=17.3 ms
64 bytes from 1.1.1.1: icmp_seq=20 ttl=57 time=150 ms
64 bytes from 1.1.1.1: icmp_seq=21 ttl=57 time=149 ms
64 bytes from 1.1.1.1: icmp_seq=22 ttl=57 time=212 ms
64 bytes from 1.1.1.1: icmp_seq=23 ttl=57 time=367 ms
64 bytes from 1.1.1.1: icmp_seq=24 ttl=57 time=281 ms
64 bytes from 1.1.1.1: icmp_seq=25 ttl=57 time=217 ms
64 bytes from 1.1.1.1: icmp_seq=26 ttl=57 time=218 ms
64 bytes from 1.1.1.1: icmp_seq=27 ttl=57 time=279 ms
64 bytes from 1.1.1.1: icmp_seq=28 ttl=57 time=221 ms
64 bytes from 1.1.1.1: icmp_seq=29 ttl=57 time=181 ms
64 bytes from 1.1.1.1: icmp_seq=30 ttl=57 time=560 ms
64 bytes from 1.1.1.1: icmp_seq=31 ttl=57 time=500 ms
64 bytes from 1.1.1.1: icmp_seq=32 ttl=57 time=196 ms
64 bytes from 1.1.1.1: icmp_seq=33 ttl=57 time=449 ms
64 bytes from 1.1.1.1: icmp_seq=34 ttl=57 time=152 ms
64 bytes from 1.1.1.1: icmp_seq=35 ttl=57 time=52.4 ms
64 bytes from 1.1.1.1: icmp_seq=36 ttl=57 time=17.4 ms
64 bytes from 1.1.1.1: icmp_seq=37 ttl=57 time=11.9 ms
64 bytes from 1.1.1.1: icmp_seq=38 ttl=57 time=11.3 ms
64 bytes from 1.1.1.1: icmp_seq=39 ttl=57 time=10.5 ms
64 bytes from 1.1.1.1: icmp_seq=40 ttl=57 time=11.3 ms
I'm having to limit my upload speed to below this to avoid massive latency and disconnects.
Please let me know if you need more information. 🙂
18-11-2023 09:48 - edited 18-11-2023 09:49
I tried uploading a file this morning and had more disconnects.
BQM:
Latency:
64 bytes from 1.1.1.1: icmp_seq=8737 ttl=57 time=9.08 ms
64 bytes from 1.1.1.1: icmp_seq=8738 ttl=57 time=8.69 ms
64 bytes from 1.1.1.1: icmp_seq=8739 ttl=57 time=11.0 ms
64 bytes from 1.1.1.1: icmp_seq=8740 ttl=57 time=10.2 ms
64 bytes from 1.1.1.1: icmp_seq=8741 ttl=57 time=11.5 ms
64 bytes from 1.1.1.1: icmp_seq=8742 ttl=57 time=10.7 ms
64 bytes from 1.1.1.1: icmp_seq=8743 ttl=57 time=14.1 ms
64 bytes from 1.1.1.1: icmp_seq=8744 ttl=57 time=16.0 ms
64 bytes from 1.1.1.1: icmp_seq=8745 ttl=57 time=16.1 ms
64 bytes from 1.1.1.1: icmp_seq=8746 ttl=57 time=20.2 ms
64 bytes from 1.1.1.1: icmp_seq=8747 ttl=57 time=22.9 ms
64 bytes from 1.1.1.1: icmp_seq=8748 ttl=57 time=15.8 ms
64 bytes from 1.1.1.1: icmp_seq=8749 ttl=57 time=24.7 ms
64 bytes from 1.1.1.1: icmp_seq=8750 ttl=57 time=26.8 ms
64 bytes from 1.1.1.1: icmp_seq=8751 ttl=57 time=30.2 ms
64 bytes from 1.1.1.1: icmp_seq=8752 ttl=57 time=38.3 ms
64 bytes from 1.1.1.1: icmp_seq=8753 ttl=57 time=38.4 ms
64 bytes from 1.1.1.1: icmp_seq=8754 ttl=57 time=52.2 ms
64 bytes from 1.1.1.1: icmp_seq=8755 ttl=57 time=47.2 ms
64 bytes from 1.1.1.1: icmp_seq=8756 ttl=57 time=60.0 ms
64 bytes from 1.1.1.1: icmp_seq=8757 ttl=57 time=52.7 ms
64 bytes from 1.1.1.1: icmp_seq=8758 ttl=57 time=50.4 ms
64 bytes from 1.1.1.1: icmp_seq=8759 ttl=57 time=56.6 ms
64 bytes from 1.1.1.1: icmp_seq=8760 ttl=57 time=55.3 ms
64 bytes from 1.1.1.1: icmp_seq=8761 ttl=57 time=59.8 ms
64 bytes from 1.1.1.1: icmp_seq=8762 ttl=57 time=31.6 ms
64 bytes from 1.1.1.1: icmp_seq=8763 ttl=57 time=43.4 ms
64 bytes from 1.1.1.1: icmp_seq=8764 ttl=57 time=55.9 ms
64 bytes from 1.1.1.1: icmp_seq=8765 ttl=57 time=54.3 ms
64 bytes from 1.1.1.1: icmp_seq=8766 ttl=57 time=57.3 ms
64 bytes from 1.1.1.1: icmp_seq=8767 ttl=57 time=56.4 ms
64 bytes from 1.1.1.1: icmp_seq=8768 ttl=57 time=36.6 ms
64 bytes from 1.1.1.1: icmp_seq=8769 ttl=57 time=38.8 ms
64 bytes from 1.1.1.1: icmp_seq=8770 ttl=57 time=51.9 ms
64 bytes from 1.1.1.1: icmp_seq=8771 ttl=57 time=50.7 ms
64 bytes from 1.1.1.1: icmp_seq=8772 ttl=57 time=47.6 ms
64 bytes from 1.1.1.1: icmp_seq=8773 ttl=57 time=48.9 ms
64 bytes from 1.1.1.1: icmp_seq=8774 ttl=57 time=64.3 ms
64 bytes from 1.1.1.1: icmp_seq=8775 ttl=57 time=68.1 ms
64 bytes from 1.1.1.1: icmp_seq=8776 ttl=57 time=18.4 ms
64 bytes from 1.1.1.1: icmp_seq=8777 ttl=57 time=23.4 ms
64 bytes from 1.1.1.1: icmp_seq=8778 ttl=57 time=39.8 ms
64 bytes from 1.1.1.1: icmp_seq=8779 ttl=57 time=41.4 ms
64 bytes from 1.1.1.1: icmp_seq=8780 ttl=57 time=38.6 ms
64 bytes from 1.1.1.1: icmp_seq=8781 ttl=57 time=59.2 ms
64 bytes from 1.1.1.1: icmp_seq=8782 ttl=57 time=35.7 ms
64 bytes from 1.1.1.1: icmp_seq=8783 ttl=57 time=40.7 ms
no answer yet for icmp_seq=8784
no answer yet for icmp_seq=8785
no answer yet for icmp_seq=8786
no answer yet for icmp_seq=8787
no answer yet for icmp_seq=8788
no answer yet for icmp_seq=8789
no answer yet for icmp_seq=8790
no answer yet for icmp_seq=8791
no answer yet for icmp_seq=8792
no answer yet for icmp_seq=8793
no answer yet for icmp_seq=8794
no answer yet for icmp_seq=8795
no answer yet for icmp_seq=8796
no answer yet for icmp_seq=8797
no answer yet for icmp_seq=8798
Modem logs:
18-11-2023 09:21:57 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:21:56 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:21:49 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:21:04 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:20:49 warning MDD message timeout;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:20:49 notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:20:38 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:20:14 notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:20:07 warning MDD message timeout;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:20:06 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 2 3 4 5 6 7 9 10 11 13 14 15 16 17 18 19 20 21 22; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:19:45 warning MDD message timeout;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:19:41 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:19:37 warning MDD message timeout;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:19:23 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:19:23 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:19:16 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:19:02 notice CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:18:05 notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 3 4 5 6 7 8 9 11 13 14 15 16 18; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:17:51 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 2 3 4 5 6 7 9 11 13 14 15 16 17 18 19 20 21 22; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:16:47 warning MDD message timeout;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:16:46 notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 3 4 5 6 7 8 9 11 14 15 16 18; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:16:43 notice CM-STATUS message sent. Event Type Code: 2; Chan ID: 3; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:16:43 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 2 3 4 5 6 7 9 11 14 15 16 17 18 19 20 21 22; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:16:35 warning MDD message timeout;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:16:34 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 2 3 4 5 6 7 9 11 14 15 16 17 18 19 20 21 22; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:16:27 warning MDD message timeout;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:16:20 notice CM-STATUS message sent. Event Type Code: 5; Chan ID: 3 4 5 6 7 8 9 14 15 16 18; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:16:09 warning MDD message timeout;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:15:58 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:15:50 notice CM-STATUS message sent. Event Type Code: 4; Chan ID: 2 3 4 5 6 7 11 14 15 16 17 18 19 20 21 22; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:15:31 warning MDD message timeout;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
18-11-2023 09:15:23 notice CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=<REMOVED>;CMTS-MAC=<REMOVED>;CM-QOS=1.1;CM-VER=3.1;
on 20-11-2023 10:10
Hey iqualms,
Welcome back to the community and thanks for taking the time to post.
I’m sorry to hear of the issues that you’re having with your connection at the moment, I have looked into this right now and cannot see any issues at the moment, I will look into this once again later this afternoon to see if I can see any further issues this evening to see if the figures change at all. We may also need to send another technician but in the 4 to 7pm slot to make sure that they are there for the times the issues are occurring. I will be back in touch
Kind Regards,
Steven_L
on 20-11-2023 11:51
Hello, thanks for checking.
Yes it appears to be fine this morning, "hopefully" there is a change later this afternoon that would help with diagnosing the issue.
20-11-2023 12:21 - edited 20-11-2023 12:23
In addition to all the downstream errors, the upstream channels were all running at 32QAM instead of 64QAM. This was/will be the main cause of your upstream speed loss.
on 20-11-2023 12:29
They're currently at 64QAM so that would make sense.
on 20-11-2023 12:43
It would be good to do a reset to zero the Error counters and see if that fault has been cleared too.
on 22-11-2023 11:28
There are a bunch of errors on the first 7 channels but it's been fine the past few days. I haven't been uploading as much as I previously was so that may be the reason. I don't think it's fixed as I've had days where it's been fine before. I'll start uploading again and see if the issue returns.