on 15-02-2023 22:01
I've been having erratic issues with ping for a few weeks now. Thought it might be a recurrence of an earlier issue with my coax cable, but no longer sure this is the case. Router stats:
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
26 | 338750000 | 7.900002 | 40.946209 | QAM256 | 26 |
1 | 138750000 | 7.599998 | 38.983261 | QAM256 | 1 |
2 | 146750000 | 7.599998 | 38.983261 | QAM256 | 2 |
3 | 154750000 | 7.199997 | 38.983261 | QAM256 | 3 |
4 | 162750000 | 7.099998 | 38.983261 | QAM256 | 4 |
5 | 170750000 | 7.199997 | 38.983261 | QAM256 | 5 |
6 | 178750000 | 7.199997 | 40.366287 | QAM256 | 6 |
7 | 186750000 | 7.199997 | 38.983261 | QAM256 | 7 |
8 | 194750000 | 7.099998 | 38.983261 | QAM256 | 8 |
9 | 202750000 | 7.099998 | 38.983261 | QAM256 | 9 |
10 | 210750000 | 7.099998 | 38.983261 | QAM256 | 10 |
11 | 218750000 | 7.000000 | 38.983261 | QAM256 | 11 |
12 | 226750000 | 6.800003 | 38.983261 | QAM256 | 12 |
13 | 234750000 | 6.599998 | 38.605377 | QAM256 | 13 |
14 | 242750000 | 6.800003 | 38.983261 | QAM256 | 14 |
15 | 250750000 | 6.800003 | 38.983261 | QAM256 | 15 |
16 | 258750000 | 6.900002 | 40.366287 | QAM256 | 16 |
17 | 266750000 | 6.900002 | 40.366287 | QAM256 | 17 |
18 | 274750000 | 7.400002 | 40.366287 | QAM256 | 18 |
19 | 282750000 | 7.599998 | 38.983261 | QAM256 | 19 |
20 | 290750000 | 7.900002 | 38.983261 | QAM256 | 20 |
21 | 298750000 | 7.400002 | 40.366287 | QAM256 | 21 |
22 | 306750000 | 7.300003 | 40.366287 | QAM256 | 22 |
23 | 314750000 | 7.500000 | 40.366287 | QAM256 | 23 |
24 | 322750000 | 8.000000 | 40.946209 | QAM256 | 24 |
25 | 330750000 | 8.300003 | 40.366287 | QAM256 | 25 |
27 | 346750000 | 7.500000 | 40.366287 | QAM256 | 27 |
28 | 354750000 | 7.199997 | 38.983261 | QAM256 | 28 |
29 | 362750000 | 7.000000 | 38.983261 | QAM256 | 29 |
30 | 370750000 | 6.800003 | 38.983261 | QAM256 | 30 |
31 | 378750000 | 6.199997 | 38.605377 | QAM256 | 31 |
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
26 | Locked | 40.946209 | 6 | 0 |
1 | Locked | 38.983261 | 0 | 0 |
2 | Locked | 38.983261 | 5 | 0 |
3 | Locked | 38.983261 | 0 | 0 |
4 | Locked | 38.983261 | 0 | 0 |
5 | Locked | 38.983261 | 6 | 0 |
6 | Locked | 40.366287 | 0 | 0 |
7 | Locked | 38.983261 | 0 | 0 |
8 | Locked | 38.983261 | 0 | 0 |
9 | Locked | 38.983261 | 0 | 0 |
10 | Locked | 38.983261 | 8 | 0 |
11 | Locked | 38.983261 | 1 | 0 |
12 | Locked | 38.983261 | 0 | 0 |
13 | Locked | 38.605377 | 6 | 0 |
14 | Locked | 38.983261 | 0 | 0 |
15 | Locked | 38.983261 | 7 | 0 |
16 | Locked | 40.366287 | 5 | 0 |
17 | Locked | 40.366287 | 0 | 0 |
18 | Locked | 40.366287 | 6 | 0 |
19 | Locked | 38.983261 | 0 | 0 |
20 | Locked | 38.983261 | 7 | 0 |
21 | Locked | 40.366287 | 0 | 0 |
22 | Locked | 40.366287 | 0 | 0 |
23 | Locked | 40.366287 | 0 | 0 |
24 | Locked | 40.946209 | 8 | 0 |
25 | Locked | 40.366287 | 0 | 0 |
27 | Locked | 40.366287 | 0 | 0 |
28 | Locked | 38.983261 | 0 | 0 |
29 | Locked | 38.983261 | 0 | 0 |
30 | Locked | 38.983261 | 0 | 0 |
31 | Locked | 38.605377 | 0 | 0 |
159 | 94 | 4K | 1840 | QAM1024 | 424 |
159 | Locked | 43 | 7.3 | 51395686 | 0 |
on 15-02-2023 22:02
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 39400000 | 41.520599 | 5120 KSym/sec | 64QAM | 3 |
2 | 32600000 | 41.270599 | 5120 KSym/sec | 64QAM | 4 |
3 | 46200000 | 41.770599 | 5120 KSym/sec | 64QAM | 2 |
4 | 53700000 | 41.770599 | 5120 KSym/sec | 64QAM | 1 |
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 | 0 | 0 |
4 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
Network access | true |
Maximum Number of CPEs | 1 |
Baseline Privacy | true |
DOCSIS Mode | 3.1 |
Config file | cxv9873254k;fg87dsfd;kfoA |
SFID | 636 |
Max Traffic Rate | 1200000450 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
SFID | 635 |
Max Traffic Rate | 55000270 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 16320 |
Scheduling Type | bestEffort |
on 15-02-2023 22:08
Today's BQM:
Sunday's BQM, with a random late-morning spike:
15-02-2023 22:33 - edited 15-02-2023 22:37
Nothing wrong with your Hub stats. Best to post a live link to the BQM.
on 15-02-2023 22:57
Live graph:
https://www.thinkbroadband.com/broadband/monitoring/quality/share/514d6fbb54a0b2e7ef89c203f4c80b8ad480bada
15-02-2023 23:08 - edited 15-02-2023 23:08
Your latency problem is due to very high contention on your local part of the VM network. There are too many users connected.
There is nothing you can do except demand that VM provides more capacity.
on 15-02-2023 23:28
I considered that, but a weird spike for a couple of hours on a Sunday morning seems an odd fit...
on 16-02-2023 09:21
I shouldn't worry about that. A sudden step usually means that some network maintenance is going on. It does happen, even on a Sunday sometimes.
on 18-02-2023 12:10
Hi @Rogueywon 👋,
Welcome back to our Community Forums and thanks for your post.
I am sorry you've been having some issues with the service.
Checking on things this side, at the time of writing, I am unable to identify any issues.
How have things been since posting?
on 18-02-2023 12:15
@Ayisha_B wrote:Checking on things this side, at the time of writing, I am unable to identify any issues.
Utilisation not withstanding.