Definitely a 9dB sync-time noise margin. As I said, that can cost as much as 1.2Mbps. Something has caused that. As you know, but the OP may not, that might self-correct in a few days. (Edit - but not if those error rates are real).

Also although it's a bad time of day to reconnect, he has gained 1Mbps.

Edited by RobertoS (Tue 28-Jan-14 19:03:46)

In reply to a post by flippery:

My opinion, others disagree, is that the HH4 sync speed is deliberately lowered to allow a good separate wifi connection for others to use..

You are wrong there. The Hub will sync at the maximum it can and does NOT reserve bandwidth for roaming WiFi users. They take part of the total - when required so if no one is using it you will get all of te bandwidth - a very very small amount maybe used for WiFi overheads but nothing you would notice.

OK. The HH4 had been up for 7 days. Was it new at that time or had it been in use for weeks?

If it was new, the HH3 may be the cause of the 9dB noise margin. Let's see the stats after an hour as Zarjaz requested . In which case with the HH4 restored, we could find the noise margin reduced to 6dB after a couple of weeks.

Unfortunately if the HH3 is the issue that might mean the 7 days stable connection on the HH4 has been wasted.

Edited by RobertoS (Tue 28-Jan-14 19:19:32)

My opinion, others disagree, is that the HH4 sync speed is deliberately lowered to allow a good separate wifi connection for others to use..

Could you explain that theory more, as there can only be one WAN connection available for all users of a Hub.

ADSL Line Status

Connection Information

Line state: Connected
Connection time: 0 days, 01:14:03
Downstream: 14 Mbps
Upstream: 1.157 Mbps

ADSL Settings

VPI/VCI: 0/38
Type: PPPoA
Modulation: G.992.5 Annex A
Latency type: Interleaved
Noise margin (Down/Up): 8.5 dB / 6.1 dB
Line attenuation (Down/Up): 23.7 dB / 12.2 dB
Output power (Down/Up): 18.3 dBm / 12.5 dBm
FEC Events (Down/Up): 7718 / 89
CRC Events (Down/Up): 17 / 33
Loss of Framing (Local/Remote): 0 / 0
Loss of Signal (Local/Remote): 0 / 0
Loss of Power (Local/Remote): 0 / 0
HEC Events (Down/Up): 151 / 11
Error Seconds (Local/Remote): 13 / 1

I would imagin that a VPN is used to carry the traffic from the BT WIFI AP.

One thing is certain - there is no way that it can have any impact on the sync rate as there can only be one data stream over the DSL link.

Yep, don't like those HEC errors in such a short space of time, also the CRC's racking up when interleaving is working .......

Where to from here ? Be brave and call BT retail, jump through their hoops, see if they'll raise a Boost visit, and hope you get an engineer with some nouse ?

In reply to a post by RobertoS:

The HH4 had been up for 7 days.

I read the 7 day OP stats as from the HH3. The HH4 was mentioned in response to request to try a diff router but was discarded as it does not provide stats.

Spoke to BT india a while back ,they arranged a engineer out to fix something with the line.The line was disconnecting every time the phone rang , He did something at the exchange and said it was fixed i heard nothing after that. This line is at my grandparents and i don't want to hassle them to stay in to wait for a engineer that not really a option.

This line is at my grandparents and i don't want to hassle them to stay in to wait for a engineer that not really a option.

They still work then your Grandparents ?

Short of listening with a MW radio tuned to around 612 then theres not so many options. Can you also confirm that those errors increment at a similar rate with the router in the test socket ?