cancel
Showing results for 
Search instead for 
Did you mean: 

Daily latency issues

c11umw
On our wavelength

Hi
I game most evenings and I noticed in the last week that I was losing packets and my in-game ping would go nuts.

First noticed 10 days ago when I was streaming and my OBS was having real issues dropping 25% of the frames and struggling to get more than 1.5Mb upload (I should have 50Mb up)

I reset my switch, reseated all my ethernet cables and rebooted my hub.
Back to normal 🙂

Next evening, the same happened.
Every day since it's been the same. Fine until the evening when I'm about to game and I do a ping test to cloudflare to make sure everything's stable. I see ping spikes and when I do a speed test it creeps up to my download and the upload starts about 12mb and drops from there.

Tried the VM "helper", but it just says to reset everything and when I say it doesn't help it says to try again tomorrow (it does work, but only for 24hrs).

Last thing I tried was a factory reset of the hub yesterday and re-seated the VM cable.
Today, same latency/ping issues, so I'm 100% sure the hub that needs replaced as a reboot of that fixes it every time. Albeit temporary

Speedtests while it's having issues:
https://www.speedtest.net/result/13851401847
https://www.speedtest.net/result/13851407322

Example ping:
Reply from 1.1.1.1: bytes=32 time=105ms TTL=57
Reply from 1.1.1.1: bytes=32 time=107ms TTL=57
Reply from 1.1.1.1: bytes=32 time=86ms TTL=57
Reply from 1.1.1.1: bytes=32 time=83ms TTL=57
Reply from 1.1.1.1: bytes=32 time=74ms TTL=57
Reply from 1.1.1.1: bytes=32 time=91ms TTL=57
Reply from 1.1.1.1: bytes=32 time=10ms TTL=57
Reply from 1.1.1.1: bytes=32 time=7ms TTL=57
Reply from 1.1.1.1: bytes=32 time=10ms TTL=57
Reply from 1.1.1.1: bytes=32 time=28ms TTL=57
Reply from 1.1.1.1: bytes=32 time=48ms TTL=57
Reply from 1.1.1.1: bytes=32 time=17ms TTL=57
Reply from 1.1.1.1: bytes=32 time=37ms TTL=57
Reply from 1.1.1.1: bytes=32 time=9ms TTL=57
Reply from 1.1.1.1: bytes=32 time=9ms TTL=57
Reply from 1.1.1.1: bytes=32 time=8ms TTL=57
Reply from 1.1.1.1: bytes=32 time=15ms TTL=57
Reply from 1.1.1.1: bytes=32 time=10ms TTL=57
Reply from 1.1.1.1: bytes=32 time=16ms TTL=57
Reply from 1.1.1.1: bytes=32 time=17ms TTL=57
Reply from 1.1.1.1: bytes=32 time=39ms TTL=57
Reply from 1.1.1.1: bytes=32 time=9ms TTL=57
Reply from 1.1.1.1: bytes=32 time=30ms TTL=57
Reply from 1.1.1.1: bytes=32 time=12ms TTL=57
Reply from 1.1.1.1: bytes=32 time=17ms TTL=57
Reply from 1.1.1.1: bytes=32 time=10ms TTL=57
Reply from 1.1.1.1: bytes=32 time=9ms TTL=57
Reply from 1.1.1.1: bytes=32 time=17ms TTL=57

Speedtest after reboot:
https://www.speedtest.net/result/13851441588

Example ping after a hub reboot:
Reply from 1.1.1.1: bytes=32 time=13ms TTL=57
Reply from 1.1.1.1: bytes=32 time=10ms TTL=57
Reply from 1.1.1.1: bytes=32 time=9ms TTL=57
Reply from 1.1.1.1: bytes=32 time=8ms TTL=57
Reply from 1.1.1.1: bytes=32 time=8ms TTL=57
Reply from 1.1.1.1: bytes=32 time=10ms TTL=57
Reply from 1.1.1.1: bytes=32 time=11ms TTL=57
Reply from 1.1.1.1: bytes=32 time=9ms TTL=57
Reply from 1.1.1.1: bytes=32 time=8ms TTL=57
Reply from 1.1.1.1: bytes=32 time=9ms TTL=57
Reply from 1.1.1.1: bytes=32 time=10ms TTL=57
Reply from 1.1.1.1: bytes=32 time=9ms TTL=57
Reply from 1.1.1.1: bytes=32 time=8ms TTL=57
Reply from 1.1.1.1: bytes=32 time=8ms TTL=57
Reply from 1.1.1.1: bytes=32 time=8ms TTL=57

 

