on 19-03-2022 14:50
I am having issues with my Virgin Media Connection (M100 and Hub3).
During MS Team meetings, my connection drops out (wifi seems connected but internet is dropped).
During gaming sessions I frequently see my ping spiking for 10-30 seconds, making games unplayable.
It doesnt happen all the time, but it happens quite frequently in the day. I do some ping tests and I can see sometimes the ping goes to 800ms or higher. I've changed my coax cable thats made it slightly better, but still seeing issues.
Are there any tests, diagnostics or logs that I can look into?
For e.g. I tried to perform a ping from inside the SuperHub 3 and I get 20% packet loss:
PING www.google.com (142.250.178.4): 64 data bytes
72 bytes from 142.250.178.4: seq=0 ttl=58 time=70.000 ms
72 bytes from 142.250.178.4: seq=1 ttl=58 time=10.000 ms
72 bytes from 142.250.178.4: seq=2 ttl=58 time=10.000 ms
72 bytes from 142.250.178.4: seq=3 ttl=58 time=20.000 ms
--- www.google.com ping statistics ---
5 packets transmitted, 4 packets received, 20% packet loss
round-trip min/avg/max = 10.000/27.500/70.000 ms
on 19-03-2022 16:39
on 19-03-2022 17:16
Thanks John. I've set up thinkbroadband but I guess it will take a while for the data to appear.
In the meantime, the tables from my router status:
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 234750000 | 3.4 | 38 | 256 qam | 13 |
2 | 138750000 | 4.6 | 38 | 256 qam | 1 |
3 | 146750000 | 5.5 | 38 | 256 qam | 2 |
4 | 154750000 | 5.4 | 38 | 256 qam | 3 |
5 | 162750000 | 5.4 | 38 | 256 qam | 4 |
6 | 170750000 | 5.3 | 38 | 256 qam | 5 |
7 | 178750000 | 5 | 38 | 256 qam | 6 |
8 | 186750000 | 4.9 | 38 | 256 qam | 7 |
9 | 194750000 | 4.9 | 38 | 256 qam | 8 |
10 | 202750000 | 4.6 | 38 | 256 qam | 9 |
11 | 210750000 | 4.3 | 38 | 256 qam | 10 |
12 | 218750000 | 4 | 38 | 256 qam | 11 |
13 | 226750000 | 3.7 | 38 | 256 qam | 12 |
14 | 242750000 | 3.2 | 38 | 256 qam | 14 |
15 | 250750000 | 3 | 38 | 256 qam | 15 |
16 | 258750000 | 3.2 | 38 | 256 qam | 16 |
17 | 266750000 | 3.2 | 38 | 256 qam | 17 |
18 | 274750000 | 2.7 | 38 | 256 qam | 18 |
19 | 282750000 | 3.2 | 38 | 256 qam | 19 |
20 | 290750000 | 2.5 | 38 | 256 qam | 20 |
21 | 298750000 | 3 | 38 | 256 qam | 21 |
22 | 306750000 | 3 | 38 | 256 qam | 22 |
23 | 314750000 | 3 | 38 | 256 qam | 23 |
24 | 322750000 | 3.2 | 38 | 256 qam | 24 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.9 | 702 | 321 |
2 | Locked | 38.6 | 1851 | 612 |
3 | Locked | 38.6 | 1549 | 385 |
4 | Locked | 38.9 | 1285 | 360 |
5 | Locked | 38.9 | 737 | 636 |
6 | Locked | 38.9 | 548 | 508 |
7 | Locked | 38.9 | 491 | 374 |
8 | Locked | 38.9 | 574 | 403 |
9 | Locked | 38.9 | 644 | 236 |
10 | Locked | 38.9 | 612 | 372 |
11 | Locked | 38.6 | 667 | 529 |
12 | Locked | 38.9 | 711 | 486 |
13 | Locked | 38.9 | 695 | 366 |
14 | Locked | 38.6 | 637 | 280 |
15 | Locked | 38.9 | 550 | 276 |
16 | Locked | 38.9 | 455 | 248 |
17 | Locked | 38.6 | 453 | 173 |
18 | Locked | 38.6 | 540 | 231 |
19 | Locked | 38.9 | 375 | 383 |
20 | Locked | 38.9 | 515 | 397 |
21 | Locked | 38.6 | 407 | 397 |
22 | Locked | 38.9 | 443 | 362 |
23 | Locked | 38.9 | 465 | 242 |
24 | Locked | 38.9 | 448 | 257 |
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 25800000 | 43.5 | 5120 | 64 qam | 6 |
2 | 39400013 | 45 | 5120 | 64 qam | 4 |
3 | 46200025 | 45.5 | 5120 | 64 qam | 3 |
4 | 32600136 | 44 | 5120 | 64 qam | 5 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
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 19-03-2022 19:08
on 19-03-2022 23:24
I had to cut out the Network Logs due to message length (and the effort to block the MAC address), here they are:
And the live graph:
https://www.thinkbroadband.com/broadband/monitoring/quality/share/601ee149cde9394e7f07b6d2b240f7d811358d51
Time Priority Description
19/03/2022 14:47:12 | notice | LAN login Success;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0; |
18/03/2022 15:03:23 | Warning! | RCS Partial Service;CM-MAC=xb;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0; |
17/03/2022 11:28:38 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0; |
14/03/2022 08:24:59 | critical | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0; |
14/03/2022 08:20:59 | Warning! | RCS Partial Service;CM-MAC=xb;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0; |
14/03/2022 08:18:57 | Warning! | Lost MDD Timeout;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0; |
14/03/2022 08:18:53 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0; |
14/03/2022 08:18:53 | Warning! | RCS Partial Service;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0; |
14/03/2022 08:18:53 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0; |
13/03/2022 17:04:10 | Warning! | RCS Partial Service;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0; |
13/03/2022 14:31:26 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0; |
10/03/2022 23:44:20 | notice | LAN login Success;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0; |
10/03/2022 23:44:18 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0; |
10/03/2022 23:43:4 | notice | LAN login Success;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0; |
10/03/2022 23:34:45 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0; |
10/03/2022 23:32:59 | Warning! | RCS Partial Service;CM-MAC=x;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0; |
10/03/2022 02:31:25 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0; |
09/03/2022 19:49:15 | critical | No Ranging Response received - T3 time-out;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0; |
09/03/2022 18:29:9 | Warning! | RCS Partial Service;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0; |
09/03/2022 18:29:9 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=x;CMTS-MAC=x4;CM-QOS=1.1;CM-VER=3.0; |
on 19-03-2022 23:27
I forgot to say, all my devices are Wifi. Unfortunately the issue happens intermittently like once every few hours, so its not easy to sit next to the hub with an ethernet cable, since all my work setup is upstairs. But I agree, it would be easier to debug the issue that way.
on 20-03-2022 19:17
on 22-03-2022 19:26
Hi habeebq
Thanks for your post and welcome back to the community!
So sorry for any issues caused regarding this.
From checking our service I can't see any readings that would contribute to the following issue.
Are you able to run a hard wired speed test?
Thanks,
on 22-03-2022 20:41
Hi,
Unfortunately I am not able to run hardwired speed tests. Right now i.e. 22/03/2022 20:34 I am experiencing ping spikes:
on 23-03-2022 14:50