In reply to a post by dect:

Lets hope they are 100% sure what the route cause is and not just replacing things as a process of elimination.

I agree, and the worse thing is despite having 4g backup right now, foc, it is very unacceptable that its taken this long and the OP not really knowing what is going on.

Devils advocate: other ISP may not necessarily provide a 4G backup or subscribe to the Ofcom compensation scheme. They could also decide it’s all just too hard and just cease the contract (with 30 days notice).

An option open to the OP if he gets tired of all this…

Finally result! After the connection being up and down the whole Friday evening, at some point after midnight on Saturday it came back up and is stable since then, I was not that excited as it happened before, but I got an email from my OR escalation contact who confirmed that they replaced a card on Friday night and it should hopefully resolve the issue. The first time someone officially said hardware was the problem! BT is still yet to contact me...

Good news! Finally 👍

Probably a supervisor card on the OLT gone dodge city, which would have affected the whole chassis. So it wasn’t just a case of moving your PoN to another port or GPON card.

Score! Now to claim your compensation and have a party

I concur !!!!!!!!!

This threads been a wild ride. Glad it's sorted for you now.

Go back a couple of years and the posts then would make you assume a thread such as this wouldn't be seen, but FTTP seems to present new problems. Our village has seen a couple of complete losses of FTTP(prior to me getting FTTP), personally my FTTP has been much more reliable than the very long FTTC line, but not without problems, whilst my speeds are almost always 10% higher than the package I pay for, every now and again the latency goes OTT and I have to reboot the router, so it's seems to highlight other network issues.

In reply to a post by burble:

Go back a couple of years and the posts then would make you assume a thread such as this wouldn't be seen, but FTTP seems to present new problems.

Numbers.

A couple of years ago there were perhaps in the high tens of thousands of active FTTP subscibers. There are now over a million on Openreach based FTTP alone and growing rapidly. So it stands to reason there will be more and more incidents publicised like this one.

Nothing is infallible or unbreakable, but overall the infrastructure used with FTTP is still relatively new and the nature and architecture of it makes it far in excess more stable and reliable than the copper network.

Burble

This has all the symptoms of an early life failure on the Head end Kit. OR would have had to convince the supplier ( Nokia) that there really was an issue to get the free repair / replacement and Spares may not be fully rolled out yet as failures should not have happened yet as the supplier is new in the network.

I am of the opinion that latency is never the fault of the FTTP but always the fault of the kit at the ends ( either end!) and the routings.

Route reboot sounds like buffer bloat or the old issue of gradually losing memory capacity, just happens much faster on a bigger connection.



.