24 REPLIES 24

c11umw
On our wavelength
Forgot to mention - the VM hub diagnostics says everything if fine.
After the first day I only reset the hub and that resolves the issue.

I just need a new hub sent to me and I'll swap them over, but I can't see how to request one from the main VM site

c11umw
On our wavelength
Raised a complaint through the main VM site as there doesn't seem to be any option for just regular customer service 😞

jbrennand
Very Insightful Person
Very Insightful Person
May not be a Hub issue - but a connectivity one

Can you check first for any “known network faults - try in 2 places

1) Try the “check service,”Area status webpage" (link at top right of this forum)

2) Then also try the “free & automated” Service Status number - 0800 561 0061 - which usually gives the most up to date info. and tells you of more local issues down to street cab/ postcode level.

Also,,,,

If you haven’t already, set up a free, secure and “offlsite” - “Broadband Quality Monitor” to continually monitor the state of your connection and record any true network dropouts , latency issues, packet drops, etc - it will thus allow you to differentiate between those and simple wifi dropouts. It does it 24/7/365 and it keeps a visual record of any/all of your network disconnections, useful data to have to match to the Network logs (in your Hub settings) and also in discussions with VM - note it will take a few hours to start seeing a sensible picture - post up the “link” to the “share live graph”. Click the lower link (Share Live Graph) then, click generate. Copy the text in the Direct Link box, beware, there may be more text than you can see. On here click the Link icon (2 links chain to the left of the camera icon) In the URL box paste the link you copied and then click OK

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

--------------------
John
--------------------

I do not work for VM. My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired, 2 on WiFi) Hub5 in modem mode with Apple Airport Extreme Router +2 Airport Express's. On Volt 350Mbps, Talk Anytime Phone, x2 Mobile SIM only iPhones.

c11umw
On our wavelength

Thanks for the reply.

If it was a connectivity issue then I wouldn't expect a reboot of the hub to fix it every time.

WiFi isn't an problem as I hard-wire everything

c11umw
On our wavelength
We can’t see any issues affecting "my postcode"
Checked at 22:10 today

jbrennand
Very Insightful Person
Very Insightful Person

@c11umw wrote:

Thanks for the reply.

If it was a connectivity issue then I wouldn't expect a reboot of the hub to fix it every time.

 


Lose connectivity and reboot goes through the remake connection procedure and can connect - no?

Lets look at the Hub stats and connection data.  can you do this....

First post up the link to "share live BQM" so we can see how good/bad the larency actually is.

Then, In your browser’s URL box type in... http://192.168.0.1 (or http://192.168.100.1 - if in modem mode) (DONT click these links) - and hit return.


If you have a Hub4 or 5 then login on the first page up. If you have an SH2 or Hub3 - dont log in -  just click on the “router status” icon/text at bottom-middle (Hub3) or top/right (SH’s) of the Login page.


Then Navigate to these “data pages” and just copy/paste the normal “Formatted Text” (not images) 3 FULL sets of data onto here – 2 tables from the Downstream, 2 from the Upstream, & the Network Logs page. Don't worry too much about the formatting it can be easily read & DON’T include personal data or MAC addresses - blank them out - if you copy/paste the data, the board software will do this for you (you may need to click the "submit" button again). If character limits are “exceeded” - just do two posts


--------------------
John
--------------------

I do not work for VM. My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired, 2 on WiFi) Hub5 in modem mode with Apple Airport Extreme Router +2 Airport Express's. On Volt 350Mbps, Talk Anytime Phone, x2 Mobile SIM only iPhones.

c11umw
On our wavelength

Hi
Yea, I did think after that that it could be struggling to cope with poor latency and if not coded right get itself into a downward spiral.
Although it's been perfectly happy for the last 18 month or so (until 2 weeks ago) so I discounted it as unlikely.

