cancel
Showing results for 
Search instead for 
Did you mean: 

Peak time latency spikes

AndyH
Grafter
Posts: 6,824
Thanks: 1
Registered: ‎27-10-2012

Re: Peak time latency spikes

The current problem (peak slow downs) seems unrelated to the original problem (PCL gateway spikes around 21:30) in this thread.
Does the gateway switching thing show where the problem lies?
I still remain unaffected and my speed tests are constantly around 80-90Mbps on all gateways.
Kelly
Hero
Posts: 5,497
Thanks: 373
Fixes: 9
Registered: ‎04-04-2007

Re: Peak time latency spikes

Anyone on PCL-AG08 and PCL-AG09 tonight will have seen really poor performance after 8:30 tonight.  You can see the problem on Sheffield Steel and Prettyflyguy's lines on http://community.plus.net/ping-graph
Kelly Dorset
Ex-Broadband Service Manager
jamesanstee
Aspiring Pro
Posts: 558
Thanks: 27
Fixes: 3
Registered: ‎20-04-2012

Re: Peak time latency spikes

Im on pcl-ag01. since connecting to that one my speeds have been almost near normal but earlier on before i gateway hopped pcl-ag08 was painfully slow
austinsom
Grafter
Posts: 164
Thanks: 3
Registered: ‎12-02-2013

Re: Peak time latency spikes

I wouldn't say I have been getting stellar performance on any of the gateways I have tried.  All have had terrible lag for online gaming and the peak ping times are really poor:
<a title="Broadband Ping" href="http://www.thinkbroadband.com/ping/share/0cde42ce765489e8a0e9ad1cfb267aeb.html"><img alt="My Broadband Ping - austinsom" src="http://www.thinkbroadband.com/ping/share-thumb/0cde42ce765489e8a0e9ad1cfb267aeb.png" /></a>
I'll post another shot later, but so far not impressed, as none of this should be necessary.
jamesanstee
Aspiring Pro
Posts: 558
Thanks: 27
Fixes: 3
Registered: ‎20-04-2012

Re: Peak time latency spikes

Not achieving full speed but certainly better than the last few nights
FAQ


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

0 Mbps 67.62 Mbps
Max Achievable Speed
Download speedachieved during the test was - 55.94 Mbps
For your connection, the acceptable range of speedsis 12 Mbps-67.62 Mbps .
Additional Information:
IP Profile for your line is - 67.62 Mbps
2. Upstream Test:  -provides background information.
Upload Speed
10.73 Mbps

0 Mbps 20 Mbps
Max Achievable Speed
Upload speed achieved during the test was - 10.73Mbps
Additional Information:
Upstream Rate IP profile on your line is - 20 Mbps

Traceroute for this evening .
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.
C:\Users\Private>tracert www.bbc.co.uk
Tracing route to www.bbc.net.uk [212.58.244.69]
over a maximum of 30 hops:
  1    1 ms    1 ms    1 ms  192.168.1.1
  2    35 ms    27 ms    15 ms  lo0-central10.pcl-ag01.plus.net [195.166.128.182
]
  3    15 ms    15 ms    15 ms  link11-central10.pcl-gw01.plus.net [84.93.249.20
]
  4    15 ms    14 ms    15 ms  xe-0-2-0.pcl-cr01.plus.net [212.159.1.0]
  5    15 ms    15 ms    15 ms  ae1.ptw-cr01.plus.net [195.166.129.0]
  6    49 ms    15 ms    15 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
  7    *        *        *    Request timed out.
  8    *        *        *    Request timed out.
  9    15 ms    16 ms    15 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]
10    20 ms    16 ms    18 ms  132.185.255.148
11    15 ms    15 ms    15 ms  bbc-vip114.telhc.bbc.co.uk [212.58.244.69]
Trace complete.
C:\Users\Private>
alegeek
Grafter
Posts: 92
Thanks: 2
Registered: ‎20-06-2011

Re: Peak time latency spikes

After all this time do plusnet really not know what the problem is? If so, that is very worrying!
Most importantly, when are you going to put this on your system status page and make it a known and official problem that's being investigated?
jamesanstee
Aspiring Pro
Posts: 558
Thanks: 27
Fixes: 3
Registered: ‎20-04-2012

Re: Peak time latency spikes

I saw an identical issue to this when i used to be with Be took months to resolve but hopefully plusnet will find a fix soon.
dick:quote
Kelly
Hero
Posts: 5,497
Thanks: 373
Fixes: 9
Registered: ‎04-04-2007

Re: Peak time latency spikes

