on 12-04-2022 12:26
Good afternoon all.
I want to bring to the attention of Virgin Media ASAP that there is an issue with the core network configuration.
It has been brought to my attention by a member of the Thinkbroadband forum that the "BGP is incorrectly configured and rather than going via Liberty Global /Aorta some traffic is going via LINX direct to VMO2"
This poses an issue since there is a lack of capacity through this routing.
https://www.thinkbroadband.com/news/9195-bqm-showing-peak-time-latency-issues-for-virgin-media-users
This is causing issues with the core network within the last few days.
Please refer to the article attached.
MY BMQ's for reference
Kind Regards
RR_THE_IT_GUY
on 04-05-2022 21:47
on 04-05-2022 21:50
Item Status Comments
Acquired Downstream Channel (Hz) | 267000000 | Locked |
Ranged Upstream Channel (Hz) | 60300000 | Locked |
Provisioning State | Online |
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 267000000 | 6.5 | 40 | 256 qam | 17 |
2 | 275000000 | 6.3 | 40 | 256 qam | 18 |
3 | 283000000 | 6.3 | 40 | 256 qam | 19 |
4 | 291000000 | 6.1 | 40 | 256 qam | 20 |
5 | 299000000 | 6.3 | 40 | 256 qam | 21 |
6 | 307000000 | 6.1 | 40 | 256 qam | 22 |
7 | 315000000 | 6.3 | 40 | 256 qam | 23 |
8 | 323000000 | 6.3 | 40 | 256 qam | 24 |
9 | 331000000 | 6.1 | 40 | 256 qam | 25 |
10 | 339000000 | 6.3 | 40 | 256 qam | 26 |
11 | 347000000 | 6 | 40 | 256 qam | 27 |
12 | 355000000 | 5.6 | 40 | 256 qam | 28 |
13 | 363000000 | 5.4 | 40 | 256 qam | 29 |
14 | 371000000 | 5.3 | 40 | 256 qam | 30 |
15 | 379000000 | 5.4 | 40 | 256 qam | 31 |
16 | 387000000 | 5.4 | 40 | 256 qam | 32 |
17 | 395000000 | 5.6 | 40 | 256 qam | 33 |
18 | 403000000 | 5.5 | 40 | 256 qam | 34 |
19 | 411000000 | 5.5 | 38 | 256 qam | 35 |
20 | 419000000 | 5.3 | 40 | 256 qam | 36 |
21 | 427000000 | 5.3 | 40 | 256 qam | 37 |
22 | 435000000 | 5 | 38 | 256 qam | 38 |
23 | 443000000 | 5 | 40 | 256 qam | 39 |
24 | 451000000 | 5 | 40 | 256 qam | 40 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 40.3 | 4 | 0 |
2 | Locked | 40.9 | 3 | 0 |
3 | Locked | 40.3 | 5 | 0 |
4 | Locked | 40.3 | 4 | 0 |
5 | Locked | 40.3 | 5 | 0 |
6 | Locked | 40.3 | 3 | 0 |
7 | Locked | 40.9 | 4 | 0 |
8 | Locked | 40.3 | 5 | 0 |
9 | Locked | 40.3 | 8 | 0 |
10 | Locked | 40.3 | 5 | 0 |
11 | Locked | 40.9 | 5 | 0 |
12 | Locked | 40.3 | 6 | 0 |
13 | Locked | 40.3 | 5 | 0 |
14 | Locked | 40.3 | 11 | 0 |
15 | Locked | 40.3 | 5 | 0 |
16 | Locked | 40.3 | 18 | 0 |
17 | Locked | 40.3 | 5 | 0 |
18 | Locked | 40.3 | 5 | 0 |
19 | Locked | 38.9 | 4 | 0 |
20 | Locked | 40.3 | 4 | 0 |
21 | Locked | 40.3 | 6 | 0 |
22 | Locked | 38.9 | 15 | 0 |
23 | Locked | 40.3 | 3 | 0 |
24 | Locked | 40.3 | 0 | 0 |
on 04-05-2022 21:50
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 60300000 | 46.5 | 5120 | 64 qam | 1 |
2 | 46200000 | 45.5 | 5120 | 64 qam | 3 |
3 | 39400000 | 45 | 5120 | 64 qam | 4 |
4 | 53700000 | 46 | 5120 | 64 qam | 2 |
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 |
Network access | Allowed |
Maximum Number of CPEs | 1 |
Baseline Privacy | Enabled |
DOCSIS Mode | Docsis30 |
Config file | cmreg-vmdg505-bbt057-b.cm |
SFID | 23254 |
Max Traffic Rate | 117000047 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
SFID | 23253 |
Max Traffic Rate | 10500047 |
Max Traffic Burst | 16320 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 16320 |
Scheduling Type | BestEffort |
Time Priority Description
04/05/2022 20:48:32 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/05/2022 00:40:15 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/05/2022 16:47:17 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/05/2022 06:29:23 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/04/2022 15:18:42 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/04/2022 18:49:33 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/04/2022 04:47:16 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
28/04/2022 04:28:33 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/04/2022 12:58:58 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/04/2022 16:54:1 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/04/2022 13:23:53 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/04/2022 22:31:45 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/04/2022 17:08:35 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/04/2022 02:02:40 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/04/2022 21:45:45 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/04/2022 13:45:40 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/04/2022 11:20:1 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/04/2022 07:35:35 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/04/2022 23:32:34 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/04/2022 23:21:43 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 04-05-2022 22:03
Virgin are a complete bunch of
Phoned faults, because i thought i should to at least report it. Offshore answered, the guy said he was going to ring through to a colleague to check something, instead transferred me to the IVR which asked for a PIN number for the agent... then i got disconnected.
How much bloody time and effort do we have to spend reporting this issue which is obviously at their end.
Absolute nonsense.
on 04-05-2022 22:13
I also called as soon as I noticed actual disconnections once again and the tech support women I spoke to basically acknowledged they are having "blips" in their feed but have booked me a tech for tomorrow to fix this issue as the "national issue was fixed a week and a half ago".... I asked if she could avert her attention for 2 seconds to this forum thread to be talked over and put on hold.
Funny how yesterday evening my local area boxes weren't getting correct signal, 24 hours later its only my home and a tech visit will fix all.... on mobile so having hard time copy pasting my bqm but it's EXACTLY the same as everyone's here, peak seem to start 7:30-8pm every night now. Been complaining since March. Absolute joke they won't even look at this forum thread too!
I'll update after tech visits, see what they have to say, should be a laugh.
on 04-05-2022 22:24
@Shinnanigans wrote:I also called as soon as I noticed actual disconnections once again and the tech support women I spoke to basically acknowledged they are having "blips" in their feed but have booked me a tech for tomorrow to fix this issue as the "national issue was fixed a week and a half ago".... I asked if she could avert her attention for 2 seconds to this forum thread to be talked over and put on hold.
Funny how yesterday evening my local area boxes weren't getting correct signal, 24 hours later its only my home and a tech visit will fix all.... on mobile so having hard time copy pasting my bqm but it's EXACTLY the same as everyone's here, peak seem to start 7:30-8pm every night now. Been complaining since March. Absolute joke they won't even look at this forum thread too!
I'll update after tech visits, see what they have to say, should be a laugh.
Bet they replace your superhub and call it a day.
on 04-05-2022 22:25
Shinnanigans, i am in exactly the same boat.
I decided to call faults though and well, they pressed the wrong button and disconnected me.
Seriously though how the hell are we going to get them to fix this. I mean March... Like wth!
I just want to leave Virgin but have 12 months left. I hate them so much now.
on 04-05-2022 22:26
on 05-05-2022 06:34
Well it seems Virgin are quick enough to delete posts in this thread but won't actually comment.... I got 14 emails saying replies had been made, yet when I log on, only one new post is showing. Could someone ask them on twitter why they're censoring their customers?
Come on Virgin, this is not on.
So last nights usual gameplay was again interrupted by packet loss, between 12 and 15% randomly every minute or so:
and just to clarify this is NOT a ThinkBroadbad problem Virgin, this is the monitoring of the server at Telehhouse I was connected to between 6.30pm and midnight last night, while I was connected to it:
So you can stick your "it's ThinkBroadband who have the problem" excuse where the sun doesn't shine because it if was, the server graph would exhibit the same hump and packet loss.
YOU ARE THE PROBLEM VIRGIN - FIX IT PLEASE.
on 05-05-2022 06:44
They are absolutely useless mate.
Not listening not fixing not responding and essentially not caring