Geforce Now

[linwelin]

Currently on VM 200 service so have plenty of speed for this but not running great, i don't know if it is the GeForce servers or VM or even me, quality isn't very good and is a bit laggy, i am just wondering if anyone here has any experience with GeForce now on VM?

[Adduxi]

Setup a BQM to monitor your incoming circuit.  It maybe the BB is causing the lag.   www.thinkbroadband.com/ping

Once done, post a link to the "shared" graph and we can comment.  It will take a few hours to populate anything meaningful on the graph.

[linwelin]

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

[jpeg1]

Your BQM trace so far shows your local circuit is quite busy with other users causing contention spikes and some packet loss at one point. But it could be much worse and some users do suffer more.

You could post here your Hub logs from 192.168.0.1 to see if there are any connection issues.

Is your games device connected to the Hub by WiFi or ethernet?  Ethernet is always best for gaming. 

[linwelin]

Thanks for the reply, i only use ethernet.

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

25	331000000	10.300003	40.946209	QAM256	25
1	139000000	8.900002	40.946209	QAM256	1
2	147000000	9.099998	40.946209	QAM256	2
3	155000000	9.500000	40.946209	QAM256	3
4	163000000	9.400002	40.366287	QAM256	4
5	171000000	9.199997	40.946209	QAM256	5
6	179000000	9.099998	40.946209	QAM256	6
7	187000000	9.099998	40.946209	QAM256	7
8	195000000	9.300003	40.946209	QAM256	8
9	203000000	9.400002	40.366287	QAM256	9
10	211000000	9.500000	40.366287	QAM256	10
11	219000000	9.400002	40.946209	QAM256	11
12	227000000	9.199997	40.946209	QAM256	12
13	235000000	9.099998	40.366287	QAM256	13
14	243000000	9.199997	40.946209	QAM256	14
15	251000000	9.400002	40.946209	QAM256	15
16	259000000	9.500000	40.946209	QAM256	16
17	267000000	9.099998	40.946209	QAM256	17
18	275000000	9.199997	40.946209	QAM256	18
19	283000000	9.500000	40.946209	QAM256	19
20	291000000	9.599998	40.946209	QAM256	20
21	299000000	9.699997	40.946209	QAM256	21
22	307000000	10.000000	40.946209	QAM256	22
23	315000000	10.300003	40.946209	QAM256	23
24	323000000	10.400002	40.946209	QAM256	24
26	339000000	10.400002	40.946209	QAM256	26
27	347000000	10.599998	40.946209	QAM256	27
28	355000000	10.400002	40.366287	QAM256	28
29	363000000	10.300003	40.946209	QAM256	29
30	371000000	10.400002	40.946209	QAM256	30
31	379000000	10.400002	40.946209	QAM256	31

3.0 Downstream channels

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

25	Locked	40.946209	0	0
1	Locked	40.946209	0	0
2	Locked	40.946209	0	0
3	Locked	40.946209	0	0
4	Locked	40.366287	0	0
5	Locked	40.946209	0	0
6	Locked	40.946209	0	0
7	Locked	40.946209	0	0
8	Locked	40.946209	0	0
9	Locked	40.366287	0	0
10	Locked	40.366287	0	0
11	Locked	40.946209	0	0
12	Locked	40.946209	0	0
13	Locked	40.366287	0	0
14	Locked	40.946209	0	0
15	Locked	40.946209	0	0
16	Locked	40.946209	0	0
17	Locked	40.946209	0	0
18	Locked	40.946209	0	0
19	Locked	40.946209	0	0
20	Locked	40.946209	0	0
21	Locked	40.946209	0	0
22	Locked	40.946209	0	0
23	Locked	40.946209	0	0
24	Locked	40.946209	0	0
26	Locked	40.946209	0	0
27	Locked	40.946209	0	0
28	Locked	40.366287	0	0
29	Locked	40.946209	0	0
30	Locked	40.946209	0	0
31	Locked	40.946209	0	0

