Menu
Reply
  • 3
  • 0
  • 0
sacredshapes
Joining in
204 Views
Message 1 of 4
Flag for a moderator

Slow speeds at peak times

My connection over the past few months has been generally unusable after 6/7pm and at weekends (both wired and wireless generally have the same performance). I'm struggling to use things like Netflix and browse the Internet simultaneously, which I didn't think would be much of an issue with VIVID 350 Optical Fibre. Speedtest.net shows speeds of 10mb or below at these times.

I am running in Modem mode with a Netgear R8000 Nighthawk X6 AC3200, which broadcasts both 2.4 and 5ghz. As mentioned earlier, wireless performance is about the same as wired - poor.

My area is 01. I've had this connection for a bit over a year now, so I'm out of contract and tempted to switch given the poor service and forthcoming price rise, however I thought it may be worth troubleshooting first before making any major decisions. It was fine for the first few months.

 

0 Kudos
Reply
  • 3
  • 0
  • 0
sacredshapes
Joining in
203 Views
Message 2 of 4
Flag for a moderator

Re: Slow speeds at peak times

Downstream bonded channels

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

12990000008.938256 qam21
2323000000838256 qam24
33150000008.538256 qam23
43070000008.638256 qam22
52910000008.938256 qam20
62830000008.838256 qam19
72750000008.838256 qam18
82670000008.938256 qam17
92590000008.838256 qam16
10251000000938256 qam15
11243000000938256 qam14
12235000000938256 qam13
132270000009.138256 qam12
142190000009.138256 qam11
152110000009.438256 qam10
162030000009.838256 qam9
171950000001038256 qam8
1818700000010.438256 qam7
1917900000010.338256 qam6
2017100000010.538256 qam5
2116300000010.638256 qam4
2215500000010.938256 qam3
2314700000011.138256 qam2
2413900000011.438256 qam1



Downstream bonded channels

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

1Locked38.6650
2Locked38.6680
3Locked38.9530
4Locked38.6450
5Locked38.6340
6Locked38.6490
7Locked38.6430
8Locked38.6390
9Locked38.9350
10Locked38.9610
11Locked38.9420
12Locked38.9450
13Locked38.6350
14Locked38.6460
15Locked38.6330
16Locked38.6400
17Locked38.6350
18Locked38.6280
19Locked38.6440
20Locked38.61381581
21Locked38.9480
22Locked38.6530
23Locked38.6620
24Locked38.6520

 

Upstream bonded channels

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

12580000043.5512064 qam4
23260000044512064 qam3
33940000043.5512064 qam2
44620000043.5512064 qam1

 

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0010
3ATDMA0020
4ATDMA0000



0 Kudos
Reply
  • 3
  • 0
  • 0
sacredshapes
Joining in
202 Views
Message 3 of 4
Flag for a moderator

Re: Slow speeds at peak times

Network Log

Time Priority Description

2018-09-06 13:34:40.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-09-06 17:05:29.00Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-09-07 00:33:12.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-09-07 16:18:14.00ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-09-07 16:18:14.00noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsxxl35016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-09-07 16:46:57.00Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-09-10 11:31:49.00criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-09-10 11:31:49.00Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-09-10 11:31:49.00criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-09-10 11:31:51.00Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-09-10 16:29:28.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-09-11 04:31:44.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-09-11 07:15:23.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-09-11 12:10:45.00ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-09-11 12:10:45.00noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsxxl35016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-09-11 19:27:58.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-09-16 02:15:52.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-09-17 08:17:20.00ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-09-17 08:17:20.00noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-rtsxxl35016u-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-09-17 17:55:41.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
  • 995
  • 27
  • 298
Moderator
Moderator
137 Views
Message 4 of 4
Flag for a moderator

Re: Slow speeds at peak times

@sacredshapes

Sorry to hear of the peak time slow speed problems, I've run a few check on your connection and can see that we have an open fault, Ref F005839783 with respect to this issue.

Upgrade work to add capacity is planned to resolve this, with the current estimate for completion currently early December.

Apologies again.

 

0 Kudos
Reply