cancel
Showing results for 
Search instead for 
Did you mean: 

M500 Still Slow

jkap
Tuning in

Experienced significant speed issues since December of last year - things have not really improved despite the various lockdown easing measures etc. Looks like our area is still suffering from over utilisation? Most frustratingly upstream tanks during the week and as we are still working from home it's really causing issues.

I've tried wired, wireless, router reboots/resets/pinhole etc etc. Upstream refuses to remain locked at 64 qam across all 4 channels.

BQM with lots of data: 

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

Router stats:

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

1723000000-338256 qam40
2539000000040256 qam17
35470000000.240256 qam18
4555000000040256 qam19
5563000000-0.440256 qam20
6571000000-0.740256 qam21
7579000000-0.940256 qam22
8587000000-0.940256 qam23
9595000000-0.740256 qam24
10603000000-0.740256 qam25
11611000000-0.740256 qam26
12619000000-0.940256 qam27
13627000000-1.238256 qam28
14635000000-1.538256 qam29
15643000000-1.740256 qam30
16651000000-1.740256 qam31
17659000000-1.740256 qam32
18667000000-1.540256 qam33
19675000000-1.538256 qam34
20683000000-238256 qam35
21691000000-2.240256 qam36
22699000000-2.540256 qam37
23707000000-2.938256 qam38
24715000000-3.238256 qam39



Downstream bonded channels

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

1Locked38.614790
2Locked40.97600
3Locked40.38500
4Locked40.97840
5Locked40.311243
6Locked40.38800
7Locked40.99066
8Locked40.98160
9Locked40.38620
10Locked40.38101
11Locked40.38260
12Locked40.38010
13Locked38.99260
14Locked38.99130
15Locked40.312570
16Locked40.39040
17Locked40.38890
18Locked40.37400
19Locked38.98320
20Locked38.99860
21Locked40.39840
22Locked40.310503
23Locked38.912762
24Locked38.914130
47 REPLIES 47

jkap
Tuning in

Upstream bonded channels

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

13940010347.3512064 qam6
22580008746.5512016 qam8
34620025747.3512064 qam5
43260021947512064 qam7



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0040
2ATDMA0060
3ATDMA0020
4ATDMA00160

 

 

Network Log

Time Priority Description

19/05/2021 09:48:40criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/05/2021 07:40:38ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/05/2021 21:32:8criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/05/2021 19:10:36ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/05/2021 15:37:12criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/05/2021 07:10:35ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/05/2021 23:31:16criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/05/2021 19:10:34ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/05/2021 13:43:47criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/05/2021 07:10:33ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/05/2021 21:44:29criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/05/2021 19:10:32ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/04/2021 16:36:31criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/04/2021 10:25:21ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/04/2021 23:39:40criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/04/2021 14:55:41ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/04/2021 08:38:48criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2021 20:39:11ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/04/2021 21:20:52criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/04/2021 08:39:11ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

We had a large outage in my area yesterday (3pm - 10pm) - most of our town lost tv, phone, internet etc. Re-posting new stats from the router this morning after I gave it a lengthy power off and restart. Also still can't get that 3rd upstream channel (258) to stick to 64 qam.

Downstream bonded channels

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

14110000002.535256 qam1
2419000000235256 qam2
34270000001.736256 qam3
44350000001.535256 qam4
54430000001.735256 qam5
64510000001.935256 qam6
7459000000236256 qam7
84670000001.735256 qam8
94750000001.736256 qam9
104830000001.735256 qam10
114910000001.535256 qam11
124990000001.435256 qam12
135070000001.435256 qam13
145150000001.935256 qam14
15523000000235256 qam15
165310000001.735256 qam16
175390000001.735256 qam17
185470000001.935256 qam18
195550000001.735256 qam19
205630000001.235256 qam20
215710000000.735256 qam21
225790000000.535256 qam22
235870000000.735256 qam23
24595000000135256 qam24