[linwelin]

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

1	32600000	46.020599	5120 KSym/sec	64QAM	5
2	39400000	46.770599	5120 KSym/sec	64QAM	4
3	46200000	46.770599	5120 KSym/sec	64QAM	3
4	25800000	45.770599	5120 KSym/sec	64QAM	6

3.0 Upstream channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	US_TYPE_STDMA	0	0	1	0
2	US_TYPE_STDMA	0	0	0	0
3	US_TYPE_STDMA	0	0	0	0
4	US_TYPE_STDMA	0	0	0	0

[linwelin]

TimePriorityDescriptionFri Oct 8 02:42:05 20216CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; 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;Fri Oct 8 07:57:28 20215Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 07:57:31 20216CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; 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;Fri Oct 8 11:43:28 20215Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 11:43:44 20216CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; 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;Fri Oct 8 12:40:32 20215Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 12:40:33 20216CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; 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;Fri Oct 8 12:50:22 20215Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 12:50:44 20216CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; 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;Fri Oct 8 12:54:30 20215Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 12:54:34 20216CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; 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;Fri Oct 8 13:17:52 20215Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 13:17:58 20216CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; 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;Fri Oct 8 15:05:03 20215Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 15:05:04 20216CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; 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;Fri Oct 8 15:05:31 20215Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 15:05:53 20216CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; 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;Fri Oct 8 15:06:13 20215Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 15:06:44 20216CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; 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;Fri Oct 8 15:06:55 20215Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 8 15:07:18 20216CM-STATUS message sent. Event Type Code: 4; Chan ID: 5; 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;Fri Oct 8 19:35:12 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat Oct 9 01:42:50 20215Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat Oct 9 01:43:06 20216CM-STATUS message sent. Event Type Code: 5; 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;Tue Oct 12 07:35:12 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue Oct 12 08:15:25 20216CM-STATUS message sent. Event Type Code: 5; 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 Oct 14 16:43:21 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Oct 15 13:32:56 20216CM-STATUS message sent. Event Type Code: 5; 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;Fri Oct 15 19:35:12 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Thu Jan 1 00:01:18 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat Oct 16 20:27:35 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Mon Oct 18 07:42:16 20216CM-STATUS message sent. Event Type Code: 5; Chan ID: 2; 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 Jan 1 00:01:21 19703No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Mon Oct 18 13:09:49 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Wed Oct 20 16:22:25 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat Oct 23 17:26:11 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Wed Oct 27 00:28:51 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Fri Nov 5 02:39:57 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat Nov 6 12:28:51 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Thu Nov 11 03:35:11 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sat Nov 13 12:28:52 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Sun Nov 14 22:35:42 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue Nov 16 13:09:58 20215MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Thu Nov 18 12:49:22 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Tue Nov 23 06:50:35 20213No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;Wed Nov 24 19:09:12 20214DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

[Andrew-G]

Having a Hub 4 on a 200 Mbps connection says that you're on a congested section of network, but the BQM looks like a different type of fault - ordinarily a pure congestion fault has a BQM that magically improves at 12:30am, and remains near perfect until 8-9am.  The small hours of your connection looks as poor as mid afternoon, and there's some suspiciously sustained (almost rectangular) latency bars showing, that's again not typical of a congestion fault.

I do note your downstream power levels are all pretty high.  Hold on for the forum staff to take a look and advise, they may be able to identify a known fault or get a technician booked for you.  If you get a "all looks normal to us" response, or they declare there's an over-utilisation fault with a fix date of next week, then it may be time to consider your options with other ISPs.

[linwelin]

Thank you for the help, i shall wait for staff to respond then and see what they say, thanks again.

[jpeg1]

Yes it's looking very odd this morning. The minimum latency is higher than average too. It's just possible the Hub has a fault, if nothing else can be done it might be worth arguing for a replacement.  Good luck!