cancel
Showing results for 
Search instead for 
Did you mean: 

Network issues after engineer visit

Aedrothica
On our wavelength

I had an engineer come out today. He changed all of my cables and connectors, as I did had some really bad readings. He fixed those and put an attenuator on the box at the front of my house as he said I was having too high of a signal coming through. He left about 15:40ish

I was told my downstream should read about 7's where before it was on 11/12's.

It was okay for about 30-40 mins and now it seems even worse than before. I am a gamer, I am unable to enjoy anything atm, I pay for a good connection and speed. This is honestly the worst service I have ever had. If everything is okay at my property what the hell is the cause of this? Can I get some help?
https://www.thinkbroadband.com/broadband/monitoring/quality/share/e18e4e2305216a9f9889895ab93d8ffb57... 

e18e4e2305216a9f9889895ab93d8ffb57a01144-24-11-2023.png

3.0 Downstream channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
13780000006.242QAM 25631
21380000008.341QAM 2561
31460000007.941QAM 2562
41540000007.941QAM 2563
51620000007.941QAM 2564
61700000007.741QAM 2565
71780000007.741QAM 2566
81860000007.741QAM 2567
91940000007.941QAM 2568
10202000000842QAM 2569
11210000000842QAM 25610
122180000007.942QAM 25611
132260000007.742QAM 25612
142340000007.642QAM 25613
152420000007.342QAM 25614
162500000007.142QAM 25615
172580000007.142QAM 25616
18266000000742QAM 25617
192740000007.142QAM 25618
202820000007.142QAM 25619
21290000000742QAM 25620
222980000007.142QAM 25621
233060000007.242QAM 25622
243140000007.242QAM 25623
253220000007.342QAM 25624
26330000000742QAM 25625
273380000006.742QAM 25626
283460000006.542QAM 25627
293540000006.442QAM 25628
303620000006.242QAM 25629
313700000006.342QAM 25630

3.0 Downstream channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked42214683139302
2Locked41584284827097
3Locked41375221724393
4Locked4193299128058
5Locked41307230353438
6Locked41251180319782
7Locked41363116311632
8Locked4171686101414
9Locked41103041133091
10Locked42511979389777
11Locked42251927227019
12Locked42527229351123
13Locked42217864180392
14Locked42536701323246
15Locked42558696325388
16Locked42213293191308
17Locked42233514232210
18Locked42173109235218
19Locked42231068180601
20Locked42521276309526
21Locked42457077246018
22Locked42527395248935
23Locked42524425247218
24Locked42491095261276
25Locked42265138213687
26Locked42242973233941
27Locked42274830222541
28Locked42465772280701
29Locked42241364236714
30Locked42240414222987
31Locked42187887175303

3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
159924K1800QAM 40961128

3.1 Downstream channels

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

 

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
046200000415120QAM 641
13940000040.55120QAM 642
232600000405120QAM 643
353700000415120QAM 644

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0ATDMA0000
1ATDMA0000
2ATDMA0000
3ATDMA0000

 

Network Log

Time Priority Description
24-11-2023 16:00:14warningDBC-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;
24-11-2023 16:00:13criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:49:11noticeREGISTRATION COMPLETE - Waiting for Operational status
24-11-2023 15:49:05warningREG-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;
24-11-2023 15:48:52warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:48:50noticeHonoring MDD; IP provisioning mode = IPv4
24-11-2023 15:43:57criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:43:53warningToD request sent - No Response received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:43:53criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:43:33criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:43:33criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:43:13criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:43:13criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:42:54criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:42:53criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:42:15warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:42:15criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:42:12criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:40:34noticeREGISTRATION COMPLETE - Waiting for Operational status
24-11-2023 15:40:28warningREG-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;
24-11-2023 15:40:15warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:40:13noticeHonoring MDD; IP provisioning mode = IPv4
24-11-2023 15:40:01criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:40:00criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:39:27criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:39:24warningToD request sent - No Response received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:38:33warningMDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:38:27warningRCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:38: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;
24-11-2023 15:38:22criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
24-11-2023 15:38:21warningDBC-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;
24-11-2023 15:38:18criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
11 REPLIES 11

Hi Aedrothica, 

Thanks for coming back to via private message to confirm your information. 🤩

I have booked you in for the next available appointment. To view this please sign in to My Virgin Media here 👉 My VM. Once you log in scroll down to Orders & appointments then click on View your orders. Please note it can take up to 24 hours to show but you should also receive a text message with the details. You can also view this in the My VM app. If you have any issues with accessing your account or unable to see your visit, please do let us know and we’ll pop you a message to pass data protection and confirm the appointment details.

Just to confirm, there will be no charge for this visit unless:

  • ➡ The technician diagnoses the faults as not being caused by our network/equipment 
  • ➡ The technician discovers that the fault or problem relates to your equipment
  • ➡ The technician discovers that the fault or problem relates to any system that we are not responsible for
  • ➡ The technician will confirm during their visit if any of these instances apply, and if so, a £25 charge will be applied to your account.

Please ensure there is someone over the age of 18 present at the time of the visit. If you need to change or cancel your appointment you can do this online or via the MyVM app by 4pm the day before the appointment. If you do miss an agreed appointment for any reason, a £25 missed appointment charge will be applied to your account on the day of the appointment.

We will continue to monitor your services and if we can see that the fault has cleared and the visit is no longer required we will cancel the appointment and let you know by text and email.

Let us know how the appointment goes. 😊

Take care.

Kath_F
Forum Team

New around here? Check out the do's and don'ts, in our Community FAQs


Hi Aedrothica, 

Thanks for sticking with me via private message. 

I can see the fault has cleared now and as you have rebooted your hub, this would have refreshed things. Keep us posted on how the connection is over the next day or so. 

If you continue to have any issues, post back here and we can look further into things with you. 

Many thanks, 

Kath_F
Forum Team

New around here? Check out the do's and don'ts, in our Community FAQs