Menu

Virgin Media Community

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Post a question

Reply
apoko
  • 32
  • 0
  • 0
Tuning in
393 Views
Message 1 of 7
Flag for a moderator

1GB line and 12 months test no where near

on ‎20-02-2022 20:23

Over 12 months speed test data and still not getting anywhere near 1GB, at you can see i was hitting over the 850 which I was happy with but its all gone downhill from then. Anyone any idea why i am not getting the speeds I am paying for, I have a cat 8 cable and when on the 300mb package never had a problem.

apoko_0-1645388014863.png

apoko_1-1645388064055.png



 



 



 

 

0 Kudos
Reply
apoko
  • 32
  • 0
  • 0
Tuning in
392 Views
Message 2 of 7
Flag for a moderator

Re: 1GB line and 12 months test no where near

on ‎20-02-2022 20:23

3.0 Downstream channels

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

202910000001.639QAM25620
11390000003.339QAM2561
21470000002.939QAM2562
31550000002.739QAM2563
41630000002.638.6QAM2564
51710000002.438.6QAM2565
61790000002.439QAM2566
71870000002.139QAM2567
81950000002.139QAM2568
92030000002.140.4QAM2569
10211000000239QAM25610
112190000001.739QAM25611
122270000001.738.6QAM25612
132350000001.338.6QAM25613
142430000001.139QAM25614
15251000000139QAM25615
162590000000.439QAM25616
172670000000.639QAM25617
182750000001.139QAM25618
192830000001.639QAM25619
212990000001.440.4QAM25621
223070000001.138.6QAM25622
233150000001.338.6QAM25623
243230000001.139QAM25624
253310000000.439QAM25625
263390000000.639QAM25626
273470000000.938.6QAM25627
283550000000.739QAM25628
293630000000.939QAM25629
303710000000.939QAM25630
313790000000.539QAM25631



3.0 Downstream channels

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

20Locked38.98326100
1Locked38.98326100
2Locked38.98326100
3Locked38.98326100
4Locked38.60537700
5Locked38.60537700
6Locked38.98326100
7Locked38.98326100
8Locked38.98326100
9Locked40.36628700
10Locked38.98326100
11Locked38.98326100
12Locked38.60537700
13Locked38.60537700
14Locked38.98326100
15Locked38.98326100
16Locked38.98326100
17Locked38.98326100
18Locked38.98326100
19Locked38.98326100
21Locked40.36628700
22Locked38.60537700
23Locked38.60537700
24Locked38.98326100
25Locked38.98326100
26Locked38.98326100
27Locked38.60537700
28Locked38.98326100
29Locked38.98326100
30Locked38.98326100
31Locked38.98326100



3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
33964K1880QAM4096759


3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
33Locked40-4.83911374960544
0 Kudos
Reply
apoko
  • 32
  • 0
  • 0
Tuning in
391 Views
Message 3 of 7
Flag for a moderator

Re: 1GB line and 12 months test no where near

on ‎20-02-2022 20:24

3.0 Upstream channels

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

13940000046.55120 KSym/sec64QAM4
25370000045.85120 KSym/sec64QAM2
36030000045.85120 KSym/sec64QAM1
446200000465120 KSym/sec64QAM3



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1US_TYPE_STDMA0010
2US_TYPE_STDMA0000
3US_TYPE_STDMA0000
4US_TYPE_STDMA0000

 

Network Log

Time Priority Description

Wed 22/12/2021 07:32:356CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 25/12/2021 17:44:344DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 25/12/2021 21:38:396CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 27/12/2021 03:54:253No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 27/12/2021 12:19:046CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 29/12/2021 05:44:344DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 29/12/2021 09:39:596CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 01/01/2022 17:44:344DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 01/01/2022 21:26:186CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 05/01/2022 05:44:344DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 05/01/2022 18:40:266CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 08/01/2022 17:44:344DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 09/01/2022 17:47:076CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 01/01/1970 00:01:223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 10/01/2022 00:23:025MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 10/01/2022 16:56:006CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 10/01/2022 21:25:465MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue 11/01/2022 10:00:476CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 13/01/2022 07:35:124DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu 13/01/2022 16:29:276CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 15/01/2022 16:42:143No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sat 15/01/2022 18:29:316CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 16/01/2022 07:10:034DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 16/01/2022 10:42:506CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 19/01/2022 19:10:034DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 19/01/2022 22:28:496CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 23/01/2022 07:10:034DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 23/01/2022 15:12:276CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 26/01/2022 15:50:403No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 26/01/2022 16:06:006CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 26/01/2022 19:10:034DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 26/01/2022 20:27:576CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 30/01/2022 07:10:034DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Mon 31/01/2022 13:37:396CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 02/02/2022 19:10:034DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed 02/02/2022 21:04:566CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 06/02/2022 07:10:034DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Sun 06/02/2022 20:24:416CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

 

0 Kudos
Reply
Carley_S
  • 3.16K
  • 166
  • 267
Forum Team
Forum Team
320 Views
Message 4 of 7
Flag for a moderator

Re: 1GB line and 12 months test no where near

on ‎23-02-2022 10:41

Hi @apoko

Welcome to the community!

I can see that you already have a thread open for the same issue that has further investigated and looked into resolving this issue with an engineer visit.

If you have any other questions or issues please refer/post to that thread. 

All the best, 

Carley - Forum Team


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


0 Kudos
Reply
apoko
  • 32
  • 0
  • 0
Tuning in
288 Views
Message 5 of 7
Flag for a moderator

Re: 1GB line and 12 months test no where near

on ‎28-02-2022 22:15

I was told it would be better to open my own post so this is what i have done

0 Kudos
Reply
apoko
  • 32
  • 0
  • 0
Tuning in
287 Views
Message 6 of 7
Flag for a moderator

Re: 1GB line and 12 months test no where near

on ‎28-02-2022 22:16

Engineer came out played around with some wires outside said everything is ok and my speed actually dropped give in now

0 Kudos
Reply
Kain_W
  • 3.77K
  • 105
  • 268
Forum Team
Forum Team
240 Views
Message 7 of 7
Flag for a moderator

Re: 1GB line and 12 months test no where near

on ‎03-03-2022 11:52

Hi apoko,

Thanks for posting and welcome back to the community!

So sorry for any issues caused, from checking our service I can't currently see any readings that would contribute to the speed issues. 

Are you able to set up a BQM so we can review any potential latency pop ups too?

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

 

Thanks,

Kain
0 Kudos
Reply

Digital life blog

Help videos

Help forum