In reply to a post by mrnelster:

As I went on to explain in the thread, The pausing was caused when BT swapped to fast path.

I had the line monitored remotely and a graph for upload and download produced. The consensus came down to packet loss and resending of data, understandable on a long line with fast path enabled.

Except that you said BT blamed it on Sky's poor equipment, so you had the problem on Sky.

In short what I explained was:

I had poor latency on Sky. That was due to high Interleaving settings.

BT blamed Sky, not me. There connection was no better. I wasn't happy paying more for something they said they could improve and didn't. In response they tried fast path. That is when the line became erratic and had to be reverted to interleaved.

My whole point was that BT should have known that they couldn't realitically improve latency on a 6km line and shouldn't have blamed Sky's equipment. That is all there in the thread.

You were being contradictory for some unknown reason. I thought it was obvious that long lines didn't handle fast path very well. I thought that was why Interleaving was adopted.

If it's just down to a noisy line, then you'll be fine with FTTC.
If it's a line fault on the E-side, once again FTTC will fix it.
However, if it's a problem on the D-side, you may suffer lower speeds on FTTC.

Sub thread closed

Please don't derail threads by bringing other discussions into them.

On the technical side, it seems people are nit picking and playing semantic games too.