Line in 10 day training period

[#1]

@ericgripp sync is the full 80Mbps.

[#2]

Wow, can't be bad ericgripp,at least your connection is good, if if there's a bit of congestion somewhere. Could be the tester congested mind 

[#3]

don't get me wrong I wasn't complaining or moaning, being fairly new to PN so far I have had nothing but a positive experience and the staff I've spoken to have always been helpful and friendly.
Its just interesting to see how speed can fluctuate so much due to, I suspect, a finite amount of bandwidth. Until top level switches and routers have the capability of 100G or 1000G Base T (I think that's the term) as more and more people around the country get FTTC, then theres only so much data you can push around.

[#4]

Estimated line speed:There's no speed estimate currently held on your account.Current line speed:38.6 Mb

[#5]

I wonder how long it will take for your Current Line Speed to update to 34.6Mbps, in theory it ought to be by 2000 ish.

[#6]

Dunno, i guess it's a waiting game. I guess DLM has been at play then ? the engineers' mate did a calculation for him, he said 30mbps for your length of line is about the best your going to see.
who knows.

[#7]

Well let's hope it holds where it is for you. You might see a bit of a slow down as more users get added to the Cab 

[#8]

Well plusnet have done all they can. i was looking at Vectoring the other day for long lines, maybe there might be something in that when it gets to the south east.
It could be worse... i could be on cable waiting for the kids to hit the limiter 

[#9]

And paying a lot more for phone calls as well 

[#10]

my latency has doubled as well, i forgot about that!
C:\Users\top>ping www.bbc.co.uk
Pinging www.bbc.net.uk [212.58.244.70] with 32 bytes of data:
Reply from 212.58.244.70: bytes=32 time=18ms TTL=55
Reply from 212.58.244.70: bytes=32 time=17ms TTL=55
Reply from 212.58.244.70: bytes=32 time=17ms TTL=55
Reply from 212.58.244.70: bytes=32 time=17ms TTL=55
Ping statistics for 212.58.244.70:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 17ms, Maximum = 18ms, Average = 17ms

[#11]

That's a ....., yes you did mention it earlier. Try that ping to bbc.co.uk without the www on the front, also try ntp.plus.net

[#12]

C:\Users\Laptop>ping ntp.plus.net -t
Pinging ntp.plus.net [212.159.13.49] with 32 bytes of data:
Reply from 212.159.13.49: bytes=32 time=17ms TTL=250
Reply from 212.159.13.49: bytes=32 time=17ms TTL=250
Reply from 212.159.13.49: bytes=32 time=18ms TTL=250
Reply from 212.159.13.49: bytes=32 time=18ms TTL=250
Reply from 212.159.13.49: bytes=32 time=19ms TTL=250
Reply from 212.159.13.49: bytes=32 time=17ms TTL=250
Reply from 212.159.13.49: bytes=32 time=17ms TTL=250
Reply from 212.159.13.49: bytes=32 time=17ms TTL=250
Reply from 212.159.13.49: bytes=32 time=17ms TTL=250
Reply from 212.159.13.49: bytes=32 time=17ms TTL=250
Reply from 212.159.13.49: bytes=32 time=17ms TTL=250
Reply from 212.159.13.49: bytes=32 time=18ms TTL=250
Reply from 212.159.13.49: bytes=32 time=18ms TTL=250
Ping statistics for 212.159.13.49:
    Packets: Sent = 13, Received = 13, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 17ms, Maximum = 19ms, Average = 17ms

hmm i didn't do a www how weird.

[#13]

Well I'm afraid you are stuck with that for the time being, Plusnet have no control over Interleaving on Fibre, and OR won't do anything, so it's a case of be patient and wait for DLM to reduce the depth, which it will do if it doesn't see any issues.

[#14]

My line has been rock solid, none of this makes any sense tbh.

[#15]

Whatever caused the change could have been some nasty burst of noise/interference which you may not have noticed, they may be something continuously there in the background (let's hope not) which is keeping up a higher error rate that DLM doesn't like - let's hope it was just transient.