cancel
Showing results for 
Search instead for 
Did you mean: 

post didnt appear

iwantraytolive
On our wavelength

just made a lengthy post about ongoing (2-3 months) network fault causing intermittent loss of service. hasnt appeared. testing

1 ACCEPTED SOLUTION

Accepted Solutions

That post has now appeared.  What you describe is a very poor customer experience (you'll understand how VM have just won the Ofcom award for "Most complained about ISP"), but I have flagged it for the helpful forum staff to take a look.

I would suggest that you let VM get this dodgy connection sorted out, and only then escalate the complaint that "resolved" to the industry arbitration scheme CISAS, asking for compensation for the poor connection and poor support (unless forum staff can sort out a couple of months credit on you account).  That escalation has to be 8 weeks after the complaint was received by VM, hence doing it after the fix.

See where this Helpful Answer was posted

4 REPLIES 4

iwantraytolive
On our wavelength

https://community.virginmedia.com/t5/Networking-and-WiFi/Post-RS-errors-a-quot-short-term-stability-...

my OP. dont know why it hasnt appeared - possibly it was too long? 


Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 331000000 1 36 256 qam 25
2 203000000 0.2 35 256 qam 9
3 211000000 -0.2 35 256 qam 10
4 219000000 0 35 256 qam 11
5 227000000 0 35 256 qam 12
6 235000000 0 35 256 qam 13
7 243000000 -0.2 35 256 qam 14
8 251000000 -0.4 35 256 qam 15
9 259000000 -0.7 35 256 qam 16
10 267000000 0 35 256 qam 17
11 275000000 -0.4 35 256 qam 18
12 283000000 -0.2 35 256 qam 19
13 291000000 -0.2 35 256 qam 20
14 299000000 -0.2 35 256 qam 21
15 307000000 0.2 35 256 qam 22
16 315000000 0.9 36 256 qam 23
17 323000000 0.7 36 256 qam 24
18 339000000 1.2 36 256 qam 26
19 347000000 1 36 256 qam 27
20 355000000 1.2 36 256 qam 28
21 363000000 1 36 256 qam 29
22 371000000 0.9 36 256 qam 30
23 379000000 1.5 36 256 qam 31
24 387000000 0.9 36 256 qam 32


Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 36.3 3010 1864
2 Locked 35.5 1024 20147
3 Locked 35.5 962 12707
4 Locked 35.5 1953 10613
5 Locked 35.7 2412 8897
6 Locked 35.7 1089 12184
7 Locked 35.7 3884 9208
8 Locked 35.5 3625 17791
9 Locked 35.7 6359 7150
10 Locked 35.7 4614 7370
11 Locked 35.7 2116 1650
12 Locked 35.5 2864 1705
13 Locked 35.5 3896 7712
14 Locked 35.7 8106 5983
15 Locked 35.7 4264 1815
16 Locked 36.3 2036 1740
17 Locked 36.3 3126 2500
18 Locked 36.3 2638 1561
19 Locked 36.3 3422 2051
20 Locked 36.6 4256 2092
21 Locked 36.3 4801 2389
22 Locked 36.3 3571 2066
23 Locked 36.3 2723 2182
24 Locked 36.6 3749 2557

Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 60300000 45.8 5120 64 qam 1
2 46199922 45.3 5120 64 qam 3
3 39399995 45.3 5120 64 qam 4
4 53699975 45.5 5120 64 qam 2


Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 0 0
2 ATDMA 0 0 1 0
3 ATDMA 0 0 0 0
4 ATDMA 0 0 0 0

Time Priority Description
08/09/2021 15:01:3 Warning! RCS Partial Service;CM-MAC=x:x:x:x:x:x;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2021 15:00:7 Warning! Lost MDD Timeout;CM-MAC=x:x:x:x:x:x;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2021 15:00:3 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=x:x:x:x:x:x;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2021 15:00:3 Warning! RCS Partial Service;CM-MAC=x:x:x:x:x:x;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2021 15:00:3 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=x:x:x:x:x:x;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2021 15:00:2 Warning! RCS Partial Service;CM-MAC=x:x:x:x:x:x;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2021 14:12:37 critical No Ranging Response received - T3 time-out;CM-MAC=x:x:x:x:x:x;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2021 09:24:17 Warning! RCS Partial Service;CM-MAC=x:x:x:x:x:x;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2021 09:24:17 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=x:x:x:x:x:x;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2021 05:32:3 Warning! RCS Partial Service;CM-MAC=x:x:x:x:x:x;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2021 05:29:9 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=x:x:x:x:x:x;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2021 05:26:59 Warning! RCS Partial Service;CM-MAC=x:x:x:x:x:x;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2021 05:26:59 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=x:x:x:x:x:x;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2021 05:16:35 Warning! RCS Partial Service;CM-MAC=x:x:x:x:x:x;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/09/2021 05:16:34 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=x:x:x:x:x:x;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/09/2021 11:05:25 Warning! RCS Partial Service;CM-MAC=x:x:x:x:x:x;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/09/2021 11:04:45 Warning! Lost MDD Timeout;CM-MAC=x:x:x:x:x:x;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/09/2021 11:04:41 Warning! RCS Partial Service;CM-MAC=x:x:x:x:x:x;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/09/2021 11:04:41 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=x:x:x:x:x:x;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/09/2021 11:04:40 Warning! RCS Partial Service;CM-MAC=x:x:x:x:x:x;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

in case first post doesnt appear - 4 engineer visits (that i agreed to) at least another 3 that VM booked without informing me, packet loss, latency, disconnections. ongoing issue. hub replaced, pinhole reset etc, new line on property installed, things only have got worse.

really despondent over this - cant even get a forum post out!

https://www.thinkbroadband.com/broadband/monitoring/quality/view/7b33a1602c33cdea93f4b2428a115125dff...

Today https://www.thinkbroadband.com/broadband/monitoring/quality/share/a1b8079635f6f3bb17f6bce7d2d055dc00...

Andrew-G
Alessandro Volta

As it's a first or second post and quite long, it may have triggered a trip to the mods' in-tray.  It will usually appear, but might be tomorrow depending on shift end times, staffing and work volumes.

ahh, thank you!

just have to hope it's approved.. it's a bit worrying that VM can edit my posts without any kind of notice appearing on my post that it has been edited.

I appreciate why the link was removed since my first thread is awaiting approval, but i don't really understand why they edited my posts in this thread to remove my BQM (this thread was the first time I posted the BQM!), hub stats and brief problem outline.. and then moved this thread out of the 'faults' forum :s

https://www.thinkbroadband.com/broadband/monitoring/quality/view/7b33a1602c33cdea93f4b2428a115125dff...

Today https://www.thinkbroadband.com/broadband/monitoring/quality/share/a1b8079635f6f3bb17f6bce7d2d055dc00...

 

That post has now appeared.  What you describe is a very poor customer experience (you'll understand how VM have just won the Ofcom award for "Most complained about ISP"), but I have flagged it for the helpful forum staff to take a look.

I would suggest that you let VM get this dodgy connection sorted out, and only then escalate the complaint that "resolved" to the industry arbitration scheme CISAS, asking for compensation for the poor connection and poor support (unless forum staff can sort out a couple of months credit on you account).  That escalation has to be 8 weeks after the complaint was received by VM, hence doing it after the fix.