Here's the live chart as requested
As you can see - chaos ensued

https://www.thinkbroadband.com/broadband/monitoring/quality/share/9260d89856fc6d92934c58ac6b037c8ef7...

Here's a corresponding Ookla Speedtest (it download crept up from 20mb to 930):
https://www.speedtest.net/result/13897463726

 

c11umw
On our wavelength

Hub pages

3.0 Downstream channels

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

2533100000022.19999740.366287QAM25625
617900000023.80000340.366287QAM2566
718700000023.80000340.366287QAM2567
819500000023.59999840.366287QAM2568
920300000023.50000040.366287QAM2569
1021100000023.40000240.946209QAM25610
1121900000023.59999840.946209QAM25611
1222700000023.50000040.946209QAM25612
1323500000023.59999840.366287QAM25613
1424300000023.80000340.946209QAM25614
1525100000023.90000240.946209QAM25615
1625900000024.19999740.946209QAM25616
1726700000023.90000240.946209QAM25617
1827500000023.40000240.366287QAM25618
1928300000022.80000340.946209QAM25619
2029100000022.80000340.366287QAM25620
2129900000023.00000040.946209QAM25621
2230700000022.90000240.366287QAM25622
2331500000022.80000340.366287QAM25623
2432300000022.59999840.366287QAM25624
2633900000022.40000240.366287QAM25626
2734700000022.69999740.366287QAM25627
2835500000022.80000340.946209QAM25628
2936300000022.69999740.366287QAM25629
3037100000022.69999740.366287QAM25630
3137900000023.00000040.946209QAM25631
3238700000022.80000340.366287QAM25632
3349100000021.40000240.366287QAM25633
3449900000021.40000240.366287QAM25634
3550700000020.59999840.366287QAM25635
3651500000020.40000240.366287QAM25636



3.0 Downstream channels

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

25Locked40.36628770
6Locked40.36628700
7Locked40.36628700
8Locked40.36628700
9Locked40.36628710
10Locked40.94620920
11Locked40.94620920
12Locked40.94620920
13Locked40.36628710
14Locked40.94620900
15Locked40.94620910
16Locked40.94620920
17Locked40.94620950
18Locked40.36628710
19Locked40.94620920
20Locked40.36628750
21Locked40.94620940
22Locked40.36628760
23Locked40.36628730
24Locked40.36628770
26Locked40.366287110
27Locked40.36628770
28Locked40.94620970
29Locked40.36628770
30Locked40.36628790
31Locked40.946209130
32Locked40.366287120
33Locked40.36628790
34Locked40.366287160
35Locked40.366287200
36Locked40.366287160
 

c11umw
On our wavelength



3.1 Downstream channels

Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
37964K1880QAM4096392


3.1 Downstream channels

Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
37Locked4321.65456316240

 

3.0 Upstream channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
14310000038.0205995120 KSym/sec32QAM2
23010000037.7705995120 KSym/sec32QAM4
33660000038.0205995120 KSym/sec32QAM3
42360000037.2705995120 KSym/sec16QAM5
54960000038.5205995120 KSym/sec64QAM1



3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1US_TYPE_STDMA0000
2US_TYPE_STDMA0000
3US_TYPE_STDMA0000
4US_TYPE_STDMA0070
5US_TYPE_STDMA0000



3.1 Upstream channels

Channel Channel Width (MHz) Power (dBmV) FFT Type Modulation
610.834.02KQAM8


3.1 Upstream channels

Channel Channel Type Number of Active Subcarriers First Active Subcarrier (Hz) T3 Timeouts T4 Timeouts
6OFDMA22053.470

 

Network Log

Time Priority Description
Thu Jan 1 00:01:26 19703Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:27 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:38 19704Missing Mandatory MDD TLV on primary DS Channel;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Nov 1 11:45:40 20225MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Nov 1 11:52:01 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Tue Nov 1 12:23:06 20225MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Nov 2 11:54:39 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:24 19703Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Thu Jan 1 00:01:24 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Nov 2 19:34:55 20225MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Wed Nov 2 19:57:47 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 4 13:00:13 20224DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
Fri Nov 4 13:14:55 20223No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;