18-12-2022 22:22 - edited 18-12-2022 22:31
Can I please get some VM staff support here please?
Since this morning, I've been experiencing unbearably high pings and general issues with connection stability. I ran a few ping tests to BBC and a foreign website. Both returned ~40% lost packets.
This definitely isn't an issue on my PC's side, as all devices connected at my home are experiencing connection issues (even my Thermomix...).
Here's the router data dump:
3.0 Downstream channels
Channel | Frequency (Hz) | Power (dBmV) | SNR (dB) | Modulation | Channel ID |
48 | 514750000 | 6.400002 | 40.366287 | QAM256 | 48 |
20 | 290750000 | 5.900002 | 40.946209 | QAM256 | 20 |
18 | 274750000 | 6.199997 | 40.946209 | QAM256 | 18 |
19 | 282750000 | 6.099998 | 40.366287 | QAM256 | 19 |
21 | 298750000 | 5.900002 | 40.366287 | QAM256 | 21 |
22 | 306750000 | 5.900002 | 40.946209 | QAM256 | 22 |
23 | 314750000 | 6.099998 | 40.366287 | QAM256 | 23 |
24 | 322750000 | 6.000000 | 40.366287 | QAM256 | 24 |
25 | 330750000 | 5.699997 | 40.366287 | QAM256 | 25 |
26 | 338750000 | 5.800003 | 40.946209 | QAM256 | 26 |
27 | 346750000 | 6.000000 | 40.946209 | QAM256 | 27 |
28 | 354750000 | 6.099998 | 40.366287 | QAM256 | 28 |
29 | 362750000 | 6.000000 | 40.366287 | QAM256 | 29 |
30 | 370750000 | 6.099998 | 40.366287 | QAM256 | 30 |
31 | 378750000 | 5.800003 | 40.946209 | QAM256 | 31 |
32 | 386750000 | 5.699997 | 40.366287 | QAM256 | 32 |
33 | 394750000 | 5.800003 | 40.946209 | QAM256 | 33 |
34 | 402750000 | 5.599998 | 40.366287 | QAM256 | 34 |
35 | 410750000 | 5.900002 | 40.946209 | QAM256 | 35 |
36 | 418750000 | 6.099998 | 40.366287 | QAM256 | 36 |
37 | 426750000 | 6.099998 | 40.366287 | QAM256 | 37 |
38 | 434750000 | 6.300003 | 40.366287 | QAM256 | 38 |
39 | 442750000 | 6.300003 | 40.366287 | QAM256 | 39 |
40 | 450750000 | 6.400002 | 40.366287 | QAM256 | 40 |
41 | 458750000 | 6.199997 | 40.366287 | QAM256 | 41 |
42 | 466750000 | 6.199997 | 40.366287 | QAM256 | 42 |
43 | 474750000 | 6.000000 | 40.366287 | QAM256 | 43 |
44 | 482750000 | 6.199997 | 40.946209 | QAM256 | 44 |
45 | 490750000 | 6.199997 | 40.946209 | QAM256 | 45 |
46 | 498750000 | 6.500000 | 40.366287 | QAM256 | 46 |
47 | 506750000 | 6.400002 | 40.946209 | QAM256 | 47 |
18-12-2022 22:23 - edited 18-12-2022 22:25
3.0 Downstream channels
Channel | Lock Status | RxMER (dB) | Pre RS Errors | Post RS Errors |
48 | Locked | 40.366287 | 0 | 0 |
20 | Locked | 40.946209 | 0 | 0 |
18 | Locked | 40.946209 | 0 | 0 |
19 | Locked | 40.366287 | 1 | 0 |
21 | Locked | 40.366287 | 0 | 0 |
22 | Locked | 40.946209 | 0 | 0 |
23 | Locked | 40.366287 | 0 | 0 |
24 | Locked | 40.366287 | 0 | 0 |
25 | Locked | 40.366287 | 0 | 0 |
26 | Locked | 40.946209 | 0 | 0 |
27 | Locked | 40.946209 | 0 | 0 |
28 | Locked | 40.366287 | 0 | 0 |
29 | Locked | 40.366287 | 0 | 0 |
30 | Locked | 40.366287 | 0 | 0 |
31 | Locked | 40.946209 | 0 | 0 |
32 | Locked | 40.366287 | 0 | 0 |
33 | Locked | 40.946209 | 0 | 0 |
34 | Locked | 40.366287 | 0 | 0 |
35 | Locked | 40.946209 | 0 | 0 |
36 | Locked | 40.366287 | 0 | 0 |
37 | Locked | 40.366287 | 0 | 0 |
38 | Locked | 40.366287 | 0 | 0 |
39 | Locked | 40.366287 | 0 | 0 |
40 | Locked | 40.366287 | 0 | 0 |
41 | Locked | 40.366287 | 0 | 0 |
42 | Locked | 40.366287 | 0 | 0 |
43 | Locked | 40.366287 | 0 | 0 |
44 | Locked | 40.946209 | 1 | 0 |
45 | Locked | 40.946209 | 0 | 0 |
46 | Locked | 40.366287 | 0 | 0 |
47 | Locked | 40.946209 | 0 | 0 |
18-12-2022 22:23 - edited 18-12-2022 22:26
3.0 Upstream channels
Channel | Frequency (Hz) | Power (dBmV) | Symbol Rate (ksps) | Modulation | Channel ID |
1 | 49600000 | 41.270599 | 5120 KSym/sec | 64QAM | 1 |
2 | 23600000 | 43.020599 | 5120 KSym/sec | 32QAM | 9 |
3 | 36600000 | 41.770599 | 5120 KSym/sec | 64QAM | 3 |
4 | 43100000 | 41.020599 | 5120 KSym/sec | 64QAM | 2 |
5 | 30100000 | 42.270599 | 5120 KSym/sec | 64QAM | 4 |
3.0 Upstream channels
Channel | Channel Type | T1 Timeouts | T2 Timeouts | T3 Timeouts | T4 Timeouts |
1 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
2 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
3 | US_TYPE_STDMA | 0 | 0 | 1 | 0 |
4 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
5 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
3.1 Upstream channels
Channel | Channel Width (MHz) | Power (dBmV) | FFT Type | Modulation |
10 | 10.8 | 37.0 | 2K | QAM8 |
3.1 Upstream channels
Channel | Channel Type | Number of Active Subcarriers | First Active Subcarrier (Hz) | T3 Timeouts | T4 Timeouts |
10 | OFDMA | 220 | 53.4 | 0 | 0 |
18-12-2022 22:23 - edited 18-12-2022 22:26
Network Log
Time | Priority | Description |
Fri Nov 25 08:44:55 2022 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Nov 25 11:09:23 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Nov 26 08:56:52 2022 | 3 | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Nov 26 08:56:56 2022 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Nov 26 08:58:36 2022 | 3 | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Nov 26 09:03:02 2022 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Nov 26 11:50:51 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Nov 27 15:54:28 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue Nov 29 02:31:59 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue Nov 29 08:55:16 2022 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue Nov 29 19:00:21 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Nov 30 15:45:18 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Nov 30 18:49:33 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 2 15:20:07 2022 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Dec 4 03:11:36 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jan 1 00:01:23 1970 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jan 1 00:01:23 1970 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Dec 4 16:38:45 2022 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Dec 4 23:30:42 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Dec 5 16:41:05 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue Dec 6 02:10:29 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue Dec 6 10:23:20 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Wed Dec 7 03:59:20 2022 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 9 03:10:11 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Dec 10 04:09:45 2022 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Dec 11 03:07:53 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Dec 11 17:04:16 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue Dec 13 16:09:45 2022 | 4 | DHCP 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:22 1970 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jan 1 00:01:22 1970 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue Dec 13 18:02:13 2022 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Tue Dec 13 18:06:55 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Dec 15 19:58:44 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 16 11:27:59 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Fri Dec 16 12:18:22 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Dec 17 03:13:57 2022 | 6 | CM-STATUS message sent. Event Type Code: 24; Chan ID: 49; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat Dec 17 05:05:54 2022 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Dec 18 10:01:33 2022 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Dec 18 10:25:43 2022 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jan 1 00:01:20 1970 | 3 | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu Jan 1 00:01:20 1970 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sun Dec 18 10:39:15 2022 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 21-12-2022 09:21
Hi Orlas,
Thanks for your post, and a warm welcome back to our Community Forums.
I'm sorry to hear you're experiencing problems with the connection on your service. I've had a look at things on our end, and can see you have spoken with our team since your post, and they have been able to assist.
How are things looking now? Please keep us updated on any further issues, and we'll do our best to help out.
Thanks,