Menu
Reply
  • 26
  • 1
  • 0
Okkio
On our wavelength
884 Views
Message 1 of 10
Flag for a moderator

Received the .608 update a few days ago, why is my graph still so bad?

image.png
Pinging the router is miles better, puma 6 test looks a bit better too:
image.png


Im in area 21, could it just be my area?

0 Kudos
Reply
  • 504
  • 26
  • 105
tonycv51
Rising star
856 Views
Message 2 of 10
Flag for a moderator

Re: Received the .608 update a few days ago, why is my graph still so bad?

Suggest post your power levels and stats. There are red flecks at the top of your BQM showing packet loss so would guess something wrong with your connection or  power levels 

0 Kudos
Reply
  • 431
  • 18
  • 49
SonarUK
Fibre optic
844 Views
Message 3 of 10
Flag for a moderator

Re: Received the .608 update a few days ago, why is my graph still so bad?

Are you sure that's the .608 firmware?

https://twitter.com/SeriousFamily

Vivid 350 | Hub 3 modem mode | Asus RT-AC86U (Stock-Firmware)
0 Kudos
Reply
  • 26
  • 1
  • 0
Okkio
On our wavelength
814 Views
Message 4 of 10
Flag for a moderator

Re: Received the .608 update a few days ago, why is my graph still so bad?

Downstream bonded channels

1298750000-0.738256 qam21
2426750000-0.438256 qam28
3418750000-0.540256 qam27
4410750000-0.238256 qam26
5402750000-0.538256 qam25
6322750000-0.538256 qam24
7314750000-0.438256 qam23
8306750000-0.538256 qam22
9290750000-0.738256 qam20
10282750000-0.740256 qam19
11274750000-0.538256 qam18
12266750000-0.440256 qam17
13258750000-0.440256 qam16
14250750000-0.440256 qam15
15242750000-0.238256 qam14
16234750000038256 qam13
172267500000.238256 qam12
182187500000.440256 qam11
192107500000.238256 qam10
202027500000.540256 qam9
211947500000.540256 qam8
221867500000.740256 qam7
231787500000.740256 qam6
241707500000.738256 qam5



Downstream bonded channels

1Locked38.6290
2Locked38.9590
3Locked40.314040
4Locked38.62460
5Locked38.9920
6Locked38.9640
7Locked38.9440
8Locked38.93950
9Locked38.9310
10Locked40.3200
11Locked38.6200
12Locked40.3150
13Locked40.9130
14Locked40.3160
15Locked38.9150
16Locked38.9200
17Locked38.9320
18Locked40.3180
19Locked38.9130
20Locked40.3300
21Locked40.3270
22Locked40.3190
23Locked40.3260
24Locked38.9240

Upstream bonded channels

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

13940000043.8512064 qam56
23260000043.5512064 qam57
32580000043.5512064 qam58
44620000043.8512064 qam55



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA00930
2ATDMA00410
3ATDMA00440
4ATDMA00670
0 Kudos
Reply
Highlighted
  • 26
  • 1
  • 0
Okkio
On our wavelength
813 Views
Message 5 of 10
Flag for a moderator

Re: Received the .608 update a few days ago, why is my graph still so bad?

Yep
image.png

0 Kudos
Reply
  • 504
  • 26
  • 105
tonycv51
Rising star
786 Views
Message 6 of 10
Flag for a moderator

Re: Received the .608 update a few days ago, why is my graph still so bad?

Suggest check your router logs for any frequent errors. 

Doesnt seem to be anything wrong with power levels - you may have to wait for VM staff to review which can take up to a week. 

Does the connection feel poor eg any buffering or low resolution when streaming, slow browsing / timeouts, lag in gaming etc ?

0 Kudos
Reply
  • 504
  • 26
  • 105
tonycv51
Rising star
784 Views
Message 7 of 10
Flag for a moderator

Re: Received the .608 update a few days ago, why is my graph still so bad?

Sorry also try resetting your stats and check error counts over an hour / day

0 Kudos
Reply
  • 26
  • 1
  • 0
Okkio
On our wavelength
761 Views
Message 8 of 10
Flag for a moderator

Re: Received the .608 update a few days ago, why is my graph still so bad?

 

2018-11-29 17:08:17.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-29 17:55:49.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-29 18:19:05.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-29 21:52:04.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-30 00:32:01.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-30 00:49:15.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-30 00:55:06.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-30 01:18:47.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-30 01:21:46.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-30 01:33:33.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-30 01:48:22.00ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-30 02:08:55.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-30 02:29:35.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-30 02:30:07.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-30 02:35:12.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-30 02:40:52.00ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-30 03:19:18.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-30 03:47:47.00ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-30 04:06:06.00ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-11-30 15:29:19.00criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
  • 3.68K
  • 52
  • 832
CarlTSpeak
Wise owl
755 Views
Message 9 of 10
Flag for a moderator

Re: Received the .608 update a few days ago, why is my graph still so bad?

T3 timeouts. Upstream problem. Needs a service tech to eliminate the Hub and wiring between cabinet and home and if no issues found a network technician to work on it from there.

Get a hold of VM via live chat or the phone. 

  • 11.7K
  • 347
  • 678
Forum Team (Retired) Samantha_L
Forum Team (Retired)
672 Views
Message 10 of 10
Flag for a moderator

Re: Received the .608 update a few days ago, why is my graph still so bad?

Hi Okkio,

 

Thanks for posting on the community and apologies you are having an issue with the broadband connection.

 

I can see there have been high time-outs reported when I check your line. For this I can arrange an engineer appointment to check this over for you.

 

We can do this via online chat.

 

Speak soon
Sam


New around here? To find out more about the Community check out our Getting Started guide


0 Kudos
Reply