on 17-10-2021 22:55
Beginning from the last 2 weeks, when gaming I get booted regularly for ping timeout related issues. The symptom is random high packet loss then shortly after, a full loss of internet followed by high ping spikes and then a return to <20 ping. This has led me to just not want to play due to the damage caused and time wasted for others from me resetting/re-joining the games.
To reply to a few quickfire support questions here are my answers:
I am using wired connection only.
I have checked all cables inside the building and the box on my outside wall-All ok.
I have reset my router using pinhole method to no avail.
I have two pcs reporting the same issue so it isn't my connected hardware.
The disconnect happens at random times and in lots of different games so it isn't down to a specific game, just games in general.
I have been auto-pinging google for the past 4 days constantly and It seems to develop the disconnect when in online games where low ping is required to maintain a connection to the servers.
HOWEVER it does disconnect at strange times like 3AM when nobody is using the internet so It's not solely down to games I suppose.
on 17-10-2021 22:57
Router status page: (reset all statistics on thursday 11pm)
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 139000000 | 5.4 | 38 | 256 qam | 1 |
2 | 147000000 | 5.3 | 38 | 256 qam | 2 |
3 | 155000000 | 5.5 | 38 | 256 qam | 3 |
4 | 163000000 | 5.1 | 38 | 256 qam | 4 |
5 | 171000000 | 5.3 | 38 | 256 qam | 5 |
6 | 179000000 | 5.3 | 38 | 256 qam | 6 |
7 | 187000000 | 5 | 38 | 256 qam | 7 |
8 | 195000000 | 4.8 | 38 | 256 qam | 8 |
9 | 203000000 | 4.5 | 38 | 256 qam | 9 |
10 | 211000000 | 4.4 | 38 | 256 qam | 10 |
11 | 219000000 | 4.5 | 38 | 256 qam | 11 |
12 | 227000000 | 3.9 | 38 | 256 qam | 12 |
13 | 235000000 | 3.4 | 38 | 256 qam | 13 |
14 | 243000000 | 3.2 | 38 | 256 qam | 14 |
15 | 251000000 | 3.4 | 38 | 256 qam | 15 |
16 | 259000000 | 3.7 | 38 | 256 qam | 16 |
17 | 267000000 | 4.5 | 38 | 256 qam | 17 |
18 | 275000000 | 4.4 | 38 | 256 qam | 18 |
19 | 283000000 | 5 | 38 | 256 qam | 19 |
20 | 291000000 | 6 | 40 | 256 qam | 20 |
21 | 299000000 | 6 | 40 | 256 qam | 21 |
22 | 307000000 | 6.1 | 40 | 256 qam | 22 |
23 | 315000000 | 6.5 | 40 | 256 qam | 23 |
24 | 323000000 | 6.9 | 40 | 256 qam | 24 |
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.6 | 4798724 | 477172 |
2 | Locked | 38.9 | 358208 | 30969 |
3 | Locked | 38.6 | 76275 | 5818 |
4 | Locked | 38.6 | 96879 | 14914 |
5 | Locked | 38.6 | 55360 | 5002 |
6 | Locked | 38.9 | 40700 | 1736 |
7 | Locked | 38.9 | 46568 | 1537 |
8 | Locked | 38.6 | 73671 | 7452 |
9 | Locked | 38.9 | 52662 | 3521 |
10 | Locked | 38.6 | 29435 | 1716 |
11 | Locked | 38.6 | 23513 | 1284 |
12 | Locked | 38.9 | 69388 | 4150 |
13 | Locked | 38.6 | 61553 | 3526 |
14 | Locked | 38.9 | 25463 | 1687 |
15 | Locked | 38.9 | 14861 | 1412 |
16 | Locked | 38.6 | 11961 | 689 |
17 | Locked | 38.9 | 12405 | 627 |
18 | Locked | 38.9 | 20069 | 1098 |
19 | Locked | 38.9 | 13794 | 1615 |
20 | Locked | 40.3 | 6679 | 1294 |
21 | Locked | 40.3 | 4021 | 348 |
22 | Locked | 40.3 | 4211 | 414 |
23 | Locked | 40.3 | 7368 | 1076 |
24 | Locked | 40.3 | 6770 | 1593 |
on 17-10-2021 22:58
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 39400000 | 45.3 | 5120 | 64 qam | 2 |
2 | 46200000 | 45.3 | 5120 | 64 qam | 1 |
3 | 25800000 | 45 | 5120 | 64 qam | 4 |
4 | 32600000 | 45 | 5120 | 64 qam | 3 |
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 3 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 3 | 0 |
on 17-10-2021 22:58
Network Log
Time Priority Description
17/10/2021 21:13:9 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2021 21:12:9 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2021 21:09:30 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2021 21:09:19 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/10/2021 21:05:54 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/10/2021 06:00:51 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/10/2021 05:41:14 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/10/2021 05:00:0 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/10/2021 04:59:33 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
16/10/2021 04:23:13 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/10/2021 04:23:48 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/10/2021 03:41:32 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/10/2021 01:34:14 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/10/2021 00:18:26 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/10/2021 22:21:30 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/10/2021 22:19:28 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/10/2021 22:07:29 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/10/2021 21:18:36 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/10/2021 21:05:22 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/10/2021 21:04:53 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17-10-2021 23:00 - edited 17-10-2021 23:06
https://www.thinkbroadband.com/broadband/monitoring/quality/share/a3bf144a909538256e4eed041bfea3935313b87d
<a title="Broadband Ping" href="https://www.thinkbroadband.com/broadband/monitoring/quality/share/a3bf144a909538256e4eed041bfea3935313b87d">My Broadband Ping</a>
Above are two attempts at thinkbroadband links to live graphs. They basically show multiple random spikes and disconnects. The house has been vacant for the entire weekend until this evening and still some disconnects have occured.
on 18-10-2021 10:38
There should be NO PostRS errors and this needs sorted by VM. It's maybe noise ingress from loose connections or a faulty cable from the street cabinet.
All you can do is check all the connections from the Hub to the outside omnibox are "finger" tight. Apart from this, VM will need to find the source of the problem and fix it.
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 20-10-2021 10:55
Hello @Betts30,
Welcome to the community page, thanks for posting on here.
I am sorry for any issues with your internet recently.
I was unable to locate your account using your forums details, can you tell me if you are still needing help with this?
Many thanks,
New around here? To find out more about the Community check out our Getting Started guide
on 01-11-2021 17:45
Hi, Yes I've been monitoring this for the last 2 weeks and it's still disrupting my usage significantly. Could an engineer be arranged to have an investigation?
on 03-11-2021 18:10
Check out the purple envelope in the top right hand corner and I'll take some further details for you to press on with an engineer visit if this is applicable
Kindest regards,
David_Bn