on 27-08-2023 22:00
Hi,
Recently my BQM graphs have been looking really bad, and i'm noticing my connection is unstable in the evening. Things like WiFi calling, video chats and gaming are being ruined by unstable pings.
Are the forum team able to check utilisation levels in the area, or check for any other problems? VM had an issue with high utilisation a few years ago in this area and this is starting to feel very similar.
Here are my most recent BQMs (although there's at least 6 weeks worth of awful graphs I could post) along with modem stats.
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 227000000 | 2 | 38 | 256 qam | 12 |
2 | 139000000 | 4.5 | 38 | 256 qam | 1 |
3 | 147000000 | 4 | 38 | 256 qam | 2 |
4 | 155000000 | 3.7 | 38 | 256 qam | 3 |
5 | 163000000 | 3.4 | 38 | 256 qam | 4 |
6 | 171000000 | 3.4 | 38 | 256 qam | 5 |
7 | 179000000 | 3.2 | 38 | 256 qam | 6 |
8 | 187000000 | 3 | 38 | 256 qam | 7 |
9 | 195000000 | 2.7 | 38 | 256 qam | 8 |
10 | 203000000 | 2.5 | 38 | 256 qam | 9 |
11 | 211000000 | 2.4 | 38 | 256 qam | 10 |
12 | 219000000 | 2.2 | 38 | 256 qam | 11 |
13 | 235000000 | 1.7 | 38 | 256 qam | 13 |
14 | 243000000 | 1.5 | 38 | 256 qam | 14 |
15 | 251000000 | 1.2 | 38 | 256 qam | 15 |
16 | 259000000 | 1.5 | 38 | 256 qam | 16 |
17 | 267000000 | 1.7 | 38 | 256 qam | 17 |
18 | 275000000 | 1.7 | 38 | 256 qam | 18 |
19 | 283000000 | 2 | 38 | 256 qam | 19 |
20 | 291000000 | 2.4 | 38 | 256 qam | 20 |
21 | 299000000 | 3.2 | 38 | 256 qam | 21 |
22 | 307000000 | 3.9 | 38 | 256 qam | 22 |
23 | 315000000 | 4.1 | 38 | 256 qam | 23 |
24 | 323000000 | 4 | 38 | 256 qam | 24 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.6 | 121 | 13 |
2 | Locked | 38.9 | 122 | 0 |
3 | Locked | 38.6 | 202 | 0 |
4 | Locked | 38.6 | 147 | 1 |
5 | Locked | 38.6 | 138 | 0 |
6 | Locked | 38.6 | 161 | 13 |
7 | Locked | 38.9 | 143 | 0 |
8 | Locked | 38.9 | 133 | 0 |
9 | Locked | 38.9 | 92 | 0 |
10 | Locked | 38.9 | 145 | 0 |
11 | Locked | 38.9 | 140 | 0 |
12 | Locked | 38.6 | 88 | 0 |
13 | Locked | 38.6 | 99 | 35 |
14 | Locked | 38.6 | 149 | 34 |
15 | Locked | 38.9 | 154 | 0 |
16 | Locked | 38.6 | 198 | 0 |
17 | Locked | 38.6 | 153 | 0 |
18 | Locked | 38.9 | 195 | 33 |
19 | Locked | 38.9 | 168 | 0 |
20 | Locked | 38.9 | 142 | 1 |
21 | Locked | 38.6 | 179 | 0 |
22 | Locked | 38.6 | 119 | 0 |
23 | Locked | 38.9 | 136 | 0 |
24 | Locked | 38.6 | 133 | 0 |
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 30100000 47.5 5120 64 qam 4
2 23600000 47 5120 64 qam 5
3 36600000 47.5 5120 64 qam 3
4 43100000 47 5120 64 qam 2
5 49600000 47.5 5120 64 qam 1
Upstream bonded channels
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 1 0
4 ATDMA 0 0 0 0
5 ATDMA 0 0 0 0
A ping test showing unstable pings:
Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=25ms TTL=52
Reply from 1.1.1.1: bytes=32 time=97ms TTL=52
Reply from 1.1.1.1: bytes=32 time=27ms TTL=52
Reply from 1.1.1.1: bytes=32 time=26ms TTL=52
Reply from 1.1.1.1: bytes=32 time=256ms TTL=52
Reply from 1.1.1.1: bytes=32 time=385ms TTL=52
Reply from 1.1.1.1: bytes=32 time=252ms TTL=52
Reply from 1.1.1.1: bytes=32 time=27ms TTL=52
Reply from 1.1.1.1: bytes=32 time=22ms TTL=52
Reply from 1.1.1.1: bytes=32 time=27ms TTL=52
Reply from 1.1.1.1: bytes=32 time=44ms TTL=52
Reply from 1.1.1.1: bytes=32 time=26ms TTL=52
Reply from 1.1.1.1: bytes=32 time=26ms TTL=52
Reply from 1.1.1.1: bytes=32 time=188ms TTL=52
Reply from 1.1.1.1: bytes=32 time=60ms TTL=52
Reply from 1.1.1.1: bytes=32 time=103ms TTL=52
Reply from 1.1.1.1: bytes=32 time=55ms TTL=52
Reply from 1.1.1.1: bytes=32 time=22ms TTL=52
Reply from 1.1.1.1: bytes=32 time=75ms TTL=52
Reply from 1.1.1.1: bytes=32 time=32ms TTL=52
Reply from 1.1.1.1: bytes=32 time=22ms TTL=52
Reply from 1.1.1.1: bytes=32 time=336ms TTL=52
Reply from 1.1.1.1: bytes=32 time=240ms TTL=52
Reply from 1.1.1.1: bytes=32 time=25ms TTL=52
Reply from 1.1.1.1: bytes=32 time=23ms TTL=52
Reply from 1.1.1.1: bytes=32 time=25ms TTL=52
Reply from 1.1.1.1: bytes=32 time=29ms TTL=52
Reply from 1.1.1.1: bytes=32 time=26ms TTL=52
Reply from 1.1.1.1: bytes=32 time=25ms TTL=52
on 01-10-2023 18:28
I presume the over-utilisation 'SNR fault' is still ongoing?
Speed test (500Mb service):
Latency is horrible:
Pinging 1.1.1.1 with 32 bytes of data:
Reply from 1.1.1.1: bytes=32 time=42ms TTL=52
Reply from 1.1.1.1: bytes=32 time=100ms TTL=52
Reply from 1.1.1.1: bytes=32 time=279ms TTL=52
Reply from 1.1.1.1: bytes=32 time=31ms TTL=52
Reply from 1.1.1.1: bytes=32 time=33ms TTL=52
Reply from 1.1.1.1: bytes=32 time=511ms TTL=52
Reply from 1.1.1.1: bytes=32 time=182ms TTL=52
Reply from 1.1.1.1: bytes=32 time=128ms TTL=52
Reply from 1.1.1.1: bytes=32 time=286ms TTL=52
Reply from 1.1.1.1: bytes=32 time=98ms TTL=52
Reply from 1.1.1.1: bytes=32 time=47ms TTL=52
Reply from 1.1.1.1: bytes=32 time=167ms TTL=52
Reply from 1.1.1.1: bytes=32 time=130ms TTL=52
Reply from 1.1.1.1: bytes=32 time=321ms TTL=52
Reply from 1.1.1.1: bytes=32 time=103ms TTL=52
Reply from 1.1.1.1: bytes=32 time=69ms TTL=52
Reply from 1.1.1.1: bytes=32 time=57ms TTL=52
Reply from 1.1.1.1: bytes=32 time=37ms TTL=52
Reply from 1.1.1.1: bytes=32 time=54ms TTL=52
Reply from 1.1.1.1: bytes=32 time=447ms TTL=52
Reply from 1.1.1.1: bytes=32 time=197ms TTL=52
Reply from 1.1.1.1: bytes=32 time=45ms TTL=52
Reply from 1.1.1.1: bytes=32 time=98ms TTL=52
Reply from 1.1.1.1: bytes=32 time=104ms TTL=52
Reply from 1.1.1.1: bytes=32 time=67ms TTL=52
Ping statistics for 1.1.1.1:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 511ms, Average = 145ms
01-10-2023 21:33 - edited 01-10-2023 21:34
Can a SNR fault cause high ping on the upstream? Like the modem is about to send something then noise happens and the sending aborted and is delayed for next time?
on 04-10-2023 09:26
Good morning @cje85
I am afraid not, the fault reference is F010948446. The estimated fix date is the tomorrow at 9am.
Best wishes.
Need a helpful hand to show you how to make a payment? Check out our guide - How to pay my Virgin Media bill