Speed permanently lowered

[#1]

@ExForce9 I dont think you can see 'Current line speed' any more! Whilst it used to still apply to accounts with static IPs, I'm not sure that's the case now

[#2]

@dave / @plusnettony 

Referencing this - https://community.plus.net/t5/Full-Fibre/Current-line-speed/m-p/1852275#M131636 - is the Workplace Profile still a "thing" and if it is, is it "in play" here as described in the linked to thread?

If it is not still a "thing" then the bottleneck is elsewhere: if we trust the stats reported by the router, then the link speed is excellent leaving consideration of the throttling being either something else in the PN space or something in the user's space.

@IngeJones 

Switching off QoS and trying a different router might help prove or eliminate there there being an issue with the third party router.

There is though also the possibility of there being RFI leading to a significant level of data transmission failures.  Remember that the "speed" test is not measuring the speed of the link, but the capability to transmit data - the are fundamentally not the same.

• One can have a poor data transfer speed and a poor sync speed, which is probably indicative of a connection (to the exchange) issue
• Also one can have poor data transfer speed with excellent (reported) sync speed (as here) which points to something other than a connection issue

Also try a different test device to eliminate the possibility of the issue being your device or run task manager and look at the performance graphs whilst running the speed test.

Not all speed testers are born equal - what results do other test sites report?

[#3]

@MisterW  are Plusnet customers on static IP not routed via an L2TP tunnel any more ?

If an L2TP tunnel is run without a download IP profile restrictor, there would be all sorts of packet loss chaos.

Whether it's setting is visible to customers is another issue, but the profile restrictor must exist unless tunnel throttling is done elsewhere.

EDIT: Townman beat me to it !

[#4]

@ExForce9 its definitely still routed via an L2TP tunnel but where/if the download profiling is done now , I'm not sure.

Certainly AFAICS there's no Current line speed visible in the account any more 

[#5]

I'm a bit out of touch on these issues, but I believe it is. 

[#6]

@plusnettony  as there is now doubt whether customers can view their "Current Line Speed", can you tell us what value @IngeJones's connection is set to ?

[#7]

I highly doubt it would be set low  enough to give speed test result of 13Mbps, without some underlying cause, which the provided evidence doesn't show.

[#8]

It just seems weird that it's so stable, with a faulty device or cable on the network or noise on the line I'd expect some fluctuation, but the steady speed test results look to me like the connection is working fine until it slams into a hard wall.

[#9]

... but that is EXACTLY the symptom you'd see if the Plusnet "Current Line Speed" is set incorrectly.

[#10]

@IngeJones Have you tried an alternative router, and if so, which one?

[#11]

I was on the phone to a support person for quite a long time and he didn't see any setting that could be causing this problem  The only weird problem is we are showing up as being in a house many cities away...

SORTED!  Turns out somehow it had  been done in the QoS setting after all.  I told my OH (who is the one who uses the QoS service) to disable it altogether temporarily and when that got the speed back up turns out someone must have had a stray finger slip over the download speed restrictions.   Whatever it was only happened in the last few weeks.

[#12]

Ah - a crossed line or connection.  Never thought of that. sounds like an OR foul up.

[#13]

The speed profile is configured based on the speed of the line using TR-101 where BTW (for ADSL) or Openreach (for FTTC/SOGEA/FTTP) send the speed of the line as part of the PPP at the point of connection and we reflect that back onto the network so they should always match.

[#14]

See above,  Mystery solved.  Somewhere he didn't even remember editing so didn't check there before.  Must have been sleepwalking

[#15]

Didn't see the edit before I posted, but these things happen. Glad you got it sorted, but I'm still mystified as to why you are not showing at your property, @IngeJones .