Downstream bonded channels

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

1Locked35.730
2Locked35.720
3Locked36.310
4Locked35.760
5Locked35.760
6Locked35.5100
7Locked36.390
8Locked35.790
9Locked36.370
10Locked35.740
11Locked35.760
12Locked35.720
13Locked35.700
14Locked35.570
15Locked35.770
16Locked35.570
17Locked35.790
18Locked35.780
19Locked35.7110
20Locked35.7130
21Locked35.5100
22Locked35.770
23Locked35.530
24Locked35.5100

 

Upstream bonded channels

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

14620000047512064 qam5
23939996147512064 qam6
32580000046.5512016 qam8
43260006846.8512064 qam7



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

 

Zoie_P
Forum Team (Retired)
Forum Team (Retired)

Hi Jkap, 

Thanks for your post 🙂

I am sorry you are having an issue with your services.

I have located your account and can see you are affected by an outage the reference for this is F008855880 and the estimated fix time is the 28th of May 14:00

Zoie

Hi Zoie,

Thanks for the reply, appreciated. Do you have more details on what this fault is? I've been experiencing this issue for the past 5 months so just curious if this is an ongoing fault for that time period or something new? I also didn't see this appear on the service status page on my account, so just curious as to what the fault is and whether it will fix anything, and if there is any way to track the status?

Zoie_P
Forum Team (Retired)
Forum Team (Retired)

Thanks for your reply Jkap, 

It is a congestion issue and the ticket was raised in march 

Zoie

Hi Zoie,

Thanks again for the response. I wondered if the fault was now closed? We are still experiencing significant issues and today we've been cut off a few times. The stats page is also showing a large amount of errors which we didn't use to have before. I've again done all the usual resets etc.

I also noticed the cable cabinet on our street has been busted open (it was previously held together with sticky tape) - so not sure if an engineer needs to take a look at that?

Posting refreshed stats below:

Network Log

Time Priority Description

02/06/2021 13:22:52Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/06/2021 13:22:43Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/06/2021 13:22:39Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/06/2021 13:22:39criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/06/2021 13:22:38Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/06/2021 13:22:38criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/06/2021 12:43:34Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:03:17criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/06/2021 12:35:43Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/06/2021 12:35:40Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/06/2021 12:35:40criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/06/2021 12:35:40Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/06/2021 12:35:40criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/06/2021 12:35:39Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/06/2021 12:35:39criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/06/2021 12:35:38Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/06/2021 12:35:38criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/06/2021 12:35:38Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/06/2021 12:35:38criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/06/2021 12:35:36Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

Downstream bonded channels

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

1539000000-0.740256 qam17
2547000000-0.540256 qam18
3555000000-0.740256 qam19
4563000000-1.240256 qam20
5571000000-1.740256 qam21
6579000000-1.740256 qam22
7587000000-1.740256 qam23
8595000000-1.740256 qam24
9603000000-1.940256 qam25
10611000000-1.940256 qam26
11619000000-2.240256 qam27
12627000000-2.538256 qam28
13635000000-2.738256 qam29
14643000000-338256 qam30
15651000000-338256 qam31
16659000000-338256 qam32
17667000000-2.740256 qam33
18675000000-2.938256 qam34
19683000000-3.238256 qam35
20691000000-3.438256 qam36
21699000000-3.740256 qam37
22707000000-438256 qam38
23715000000-4.238256 qam39
24723000000-4.238256 qam40



Downstream bonded channels

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

1Locked40.96118882
2Locked40.311695810
3Locked40.99287526
4Locked40.39978472
5Locked40.310358610
6Locked40.39329766
7Locked40.39948051
8Locked40.310907345
9Locked40.310299786
10Locked40.311148320
11Locked40.319676126
12Locked38.937474755
13Locked38.915008637
14Locked38.616489017
15Locked38.914518045
16Locked38.9133910150
17Locked40.312058008
18Locked38.910409733
19Locked38.99898949
20Locked38.999311526
21Locked40.310177909
22Locked38.910087367
23Locked38.636645606
24Locked38.620127448

