2 weeks ago
Hi All,
We started getting a CS2004 error on our Virgin 360 box towards the back end of October. I researched this and posts said connection problems, so I disconnected all of the cables and reseated them but problems persisted so I reset the box to factory defaults. We then started to experience drop outs, performance issues whilst gaming such as Lag etc so the router was also reset to factory defaults but to no joy.
I then did a test on the app and it was telling me that there was a communication problem between TV and broadband, then issues in the local area wait 24 hours. Eventually after a week or so of waiting I finally logged a fault with the support team back at the end of October/Early November. An engineer attended and he showed me that all the lights were currently green on his device (he did see drop outs on the connection history though).
He checked all cables, connections etc but as this did not cure the problem he then cleaned the external cable, replaced the internal cable which links the 360 box to coax and hub. Seemed to cure the problem but just as he was leaving it came back, he asked me to wait a while and see if it returned - it did. The engineer said the next step was to change the way the connection entered the house, something about a new way of bringing the cable inside and that he would arrange it. Sure enough another engineer came but at this point I was at work, and they replaced the cable from the road to the house, I mentioned this to the original engineer who stated that was not what should have happened - apologised and said he would sort it, this was 26th November.
The Virgin Media app and web site alternate between every thing is fine, to The TV box is having broadband connection issues to intermittent broadband issues in your area all within minutes of each other.
I don't really understand the Think Broadband Quality Monitoring graphs but here is a typical connection graph we used to get at the beginning of October.
https://www.thinkbroadband.com/broadband/monitoring/quality/share/006af32641b153dd2bd253a57622f0f167eba1f2-01-10-2024
This is today's
https://www.thinkbroadband.com/broadband/monitoring/quality/share/d790454fa2d892b52aa9292e387c003f845b14b8-04-12-2024
This is yesterdays
https://www.thinkbroadband.com/broadband/monitoring/quality/share/92e75568a34652eb700f5175ffc2b41809ef1805-03-12-2024
Another graph which seems to show some issues with packet loss, bit of an odd time though as we are generally sleeping through the night so if the spikes show traffic this is a bit weird.
https://www.thinkbroadband.com/broadband/monitoring/quality/share/f4fb120629d722d70b0abad6b38544f326d547ae-22-11-2024
Whilst I am patiently waiting for an update from the engineer on when the changes will be done I thought I would post here to see if anyone had any ideas on what I can do if anything.
2 weeks ago
Hi @shallow
I've moved your thread from the TV360 forum to the broadband forums.
The BQM link that you posted showing the connection for 4th December shows that you have you have an internet issue. Whilst you are waiting for your 'update from the engineer', it would be helpful to post the actual hub stats.
Type 192.168.0.1 (192.168.100.1 if you are in Modem mode) into your browser URL bar and press enter.
When the page appears click ‘Check Router Status’
When that page appears, log in (using the details on the hub) and then go to Advanced Settings > Tools > Network Status.
Then copy paste (don't screenshot) the information from the Downstream, Upstream, Configuration and Network logs.
2 weeks ago
Ok will do, thanks. The Hub 4 admin pages are so slow and unresponsive, sometimes they load other times they don't, currently they are not loading in but will keep trying.
2 weeks ago
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
25 | 330750000 | -1.8 | 39 | QAM256 | 25 |
1 | 138750000 | 0.8 | 40.4 | QAM256 | 1 |
2 | 146750000 | 0.7 | 40.4 | QAM256 | 2 |
3 | 154750000 | 0.7 | 40.9 | QAM256 | 3 |
4 | 162750000 | 0.7 | 40.9 | QAM256 | 4 |
5 | 170750000 | 0.7 | 40.9 | QAM256 | 5 |
6 | 178750000 | 0.8 | 40.4 | QAM256 | 6 |
7 | 186750000 | 0.7 | 40.4 | QAM256 | 7 |
8 | 194750000 | 0.8 | 40.4 | QAM256 | 8 |
9 | 202750000 | 0.8 | 40.4 | QAM256 | 9 |
10 | 210750000 | 0.8 | 40.4 | QAM256 | 10 |
11 | 218750000 | 0.5 | 40.4 | QAM256 | 11 |
12 | 226750000 | 0.5 | 40.4 | QAM256 | 12 |
13 | 234750000 | 0.3 | 40.4 | QAM256 | 13 |
14 | 242750000 | 0.1 | 40.4 | QAM256 | 14 |
15 | 250750000 | 0.1 | 40.4 | QAM256 | 15 |
16 | 258750000 | -0.4 | 40.4 | QAM256 | 16 |
17 | 266750000 | -0.7 | 40.9 | QAM256 | 17 |
18 | 274750000 | -0.7 | 40.4 | QAM256 | 18 |
19 | 282750000 | -0.7 | 40.4 | QAM256 | 19 |
20 | 290750000 | -0.8 | 40.4 | QAM256 | 20 |
21 | 298750000 | -0.9 | 40.4 | QAM256 | 21 |
22 | 306750000 | -1.3 | 40.4 | QAM256 | 22 |
23 | 314750000 | -1.5 | 40.4 | QAM256 | 23 |
24 | 322750000 | -1.7 | 39 | QAM256 | 24 |
26 | 338750000 | -1.7 | 39 | QAM256 | 26 |
27 | 346750000 | -1.5 | 40.4 | QAM256 | 27 |
28 | 354750000 | -1.5 | 39 | QAM256 | 28 |
29 | 362750000 | -1.4 | 38.6 | QAM256 | 29 |
30 | 370750000 | -1.2 | 39 | QAM256 | 30 |
31 | 378750000 | -1.4 | 39 | QAM256 | 31 |
32 | 386750000 | -1.7 | 39 | QAM256 | 32 |
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
25 | Locked | 38.983261 | 0 | 0 |
1 | Locked | 40.366287 | 0 | 0 |
2 | Locked | 40.366287 | 0 | 0 |
3 | Locked | 40.946209 | 0 | 0 |
4 | Locked | 40.946209 | 0 | 0 |
5 | Locked | 40.946209 | 0 | 0 |
6 | Locked | 40.366287 | 0 | 0 |
7 | Locked | 40.366287 | 0 | 0 |
8 | Locked | 40.366287 | 0 | 0 |
9 | Locked | 40.366287 | 0 | 0 |
10 | Locked | 40.366287 | 0 | 0 |
11 | Locked | 40.366287 | 0 | 0 |
12 | Locked | 40.366287 | 0 | 0 |
13 | Locked | 40.366287 | 0 | 0 |
14 | Locked | 40.366287 | 0 | 0 |
15 | Locked | 40.366287 | 0 | 0 |
16 | Locked | 40.366287 | 0 | 0 |
17 | Locked | 40.946209 | 0 | 0 |
18 | Locked | 40.366287 | 0 | 0 |
19 | Locked | 40.366287 | 0 | 0 |
20 | Locked | 40.366287 | 0 | 0 |
21 | Locked | 40.366287 | 0 | 0 |
22 | Locked | 40.366287 | 0 | 0 |
23 | Locked | 40.366287 | 0 | 0 |
24 | Locked | 38.983261 | 0 | 0 |
26 | Locked | 38.983261 | 0 | 0 |
27 | Locked | 40.366287 | 0 | 0 |
28 | Locked | 38.983261 | 0 | 0 |
29 | Locked | 38.605377 | 0 | 0 |
30 | Locked | 38.983261 | 0 | 0 |
31 | Locked | 38.983261 | 0 | 0 |
32 | Locked | 38.983261 | 0 | 0 |
159 | 94 | 4K | 1800 | QAM4096 | 424 |
159 | Locked | 42 | -0.5 | 2913675727 | 14259 |
2 weeks ago
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 46200000 | 35 | 5120 KSym/sec | QAM64 | 3 |
2 | 23600000 | 36 | 5120 KSym/sec | QAM64 | 6 |
3 | 32600000 | 35.5 | 5120 KSym/sec | QAM64 | 5 |
4 | 39400000 | 35 | 5120 KSym/sec | QAM64 | 4 |
5 | 53700000 | 35.5 | 5120 KSym/sec | QAM64 | 2 |
6 | 60300000 | 35 | 5120 KSym/sec | QAM64 | 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 | 0 | 0 |
5 | ATDMA | 0 | 0 | 0 | 0 |
6 | ATDMA | 0 | 0 | 0 | 0 |
2 weeks ago
Network access | true |
Maximum Number of CPEs | 1 |
Baseline Privacy | true |
DOCSIS Mode | 3.1 |
Config file | kfoA,.iyewrkldJKDHSUBsgvca698 |
SFID | 6750 |
Max Traffic Rate | 575000085 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
SFID | 6749 |
Max Traffic Rate | 55000085 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 42600 |
Scheduling Type | bestEffort |
2 weeks ago
Time Priority Description
Thu 05/12/2024 18:54:05 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 17; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 18:53:38 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 18:33:28 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 18:33:09 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 18:11:47 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 9; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 18:11:00 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 18:10:33 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 18:10:29 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 18:09:27 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 18:08:53 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 17:53:51 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 20; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 17:53:37 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 17:37:56 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 1; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 17:37:51 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 17:27:58 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 3; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 17:27:53 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 17:09:54 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 2; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 17:09:32 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 17:06:31 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 17:06:12 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 17:00:21 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 17:00:19 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 16:57:49 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 16:57:39 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 16:57:01 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 16:56:25 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 16:36:34 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 19; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 16:36:16 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 16:17:25 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 19; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 16:17:06 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 15:57:31 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 19; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 15:57:01 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 15:47:51 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 21; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 15:47:41 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 15:30:18 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 21; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 15:29:55 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 15:22:57 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 21; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 15:22:55 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 14:55:05 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 21; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 14:54:51 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 14:36:52 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 13; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 14:36:15 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 14:27:53 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 14:27:15 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 14:16:36 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 14:16:03 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 13:47:47 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 13:47:33 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 13:29:01 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 05/12/2024 13:28:36 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
2 weeks ago
More issues which affected meetings this morning! Need to log another support request I guess though the service status is once again stating intermittent signal in your area and to wait 24 hours!
2 weeks ago
Original engineer not getting back to me and no response from VM Team on here. Finally managed to get an appointment booked for Tuesday after the online checker wouldn't let me due to "intermittent problem in your area".
Spoke to several people on my estate who have no problems so can't be a problem in the area imo.
Yesterday's BQM
Today's BQM
Pixellated video continues along with lag in games on different consoles etc.
2 weeks ago
Hi there @shallow 👋 Welcome to the community and thanks for your post 😊
Sorry to see that these issues you've had have continued. I've checked our system and can see you've been in touch since your last post. Have you now been able to get help with this?
Let us know if you need anything further, we're always happy to help.
Regards
Nathan
The do's and don'ts. Keep the community welcoming for all. Follow the house rules