theoddbot:  That's a good point. I'll get something put out tomorrow.
Embarrassed
Kelly Dorset
Ex-Broadband Service Manager
Joopzor
Grafter
Posts: 36
Registered: ‎20-02-2013

Re: Peak time latency spikes

I been here from the 4th of feb and it not been to bad but when it hits, you have to reconnect so many times to get a play able internet its annoying
Anonymous
Not applicable

Re: Peak time latency spikes

Quote from: theoddbot
Most importantly, when are you going to put this on your system status page and make it a known and official problem that's being investigated?

Why isn't it also shown on the "Priority Problems" page - http://www.plus.net/support/service/problems/index.php  ?

Is this NOT a problem, or is it NOT a priority ?   Angry
ITWorks
Superuser
Superuser
Posts: 2,121
Thanks: 739
Fixes: 9
Registered: ‎05-11-2008

Re: Peak time latency spikes

So there no mention on the service status page, no current priority problems ,  this gives the view that PN don't want to inform the customer base ( beyond the forum) about this problem.
Regards
Mike

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

austinsom
Grafter
Posts: 164
Thanks: 3
Registered: ‎12-02-2013

Re: Peak time latency spikes

So, finished my gaming session on the xbox, and sadly must report that lag was really bad, almost unplayable at times - the TBB monitor shows high spikes thrughout most of the time I was online.  WHilst the average was acceptable it is the spikes that do the damage and also the packet loss at the start of the session didn't help.
This all smacks of what happened at an old ISP.  The problem was very similar to this and was never sorted properly whilst I was waiting, which was at least 6 months.
Whilst I appreciate that the staff at Plusnet are trying to do their best to resolve this issue, the fact of the matter is the broadband service does not currently fit the product it is sold as on the sites homepage which is as 'reliable' broadband.  In my experience so far it has been anything but - you certainly cannot rely on it at peak times.  This needs to be sorted, and quickly, or people will vote with their feet.  I am already thinking it's MAC time and I have been with PN less than a month and the ongoing fault, coupled with this has really made me think it just isn't worth the hassle.
If there was a discount for managing your own congested gateway then fine, but there isn't.  I'm sure there should be some sort of software algorithm that should flip you around automatically when congestion becomes a problem, I'm sure it wouldn't be that hard to do as the current situation is plainly wrong and cannot be allowed to go on.  After all, if an IT consultant was being paid to do all this fault finding, they'd be off to Barbados for a few weeks after it all.  However we are paying to put up with slow service speeds, a fault that isn't getting fixed and also to do our own fault finding and analysis.  Something is very wrong with this picture.
This evenings stats from me:
<a title="Broadband Ping" href="http://www.thinkbroadband.com/ping/share/0cde42ce765489e8a0e9ad1cfb267aeb.html"><img alt="My Broadband Ping - austinsom" src="http://www.thinkbroadband.com/ping/share-large/0cde42ce765489e8a0e9ad1cfb267aeb.png" /></a>
Speeds and ping on 'instant tests' seem to be more or less pack to normal:
   

Gateway is: ptn-ag04
Even the forum isn't working properly!
Anotherone
Champion
Posts: 19,107
Thanks: 457
Fixes: 21
Registered: ‎31-08-2007

Re: Peak time latency spikes

Didn't Kelly say he'd get something posted up on Service Status tomorrow?
20CN ptn-ag04 nothing really exciting to report, pretty much as last night. No speed reductions noticed, other than one bad test on BT speedtester which wasn't repeated and iPlayer Diagnostics were fine. Pings started to be a bit wild after 8.00pm, normal is typically 36/37ms on this Gateway, and started to peak between 50 & 60 ms typically by about 8.30pm continuing until around 10.00pm with very occasional large peaks when they started reducing. Generally it was a bit better than last night, and apart from a burst of high pings over 100 ms between 2240 &2243 things have been pretty much as normal for just over an hour now.
Pettitto
Plusnet Alumni (retired)
Plusnet Alumni (retired)
Posts: 6,346
Fixes: 5
Registered: ‎26-11-2011

Re: Peak time latency spikes

I was affected by the broadband issues tonight which doesn't usually happen.
@austinsom - I'm really sorry that this problem is affecting your service so much, honestly, we are working hard to try to get to the bottom of it. I would be more than happy to take a look at your line just to be sure there isn't anything that could be causing issues?
@Anotherone - See Kelly's response here: http://community.plus.net/forum/index.php/topic,111170.msg965039.html#msg965039 - that gives a bit of an insight into what's been happening on a couple of the affected gateways this evening too.
Anotherone
Champion
Posts: 19,107
Thanks: 457
Fixes: 21
Registered: ‎31-08-2007

