Community FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Constant Packet Loss & Disconnection

Chiaration
Tuning in

on ‎20-04-2022 20:13

https://www.thinkbroadband.com/broadband/monitoring/quality/share/48f2f9f582199f2aba1c3e5865d906232d...

Postcode Area NW10

Downstream bonded channels

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

133075000011.538256 qam25
226675000012.338256 qam17
327475000011.638256 qam18
428275000011.938256 qam19
529075000011.538256 qam20
629875000010.938256 qam21
730675000011.338256 qam22
831475000011.538256 qam23
932275000011.638256 qam24
1033875000011.538256 qam26
1134675000011.538256 qam27
1235475000011.638256 qam28
1336275000011.538256 qam29
1437075000011.538256 qam30
153787500001137256 qam31
163867500001138256 qam32
1739475000010.938256 qam33
184027500001137256 qam34
1941075000010.937256 qam35
204187500001138256 qam36
215227500009.337256 qam37
225307500009.937256 qam38
2353875000010.438256 qam39
245467500009.837256 qam40



Downstream bonded channels

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

1Locked38.600
2Locked38.650
3Locked38.650
4Locked38.660
5Locked38.660
6Locked38.600
7Locked38.940
8Locked38.640
9Locked38.670
10Locked38.670
11Locked38.660
12Locked38.650
13Locked38.650
14Locked38.950
15Locked37.670
16Locked38.6130
17Locked38.640
18Locked37.6120
19Locked37.670
20Locked38.600
21Locked37.650
22Locked37.650
23Locked38.6120
24Locked37.360
 

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
14620000040.5512064 qam3
23940000041512064 qam4
35370000038512064 qam2
46030000035.8512064 qam1


Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1ATDMA0000
2ATDMA0010
3ATDMA0000
4ATDMA00152

 

 
0 Kudos
10 REPLIES 10

Chiaration
Tuning in

on ‎20-04-2022 20:14

Network Log

Time Priority Description

20/04/2022 18:46:47criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2022 18:46:47criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2022 18:45:27criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2022 18:45:27criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2022 18:44:7criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2022 18:44:7criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2022 18:42:47criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2022 18:42:47criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2022 18:41:28criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2022 18:41:27criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2022 18:39:48criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2022 18:39:47criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2022 18:38:28criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2022 18:38:28criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2022 18:37:8criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2022 18:37:8criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2022 18:35:48criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2022 18:35:48criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2022 18:34:28criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2022 18:34:28criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos

Chiaration
Tuning in
In response to Chiaration

on ‎22-04-2022 09:46 

https://www.thinkbroadband.com/broadband/monitoring/quality/share/480128a94f39b676ec5721afe87662747ebb97f3

It's so bad!

 

0 Kudos

Chiaration
Tuning in
In response to Chiaration

on ‎24-04-2022 19:33

https://www.thinkbroadband.com/broadband/monitoring/quality/share/2137f818efed04070849007b5add6871aa...

Another update for today! It's getting worse and worse..

0 Kudos

Tudor
Very Insightful Person
Very Insightful Person
In response to Chiaration

on ‎24-04-2022 23:52

Downstream power levels way too high, you probably need a technician’s visit to rectify. 

Check with Area faults on 0800 561 0061 If you have a VM landline 150 this goes down to post code level. You could also try the web page http://www.virginmedia.com/servicechecker

VM will not dispatch any technicians when an area fault exists.

If no faults found:

Call Customer Services on 0345 454 1111/150 if you have a VM landline or wait a day or two for a VM staff member to get to your post.


Tudor
There are 10 types of people: those who understand binary and those who don't and F people out of 10 who do not understand hexadecimal c1a2a285948293859940d9a49385a2
0 Kudos

legacy1
Alessandro Volta
In response to Tudor

‎25-04-2022 00:14 - edited ‎25-04-2022 00:18

Likely a upstream problem....

....you could verify this by modem mode with a PC to the hub and Wireshark with a new BQM and allow ICMP inbound on the firewall

Wireshark · Go Deep.

filter
host 80.249.99.164
then filter
ip.src== 80.249.99.164

in main bar > view > time display format set to
seconds since previous displayed packet

and in milliseconds

Under time you see 1.000 ~0.999 when this goes beyond that 2.000 its downstream packet loss but if its stable its upstream packet loss.

---------------------------------------------------------------

BQM, Test for outgoing ports and SSL/L2TP VPN test

0 Kudos

Hayley_S
Forum Team (Retired)
Forum Team (Retired)
In response to Chiaration

on ‎25-04-2022 14:09

Hello @Chiaration,

Welcome back, thanks for posting.

I am sorry for the issues with your connection.

I checked the system, I can see you are in the process of upgrading your services. This can caused some intermittent signal on the broadband, but this should stop once the upgrade has been completed.

Many thanks,

Hayley
Forum Team



New around here? To find out more about the Community check out our Getting Started guide
0 Kudos

Chiaration
Tuning in
In response to Hayley_S

on ‎02-05-2022 20:37

Thank you for checking but I feel like it's another underlying issue regarding the connection. It's been two weeks since I bought this issue up and the internet works fine until it isn't. This "upgrade" is taking its time.

Current Live BQM:

https://www.thinkbroadband.com/broadband/monitoring/quality/share/480128a94f39b676ec5721afe87662747ebb97f3

It's not useable at all when this happens. Driving me crazy during these times when it's not working. 

0 Kudos

Chiaration
Tuning in
In response to Chiaration

on ‎02-05-2022 20:50

Rebooted my Router and everything...

Downstream bonded channels

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

133075000011.638256 qam25
226675000012.438256 qam17
327475000011.938256 qam18
428275000011.938256 qam19
529075000011.637256 qam20
62987500001138256 qam21
730675000011.538256 qam22
831475000011.638256 qam23
932275000011.838256 qam24
1033875000011.638256 qam26
1134675000011.638256 qam27
1235475000011.938256 qam28
1336275000011.638256 qam29
1437075000011.538256 qam30
1537875000011.137256 qam31
163867500001138256 qam32
173947500001138256 qam33
184027500001138256 qam34
194107500001138256 qam35
204187500001138256 qam36
215227500009.137256 qam37
225307500009.937256 qam38
2353875000010.338256 qam39
245467500009.637256 qam40



Downstream bonded channels

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

1Locked38.600
2Locked38.650
3Locked38.950
4Locked38.960
5Locked37.650
6Locked38.600
7Locked38.650
8Locked38.640
9Locked38.640
10Locked38.670
11Locked38.600
12Locked38.940
13Locked38.940
14Locked38.640
15Locked37.600
16Locked38.6110
17Locked38.600
18Locked38.690
19Locked38.670
20Locked38.600
21Locked37.650
22Locked37.660
23Locked38.600
24Locked37.650

 

Upstream bonded channels

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

14620000039.5512032 qam3
23940000039.5512032 qam4
35370000039.5512032 qam2
46030000035.5512032 qam1

 

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0010

 

0 Kudos

Chiaration
Tuning in
In response to Chiaration

on ‎02-05-2022 20:51

Network Log

Time Priority Description

02/05/2022 19:43:28criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 19:43:28criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 19:43:3noticeReceived REG-RSP while in REG-HOLD1 state;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:02:2Warning!ToD request sent - No Response received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 19:38:45noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 19:31:30criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 19:31:30criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 19:24:51criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 19:24:51criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 18:56:54criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 18:56:53criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 18:48:34criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 18:48:34criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 18:01:59criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 18:01:59criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 18:00:39criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 18:00:39criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 17:58:59criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 17:58:59criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/05/2022 17:57:19criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Top