Forum Discussion
- jpeg1Alessandro Volta
Set up a free BQM monitor, that will plot your connection over time, and follow the instructions to post a link here.
- yumsoupTuning in
hi, ive set it up, here is the link
https://www.thinkbroadband.com/broadband/monitoring/quality/view/0c2fc160f3ac5d33bff2b85e16cdcc4f378115ff/17/04/2024
I am guessing the packet losses are where the internet is becoming unusuble, I'm not sure if the yellow spikes are normal either and this inconsistent latency could affect experience in online games too. - yumsoupTuning in
I have just tested my internet through ethernet in online games and there is a lot of glitches and rubber banding, so I'm led to beleive the spiking yellow on the graph is also an issue
- Client62Alessandro Volta
When you encounter this issues ...
https://www.samknows.com/realspeed/Once the test begins click on: Run full test to see the Latency / Packet Loss / Jitter.
- Client62Alessandro Volta
Tests in games do not show there is an issue with your VM connection.
The problem being your not just testing your VM connection, you have included hundreds or thousands on miles of network most of which does not belong to Virgin Media as well as game servers & your own network / PC / Console.
VM provided the Realspeed tests to enable the service to the VM Hub to be checked in isolation.- yumsoupTuning in
Hi,
Although I'd generally agree, further tests during these periods show it is my VM connection. Whenever I am cutting out in video calls or lagging in games, I run a test and it usually looks like this:
- jpeg1Alessandro Volta
The BQM link isn't working without your login. Try again.
- yumsoupTuning in
Sorry, here is another link that should work:
- jpeg1Alessandro Volta
That recording shows there had been some network switching at 3am, after which the trace is reasonable. Many users suffer those brief yellow spikes, often caused by something like a speed test that saturates the link for a few seconds.
If you are lucky, that network switching has removed or greatly reduced the problem.
Since you haven't posted a live link we can't see if it's still the same today.
- yumsoupTuning in
Hi, here is a live version:
https://www.thinkbroadband.com/broadband/monitoring/quality/share/fdd1f1703638ca353a06f4af682a84d658c75854
It doesn't look too bad today, however multiple times i've been cutting out and losing connection in calls just today, and using a pingtest webtool, it often looks like this.
- jpeg1Alessandro Volta
The next step is to post the downstream, upstream and log data from your Hub. Copy and paste it as text, not screenshots.
- yumsoupTuning in
Hello, sorry for the late response. I have been in the hospital.
Here are the logs, I hope these are the right ones.Network Log
Time Priority Description16/05/2024 14:57:37 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 16/05/2024 14:51:41 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 15/05/2024 23:09:11 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 15/05/2024 08:19:57 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 14/05/2024 02:45:25 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 13/05/2024 14:17:5 notice DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 13/05/2024 14:17:5 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 12/05/2024 14:17:14 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 12/05/2024 11:36:37 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 11/05/2024 09:16:20 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 11/05/2024 05:57:42 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 11/05/2024 01:11:27 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 10/05/2024 15:08:41 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 10/05/2024 14:51:46 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 10/05/2024 02:36:9 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 10/05/2024 02:17:6 notice DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 10/05/2024 02:17:6 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 09/05/2024 17:02:31 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 08/05/2024 14:40:45 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 08/05/2024 14:40:43 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
- David_BnForum Team
Thanks for coming back to us yumsoup, and hope you're on the mend 👍
I've been able to look into your router and have ran a flow.
No issues, have been detected, however it may be worth doing either a reboot on the hub, or if possible a reset on the hub as the uptime is showing as 40 days.
Thanks,
David_Bn
- ns006mTuning in
There is an issue with the hub 5 wifi.
I had the same problem, 3 engineer visits, all connections changed inside and out, a hub change and was still getting disconnects. I cured the problem by putting the router into modem only mode. Not had a disconnect since.
Related Content
- 9 months ago
- 8 months ago
- 9 months ago