Peak time latency spikes

[#1]

ptw-ag04

[#2]

You are currently connected to gateway ptw-ag03.

[#3]

Can I ask you to do a traceroute too please?

[#4]

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.246.95]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    21 ms    20 ms    41 ms  lo0-central10.ptw-ag03.plus.net [195.166.128.197
]
  3    59 ms    51 ms    48 ms  link2-central10.ptw-gw02.plus.net [84.93.248.66]
  4    62 ms    44 ms    64 ms  xe-7-2-0.ptw-cr02.plus.net [212.159.1.22]
  5    67 ms    94 ms    58 ms  ae2.ptw-cr01.plus.net [195.166.129.4]
  6    33 ms    32 ms    31 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
  7    *        *        *    Request timed out.
  8    71 ms    69 ms    70 ms  ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
  9    54 ms    52 ms    49 ms  132.185.255.165
10    42 ms    39 ms    39 ms  bbc-vip016.cwwtf.bbc.co.uk [212.58.246.95]
Trace complete.

[#5]

Quote from: Anotherone

Edit: I thought all VoIP traffic was Titanium? Edit2: Unless the Upstream is the source of the VoIP issue?? (graph won't apply then)

For some reason we haven't been able to work out, when Jelv uses xlite, it doesn't identify properly. 😕
Jelv:  Have you got us a new capture to send over?  

Quote from: Anotherone

So there's 3 of us here on 20CN connections seeing the latency peaks (no worse than any one else?) but the Speed impacts (on 2 of us at least) certainly aren't as severe as the faster connection, Fibre in particular, as mentioned by Kelly IIRC. I'll have to run some time sensitive apps at the peak times to see what the effects are on packet drops. I'm normally only doing a bit of browsing at those times. My latency increases seem to be consistent with the general pattern, although there are obviously some related to my own activity, but I get an odd few at assorted times which I suspect may be due to activity through the local exchange - the VP status has been Green for a long time, but that doesn't mean there isn't congestion - putting my cynic hat on, if there is any congestion on my exchange, I don't believe BT will own up until it get's that bad that they have no option as occurred a few years back when we had to make a sort of "class" complaint to BT (because it was spread across various ISPs - Market 1 exchange!).

20CN has been much busier than it should be recently.   Dave is working to correct that.  This is why I think Jelv, Purleigh. (and someone else... possibly I.T. Works) have been seeing some increase in latency or slowdowns at peak.
With people on WBC, we just aren't seeing congestion on our platform.

[#6]

Quote from: Bright

Just to clarify... by "either" do you mean latency and packet loss? Or high buffer utilisation? Or all three?

On the WBC platform we aren't seeing packet loss or latency that is significant.  Buffer utilisation will directly = latency.

[#7]

Quote from: jelv

During the evenings I'm finding that the sound quality on VoIP calls is absolutely dreadful - at best it's just about usable but quite a bit of distortion, at worst it drops out altogether for seconds at a time. Looking at the latency graph I can see why!

Yeah, so because some of your xlite packets are being forced down into the best effort queue, plus the tightness we are running IPSC at right now (which we are remedying) means that some of these packets get buffered, hence the spikes in latency on that graph

[#8]

Tracing route to bbc.co.uk [212.58.241.131]
over a maximum of 30 hops:
  0  SERVER.lan [192.168.1.70] 
  1  dsldevice.lan [192.168.1.254] 
  2  lo0-central10.ptw-ag04.plus.net [195.166.128.194] 
  3  link13-central10.ptw-gw01.plus.net [84.93.248.120] 
  4  xe-10-0-0.ptw-cr01.plus.net [212.159.1.40] 
  5  ae2.ptw-cr02.plus.net [195.166.129.5] 
  6  ae2.ptw-cr01.plus.net [195.166.129.4] 
  7  kingston-gw.thdo.bbc.co.uk [212.58.239.6] 
  8     *        *        *     
Computing statistics for 175 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           SERVER.lan [192.168.1.70] 
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  dsldevice.lan [192.168.1.254] 
                                0/ 100 =  0%   |
  2   23ms     0/ 100 =  0%     0/ 100 =  0%  lo0-central10.ptw-ag04.plus.net [195.166.128.194] 
                                0/ 100 =  0%   |
  3   14ms     0/ 100 =  0%     0/ 100 =  0%  link13-central10.ptw-gw01.plus.net [84.93.248.120] 
                                0/ 100 =  0%   |
  4   11ms     0/ 100 =  0%     0/ 100 =  0%  xe-10-0-0.ptw-cr01.plus.net [212.159.1.40] 
                                0/ 100 =  0%   |
  5   11ms     0/ 100 =  0%     0/ 100 =  0%  ae2.ptw-cr02.plus.net [195.166.129.5] 
                                0/ 100 =  0%   |
  6   10ms     1/ 100 =  1%     1/ 100 =  1%  ae2.ptw-cr01.plus.net [195.166.129.4] 
                                0/ 100 =  0%   |
  7    9ms     0/ 100 =  0%     0/ 100 =  0%  kingston-gw.thdo.bbc.co.uk [212.58.239.6] 
Trace complete.

Down to 2Mb now:

[#9]

Quote from: kareha

Touch wood but my peak time latency seemed to disappear last night due to my Max Premium service being switched back on.  Will see how it is tonight whilst I'm gaming.

Which to me, suggested BT congestion.  Your traffic is now elevated over the BT platform 😕

[#10]

Speed is dropping rather rapidly now

[#11]

For information: I'm on Max Premium so it's unlikely anything I'm seeing is down to BT congestion. Also, my exchange has a pretty good history: http://usertools.plus.net/exchanges/?exchange=Mere&exact=4464&plugin=vp&etashow=yes&full=1

[#12]

No problems here (so far), TTB graph peaks are quite low, normal ping times, and speedtest is only 5% down from maximum. 

[#13]

30 mins later speed still dropping  bt wholesale speed tester also showing the same result but is not allowing me to run further diagnostics.
Updated tracert report.
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.66]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2  185 ms  114 ms    34 ms  lo0-central10.ptw-ag03.plus.net [195.166.128.197
]
  3  225 ms  197 ms    76 ms  link12-central10.ptw-gw02.plus.net [84.93.248.86
]
  4    49 ms    45 ms    58 ms  xe-7-2-0.ptw-cr02.plus.net [212.159.1.22]
  5    68 ms    78 ms    76 ms  ae2.ptw-cr01.plus.net [195.166.129.4]
  6    47 ms    44 ms    37 ms  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
  7    *        *        *    Request timed out.
  8    *        *        *    Request timed out.
  9    51 ms    59 ms    55 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]
10    75 ms    82 ms    74 ms  132.185.255.148
11    65 ms    69 ms    69 ms  bbc-vip111.telhc.bbc.co.uk [212.58.244.66]
Trace complete.
C:\Users\Private>

[#14]

Quote from: Kelly

For some reason we haven't been able to work out, when Jelv uses xlite, it doesn't identify properly. 😕 Jelv:  Have you got us a new capture to send over?

New capture of X-lite startup and check voice mail added to the open ticket.
Presumably with the Pro add-on the unidentified traffic would be gold which might improve things and you'd still be able to see the issue as it should be titanium.

[#15]

Quote from: Kelly

On the WBC platform we aren't seeing packet loss or latency that is significant.   Buffer utilisation will directly = latency.

So this problem only affects customers on 20CN IPSC products?
The latency graphs for yesterday evening showed the same increased latency for bronze and best efforts queues on WBC as on IPSC, I thought. Although tonight the WBC graphs look OK