Forum Discussion

Rnash2002's avatar
Rnash2002
Tuning in
11 months ago

Frustration is now setting in! low upload in the evenings.

Ok so i hope someone can help on here as Virgin are scratching there heads, after 6 engineers have been out, replaced everything even the line from the box up the street to my house im still getting very low upload speeds on an evening.

Since changing the line from the box up the street its got better but only to not go down to 0 upload and chuck me off my stream.

Its always in the evenings, worst being Fridays and it also seems to be when i get packet loss, this also seems to run till like 1 to 2am, when im not even on the internet.

One evening i pulled everything off my internet, went to bed and still was getting packet loss through to the early hours!

So what can it be? could it be that the line cant handle the 100 upload im paying for at peak times? this issue only seems to have started when i upgraded to the 1gig package with the hub 5.

Please help as i stream, i also get payed to stream and its not getting to the point that i dont want to stream on an evening because of this.

 

10 Replies

  • jpeg1's avatar
    jpeg1
    Alessandro Volta

    Yes the packet loss is clear to see. 

    Can you post all the router stats on here?  Use text copy-paste, not screen shots as they are often difficult to see.

  • 3.0 Downstream channels

    Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
    13310000000.440QAM 25625
    21710000000.140QAM 2565
    31790000000.240QAM 2566
    41870000000.340QAM 2567
    51950000000.540QAM 2568
    62030000000.440QAM 2569
    72110000000.740QAM 25610
    82190000000.741QAM 25611
    92270000000.640QAM 25612
    102350000000.541QAM 25613
    112430000000.541QAM 25614
    122510000000.441QAM 25615
    132590000000.440QAM 25616
    142670000000.440QAM 25617
    152750000000.440QAM 25618
    162830000000.540QAM 25619
    172910000000.740QAM 25620
    182990000000.540QAM 25621
    193070000000.540QAM 25622
    203150000000.640QAM 25623
    213230000000.540QAM 25624
    223390000000.540QAM 25626
    233470000000.640QAM 25627
    243550000000.640QAM 25628
    253630000000.640QAM 25629
    263710000000.640QAM 25630
    273790000000.740QAM 25631
    283870000000.740QAM 25632
    293950000000.840QAM 25633
    304030000000.740QAM 25634
    314110000000.740QAM 25635
    324190000000.740QAM 25636

    3.0 Downstream channels

    Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
    1Locked401667
    2Locked40757227
    3Locked40490310
    4Locked4010
    5Locked4000
    6Locked4000
    7Locked4010
    8Locked4100
    9Locked4000
    10Locked4100
    11Locked4100
    12Locked4100
    13Locked40113129
    14Locked4000
    15Locked4000
    16Locked4000
    17Locked4000
    18Locked4000
    19Locked404866
    20Locked4000
    21Locked4000
    22Locked4000
    23Locked4016778
    24Locked401080
    25Locked40674
    26Locked40874
    27Locked40965
    28Locked401064
    29Locked40711180
    30Locked4010
    31Locked401069194
    32Locked401084218

    3.1 Downstream channels

    Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
    159944K1840QAM 40961108

    3.1 Downstream channels

    Channel ID Locked Status RxMER Data (dB) PLC Power (dBmV) Corrected errors (Active Profile) Uncorrectable errors (Active Profile)
    159Locked412.728307086160

    3.0 Upstream channels

    Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
    060300000355120QAM 641
    153700000355120QAM 642
    24620000035.55120QAM 643
    33940000035.55120QAM 644
    43260000035.55120QAM 645
    523600000365120QAM 646

    3.0 Upstream channels

    Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
    0ATDMA0010
    1ATDMA0060
    2ATDMA0030
    3ATDMA0060
    4ATDMA0020
    5ATDMA001

    0

  • jpeg1's avatar
    jpeg1
    Alessandro Volta

    All the levels are OK, there's nothing there to be corrected. The QAM settings OK as well. Too many T3 errors that are likely a result of the external packet loss and the consequent effect on your streaming.   It looks like there is nothing you can do but complain again. 

  • 10-07-2024 12:40:36noticeGUI Login Status - Login Success from LAN interface
    09-07-2024 23:57:37criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    09-07-2024 20:21:58noticeGUI Login Status - Login Success from LAN interface
    09-07-2024 02:23:44errorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    07-07-2024 17:22:30criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    06-07-2024 19:45:42noticeGUI Login Status - Login Success from LAN interface
    05-07-2024 14:23:42errorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    04-07-2024 10:12:57noticeGUI Login Status - Login Success from LAN interface
    04-07-2024 07:17:47noticeGUI Login Status - Login Success from LAN interface
    03-07-2024 23:27:20noticeGUI Login Status - Login Success from LAN interface
    03-07-2024 23:08:18noticeGUI Login Status - Login Success from LAN interface
    03-07-2024 22:10:11noticeGUI Login Status - Login Success from LAN interface
    03-07-2024 18:14:17criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    02-07-2024 11:04:20noticeGUI Login Status - Login Success from LAN interface
    02-07-2024 02:23:41errorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    30-06-2024 18:40:07criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    30-06-2024 11:41:27warningDBC-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;
    29-06-2024 20:50:20noticeGUI Login Status - Login Success from LAN interface
    29-06-2024 20:49:55noticeGUI Login Status - Login Fail from LAN interface
    29-06-2024 10:10:49noticeGUI Login Status - Login Success from LAN interface
    28-06-2024 19:21:19criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    28-06-2024 16:05:37noticeGUI Login Status - Login Success from LAN interface
    28-06-2024 16:04:39noticeGUI Login Status - Login Success from LAN interface
    28-06-2024 16:02:19noticeREGISTRATION COMPLETE - Waiting for Operational status
    28-06-2024 16:02:14warningDynamic Range Window violation
    28-06-2024 16:02:14warningRNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    28-06-2024 16:02:13warningREG-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;
    28-06-2024 16:02:13warningRNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    28-06-2024 16:02:13warningDynamic Range Window violation
    28-06-2024 16:02:07noticeDS 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;
    28-06-2024 16:02:00warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    28-06-2024 16:01:58noticeHonoring MDD; IP provisioning mode = IPv4
    28-06-2024 16:01:33criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    28-06-2024 16:01:27criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    28-06-2024 16:01:27criticalCable Modem Reboot because of - Reboot Timezone Change
    28-06-2024 15:59:14criticalNo Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    28-06-2024 15:58:43criticalNo Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    28-06-2024 15:58:29criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    28-06-2024 15:58:20criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    28-06-2024 15:58:19criticalCable Modem Reboot because of - pin-reset

    Some of these were before the cable from house to box was changed as i was getting micro drop outs, these for me seemed to have stopped.

    So this was like 10 minutes ago.

    As you can see on the graph im getting packet loss right now and thats the speed test showing very low upload, so its not just at peak times i get it, the frustrating this is im still paying for the top package each month and have been for 4 months since this started!

     

    • JoeC87's avatar
      JoeC87
      Joining in

      Seems to be fairly common at the moment with VM.. I've never had issues with my speeds, packet loss in 5+ years.. but suddenly I've had nothing but issues.

       

      I'm on the top package too and barely breaking 20mb upload and was getting consistently 100mbps+ 

      Engineer has been out with no luck he said he thinks it's their side and will speak to networking team, seemed like it was fixed for 2 days then went back to being low and consistant packet loss.

  • Do you think maybe the more that go to VM then there lines/networks cant handle the extra people?

    I now understand why they dont garantee there upload as it seems thats the part that is affected when there is an issue!