cancel
Showing results for 
Search instead for 
Did you mean: 

Peak time packet loss on ptw-bng01

beeceegee
Pro
Posts: 611
Thanks: 75
Fixes: 4
Registered: ‎27-11-2012

Re: Peak time packet loss on ptw-bng01

I'm on  ptw-bng01

I've been away over easter with just a couple of webcams running internally, so no serious traffic being generated (as proved by the rest of the period), but yesterday's graph shows exactly the same profile (and has done for many days) and looks like today's will be no different, apart from normal traffic as we are now home

jimbof
Grafter
Posts: 348
Thanks: 2
Registered: ‎02-05-2013

Re: Peak time packet loss on ptw-bng01

It actually looks worse tonight than last night; that IPTV test I was running is now showing almost 5% packet loss for UDP traffic.
mrcoyote
Dabbler
Posts: 21
Registered: ‎15-12-2012

Re: Peak time packet loss on ptw-bng01

Another one on ptw-bng01 here Sad
AndyH
Grafter
Posts: 6,824
Thanks: 1
Registered: ‎27-10-2012

Re: Peak time packet loss on ptw-bng01

Is anyone seeing any issues with performance (ignoring the BQMs for the moment)? Websites slow? Streaming video buffering? Gaming lag?
mrcoyote
Dabbler
Posts: 21
Registered: ‎15-12-2012

Re: Peak time packet loss on ptw-bng01

Not tried any streaming, but random sites are slow to load.
jimbof
Grafter
Posts: 348
Thanks: 2
Registered: ‎02-05-2013

Re: Peak time packet loss on ptw-bng01

Speed test results are pretty abysmal for me.
BT Wholesale:
"Download speed achieved during the test was - 17.47 Mbps
For your connection, the acceptable range of speeds is 40 Mbps-77.44 Mbps .
Additional Information:
IP Profile for your line is - 77.44 Mbps"
Wired gigabit from my machine to the router.  I usually get line speed pretty much.
AndyH
Grafter
Posts: 6,824
Thanks: 1
Registered: ‎27-10-2012

Re: Peak time packet loss on ptw-bng01

I don't think it's the actual gateway that's the problem. I tried pinging it 1,000 times and didn't get a single dropped packet.
--- 195.166.128.170 ping statistics ---
1000 packets transmitted, 1000 received, 0% packet loss, time 1000727ms
rtt min/avg/max/mdev = 3.976/5.281/23.062/1.346 ms
I would think it's the extension path/MSIL your traffic takes to Plusnet that's the issue.
jimbof
Grafter
Posts: 348
Thanks: 2
Registered: ‎02-05-2013

Re: Peak time packet loss on ptw-bng01

Well, whatever it is it seems to be affecting quite a lot of users.  If you took the Plusnet FTTC graphs on the TBB page as a representative sample, it looks like 1 in 7 users would be expected to be seeing poor performance this evening.
beeceegee
Pro
Posts: 611
Thanks: 75
Fixes: 4
Registered: ‎27-11-2012

Re: Peak time packet loss on ptw-bng01

Quote from: jimbof
It actually looks worse tonight than last night;

I think you are right

fortunately we are not gamers, but that really doesn't look great
deathtrap
Grafter
Posts: 1,064
Thanks: 4
Registered: ‎23-04-2013

Re: Peak time packet loss on ptw-bng01

The packet loss was only on usa servers that used Level3's peering transit,  that Steampowered IP address is only one that the steam client uses each time launch it, here's another IPit uses with an even higher  ping,
Target Name: 208-64-200-137.steampowered.com
        IP: 208.64.200.137
  Date/Time: 22/04/2014 02:30:54 to 22/04/2014 02:33:17
