cancel
Showing results for 
Search instead for 
Did you mean: 

More slow speed

Loofah
Joining in

After all the planned works in the area and you sending a note of being so very helpful in adjusting my settings on the router 'to make it faster'... I'm now getting very slow speeds!

No changes my side so must be down to whatever VM have done.

Have tried to follow advice on c/p the downstream/upstream and network logs but it gives me an error on exceeding 20k characters

10 REPLIES 10

jbrennand
Very Insightful Person
Very Insightful Person
Split the data into 2 or 3 posts and keep pressing "post".... till they do.

What Hub do you have and what package are you on and what speeds are you getting? And on what devices - over both wifi and ethernet cable connections?

--------------------
John
--------------------

I do not work for VM. My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired, 2 on WiFi) Hub5 in modem mode with Apple Airport Extreme Router +2 Airport Express's & TP-Link Archer C64 WAP. On Volt 350Mbps, Talk Anytime Phone, x2 Mobile SIM only iPhones.

Speed has come back up today so will keep watch on it. Thanks for the tip on splitting the posts. Can't believe I didn't think of that, doh!

 

Hayley_S
Forum Team (Retired)
Forum Team (Retired)

Hello @Loofah,

 

Welcome to the community, thanks for posting.

 

I am sorry for your slow speeds recently.

 

I can see that your speeds have come back from the help of @jbrennand.

 

Please do let us know if you need further help.

 

Many thanks,

Hayley
Forum Team



New around here? To find out more about the Community check out our Getting Started guide


more issues today.

 

Downstream

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

12030000002.936256 qam9
22110000002.536256 qam10
32190000002.236256 qam11
42270000001.936256 qam12
52350000001.736256 qam13
62430000001.737256 qam14
72510000001.737256 qam15
82590000001.537256 qam16
92670000001.537256 qam17
102750000001.437256 qam18
112830000001.737256 qam19
122910000001.737256 qam20
132990000001.937256 qam21
143070000001.737256 qam22
153150000001.536256 qam23
16323000000236256 qam24
173310000001.736256 qam25
18371000000136256 qam26
193790000000.736256 qam27
203870000000.536256 qam28
213950000000.436256 qam29
22403000000036256 qam30
23411000000036256 qam31
24419000000036256 qam32

 

 

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked36.6480364
2Locked36.3324362
3Locked36.6268387
4Locked36.3264367
5Locked36.6281373
6Locked37.62841516
7Locked37.3279373
8Locked37.3273367
9Locked37.3291367
10Locked37.3260369
11Locked37.3258378
12Locked37.3325485
13Locked37.3242472
14Locked37.3269366
15Locked36.6319375
16Locked36.62591760
17Locked36.6235405
18Locked36.6267368
19Locked36.6307479
20Locked36.6423385
21Locked36.6357376
22Locked36.63741742
23Locked36.3494499
24Locked36.6402388

Upstream bonded channels

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

14620143540.7512016 qam9
23939932940.7512016 qam10
32579995940.2512016 qam12
43260110540.2512016 qam11



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0070
2ATDMA00140
3ATDMA0050
4ATDMA0050

Network Log

Time Priority Description

14/10/2021 10:49:44criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/10/2021 23:20:35ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/10/2021 01:58:22Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/10/2021 00:06:41criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/10/2021 10:56:3noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/10/2021 10:55:45Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/10/2021 06:56:8criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/10/2021 21:08:28ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2021 13:50:6Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2021 13:50:6criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2021 13:50:6Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2021 13:50:6Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2021 13:50:6criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2021 13:50:1Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2021 13:50:1criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2021 13:50:0Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2021 13:50:0criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2021 13:49:58Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2021 13:49:6Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2021 13:49:0Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Hi Loofah,

Our apologies you're still having issues. I have been able to locate your account and checked your levels and everything seems to be working fine. 

Can you confirm if you're experiencing this issue?

^Martin

I suppose if there's been an area fault things could have improved, but levels weren't fine on Thursday, since the upstream had dropped modulation on all channels to 16 QAM, there were multiple T3 timeouts on the upstream, the network log was showing repeated channel loss and re-registration entries, and the downstream was riddled with post-RS (uncorrectable) errors affecting all channels.  All of those indicate that there's a wideband noise problem that affects the DOCSIS connection.