WAN: 0 days, 12:18:37

SuperFrames: 2606938
SF (CRC) Errors: 224
Reed Solomon: 89939390
RS Corrected: 11917
RS Un-Corrected: 3220
HEC: 207
Errored Seconds: 67
Severe ES: 2

Interleave Depth: 16
Bitswaps: 3670

If they have changed your line on the D and E side, lift and shft and equipment at the excahnge it could be water or moisture in one of the underground joints. Its getting someone who will investigate this . At the moment BT seem very eager just to do a PQ test and if that shows satisfactory at the time of the test then they will not do any more.
If your neighbour also has the same problem that gives you more ammo to get this investigated further.

I also have had the errors come back on the upstream since last night but luckily the disconnections have not happened yet like previously on the incomming calls.

Started to rain last night and this is what i woke upto
WAN: 0 days, 19:06:54
Noise Margin: 10.9 dB
Connection Rate: 3941 Kbps
Line Attenuation: 51.0 dB
Power: 0.0 dBm
Max Rate: 4280 Kbps

SuperFrames: 4047929
SF (CRC) Errors: 26795
Reed Solomon: 291450890
RS Corrected: 188062
RS Un-Corrected: 1789211
HEC: 6502
Errored Seconds: 1018
Severe ES: 653

Interleave Depth: 32
Bitswaps: 6556

Also my snr is going mad
will give Isp a call

Small update
We are waiting for a BT engineer to come and look at our ADSL today
We can collect over 600 severely errored seconds in a 2 hour period and both up and down snr was going like a heart beat
Bang on 12:39 today snr was spot on and all down stream errors stopped
Upstream errors still go mad if we phone our line from a mobile phone, and that's with no phone plugged in and the router at the test socket

Think Engineer has probably found something wrong at the exchange before he comes out
Will ask when he does

Edited by deleted (Fri 04-Feb-11 13:21:04)

New and i hope will be last update
Bt engineer came to the house and did all the tests and could not find any fault
I said no way buddy, so he says he will do one last check, and this will be from the cabinet.
50 mins late i get a call, HRF found when test was done from the cabinet
Fault is with the hardware at the exchange
So 3 month later and we now have a working line again
Lets see it this is the last of my troubles

Keep us updated.

The errors on my upstream have reappaered also. Been watching your posts for a long time and your symptons are nearly identical to mine including the BT visits and their findings. I think its only a matter of time before my re-syncs begin again. The engineer who came here last time also said although at that time he couldnt find anything he strongly believed it was faulty itermitent exchange equipment and software bugs? Not sure what he ment by this.
It is very frustrating to wait for the dam thing to completyly breakdown before BT resolves the issue

BT engineers have there hands tied to be honest
how bad are the errors on your line over a 2 hour period
today i had 649 server bad errors in just over 2 hours
I told him that my ISP had logged all errors as proof of line problems and that BT had also installed a hard cap in order to help the line and in no way was i going to let him walk away and declare the line fault free and i get hit with a bill
no idea why the fault does not show from the house but does from the cabinet

This is my line stats after an hour... note my fault will not be fixed until tomorrow

SF (CRC) Errors: 36
Reed Solomon: 15623350
RS Corrected: 1306
RS Un-Corrected: 543
HEC: 33
Errored Seconds: 18
Severe ES: 1

Interleave Depth: 16
Bitswaps: 676

In reply to a post by iwish:

BT engineers have there hands tied to be honest
how bad are the errors on your line over a 2 hour period
today i had 649 server bad errors in just over 2 hours
I told him that my ISP had logged all errors as proof of line problems and that BT had also installed a hard cap in order to help the line and in no way was i going to let him walk away and declare the line fault free and i get hit with a bill
no idea why the fault does not show from the house but does from the cabinet

This is my line stats after an hour... note my fault will not be fixed until tomorrow

SF (CRC) Errors: 36
Reed Solomon: 15623350
RS Corrected: 1306
RS Un-Corrected: 543
HEC: 33
Errored Seconds: 18
Severe ES: 1

Interleave Depth: 16
Bitswaps: 676

It can vary quite a lot. When the line use to re-sync on incomming calls the RS uncorrected at sync could be as high as 10 million but once synced just a few hundred over the following hour.
I am currently showing about 753 for the last few days. Something i have noticed is ny line use to be very clean with no errors on the upstream untill BT ugraded the exchange and my line on 15 Dec 2010 to ADSL2+. That is the day my problems started, I go on to FTTC next week so i am really hoping its exchange equipment and NOT the Dside cabling. I no like yours when the problems start the engineer can normally get the same problem with incomming calls breaking the sync at the cab and at the exchange. Last time they reckoned they changed the equipment but the problem was still there. Then they did some software tweaks at the exchange and that seemed to help on maintaining sync bit some upstream errors were still there. That was on the third visit.

Well nothing has been done to resolve the fault and am not happy
Angry phone call to ISP tomorrow
Stats and do tell me how bad you think these are
WAN: 1 days, 08:00:20
Noise Margin: 11.0 dB
Connection Rate: 3666 Kbps
Line Attenuation: 52.0 dB
Power: 0.0 dBm
Max Rate: 3920 Kbps

SuperFrames: 6777685
SF (CRC) Errors: 56680
Reed Solomon: 227052424
RS Corrected: 668850
RS Un-Corrected: 1420690
HEC: 43354
Errored Seconds: 2280
Severe ES: 1393

Interleave Depth: 16
Bitswaps: 11109

Internet is of no use to any of us right now
downloads are useless
Online gaming is a no go
And am really fed up

where are you?