Re: Peak time latency spikes

Yes I saw that thanks Chris.
0006 had the following pings, not surprised really considering all the downloads that people start at midnight
Reply from 212.159.6.10: bytes=32 time=48ms TTL=250
Reply from 212.159.6.10: bytes=32 time=101ms TTL=250
Reply from 212.159.6.10: bytes=32 time=51ms TTL=250
Reply from 212.159.6.10: bytes=32 time=46ms TTL=250
Reply from 212.159.6.10: bytes=32 time=43ms TTL=250
Reply from 212.159.6.10: bytes=32 time=87ms TTL=250
Reply from 212.159.6.10: bytes=32 time=43ms TTL=250
Reply from 212.159.6.10: bytes=32 time=41ms TTL=250
Reply from 212.159.6.10: bytes=32 time=43ms TTL=250
Reply from 212.159.6.10: bytes=32 time=86ms TTL=250
Reply from 212.159.6.10: bytes=32 time=42ms TTL=250
Reply from 212.159.6.10: bytes=32 time=40ms TTL=250
Reply from 212.159.6.10: bytes=32 time=44ms TTL=250
Reply from 212.159.6.10: bytes=32 time=88ms TTL=250
Reply from 212.159.6.10: bytes=32 time=44ms TTL=250
Reply from 212.159.6.10: bytes=32 time=41ms TTL=250
Reply from 212.159.6.10: bytes=32 time=45ms TTL=250
Reply from 212.159.6.10: bytes=32 time=74ms TTL=250
Reply from 212.159.6.10: bytes=32 time=40ms TTL=250
Reply from 212.159.6.10: bytes=32 time=40ms TTL=250
Reply from 212.159.6.10: bytes=32 time=40ms TTL=250
Reply from 212.159.6.10: bytes=32 time=75ms TTL=250
Reply from 212.159.6.10: bytes=32 time=40ms TTL=250
Reply from 212.159.6.10: bytes=32 time=39ms TTL=250
Reply from 212.159.6.10: bytes=32 time=39ms TTL=250
Reply from 212.159.6.10: bytes=32 time=74ms TTL=250
Reply from 212.159.6.10: bytes=32 time=39ms TTL=250
Reply from 212.159.6.10: bytes=32 time=40ms TTL=250
Reply from 212.159.6.10: bytes=32 time=40ms TTL=250
Reply from 212.159.6.10: bytes=32 time=74ms TTL=250
Reply from 212.159.6.10: bytes=32 time=39ms TTL=250
Reply from 212.159.6.10: bytes=32 time=40ms TTL=250
Reply from 212.159.6.10: bytes=32 time=39ms TTL=250
Reply from 212.159.6.10: bytes=32 time=75ms TTL=250
Reply from 212.159.6.10: bytes=32 time=39ms TTL=250
Reply from 212.159.6.10: bytes=32 time=39ms TTL=250
Reply from 212.159.6.10: bytes=32 time=39ms TTL=250
Reply from 212.159.6.10: bytes=32 time=76ms TTL=250
Reply from 212.159.6.10: bytes=32 time=40ms TTL=250
Reply from 212.159.6.10: bytes=32 time=39ms TTL=250
Reply from 212.159.6.10: bytes=32 time=40ms TTL=250
Reply from 212.159.6.10: bytes=32 time=80ms TTL=250
Reply from 212.159.6.10: bytes=32 time=39ms TTL=250
Reply from 212.159.6.10: bytes=32 time=39ms TTL=250
Reply from 212.159.6.10: bytes=32 time=40ms TTL=250
Reply from 212.159.6.10: bytes=32 time=123ms TTL=250
Reply from 212.159.6.10: bytes=32 time=40ms TTL=250
Reply from 212.159.6.10: bytes=32 time=40ms TTL=250
Reply from 212.159.6.10: bytes=32 time=39ms TTL=250
Reply from 212.159.6.10: bytes=32 time=79ms TTL=250
Reply from 212.159.6.10: bytes=32 time=40ms TTL=250
Reply from 212.159.6.10: bytes=32 time=39ms TTL=250
Reply from 212.159.6.10: bytes=32 time=39ms TTL=250
Reply from 212.159.6.10: bytes=32 time=80ms TTL=250
Reply from 212.159.6.10: bytes=32 time=39ms TTL=250
Reply from 212.159.6.10: bytes=32 time=39ms TTL=250
Reply from 212.159.6.10: bytes=32 time=41ms TTL=250