From the Fact sheet:

Maintenance Level target fix times
Level 1
Clear by 23.59 day after next, Monday to Friday, excluding Public and Bank Holidays.
For example, report Tuesday, clear Thursday.

Level 2
Clear by 23.59 next day, Monday to Saturday, excluding Public and Bank Holidays.
For example, report Tuesday, clear Wednesday.

Level 3
Report 13.00, clear by 23.59 same day. Report after 13.00 clear by 12.59 next day, seven days a week, including Public and Bank Holiday.

Level 4
Clear within 6 hours, any time of day, any day of the year.

Consider also that these are the Openreach services and prices, so your Service Provider may or may not offer them and if they do it may be at a different price.

In reply to a post by Chrysalis:

So previously I revealed in the first few weeks of my FTTC service I went from 110 attainable down to about 73. Then after that was just a stacking of smaller drops to high 60s. But the last few months I have actually been synced at 75.

Well on the 26th 6pm evening I lost about another 17 attainable so again new fault raised, will see what happens now, am on the lowest ever fast path sync I have had, over 13mbit below my estimate. There is a moderate chance I will lose more to FEC tommorow as was on 1.4db snrm this morning and had a massive burst of errors.

In terms of % my line has now lost 48% at 58 attainable/sync US is still the same, its the D1 and D2 been battered, so much so that D3 now has higher snr/bitloading than D2 and D1 is only slightly higher than D3.

Need to go through a voice engineer first as I am also hearing very slight hiss and plusnet want to check that out first.

Wow Plusnet and Openreach must love you! Good luck to the engineer that visits

ok I now dont think this is extra crosstalk, given the errors and repeated drops. Probably is a fault.

I am still on fast path no INP, with FEC enabled.

I did sync this morning at around 55mbit, but attainable has since dropped again to 49 so I have a 4.9 snr margin.

BE I am not on the latest firmware but I am on the latest openreach blob (2nd newest firmware).

Edited by Chrysalis (Sat 30-Aug-14 11:17:49)

well I had a feeling this would happen.

I am still on a mid 50s sync but now the errors have pretty much stopped, so the slow lead time for an engineer looks like it will mean they wont witness the errors so I will have to now push for a fix just based on the low sync speed.

I might get a chance to look later this week. Fingers crossed...

As you say, a low-level of FEC on the downstream. Interesting to see the slight change in upstream (12/140 vs 12/124), but I'm not sure it is significant.

But neither of your speeds are at the top of their package limits, are they? That means FEC is taking some of the bandwidth without DLM ordering it... and I'm not sure I've seen that before either. There must be another element at play.

Shame - values like that in D1 and D2 relative to D3 ought to point at a distinct fault.

Fingers crossed it re-appears in time.

voice engineer been says line tests ok although he also said its noisy, left without doing anything and was moaning how his manager tells them to do test and leave.

So now need to get broadband engineer, the error rates since yesterday have gone to normal levels tho so now they not going to witness 1000s of crc errors. I will have to push for a fix based on sync speed.

Currently 53mbit on fast path, was at 75mbit albeit at 4db snr which probably translates to about 68-70 at 6db and estimate at 73.

The current FEC seems to have no sync overhead as attainable is same as sync speed when it syncs up.

The D1 and D2 are still messed up the issue is tho engineers I think dont look at that data they just do what their JDSU says.

Edited by Chrysalis (Mon 01-Sep-14 10:05:20)

I was going to order a new line but am now going to hold off.

My line failed the GEA test with a note speed has dropped more than 25% in analyse period, so it has been recognised as a fault.

Will openreach actually fix it?

Sounds similar to the problem I had, OR just said the jointboxes etc were too old to open up, and left without doing anything.

Hopefully you'll have more luck though!