cancel
Showing results for 
Search instead for 
Did you mean: 

Constant low-level packet loss

tievolu
On our wavelength

For the last month or so I've been getting constant low levels of packet loss (note the red signal at the top of the chart):

tievolu_0-1665488729476.png

It doesn't seem to be affecting general day to day usage, but clearly something's not quite right. Rebooting the hub doesn't make any difference. The VM service page isn't working right now but last time I checked it indicated problems with TV in my area, but no issues with broadband.

Any ideas?

Downstream bonded channels

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

1258750000-3.537256 qam16
21387500000.237256 qam1
3146750000037256 qam2
4154750000-0.737256 qam3
5162750000-137256 qam4
6170750000-1.537256 qam5
7178750000-1.937256 qam6
8186750000-2.237256 qam7
9194750000-2.737256 qam8
10202750000-337256 qam9
11210750000-3.537256 qam10
12218750000-3.937256 qam11
13226750000-4.537256 qam12
14234750000-4.737256 qam13
15242750000-4.737256 qam14
16250750000-4.237256 qam15
17266750000-3.937256 qam17
18274750000-3.737256 qam18
19282750000-3.537256 qam19
20290750000-437256 qam20
21298750000-3.737256 qam21
22306750000-3.737256 qam22
23314750000-4.237256 qam23
24322750000-4.237256 qam24



Downstream bonded channels

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

1Locked37.64740
2Locked37.31440
3Locked37.61660
4Locked37.62440
5Locked37.63470
6Locked37.62530
7Locked37.32140
8Locked37.32230
9Locked37.62720
10Locked37.33570
11Locked37.35780
12Locked37.66470
13Locked37.610010
14Locked37.312950
15Locked37.311280
16Locked37.67350
17Locked37.67560
18Locked37.65860
19Locked37.36450
20Locked37.68750
21Locked37.36810
22Locked37.67660
23Locked37.610630
24Locked37.69980

 

Upstream bonded channels

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

14310000044.5512064 qam2
24959997644.8512064 qam1
33010000044.8512064 qam4
43660000044512064 qam3
52360011047.2512016 qam5



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0030
2ATDMA0010
3ATDMA0020
4ATDMA0000
5ATDMA00120
127 REPLIES 127

In fact SH4 got 45 - 49 C on top plastic mesh at room temp of 22 C on 100mbit service - imagine how hot is the router CPU if plastic mesh is 45-49C.

tievolu
On our wavelength

So the SNR issue that made things much worse last week now appears to be resolved, and I'm back to square one - everything is working more or less ok, but there's still some low level background packet loss:

tievolu_0-1668421752688.png

Presumably this upstream channel is the likely reason?

tievolu_1-1668421873670.png

tievolu
On our wavelength

@redhowler wrote:

Do you have your own router or you run only the Superhub?

...

VM never fixed my issues with Packet Loss to my old address for 4 years I used to have SH 3 back than.


I have my own router and the SH3 is in modem mode. Mostly it's ok apart from the well-known issue of it grinding to a halt if there's too much UDP traffic.

I'm not hopeful that the signal issue will be fixed either. I'm hoping this will be my last Virgin Media contract as City Fibre are rolling out FTTP in my area soon - symmetric 900Mbps, half the latency, and 25% cheaper. It's a total no brainer.

@tievolu

Lucky you, you can have another ISP. Some of us can't.

I'm on SH 4 dumb mode and my router which always delivered 106-108 Mbit dwl on 100 service but since VM work on my street it went down to 92- 94 despite the fact that VM said in the email they will upgrade free of charge to 132 mbit upgrade.

There is packet loss but less than it was for years on 200 Mbit service. SH are not capable for high services.

tievolu
On our wavelength

For any VM staff that might be interested, the problem is still not resolved.

tievolu_0-1669717701385.png

 

Kain_W
Forum Team (Retired)
Forum Team (Retired)

Apologies for the issues faced tievolu,

Welcome back to the community.

Can I ask is this happening with the Hub in router mode?

Also from checking I can see that there is curerntly still an area fault raised with an estimated fix time of 5th December at 13:15.

Regards,

Kain

tievolu
On our wavelength

@Kain_W wrote:

Can I ask is this happening with the Hub in router mode?


No, I'm using the hub in modem mode with my own router.

 


@Kain_W wrote:

Also from checking I can see that there is curerntly still an area fault raised with an estimated fix time of 5th December at 13:15.


Good to know VM are aware of it at least. I assume this is the same issue that was supposed to be fixed three weeks ago? As far as I can tell there's no way for me to track this - the service status page says everything's fine, but if I run a test on my connection it says there's a problem in my area (but no details or tracking link provided).

legacy1
Alessandro Volta

@Kain_W wrote:

Can I ask is this happening with the Hub in router mode?


will be the same damn thing only your "tests" show nothing wrong more then likely  

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

Hi tievolu, 

Thanks for coming back to us on this one. 

The reference for the fault is: F010239012. We can check for updates on the fault from here if you pop a post here. 

Whilst it's ongoing you will continue to have some disruption I'm afraid. 
The estimated fix time is still showing as 05 DEC 2022 13:15 so give the hub a reboot tomorrow afternoon and let us know how things are going. 

Many thanks, 

Kath_F
Forum Team

New around here? Check out the do's and don'ts, in our Community FAQs