Upstream bonded channels

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

13940000048.5512064 qam6
22580000047.8512032 qam8
33260000048.3512032 qam7
44619998048.8512064 qam5



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0060
2ATDMA0000
3ATDMA0000
4ATDMA0000

Hi @jkap

 

Thanks for posting on our community forum!

 

I'm going to private message you now so I can take a look further into this. Please keep an eye on your inbox.

 

Regards

Travis_M
Forum Team

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


Well, weeks later (and months later since this became an issue)...it's still an issue. Looks like I have the dreaded "your fault will be fixed by x" constantly moved out problem. F008855880 is the reference I believe, due to be resolved 15th June but suspect it's pushed out again.

BQM last few days is hilarious and making working from home impossible:

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

 

Network Log

Time Priority Description

17/06/2021 10:34:31noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/06/2021 10:34:24Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/06/2021 02:01:26Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/06/2021 02:01:26criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/06/2021 02:01:25Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/06/2021 02:01:25criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/06/2021 02:01:24Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/06/2021 02:01:24criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/06/2021 02:01:22Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/06/2021 02:01:22criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/06/2021 02:01:20Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/06/2021 02:01:20criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/06/2021 02:01:18Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/06/2021 02:01:18criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/06/2021 20:49:53criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/06/2021 23:30:16ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/06/2021 11:43:27criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/06/2021 11:30:16ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2021 21:14:20criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/06/2021 23:30:15Error

DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

Upstream bonded channels

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

13940000047.7512016 qam6
22580000046.7512016 qam8
33260000047.3512032 qam7
44620002947.5512032 qam5



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0080
2ATDMA0000
3ATDMA0040
4ATDMA0020

 

Downstream bonded channels

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

15390000000.240256 qam17
25470000000.440256 qam18
35550000000.240256 qam19
4563000000-0.240256 qam20
5571000000-0.540256 qam21
6579000000-0.540256 qam22
7587000000-0.540256 qam23
8595000000-0.440256 qam24
9603000000-0.540256 qam25
10611000000-0.440256 qam26
11619000000-0.740256 qam27
12627000000-140256 qam28
13635000000-1.238256 qam29
14643000000-1.440256 qam30
15651000000-1.440256 qam31
16659000000-1.440256 qam32
17667000000-1.240256 qam33
18675000000-1.238256 qam34
19683000000-1.740256 qam35
20691000000-1.940256 qam36
21699000000-2.240256 qam37
22707000000-2.538256 qam38
23715000000-2.938256 qam39
24723000000-2.738256 qam40

 

 

Downstream bonded channels

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

1Locked40.9161011139
2Locked40.321417777
3Locked40.319429856
4Locked40.3225211013
5Locked40.3226211625
6Locked40.3219412893
7Locked40.9216411172
8Locked40.3225010540
9Locked40.3221113010
10Locked40.3237211814
11Locked40.333849415
12Locked40.353137969
13Locked38.9312711950
14Locked40.3346312155
15Locked40.9307711331
16Locked40.3283613563
17Locked40.3246011286
18Locked38.9241513028
19Locked40.3252112271
20Locked40.3261614728
21Locked40.9280811245
22Locked38.6303110594
23Locked38.958758605
24Locked38.9409910690

Hi jkap,

 

Thanks for coming back to us. I am sorry it's not resolved. I've done a system check today to get you more information.

 

There is a congestion issue as you know and the fault reference is F008855880. We are planning to undertake some upgrades to support the increased demand for our services in your area. When completed, any slow broadband speeds and buffering on TiVo apps you may be experiencing (particularly at peak times) will be resolved.

 

The current estimated fix date for this is the 29th June.

 

Best,

John_GS
Forum Team


Need a helpful hand to show you how to make a payment? Check out our guide - How to pay my Virgin Media bill