on 02-11-2024 11:55
Hi VM,
Can you run a line test on my connection? We've had issues with the line for a year or so now, since a neighbour had VM installed. These are the current line stats since I last rebooted the modem on Monday 25th October:
1 | 163000000 | 0.3 | 39 | QAM 256 | 4 |
2 | 139000000 | 1.3 | 35 | QAM 256 | 1 |
3 | 155000000 | 0.4 | 40 | QAM 256 | 3 |
4 | 171000000 | 0.6 | 40 | QAM 256 | 5 |
5 | 179000000 | 0.9 | 35 | QAM 256 | 6 |
6 | 187000000 | 0.5 | 39 | QAM 256 | 7 |
7 | 195000000 | 0 | 39 | QAM 256 | 8 |
8 | 203000000 | 0.9 | 35 | QAM 256 | 9 |
9 | 211000000 | 0 | 39 | QAM 256 | 10 |
10 | 227000000 | 1 | 38 | QAM 256 | 12 |
11 | 235000000 | 1.4 | 41 | QAM 256 | 13 |
12 | 259000000 | 0.5 | 41 | QAM 256 | 16 |
13 | 267000000 | 1.2 | 41 | QAM 256 | 17 |
14 | 291000000 | 1.6 | 41 | QAM 256 | 20 |
15 | 299000000 | 0.9 | 41 | QAM 256 | 21 |
16 | 323000000 | 0.7 | 39 | QAM 256 | 24 |
17 | 339000000 | -1.3 | 39 | QAM 256 | 26 |
18 | 355000000 | 0.8 | 40 | QAM 256 | 28 |
19 | 363000000 | 0.3 | 40 | QAM 256 | 29 |
20 | 387000000 | 0.9 | 41 | QAM 256 | 32 |
21 | 419000000 | 0.8 | 40 | QAM 256 | 36 |
22 | 427000000 | 0.7 | 41 | QAM 256 | 37 |
23 | 451000000 | 0.5 | 41 | QAM 256 | 40 |
24 | 459000000 | 0.5 | 41 | QAM 256 | 41 |
25 | 467000000 | 0 | 41 | QAM 256 | 42 |
26 | 475000000 | 0.3 | 41 | QAM 256 | 43 |
27 | 483000000 | 0.3 | 40 | QAM 256 | 44 |
28 | 491000000 | 0.1 | 40 | QAM 256 | 45 |
29 | 499000000 | 0.1 | 41 | QAM 256 | 46 |
30 | 507000000 | 0.2 | 41 | QAM 256 | 47 |
31 | 515000000 | 0.2 | 40 | QAM 256 | 48 |
3.0 Downstream channels
1 | Locked | 39 | 486955 | 228556 |
2 | Locked | 35 | 212151 | 24361 |
3 | Locked | 40 | 159612 | 10005 |
4 | Locked | 40 | 159010 | 12368 |
5 | Locked | 35 | 387266 | 18468 |
6 | Locked | 39 | 369112 | 16164 |
7 | Locked | 39 | 296053 | 12710 |
8 | Locked | 35 | 1755379 | 11705 |
9 | Locked | 39 | 182049 | 5319 |
10 | Locked | 38 | 84621 | 2864 |
11 | Locked | 41 | 93402 | 2167 |
12 | Locked | 41 | 86018 | 1886 |
13 | Locked | 41 | 152564 | 1670 |
14 | Locked | 41 | 16852 | 616 |
15 | Locked | 41 | 11806 | 265 |
16 | Locked | 39 | 23283 | 1137 |
17 | Locked | 39 | 16943 | 838 |
18 | Locked | 40 | 15052 | 593 |
19 | Locked | 40 | 14038 | 521 |
20 | Locked | 41 | 5345 | 66 |
21 | Locked | 40 | 6567 | 96 |
22 | Locked | 41 | 27004 | 2419 |
23 | Locked | 41 | 7306 | 175 |
24 | Locked | 41 | 6146 | 14 |
25 | Locked | 41 | 4982 | 1 |
26 | Locked | 41 | 5039 | 5 |
27 | Locked | 40 | 5454 | 11 |
28 | Locked | 40 | 5055 | 0 |
29 | Locked | 41 | 3831 | 0 |
30 | Locked | 41 | 3161 | 0 |
31 | Locked | 40 | 3147 | 0 |
I run the hub in modem mode, connected to an Opnsense Firewall box and the speed test results connected via the 2,5gb ports look like this:
Timestamp (GMT) Server id Server name Download Upload Latency
2024-11-02T11:20:32 | 4058 | Wildcard Networks, Newcastle upon Tyne | 42.63 | 90.07 | 30.22 |
2024-11-02T11:11:10 | 4058 | Wildcard Networks, Newcastle upon Tyne | 2.55 | 86.56 | 94.70 |
2024-11-02T11:08:30 | 25646 | Odyssey Systems Limited, Stockton-on-Tees | 4.93 | 99.19 | 75.07 |
2024-10-25T12:14:30 | 4058 | Wildcard Networks, Newcastle upon Tyne | 1142.55 | 103.61 | 27.95 |
2024-10-25T12:08:20 | 4058 | Wildcard Networks, Newcastle upon Tyne | 44.08 | 89.36 | 28.13 |
2024-10-25T11:57:01 | 63731 | Virgin Media, London | 9.63 | 85.74 | 27.99 |
2024-10-25T11:22:37 | 63731 | Virgin Media, London | 38.03 | 91.46 | 27.83 |
2024-10-14T20:25:42 | 25646 | Odyssey Systems Limited, Stockton-on-Tees | 1111.45 | 98.48 | 23.97 |
2024-10-14T18:51:59 | 25646 | Odyssey Systems Limited, Stockton-on-Tees | 40.90 | 94.86 | 24.55 |
2024-10-14T18:51:06 | 63731 | Virgin Media, London | 42.10 | 79.15 | 26.53 |
2024-10-14T09:06:16 | 4058 | Wildcard Networks, Newcastle upon Tyne | 43.92 | 90.99 | 27.97 |
2024-10-14T08:43:43 | 4058 | Wildcard Networks, Newcastle upon Tyne | 43.92 | 104.32 | 28.00 |
2024-10-14T07:59:40 | 17449 | razorblue, Leeds | 3.34 | 103.31 | 83.18 |
I don't have an omnibox setup on the house as the incoming cable runs into a rediffusion box built into the wall. The drop from the tap point to the house is most likely the original cable from when blueyonder were doing the installs around 20+ years ago.
Thanks.
Peav
on 02-11-2024 14:27
Does not look good, but must also have the upstream and hub log.
on 02-11-2024 15:23
Upload stats: These look ok. and speeds are always 90-100mbit
3.0 Upstream channels
0 | 49600000 | 46.5 | 5120 | QAM 64 | 9 |
1 | 43100000 | 46.8 | 5120 | QAM 64 | 10 |
2 | 36600000 | 47.5 | 5120 | QAM 64 | 11 |
3 | 30100000 | 48.5 | 5120 | QAM 64 | 12 |
4 | 23600000 | 47.5 | 5120 | QAM 64 | 13 |
3.0 Upstream channels
0 | ATDMA | 0 | 0 | 0 | 0 |
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 1 |
4 | ATDMA | 0 | 0 | 20 | 1 |
3.1 Upstream channels
14 | 10 | 41.0 | 2K | QAM 256 |
3.1 Upstream channels
14 | OFDMA | 200 | 74000000 | 0 | 0 |
on 02-11-2024 15:25
Network Log
02-11-2024 15:21:52 | notice | CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 15:15:38 | notice | CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 15:12:53 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 15:07:26 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 15:03:33 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 14:58:12 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 14:49:56 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 14:46:39 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 14:42:02 | notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 3; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 14:42:02 | notice | CM-STATUS message sent. Event Type Code: 2; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 14:36:12 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 14:24:53 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 14:22:55 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 13:57:38 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 13:55:12 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 13:50:15 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 13:48:49 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 13:38:07 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 13:35:00 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 13:24:13 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 13:21:49 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 13:18:15 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 13:08:23 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 13:02:13 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 13:01:51 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 12:59:33 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 12:55:32 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 12:50:20 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 12:35:54 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 12:33:24 | notice | CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 12:30:48 | notice | CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
02-11-2024 12:17:07 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 02-11-2024 16:13
I think you possibly need a technician’s visit, but first check all cables are tight.
on 04-11-2024 10:17
Thanks Tudor,
I doubled checked the connections were tight on the 25th. Speeds from over the weekend in the screen below - going from 1gbit to 40mbit.
on 04-11-2024 17:22
Is your cable a single run from the wall box into the cable modem or do you have two with a joiner? I was getting lots of pre and post RS errors until I removed the joiner and used a single piece of coax from the wall to the modem, now I hardly have any pre and no post at all.
a month ago
Its a single run from the isolator outside to the modem.
4 weeks ago
Hey Peav, thank you for reaching out and I am so sorry you are having some connection issues.
Let me send you a PM over and we will look into this.
Matt - Forum Team
New around here?