on 02-03-2022 14:46
So this is my current speed im getting The problem is im on 200mb package and the speeds have gone lower 30ish mb download at one point done all the online tests checked cables etc, this started just before christmas. ive always had 200mb or damn close to it but since december its shocking paying for something and not getting it at this point I am very close to Leaving Virgin media and going to city fibre.
Answered! Go to Answer
on 03-03-2022 15:37
on 02-03-2022 16:32
on 03-03-2022 08:40
Hi John,
That is over ethernet as per your advice im going to try the automated line today and failing that I will try and get an engineer again, this seem to coincide with the Gig rollout in this area
on 03-03-2022 15:37
on 03-03-2022 19:29
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 331000000 | -2.7 | 40 | 256 qam | 25 |
2 | 203000000 | -1 | 40 | 256 qam | 9 |
3 | 211000000 | -0.5 | 40 | 256 qam | 10 |
4 | 219000000 | -0.9 | 40 | 256 qam | 11 |
5 | 227000000 | -0.7 | 40 | 256 qam | 12 |
6 | 235000000 | -1.7 | 40 | 256 qam | 13 |
7 | 243000000 | -2.5 | 40 | 256 qam | 14 |
8 | 251000000 | -3.2 | 40 | 256 qam | 15 |
9 | 259000000 | -2.5 | 40 | 256 qam | 16 |
10 | 267000000 | -2.5 | 40 | 256 qam | 17 |
11 | 275000000 | -2 | 40 | 256 qam | 18 |
12 | 283000000 | -3 | 40 | 256 qam | 19 |
13 | 291000000 | -2.2 | 40 | 256 qam | 20 |
14 | 299000000 | -2.7 | 40 | 256 qam | 21 |
15 | 307000000 | -2.2 | 40 | 256 qam | 22 |
16 | 315000000 | -2.5 | 40 | 256 qam | 23 |
17 | 323000000 | -2.7 | 40 | 256 qam | 24 |
18 | 339000000 | -3 | 38 | 256 qam | 26 |
19 | 347000000 | -2.9 | 40 | 256 qam | 27 |
20 | 355000000 | -2.7 | 40 | 256 qam | 28 |
21 | 363000000 | -2.7 | 40 | 256 qam | 29 |
22 | 371000000 | -2.7 | 40 | 256 qam | 30 |
23 | 379000000 | -2.2 | 40 | 256 qam | 31 |
24 | 387000000 | -2.7 | 40 | 256 qam | 32 |
on 03-03-2022 19:30
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 40.3 | 106 | 552 |
2 | Locked | 40.3 | 101 | 614 |
3 | Locked | 40.3 | 136 | 648 |
4 | Locked | 40.9 | 93 | 686 |
5 | Locked | 40.3 | 118 | 370 |
6 | Locked | 40.3 | 157 | 355 |
7 | Locked | 40.3 | 99 | 361 |
8 | Locked | 40.3 | 84 | 380 |
9 | Locked | 40.9 | 120 | 366 |
10 | Locked | 40.9 | 132 | 330 |
11 | Locked | 40.3 | 69 | 326 |
12 | Locked | 40.3 | 116 | 500 |
13 | Locked | 40.3 | 143 | 400 |
14 | Locked | 40.3 | 143 | 410 |
15 | Locked | 40.9 | 157 | 454 |
16 | Locked | 40.9 | 161 | 528 |
17 | Locked | 40.3 | 133 | 578 |
18 | Locked | 38.9 | 107 | 642 |
19 | Locked | 40.3 | 99 | 646 |
20 | Locked | 40.3 | 99 | 525 |
21 | Locked | 40.3 | 120 | 515 |
22 | Locked | 40.3 | 171 | 586 |
23 | Locked | 40.9 | 92 | 529 |
24 | Locked | 40.3 | 86 | 614 |
on 03-03-2022 19:31
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 46199993 | 48 | 5120 | 64 qam | 3 |
2 | 39399993 | 48 | 5120 | 64 qam | 4 |
3 | 53699981 | 48 | 5120 | 64 qam | 2 |
4 | 60299966 | 48 | 5120 | 64 qam | 1 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 2 | 0 |
on 03-03-2022 19:33
02/03/2022 18:40:17 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/03/2022 14:00:39 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/03/2022 14:00:39 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/03/2022 13:59:54 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/03/2022 13:59:54 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/03/2022 13:59:53 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/03/2022 02:16:14 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/02/2022 22:45:52 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/02/2022 22:45:52 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/02/2022 16:07:1 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/02/2022 23:32:38 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/02/2022 23:32:38 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/02/2022 00:23:48 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/02/2022 08:59:11 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
19/02/2022 08:59:11 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/02/2022 10:26:44 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/02/2022 20:59:11 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/02/2022 20:59:11 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/02/2022 06:47:59 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/02/2022 08:59:11 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 03-03-2022 19:44
https://www.thinkbroadband.com/broadband/monitoring/quality/share/e6b208670f711ab619845455be6cd25fb6a2010c
on 06-03-2022 09:42
Hi micric5,
Thank you for posting to the community.
I am very sorry to hear of the issues you have been experiencing with your broadband, I appreciate this must be frustrating.
I have gone ahead and ran a full health check on the service from our side and can confirm the equipment appears to be running within specification with no known errors detected.
This is a check performed on the day so I would be keen to know how things have been since your last post here, have you noticed any improvements?
Thanks