Not really a new topic - Peak Time slowdown still happening.

[#1]

I'm pretty sure my slowdowns are caused by exchange congestion. PN have raised an escalation with BT regarding the exchange and we're just awaiting an update. I ran a test at half past midnight and got this:

which is the best I've had for ages, although I had previously been getting over 14Mb downstream. I'm not sure if all the work (tree cutting was mentioned) has been done, and I can't tell from my new BT Hub 4 if interleaving has been switched off - the lowering of pings from mid-40s to mid-20s suggests it may have been.
ETA: Just so it's clear the above speed test isn't a flash in the pan, I've just run a TBB speedtest - my graph there goes steadily downhill, but this is right up there...

And a proper ping:
[tt]
C:\Users\Brian>ping -n 10 ntp.plus.net
Pinging ntp.plus.net [212.159.6.9] with 32 bytes of data:
Reply from 212.159.6.9: bytes=32 time=31ms TTL=250
Reply from 212.159.6.9: bytes=32 time=31ms TTL=250
Reply from 212.159.6.9: bytes=32 time=31ms TTL=250
Reply from 212.159.6.9: bytes=32 time=31ms TTL=250
Reply from 212.159.6.9: bytes=32 time=39ms TTL=250
Reply from 212.159.6.9: bytes=32 time=31ms TTL=250
Reply from 212.159.6.9: bytes=32 time=31ms TTL=250
Reply from 212.159.6.9: bytes=32 time=31ms TTL=250
Reply from 212.159.6.9: bytes=32 time=30ms TTL=250
Reply from 212.159.6.9: bytes=32 time=31ms TTL=250
Ping statistics for 212.159.6.9:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 30ms, Maximum = 39ms, Average = 31ms[/tt]

[#2]

Another engineer visit has come and gone - got a call a couple of hours ago and engineer no 4 arrived a few minutes later. Proceeded to test the line and got all sorts of errors, saying that he was surprised the line was working at all. It's been raining quite heavily this morning which may explain it. Anyway, he went off and swapped pairs, came back and all now testing OK.
ADSL Line Status
Connection Information
Line state: Connected
Connection time: 0 days, 00:08:24
Downstream: 16.49 Mbps
Upstream: 1.086 Mbps

1. Best Effort Test: -provides background information.
Download  Speed
14.01 Mbps

0 Mbps 21 Mbps
Max Achievable Speed
Download speed achieved during the test was - 14.01 Mbps
For your connection, the acceptable range of speeds is 4 Mbps-21 Mbps.
IP Profile for your line is - 14.9 Mbps
2. Upstream Test: -provides background information.
Upload Speed
0.94 Mbps

0 Mbps 0.83 Mbps
Max Achievable Speed
Upload speed achieved during the test was - 0.94Mbps
Additional Information:
Upstream Rate IP profile on your line is - 0.83 Mbps
[tt]C:\Users\Brian>ping -n 10 ntp.plus.net
Pinging ntp.plus.net [212.159.6.9] with 32 bytes of data:
Reply from 212.159.6.9: bytes=32 time=35ms TTL=250
Reply from 212.159.6.9: bytes=32 time=35ms TTL=250
Reply from 212.159.6.9: bytes=32 time=36ms TTL=250
Reply from 212.159.6.9: bytes=32 time=36ms TTL=250
Reply from 212.159.6.9: bytes=32 time=35ms TTL=250
Reply from 212.159.6.9: bytes=32 time=35ms TTL=250
Reply from 212.159.6.9: bytes=32 time=35ms TTL=250
Reply from 212.159.6.9: bytes=32 time=36ms TTL=250
Reply from 212.159.6.9: bytes=32 time=35ms TTL=250
Reply from 212.159.6.9: bytes=32 time=35ms TTL=250
Ping statistics for 212.159.6.9:
    Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 35ms, Maximum = 36ms, Average = 35ms[/tt]
Looks good so far - proof of the pudding will be later this evening...

[#3]

Hmm, I'm wondering whether what appears to have been a line fault was causing a very significant increase in errors after dark and that's what caused the slow-down, because huge errors certainly would.

[#4]

@Anotherone
It appears not.
(a) still slowing down.

(b) It isn't dark yet...

[#5]

OMG, You have my sympathy, there's nothing I can think of at the moment that might help. Out of curiosity do you see any change in Ping times if you ping ntp.plus.net from a command prompt compared the very slow period with no slow down? Have you tried another Speedtest.net server just in case by the way?

[#6]

I've been using Milton Keynes as the preferred speedtest.net server for ages, for consistency. I suppose it could be showing congestion issues in the evening, however it appears not:
(Switched to Maidenhead)

1. Best Effort Test: -provides background information.
Download  Speed
6.73 Mbps

0 Mbps 21 Mbps
Max Achievable Speed
Download speed achieved during the test was - 6.73 Mbps
For your connection, the acceptable range of speeds is 4 Mbps-21 Mbps.
IP Profile for your line is - 14.9 Mbps
2. Upstream Test: -provides background information.
Upload Speed
0.92 Mbps

0 Mbps 0.83 Mbps
Max Achievable Speed
Upload speed achieved during the test was - 0.92Mbps
Additional Information:
Upstream Rate IP profile on your line is - 0.83 Mbps
[tt]C:\Users\Brian>ping -n 10 ntp.plus.net
Pinging ntp.plus.net [212.159.6.9] with 32 bytes of data:
Reply from 212.159.6.9: bytes=32 time=40ms TTL=250
Reply from 212.159.6.9: bytes=32 time=42ms TTL=250
Reply from 212.159.6.9: bytes=32 time=38ms TTL=250
Request timed out.
Reply from 212.159.6.9: bytes=32 time=39ms TTL=250
Reply from 212.159.6.9: bytes=32 time=37ms TTL=250
Reply from 212.159.6.9: bytes=32 time=38ms TTL=250
Reply from 212.159.6.9: bytes=32 time=38ms TTL=250
Reply from 212.159.6.9: bytes=32 time=41ms TTL=250
Reply from 212.159.6.9: bytes=32 time=39ms TTL=250
Ping statistics for 212.159.6.9:
   Packets: Sent = 10, Received = 9, Lost = 1 (10% loss),
Approximate round trip times in milli-seconds:
   Minimum = 37ms, Maximum = 42ms, Average = 39ms[/tt]
(Edited to correct speedtest.net server name in line 1. D'oh!)

[#7]

Oh well, speed still rubbish and pings look pretty typical.
Sorry if it's been asked before, I couldn't see it, any of your neighbours or anyone else you know on the same exchange on a BTw product seeing similar issues?

[#8]

I haven't spoken to my neighbours, but others, both on and off the forum, on NSIMD have reported slow downs in the evening. The latest I have from Chris Purvey is that PN have raised an escalation with their "supplier".
We'll see...

[#9]

Well let's hope he gets his hob nail boots on 

[#10]

The latest on my Question #68600921:
2:34pm, Saturday 18 May 2013
Internal
18/05/2013 12:30:35 CRM User Attention - Escalation update: Suppliers informed that that the controls have kicked the engineer activity for pole work and the next review date is on 21/05 after 1600 hours. We will post you once we have an update.
2:36pm, Saturday 18 May 2013
Dear Mr (Removed),
Putting on hold
The next action on your Help Assistant Question is due on Tuesday 21st May at 7:00am. This Question will remain open with the BOT - DSL Logged Faults ADSL2 - Speed until this time.
No mention of the engineer visit (not appointed) I had on Saturday, where the engineer's JDSU test showed what would have been a completely non-working line, when he swapped pairs and the line test is now fine but no noticeable change to the ADSL performance in the evenings.
I also have a BT IP profile of 14.93 Mbps but my Current Line Speed is 21.5 Mb. I've certainly never synched high enough for the latter figure to be correct!
Also no word of the escalation with the traffic management team mentioned further up-thread by Chris Purvey (reply no 51).

[#11]

The latest update was as you just mentioned, our suppliers informed that that the controls have kicked the engineer activity for pole work and the next review date is on 21/05 after 1600 hours, this has been actioned by the traffic management team.
We'll keep you updated.

[#12]

Appreciate the help, Chris. Any thoughts on the Current Line Speed figure?
[tt]IP Profile for your line is - 14.9 Mbps[/tt]
[tt]Current line speed: 21.5 Mb[/tt]
As I said, I've never synched high enough for the latter figure to be anywhere near accurate.

[#13]

It looks like your sync rate very briefly jumped up-to 21Mb/s, but is now back down at 14.8Mb/s.
We received an update regarding the escalation and they are now advising that any issues should be resolved although I've asked our faults team to chase this up to confirm.
Let me know what you're connection is like tonight.

[#14]

Sorry, Chris, I was out this evening so couldn't run any tests, and I'm back on night shift from 8pm tonight so will be out of the house from just before 7pm. I'll try and get a test run before I go to work, but Monday night wasn't looking too hot:

Right now, it's flying along:

[#15]

If you could keep the tests coming it would be appreciated, I'll pass this onto the escalation team.