cancel
Showing results for 
Search instead for 
Did you mean: 

Slow upload speed

hd3
On our wavelength

On a M200 package but get upload speeds of <4Mbps consistently throughout the day. Download speeds typically almost always hitting 200 Mbps. 

It's been consistently slow on upload for almost a year. Occasionally I'll get 20 Mbps.

I've called VM a few times and followed the full reset on router procedure but it hasn't changed anything.

Any help appreciated.

BQM:

https://www.thinkbroadband.com/broadband/monitoring/quality/share/d6c8de7feb99df6e2fbb9d901357a671fa... 

2 ACCEPTED SOLUTIONS

Accepted Solutions

Hey @hd3

 

Welcome to the community and thanks for your posts.

 

I'm sorry that it has taken so long to get back to you and for the issues that you've been having. 

 

I have been able to locate your account and can see that there is a congestion issue in your area that is being looked into by our networks team and currently the estimated resolution date of 26th Feb at around 9am under reference F008611099 .

 

Regards

Steven_L

See where this Helpful Answer was posted

Sorry to say hd3, but network congestion has been reinstated in your local area and is due to be fixed on 24/03 at 10:00

 

We apologise for any inconvenience this may cause you

 

Kindest regards,

 

David

See where this Helpful Answer was posted

82 REPLIES 82

hd3
On our wavelength
 
Cable Modem StatusItem Status Comments
Acquired Downstream Channel (Hz)
266750000
Locked
Ranged Upstream Channel (Hz)
39399942
Locked
Provisioning State
Online

 

Downstream bonded channelsChannel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1266750000-1.738256 qam17
2138750000138256 qam1
3146750000137256 qam2
41547500000.437256 qam3
5162750000-0.237256 qam4
6170750000-137256 qam5
7178750000-1.537256 qam6
8186750000-1.437256 qam7
9194750000-1.538256 qam8
10202750000-1.738256 qam9
11210750000-1.737256 qam10
12218750000-238256 qam11
13226750000-238256 qam12
14234750000-1.938256 qam13
15242750000-1.938256 qam14
16250750000-1.738256 qam15
17258750000-1.738256 qam16
18274750000-1.938256 qam18
19282750000-1.938256 qam19
20290750000-1.938256 qam20
21298750000-1.738256 qam21
22306750000-1.738256 qam22
23314750000-2.238256 qam23
24322750000-2.737256 qam24



Downstream bonded channelsChannel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked38.97300
2Locked38.92560
3Locked37.62860
4Locked37.36370
5Locked37.64080
6Locked37.67740
7Locked37.696322
8Locked37.67861
9Locked38.64820
10Locked38.93670
11Locked37.64660
12Locked38.65471
13Locked38.64800
14Locked38.64970
15Locked38.64570
16Locked38.94390
17Locked38.65150
18Locked38.65260
19Locked38.95910
20Locked38.65510
21Locked38.612710
22Locked38.915170
23Locked38.619920
24Locked37.615980

hd3
On our wavelength

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

13939994243.8512064 qam4
24619994744.8512064 qam3
33259996743512064 qam5
42580028442.3512064 qam11



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0090
2ATDMA00100
3ATDMA00110
4ATDMA0080

 

General Configuration

Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
cmreg-vmdg505-bbt060-b.cm



Primary Downstream Service Flow

SFID847080
Max Traffic Rate230000061
Max Traffic Burst42600
Min Traffic Rate0



Primary Upstream Service Flow

SFID847079
Max Traffic Rate22000061
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst42600
Scheduling TypeBestEffort

hd3
On our wavelength

Network Log

Time Priority Description

11/02/2021 17:22:12noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/02/2021 03:32:40criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/02/2021 01:30:35ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/02/2021 11:03:34criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/02/2021 13:30:35ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/02/2021 04:02:57criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2021 01:30:35ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/01/2021 16:12:19criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/01/2021 13:30:35ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/01/2021 17:21:4criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/01/2021 01:30:35ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 04:21:58criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/01/2021 13:30:35ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/01/2021 17:16:4criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/01/2021 01:30:34ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/01/2021 22:41:52criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/01/2021 13:30:34ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/01/2021 19:19:0criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/01/2021 15:55:38noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/01/2021 01:56:53criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Hey @hd3

 

Welcome to the community and thanks for your posts.

 

I'm sorry that it has taken so long to get back to you and for the issues that you've been having. 

 

I have been able to locate your account and can see that there is a congestion issue in your area that is being looked into by our networks team and currently the estimated resolution date of 26th Feb at around 9am under reference F008611099 .

 

Regards

Steven_L

hd3
On our wavelength

Thank You.

Look forward to the the fix on Friday.

No problem @hd3 and I hope that this issue is finally resolved on Friday.

 

Regards

Steven_L

Lets us know how it goes?

The Giggitty 1

hd3
On our wavelength

Unfortunately 9am has been and gone and uploads are still around 1-2Mbps.

@Virgin Media - any idea when reference F008611099 is likely to be fixed?

I'll expect the fault date has been extended, these faults are occurring nationwide due to WFH and home schooling, I wouldn't expect anything to change until the country resumes a normal active life.

The Giggitty 1