Hop Sent Err PL% Min Max Avg  Host Name / [IP]
1  144  0 0.0  0  0  0  home.gateway.home.gateway [192.168.1.254]
2  144  0 0.0  13 648  37  lo0-central10.ptw-ag04.plus.net [195.166.128.194]
3  144  0 0.0  12  25  13  link-b-central10.ptw-gw02.plus.net [212.159.2.158]
4  144  0 0.0  12  46  13  xe-7-2-0.ptw-cr02.plus.net [212.159.0.254]
5  144  0 0.0  13  40  14  ae2.ptw-cr01.plus.net [195.166.129.4]
6  144  0 0.0  12  36  13  ae1.pcl-cr01.plus.net [195.166.129.1]
7  144  0 0.0  13  69  14  xe-11-1-0.edge3.London2.Level3.net [212.187.201.209]
8  144  0 0.0 158 165 158  vl-3201-ve-128.ebr2.London2.Level3.net [4.69.202.177]
9  144  0 0.0 157 159 157  ae-44-44.ebr1.Paris1.Level3.net [4.69.159.94]
10  144  0 0.0 158 159 158  ae-61-61.csw1.Paris1.Level3.net [4.69.161.78]
11  144  0 0.0 158 160 158  ae-62-62.ebr2.Paris1.Level3.net [4.69.161.93]
12  144  0 0.0 159 164 159  ae-44-44.ebr2.Washington1.Level3.net [4.69.137.62]
13  139  0 0.0 159 166 159  ae-46-46.ebr2.Washington12.Level3.net [4.69.202.54]
14  144  0 0.0 159 166 159  ae-6-6.ebr2.Chicago2.Level3.net [4.69.148.146]
15  144  0 0.0 159 168 159  ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]
16  144  0 0.0 157 159 157  ae-3-3.ebr2.Denver1.Level3.net [4.69.132.61]
17  144  0 0.0 160 168 160  ae-2-2.ebr2.Seattle1.Level3.net [4.69.132.53]
18  144  0 0.0 160 221 162  ae-2-52.edge1.Seattle3.Level3.net [4.69.147.170]
19  144  0 0.0 159 189 160  CENTURYTEL.edge1.Seattle3.Level3.net [4.59.232.74]
20  144  0 0.0 160 164 160  [205.196.6.36]
21  144  0 0.0 160 161 160  208-64-200-137.steampowered.com [208.64.200.137]
Oh look it goes via paris and is 7ms higher than my other tracert that is routed in a more direct fashion , exactly the same effect it had on latency to Ubisoft.com Level 3 cack handed routing peering , must be the cheapest peering available  is all i can say , oh, and they won't fix it neither will Plusnet  just have a read of my thread in the gaming forum 5 mths  before they turned around and say they can't /wont do anything for me
Fortunately the packet loss did stop a short time after i reported it here, but it shouldn't be happening in the first place, if level3 didn't overload their links  perhaps it wouldn't happen , but  some will say and believe that this wont be the case
jimbof
Grafter
Posts: 348
Thanks: 2
Registered: ‎02-05-2013

Re: Peak time packet loss on ptw-bng01

@deathdrap
I feel your pain; though these are quite different issues I believe - the thinkbroadband traffic and BT wholesale speed test go no-where near level3.  All tests seem to be fine again this morning (BT wholesale, IPTV, TBB BQM). 
However, I do notice the IPTV test I was running (showing ~5% packet loss at worst) does go to the US via Level3, so that could have been affected by the issue you mention.  I guess the way to test that is to wait until I see the issue again and then hop gateway and run the IPTV test again.
I plan to stick it out on the current gateway until this evening to let the support guys pick up the extended details for my connection from the gateway, and see if it is still doing it tonight, and then hopping to another one.  That should get a bit more useful information.
RichardB
Seasoned Champion
Posts: 1,039
Thanks: 385
Fixes: 39
Registered: ‎19-11-2008

Re: Peak time packet loss on ptw-bng01

Hi
We were experiencing problems with streaming Love Film last week & i noticed the packet loss on my TBB ping graph.
I noticed I was connected to ptw-bng01 & reconnected to a pcl gateway,  then packet loss was no more, but I was not sure whether that was due to the peak time traffic being lower on Fridays & Saturdays.
I also had the same problem last night I noticed I was back on ptw-bng01 so jumped gateways again, whilst maintaining ADSL synch. Graph attached.
Pity I did not spot this thread as I would have remained connected to ptw-bng01 & flagged it here.
Richard
Kelly
Hero
Posts: 5,497
Thanks: 380
Fixes: 9
Registered: ‎04-04-2007

Re: Peak time packet loss on ptw-bng01

I've raised problem:80657 for us to have a look at. First glance of our end point graphing doesn't show an issue, so digging deeper.
Kelly Dorset
Ex-Broadband Service Manager
froggy666uk
Dabbler
Posts: 11
Registered: ‎25-04-2013

Re: Peak time packet loss on ptw-bng01

Quote from: AndyH
Is anyone seeing any issues with performance (ignoring the BQMs for the moment)? Websites slow? Streaming video buffering? Gaming lag?

I was experiencing random slow downs opening/accessing websites yesterday through the day and dropouts whilst listening to internet radio - was doing my head in!  Unfortunately I can't tell you if it was any worse in the evening as I was in bed by 6 after overdoing it on the gin and tonic Shocked  (Mine is one of the graphs on the community ping graphs sites - froggy666uk).
jimbof
Grafter
Posts: 348
Thanks: 2
Registered: ‎02-05-2013

Re: Peak time packet loss on ptw-bng01

Quote from: Kelly
I've raised problem:80657 for us to have a look at.

Cool.  I plan to wait til the middle of peak time, run some tests and perhaps gateway hop and test again.  Let me know if you would rather I stayed put.