All of a sudden, seem to be getting a mountain of post RS errors on my connection, having never had a problem with them before. As an example, I reset the counts last night following turning the router on and off. Have woke up this morning and already the counts are as shown below:
The post RS errors are normal, as it is usual to acquire a few hundred post RS errors on boot up as the hub has to sift through a fair bit of rubbish before it can hunt down a downstream channel to lock on to.
The number of errors is not important, but the rate of increase of the errors is. A rapid increase in errors, say hundreds per minute would indicate a downstream problem You would also expect to see other evidence of a downstream problem in the logs and in the hub's stats.
Understood, though I did clear the error counts after the reboot - so it had already locked onto the channels at that point. The figures shown there came during the nine or ten hours once the reboot process was complete.
Will take another look at the figures when I'm home from work and see if there's been any changes...
Every network on the planet has errors, they are unavoidable. Cablelabs Docsis specification specifies a max error rate of 9*10^-7, or 90 bits per second on a 100Mbps connection. (See p96 of spec to see how this is dervied). 90 bad bits in a hundred million bits is not bad.
Depending on your usage, a few thousand pre RS errors and a couple of hubdred post RS errors should not affect performance at all. Brady Volpe provides a more practical insight here and a description here. . This is also a good read.
Noise bursts can cause Errors, but I would expect the logs to show some errors if this was happening and would expect a higher error count.
Are you having problems with your connection?
If so, please post further details so we can help.
After being advised there was a 'SNR issue with one channel' (?) on the phone on Saturday, and that it'd be 'fixed within 48hrs', things were suddenly fine with no post RS errors at all since Sunday last weekend.. until today, when it's back to errors again as of a few hours ago.
Very frustrating. As is the lack of reply from Virgin on here at any point, and the very vague response provided on the phone (including vague resolution time).