cancel
Showing results for 
Search instead for 
Did you mean: 

Packet Loss

Crossy1986
Tuning in

Good afternoon all, 

Fairly new Virgin Media customer here, over the last few days we have started to notice rubber banding and connection issues when gaming. At first we thought it was a issue with Xbox Live but in the last 24 hours we have seen it impact other devices as well, when running diagnostic tests on the consoles which are connected via ethernet cables we noticed a considerable amount of packet loss occurring (sometimes as high as 66% as shown in the screenshot below.) When contacting Virgin Media via telephone they ran a check and said they could see no issue and had little to no idea what I was talking about concerning packet loss and suggested I speak to Microsoft about the issue (disregarding the fact I said this was happening across multiple devices) 

Following the call the packet loss across the devices returned to 0 which we thought was the end of it but sadly in the last hour or so things have been getting worse again, I have registered for the Broadband Quality Monitor but do not have any data to show yet regarding this. Any help would be appreciated as we appear to be going around in circles

IMG_20211015_172939.jpg

11 REPLIES 11

Crossy1986
Tuning in

Here is a link to the Broadband Quality Monitor (as I said above not much to go off so far

https://www.thinkbroadband.com/broadband/monitoring/quality/share/5677c961d954f8faeb64609ffc708a6941...

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

15370000034.2512064 qam6
26030000034.5512064 qam5
34620000034512064 qam7
43939999034.3512064 qam8

 

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0020
2ATDMA0000
3ATDMA0010
4ATDMA0020

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

13307500001.938256 qam25
22027500003.738256 qam9
32107500003.538256 qam10
42187500003.538256 qam11
52267500003.438256 qam12
62347500003.238256 qam13
7242750000338256 qam14
8250750000338256 qam15
92587500002.738256 qam16
102667500002.238256 qam17
11274750000238256 qam18
122827500001.537256 qam19
132907500001.537256 qam20
142987500001.537256 qam21
15306750000238256 qam22
163147500001.937256 qam23
173227500001.938256 qam24
18338750000238256 qam26
193467500001.937256 qam27
203547500001.938256 qam28
213627500001.737256 qam29
223707500002.237256 qam30
233787500002.437256 qam31
243867500001.738256 qam32

 

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked38.680
2Locked38.660
3Locked38.6100
4Locked38.950
5Locked38.680
6Locked38.670
7Locked38.650
8Locked38.670
9Locked38.650
10Locked38.660
11Locked38.6110
12Locked37.6170
13Locked37.6160
14Locked37.6230
15Locked38.6130
16Locked37.6170
17Locked38.6210
18Locked38.6120
19Locked37.680
20Locked38.680
21Locked37.6240
22Locked37.6100
23Locked37.6100
24Locked38.650

Network LogTime Priority Description
15/10/2021 17:52:13noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/10/2021 00:01:56criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/10/2021 22:11:48noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/10/2021 22:05:11criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/10/2021 22:02:34noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/10/2021 21:15:9criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/10/2021 20:06:55noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/10/2021 20:05:34Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/10/2021 22:41:36criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/10/2021 21:33:29ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/10/2021 06:28:15criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/10/2021 05:43:45ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/10/2021 05:43:43ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2021 15:25:33criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2021 07:53:7ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/10/2021 07:53:5ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/10/2021 02:22:18criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/10/2021 08:05:21noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/10/2021 06:26:13criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/10/2021 12:23:7ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Anonymous
Not applicable

As per other post I can confirm I had a reply from a staff member who advised many SK post codes are affected. My friend in SK5 is also suffering. 5 day fix ETA they say. 

That's potentially good news Notaker, what did they say it was? So it will be sorted by the middle of next week?

Anonymous
Not applicable

Fingers crossed. Yeah, 20th they said. They didn’t give a reason unfortunately other than a lot of SK is affected by this issue.

Corey_C
Moderator
Moderator

Thanks for your post and welcome to the Community Forums, Crossy1986,


Sorry to hear that you have been having connection issues. How has things been since your post? I have run a remote diagnostic and have not been able to identify any issues with your connection.
We can also provide online broadband help here: https://www.virginmedia.com/help/services-support/broadband
Let us know if you need any further help.


Cheers,
Corey C

Hi Corey thanks for getting in touch, apparantly SK postcodes should have the issue fixed by 20th October. I'll provide a further update then but I have noticed a reduction in packet loss occurring