on 03-01-2022 23:15
Hi
This has been happening for a while now, but ever since around Christmas time it's been absolutely awful. During the early hours 3/4am it's not bad and when I've played during the daytime it's been the same, but at nighttime/peak hours the game is unplayable. I'm talking about players moving like they are in mud, passes going everywhere, all my players are slow and unresponsive.. input delay too. My opponent does not seem to have this issue.
I'm using ethernet, not wifi, although even on wifi it's bad too. When i run a speedtest I get about 650Mbps download, 40Mbps upload and ping is 19. In game the ping is between 19 and 25.
BQM live link:
https://www.thinkbroadband.com/broadband/monitoring/quality/share/acb26ec9bfc7f1992d3b35be6efd0adb51...
Could this be because of peak times and not enough resources being given to my area? Again, during the game I monitor my ping and it's good - between 19 and 25, usually. FIFA also provide a game quality tool which allows you to monitor the server connection you had for your previous matches played. When I look at the tool it tells me all my games have perfect connection with minimal jitter and normal ping, but in game the story is completely different.
on 04-01-2022 11:54
Your BQM is atypical of over utilisation and there's not much you can do about it, apart from raise a complaint to VM.
I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more
Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks
on 07-01-2022 12:45
Hi @johanlon thanks for posting and welcome to our community.
Sorry to hear of your ongoing connection issues. I would like to take a closer look on your behalf. I am going to send you a private message.
Regards
Lee_R
on 23-02-2022 04:30
It’s the EA servers that cause these issues. You’ll find during the afternoon, early evening, it feels awful. That’s because SBC’s drop & there’s loads of players hammering the servers. Late at night, early morning it feels better because less people are playing online in our region. I have 1GB connection, wired to a PS5 & I’m using a 1ms gaming monitor. I also have the added advantage of being a network engineer for the company & tested my connection from my home to the node. Everything is perfect & in spec, no utilisation issues. EA uses peer to peer connection in every game mode apart from FUT Champs. If you connect to someone using wireless, it can cause issues with your in-game connection. I never get these issues playing Call of Duty or Battlefield, no matter what time of the day it is. You’d expect a similar issue in regards to the character online feeling unresponsive. It’s only in FIFA where this happens.
on 13-06-2022 14:46
I'm replying because this issue is still ongoing. Awful connection issues when trying to play games.
Here's my downstream:
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 227000000 | -0.7 | 40 | 256 qam | 12 |
2 | 139000000 | -0.4 | 40 | 256 qam | 1 |
3 | 147000000 | -0.5 | 40 | 256 qam | 2 |
4 | 155000000 | -0.4 | 40 | 256 qam | 3 |
5 | 163000000 | -0.7 | 40 | 256 qam | 4 |
6 | 171000000 | -0.7 | 40 | 256 qam | 5 |
7 | 179000000 | -0.5 | 40 | 256 qam | 6 |
8 | 187000000 | -0.5 | 40 | 256 qam | 7 |
9 | 195000000 | -1 | 40 | 256 qam | 8 |
10 | 203000000 | -1.2 | 40 | 256 qam | 9 |
11 | 211000000 | -0.7 | 40 | 256 qam | 10 |
12 | 219000000 | -0.7 | 36 | 256 qam | 11 |
13 | 235000000 | -0.7 | 40 | 256 qam | 13 |
14 | 243000000 | -0.9 | 40 | 256 qam | 14 |
15 | 251000000 | -1 | 40 | 256 qam | 15 |
16 | 259000000 | -1 | 40 | 256 qam | 16 |
17 | 267000000 | -1 | 40 | 256 qam | 17 |
18 | 275000000 | -1.2 | 40 | 256 qam | 18 |
19 | 283000000 | -1 | 40 | 256 qam | 19 |
20 | 291000000 | -1.2 | 40 | 256 qam | 20 |
21 | 299000000 | -1 | 40 | 256 qam | 21 |
22 | 307000000 | -1.2 | 40 | 256 qam | 22 |
23 | 315000000 | -1.2 | 40 | 256 qam | 23 |
24 | 323000000 | -1.2 | 40 | 256 qam | 24 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 40.3 | 7 | 0 |
2 | Locked | 40.9 | 18 | 0 |
3 | Locked | 40.3 | 17 | 0 |
4 | Locked | 40.9 | 10 | 0 |
5 | Locked | 40.3 | 19 | 0 |
6 | Locked | 40.3 | 15 | 0 |
7 | Locked | 40.3 | 12 | 0 |
8 | Locked | 40.3 | 13 | 0 |
9 | Locked | 40.9 | 6 | 0 |
10 | Locked | 40.9 | 10 | 0 |
11 | Locked | 40.9 | 6 | 0 |
12 | Locked | 36.3 | 6 | 0 |
13 | Locked | 40.3 | 6 | 0 |
14 | Locked | 40.3 | 6 | 0 |
15 | Locked | 40.3 | 5 | 0 |
16 | Locked | 40.3 | 0 | 0 |
17 | Locked | 40.9 | 6 | 0 |
18 | Locked | 40.9 | 6 | 0 |
19 | Locked | 40.3 | 5 | 0 |
20 | Locked | 40.9 | 8 | 0 |
21 | Locked | 40.3 | 9 | 0 |
22 | Locked | 40.9 | 7 | 0 |
23 | Locked | 40.3 | 6 | 0 |
24 | Locked | 40.3 | 5 | 0 |
Upstream:
1 | 39400004 | 48.5 | 5120 | 64 qam | 12 |
2 | 32600021 | 48.5 | 5120 | 64 qam | 13 |
3 | 46200002 | 50 | 5120 | 64 qam | 11 |
4 | 53699996 | 50.5 | 5120 | 64 qam | 10 |
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
on 13-06-2022 14:47
Network log:
Time Priority Description
13/06/2022 14:41:39 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/06/2022 12:44:25 | notice | NOTICE ATOM is restarted due to RPC timeout as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/06/2022 12:00:44 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/06/2022 08:44:16 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/06/2022 13:23:17 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt078+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/06/2022 13:23:17 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/06/2022 12:03:16 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/06/2022 01:54:49 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/06/2022 06:36:13 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/06/2022 21:49:10 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/06/2022 08:36:33 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/06/2022 07:59:49 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt078+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/06/2022 07:59:49 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/06/2022 11:18:1 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/06/2022 11:18:1 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
06/06/2022 13:12:28 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/06/2022 20:24:38 | notice | NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/06/2022 15:44:17 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/06/2022 10:20:33 | notice | NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/06/2022 10:20:7 | notice | NOTICE ATOM is restarted due to RPC timeout as part of Self Healing Mechanism;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 14-06-2022 09:55
Am I going to get a reply any time soon?
I replied to a PM someone sent me when I originally posted this topic and then I got an automated reply that I shouldn't reach out to moderators... ehhh, they reached out to me! I only replied.
Is my power levels and BQM looking okay?
on 14-06-2022 10:08
Downstream power is within spec, and the Upstream is nearing the upper limit of 51, but still in spec.
Your BQM is not great and has a few outages recorded at this time. Could be noise on the line, but the PostRS errors are clear?
Let's hope VM can do a bit more investigations around the poor BQM.
I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more
Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks
on 16-06-2022 18:30
Hello @johanlon,
I am sorry for that, but the PM was sent to you in January. Which means it was past the time frame that you are able to respond.
I will send you a new private message now, so I can investigate this further.
Many thanks,
New around here? To find out more about the Community check out our Getting Started guide