Packet loss in evenings, 21CN ADSL

[#1]

pathping is available in Windows and will show where packet loss occurs.

[#2]

See reply #21 for pathping results.

[#3]

Ok, that doesn't point to anything really, apart from that the gateway isn't responding to every icmp request,and there is no packet loss @  cdns01.plus.net, Can you try a pathping to the bbc.co.uk or pingbox1.thinkbroadband.com
You could also posibly be able to see  where the packet loss is on the return leg by using the traceroute utility on tbb web site http://www.thinkbroadband.com/tools/traceroute.html it may give a clue or it may not

[#4]

@deathtrap
Tracing route to pingbox1.thinkbroadband.com [80.249.99.164]
over a maximum of 30 hops:
  0  PMB1.lan [192.168.0.3]
  1  dsldevice.lan [192.168.0.101]
  2  lo0-central10.ptn-ag02.plus.net [195.166.128.191]
  3  link-b-central10.ptn-gw02.plus.net [212.159.2.134]
  4  xe-1-2-0.ptw-cr02.plus.net [212.159.0.114]
  5  lonap-gw1.thdo.ncuk.net [5.57.80.142]
  6  gi1-24-10-star1.core-rs2.thdo.ncuk.net [80.249.97.9]
  7  pingbox1.thinkbroadband.com [80.249.99.164]
Computing statistics for 175 seconds...
            Source to Here  This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                          PMB1.lan [192.168.0.3]                                0/ 100 =  0%  |
  1    0ms    0/ 100 =  0%    0/ 100 =  0%  dsldevice.lan [192.168.0.101]                                9/100 9%  |
  2  16ms    9/ 100 =  9%    0/ 100 =  0%  lo0-central10.ptn-ag02.plus.net [195.166.128.191]  3/ 100 =  3%  |
  3  10ms    16/ 100 = 16%    4/ 100 =  4%  link-b-central10.ptn-gw02.plus.net [212.159.2.134]  0/ 100 =  0%  |
  4  11ms    12/ 100 = 12%    0/ 100 =  0%  xe-1-2-0.ptw-cr02.plus.net [212.159.0.114]                  0/ 100 =  0%  |
  5  11ms    19/ 100 = 19%    7/ 100 =  7%  lonap-gw1.thdo.ncuk.net [5.57.80.142]                          0/ 100 =  0%  |
  6  12ms    12/ 100 = 12%    0/ 100 =  0%  gi1-24-10-star1.core-rs2.thdo.ncuk.net [80.249.97.9]  6/ 100 =  6%  |
  7  10ms    18/ 100 = 18%    0/ 100 =  0%  pingbox1.thinkbroadband.com [80.249.99.164]
Trace complete.
Tracing route to bbc.co.uk [212.58.246.104]
over a maximum of 30 hops:
  0  PMB1.lan [192.168.0.3]
  1  dsldevice.lan [192.168.0.101]
  2  lo0-central10.ptn-ag02.plus.net [195.166.128.191]
  3  link-b-central10.ptn-gw02.plus.net [212.159.2.134]
  4  xe-1-2-0.ptw-cr02.plus.net [212.159.0.114]
  5  ae2.ptw-cr01.plus.net [195.166.129.4]
  6  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
  7    *        *        *
Computing statistics for 150 seconds...
            Source to Here  This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                          PMB1.lan [192.168.0.3]                                0/ 100 =  0%  |
  1    0ms    0/ 100 =  0%    0/ 100 =  0%  dsldevice.lan [192.168.0.101]                              10/ 100 = 10%  |
  2  20ms    14/ 100 = 14%    4/ 100 =  4%  lo0-central10.ptn-ag02.plus.net [195.166.128.191]        0/ 100 =  0%  |
  3  10ms    11/ 100 = 11%    1/ 100 =  1%  link-b-central10.ptn-gw02.plus.net [212.159.2.134]        0/ 100 =  0%  |
  4  11ms    16/ 100 = 16%    6/ 100 =  6%  xe-1-2-0.ptw-cr02.plus.net [212.159.0.114]                        0/ 100 =  0%  |
  5  11ms    10/ 100 = 10%    0/ 100 =  0%  ae2.ptw-cr01.plus.net [195.166.129.4]                            12/ 100 = 12%  |
  6  10ms    22/ 100 = 22%    0/ 100 =  0%  kingston-gw.thdo.bbc.co.uk [212.58.239.6]
Trace complete.

[#5]

Well that is more conclusive there is a issue at network level , more than likely down to capacity or the lack of  somewhere , and because it is on the gateway hop, it could be  at plusnets handover point (where bt wholesale ends) or part of BT's network inc virtual paths at the exchange, or it's a peering issue of some kind,
But the exchange vp or handover point are  probably favourite ,

[#6]

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host                                      -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------------------|------|---- --|------|------|------|------|
|                           dsldevice.lan -                       0 |   89 |   89 |    0 |    0 |    1 |    0 |
|         lo0-central10.ptn-ag02.plus.net -      27 |   46 |   34 |    9 |   19 |  131 |    9 |
|      link-b-central10.ptn-gw02.plus.net -    10 |   66 |   60 |    9 |    9 |   15 |    9 |
|              xe-1-2-0.ptw-cr02.plus.net -           32 |   41 |   28 |    8 |   13 |   26 |    9 |
|                 lonap-gw1.thdo.ncuk.net -           14 |   58 |   50 |    8 |    9 |   41 |    9 |
|  gi1-24-10-star1.core-rs2.thdo.ncuk.net - 14 |   58 |   50 |    0 |   11 |   20 |   11 |
|             pingbox1.thinkbroadband.com -     20 |   50 |   40 |    0 |    9 |   11 |    9 |
|________________________________________________|______|______|______|______|______|______|
  WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

[#7]

@deathtrap
I agree with your conclusion.
From my original post on 15 Jan 2014

Quote

What could be causing this, exchange congestion? If so how do I go about getting it reported to BTw? Can anyone suggest other possibilities?

Just have to continue pushing the problem back to Plusnet I guess.

[#8]

Needs pushing back into BTW

[#9]

Quote

20CN virtual paths: Green There are currently no known 20CN VP capacity problems on your exchange. There may still be an exchange problem, however BT are not currently reporting that they are aware of it. Please contact Support if you are having speed problems, who can advise further. Record last updated: 31 Jan 14 Historical information for this exchange: Status Date amber 03 Jan 14 green 05 Dec 13

Just noticed the above change from Amber back to Green in the Plusnet Exchange Status Checker for Mogador.
Shame I am on 21CN.
Suspect that Users might have been moved from 20CN to 21CN over this period therefore moving the problem in the same way.
21CN went live for this exchange in mid November 2013.
@Kelly
Since my contract is with Plusnet it is their (your) responsibility to push it back to BTW.

[#10]

Yes.  I'm looking at this.

[#11]

@ Kelly
Very many thanks for your update.
Out of interest is there anything showing up for the Mogador exchange on the traffic management platform monitoring? http://community.plus.net/exchange-information/

[#12]

We're seeing packet loss at you exchange.  We don't have a large number of users there though.  Dave is investigating.

[#13]

Small exchange, only got 21CN in November 2013.
Waiting for FTTC as part of Superfast Surrey BDUK funding.
SamKnows says: 1,712 residential premises, 44 non-residential premises

[#14]

Dave is going to speak to our suppliers regarding this. We'll let you know when we got more information on it for you.

[#15]

@Chris.
Thanks for the update. Will let my neighbour, who is also with Plusnet, know.