Menu
Reply
Highlighted
  • 31
  • 0
  • 0
Tuning in
208 Views
Message 2 of 5
Flag for a moderator

Latency issues on Gig1

I've upgraded to Gig1, however, the BQM is spikier than before. I run in modem mode so thought it was something to do with that. 

Put the hub back into router mode and, to eliminate any of my devices doing anything, switched over to the secondary VDSL line I have coming into the house. Interestingly, there is some sort of latency spike every hour...

The above shows it (I switched it over at 12am). The minimum latency is fine, the yellow spikes are concerning. This was noticeable when on video calls as I'd randomly have a delay. 

Given there is literally (and I mean literally) no traffic going through the hub, why would spikes be happening every hour in this way? 

foolishlywise_0-1605260535473.png

Modem stats below:

Cable Modem StatusItem Status CommentsChannel Overview Downstream Upstream

Cable Modem Status
Online
DOCSIS 3.1
Primary downstream channel
Locked
SC-QAM
DOCSIS 3.0 channels
31
4
DOCSIS 3.1 channels
1
0

 

3.0 Downstream channels

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

304027500006.09999838.983261QAM25630
11387500006.09999838.605377QAM2561
21467500005.30000338.983261QAM2562
31547500005.09999837.636276QAM2563
41627500005.19999737.636276QAM2564
51707500005.30000338.605377QAM2565
61787500005.30000338.983261QAM2566
71867500005.09999838.605377QAM2567
81947500005.09999838.983261QAM2568
92027500005.19999738.605377QAM2569
102107500005.19999738.605377QAM25610
112187500005.30000338.983261QAM25611
122267500005.40000238.605377QAM25612
132347500005.30000338.605377QAM25613
142427500005.19999738.605377QAM25614
152507500005.30000338.605377QAM25615
162587500005.30000338.605377QAM25616
172667500004.90000237.636276QAM25617
182747500005.09999838.605377QAM25618
192827500005.50000038.605377QAM25619
202907500005.40000238.605377QAM25620
212987500005.69999737.636276QAM25621
223067500005.59999837.636276QAM25622
233147500005.30000338.605377QAM25623
243227500005.09999837.636276QAM25624
253307500005.40000237.636276QAM25625
263707500006.19999738.983261QAM25626
273787500006.00000038.605377QAM25627
283867500005.69999738.983261QAM25628
293947500005.69999738.605377QAM25629
314107500005.90000238.983261QAM25631

 

0 Kudos
Reply
Highlighted
  • 31
  • 0
  • 0
Tuning in
173 Views
Message 1 of 5
Flag for a moderator

Gig1/hub 4 latency spikes every hour

I'm one of the first ones to get Gig1 in the area (literally ordered as soon as I saw it was available in London). Speed is fast but latency has become. Back on 350Mb, latency was smooth, no spikes or anything. Now on Gig1, the BQM is spikier than ever before. I run in modem mode so thought it was something to do with that. 

Put the hub back into router mode and, to eliminate any of my devices doing anything, switched over to the secondary VDSL line I have coming into the house. Interestingly, there is some sort of latency spike every hour on my connection! 

The above shows it (I switched it over at 12am). The minimum is fine, the yellow spikes are concerning. This was noticeable when on video calls as I'd randomly drop out/have a delay. Can't remember the frequency though. 

Given there is literally (and I mean literally) no traffic going through the hub (the VM public network thing is also disabled), why would spikes be happening every hour in this way? 

My Broadband Ping - VM Temporary

Modem stats below:

Cable Modem StatusItem Status CommentsChannel Overview Downstream Upstream

Cable Modem Status
Online
DOCSIS 3.1
Primary downstream channel
Locked
SC-QAM
DOCSIS 3.0 channels
31
4
DOCSIS 3.1 channels
1
0

 

3.0 Downstream channels

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

304027500006.09999838.983261QAM25630
11387500006.09999838.605377QAM2561
21467500005.30000338.983261QAM2562
31547500005.09999837.636276QAM2563
41627500005.19999737.636276QAM2564
51707500005.30000338.605377QAM2565
61787500005.30000338.983261QAM2566
71867500005.09999838.605377QAM2567
81947500005.09999838.983261QAM2568
92027500005.19999738.605377QAM2569
102107500005.19999738.605377QAM25610
112187500005.30000338.983261QAM25611
122267500005.40000238.605377QAM25612
132347500005.30000338.605377QAM25613
142427500005.19999738.605377QAM25614
152507500005.30000338.605377QAM25615
162587500005.30000338.605377QAM25616
172667500004.90000237.636276QAM25617
182747500005.09999838.605377QAM25618
192827500005.50000038.605377QAM25619
202907500005.40000238.605377QAM25620
212987500005.69999737.636276QAM25621
223067500005.59999837.636276QAM25622
233147500005.30000338.605377QAM25623
243227500005.09999837.636276QAM25624
253307500005.40000237.636276QAM25625
263707500006.19999738.983261QAM25626
273787500006.00000038.605377QAM25627
283867500005.69999738.983261QAM25628
293947500005.69999738.605377QAM25629
314107500005.90000238.983261QAM25631

 

0 Kudos
Reply
Highlighted
  • 31
  • 0
  • 0
Tuning in
202 Views
Message 3 of 5
Flag for a moderator

Re: Latency issues on Gig1

BQM image is in moderation queue but here's the link: https://www.thinkbroadband.com/broadband/monitoring/quality/share/3e54879537536b88052fdafd7028f52ee0...

More stats:

3.0 Downstream channels

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

30Locked000
1Locked28924549400
2Locked29199481500
3Locked31048344900
4Locked102643554400
5Locked104793411000
6Locked43374085200
7Locked112734827600
8Locked38534211700
9Locked48798976100
10Locked49060734400
11Locked44229814500
12Locked46386236600
13Locked44471351400
14Locked44561110700
15Locked40032055100
16Locked9289036900
17Locked11949031700
18Locked12306195000
19Locked13307057200
20Locked14690745800
21Locked16892143200
22Locked15020099000
23Locked21756643600
24Locked32100173500
25Locked39552803800
26Locked39988442600
27Locked50464810200
28Locked49985810900
29Locked47805785300
31Locked122449404300



3.1 Downstream channelsChannel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
33864K1680QAM4096424


3.1 Downstream channelsChannel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
33Locked 5.52977793

0

 

3.0 Upstream channelsChannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
12580000045.7705995120 KSym/sec64QAM4
23940000046.0205995120 KSym/sec64QAM2
34620000046.0205995120 KSym/sec64QAM1
43260000046.0205995120 KSym/sec64QAM3



3.0 Upstream channelsChannel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1US_TYPE_STDMA0020
2US_TYPE_STDMA0020
3US_TYPE_STDMA0020
4US_TYPE_STDMA0020

 

General Configuration
Network access
true
Maximum Number of CPEs
1
Baseline Privacy
true
DOCSIS Mode
3.1
Config file
cmreg-vmdg640-bbt076+voc-b.cm



Primary Downstream Service Flow
SFID
56722
Max Traffic Rate
1200000450
Max Traffic Burst
42600
Min Traffic Rate
0



Primary Upstream Service Flow
SFID
56721
Max Traffic Rate
55000270
Max Traffic Burst
42600
Min Traffic Rate
0
Max Concatenated Burst
42600
Scheduling Type
bestEffort
0 Kudos
Reply
Highlighted
  • 31
  • 0
  • 0
Tuning in
201 Views
Message 4 of 5
Flag for a moderator

Re: Latency issues on Gig1

And the log: 

Network Log

Time

Priority

Description

Thu 01/01/1970 00:01:24

3

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Thu 01/01/1970 00:01:49

5

ToD request sent - No Response received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Wed 11/11/2020 16:54:42

5

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Thu 01/01/1970 00:01:22

3

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Wed 11/11/2020 18:36:08

5

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Thu 01/01/1970 00:01:18

3

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Wed 11/11/2020 23:00:13

5

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Thu 12/11/2020 07:46:11

3

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Thu 12/11/2020 07:46:12

6

CM-STATUS message sent. Event Type Code: 21; Chan ID: 33; 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 12/11/2020 07:46:14

3

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Thu 12/11/2020 07:46:15

5

Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Thu 12/11/2020 07:46:19

6

CM-STATUS message sent. Event Type Code: 4; 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 12/11/2020 19:56:08

5

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Thu 12/11/2020 19:56:19

5

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Thu 12/11/2020 19:56:48

6

CM-STATUS message sent. Event Type Code: 5; Chan ID: 33; 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 12/11/2020 22:27:23

5

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Thu 12/11/2020 22:27:34

5

RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Thu 12/11/2020 22:27:39

6

CM-STATUS message sent. Event Type Code: 4; Chan ID: 33; 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 01/01/1970 00:01:17

3

No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

Fri 13/11/2020 00:07:10

5

MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

 

0 Kudos
Reply
Highlighted
  • 3.97K
  • 237
  • 465
Forum Team
Forum Team
51 Views
Message 5 of 5
Flag for a moderator

Re: Gig1/hub 4 latency spikes every hour

HI there @foolishlywise

 

Welcome back to our Community - we have merged your two posts as they are the same query. 

 

Sorry that you seem to be having some issues with your broadband since getting the Hub4. I have located your account from here and can see that it's been over a week since you last rebooted - possibly around the time if of your thread post. 

 

We have no known area issues listed and no errors showing this end either. Your signal levels are looking to be spot on for what we'd expect for your package and equipment. We can still see that you're in modem mode. How long did you test in Router mode?

 

You still having issues since your post last week? 

Katie - Forum Team


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


0 Kudos
Reply