Huge intermittent peak time packet loss

[#1]

Anyone on ADSL2+ having trouble at peak time ~ (18:00-02:00) I know theres prioritisation trouble happening but lately I haven't been able to even browse websites or get email.
I've also noticed that my upstream sync has become stuck on 440kbps. Usualy it fluctuated around 800+
Are there any other problems plusnet are having which haven't been reported which sound like mine?

[#2]

I have the same problem, between 6 and 2 it's so intermittent, it can be fine for 10 minute then absolute rubbish. Pages take forever to load, often have to be loaded several times, and to make matters worse I keep getting a really rubbish ping for my gaming, I'm tempted to move from Plusnet to Virgin if it doesn't improve soon. Odd thing is it started when the 21CN upgrade in my area did, improved for a few days after and its now back to being rubbish again.

[#3]

Mines not great either since moving to ADSL2+ ... sometimes gaming i can get really bad lag... although downloading seems fine most of the time
Think ill stick it out because on the status pages it says there is a problem and they are looking to the vendors of the routers for a fix

[#4]

I've also experienced my upstream getting stuck at 440 (443 in my case, if I remember correctly) for no apparent reason, when it was normally around 800. You could check with Plusnet to make sure they haven't put on any restrictions, but if that's not the case you might just have to wait. My upstream speed went up to 665 after about a fortnight, then returned to its normal 800+ range a couple of weeks later.
Graham

[#5]

Still the same, frankly I'm getting sick of it, no update on when this will be resolved, almost a month now its been like this. If it doesn't get any better soon I'll just pay the money and move to Virgin.

[#6]

I've also been getting this for about a month now and it's driving me insane: I am currently paying for a service that I can all but guarantee I won't be able to use most nights. Gateway hopping doesn't work; I can successfully ping and traceroute through to servers but cannot get any web traffic, email or anything else. It seems to be a problem with the gateways, as the packet loss (around 30%) from pings is the same to the gateway as it is to further out on the network.
Here are some traceroute logs from last night:

traceroute: Warning: www.google.com has multiple addresses; using 216.239.59.104
traceroute to www.l.google.com (216.239.59.104), 64 hops max, 52 byte packets
 1  voyager.home (192.168.1.1)  8.079 ms  1.728 ms  1.610 ms
 2  * lo0.homesurf.thn-ag2.plus.net (195.166.128.94)  27.942 ms  27.451 ms
 3  * * vl605.thn-gw1.plus.net (84.92.4.177)  28.997 ms
 4  te3-2.ptn-gw01.plus.net (212.159.1.53)  32.197 ms  27.125 ms  27.298 ms
 5  te3 (212.159.1.110)  27.104 ms  26.547 ms  28.098 ms
 6  195.66.226.125 (195.66.226.125)  26.792 ms  27.305 ms  27.793 ms
 7  209.85.255.175 (209.85.255.175)  82.330 ms  27.457 ms *
 8  209.85.251.190 (209.85.251.190)  40.790 ms *
    209.85.250.216 (209.85.250.216)  45.298 ms
 9  72.14.232.241 (72.14.232.241)  44.107 ms *  62.452 ms
10  216.239.49.126 (216.239.49.126)  54.647 ms  52.707 ms  53.929 ms
11  www.l.google.com (216.239.59.104)  41.629 ms  41.802 ms  41.809 ms
traceroute: Warning: www.google.com has multiple addresses; using 216.239.59.104
traceroute to www.l.google.com (216.239.59.104), 64 hops max, 52 byte packets
 1  voyager.home (192.168.1.1)  2.147 ms  1.585 ms  1.623 ms
 2  lo0.homesurf.thn-ag2.plus.net (195.166.128.94)  28.628 ms *  28.073 ms
 3  vl605.thn-gw1.plus.net (84.92.4.177)  27.497 ms  27.733 ms  27.275 ms
 4  te3-2.ptn-gw01.plus.net (212.159.1.53)  27.074 ms  27.673 ms  27.292 ms
 5  * te3 (212.159.1.110)  30.909 ms  27.321 ms
 6  195.66.226.125 (195.66.226.125)  28.598 ms  27.041 ms  27.548 ms
 7  * * 209.85.255.175 (209.85.255.175)  30.054 ms
 8  209.85.250.216 (209.85.250.216)  43.368 ms  45.702 ms  42.549 ms
 9  * 72.14.232.241 (72.14.232.241)  47.310 ms  44.300 ms
10  216.239.49.126 (216.239.49.126)  42.620 ms  48.700 ms  52.635 ms
11  www.l.google.com (216.239.59.104)  42.819 ms  41.316 ms  41.448 ms
traceroute: Warning: www.google.com has multiple addresses; using 216.239.59.104
traceroute to www.l.google.com (216.239.59.104), 64 hops max, 52 byte packets
 1  voyager.home (192.168.1.1)  1.815 ms  1.592 ms  1.571 ms
 2  * lo0-homesurf.pcl-ag04.plus.net (195.166.128.135)  30.883 ms  32.344 ms
 3  gi1-7-605.pcl-gw01.plus.net (84.92.0.233)  29.655 ms  31.688 ms *
 4  * te2-2.pte-gw1.plus.net (212.159.0.186)  32.723 ms  29.733 ms
 5  te2-4.pte-gw2.plus.net (212.159.1.102)  32.388 ms  29.877 ms *
 6  195.66.224.125 (195.66.224.125)  32.426 ms  31.185 ms  30.170 ms
 7  64.233.175.27 (64.233.175.27)  32.883 ms  73.497 ms  30.254 ms
 8  209.85.251.190 (209.85.251.190)  40.503 ms  41.928 ms *
 9  * 66.249.95.169 (66.249.95.169)  46.738 ms  48.477 ms
10  * * *
11  www.l.google.com (216.239.59.104)  45.282 ms  44.989 ms *

I raised a ticket but was told that PN can't find any faults and that I might be charged £170 if they raise it with BT  

[#7]

Still the same for me. Have switched routers and microfilters, connected to master socket, still no change. As far as my router is concerned I am connected. A quiet line test brings up nothing. Sending a ticket off now.

[#8]

Bojangles, if you're at your computer now could you try pinging the gateway and posting up what you find? I have a theory but am not at home to test....

[#9]

Nothing out of the ordinary. It doesn't get bad till after 18:00
Tracing route to plus.net [212.159.9.2]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  my.router [192.168.1.1]
  2    32 ms    34 ms    34 ms  lo0.plusnet.thn-ag2.plus.net [195.166.128.93]
  3    48 ms    32 ms    32 ms  vl604.thn-gw1.plus.net [84.92.4.169]
  4    37 ms    33 ms    45 ms  vl22.pte-gw1.plus.net [212.159.4.11]
  5    35 ms    33 ms    33 ms  te2-2.pcl-gw01.plus.net [212.159.0.185]
  6    39 ms    39 ms    39 ms  gi5-8.ptp-cr01.plus.net [84.93.224.48]
  7    39 ms    39 ms    40 ms  vlan2657.ptp-elb01.plus.net [84.93.224.36]
  8    41 ms    40 ms    39 ms  portal.plus.net [212.159.9.2]
Trace complete.
C:\Documents and Settings\Jonathan>ping -t 195.166.128.93
Pinging 195.166.128.93 with 32 bytes of data:
Reply from 195.166.128.93: bytes=32 time=34ms TTL=126
Reply from 195.166.128.93: bytes=32 time=33ms TTL=126
Reply from 195.166.128.93: bytes=32 time=33ms TTL=126
Reply from 195.166.128.93: bytes=32 time=32ms TTL=126
Reply from 195.166.128.93: bytes=32 time=32ms TTL=126
Reply from 195.166.128.93: bytes=32 time=33ms TTL=126
Reply from 195.166.128.93: bytes=32 time=32ms TTL=126
Reply from 195.166.128.93: bytes=32 time=32ms TTL=126
Reply from 195.166.128.93: bytes=32 time=41ms TTL=126
Reply from 195.166.128.93: bytes=32 time=33ms TTL=126
Reply from 195.166.128.93: bytes=32 time=34ms TTL=126
Reply from 195.166.128.93: bytes=32 time=33ms TTL=126
Reply from 195.166.128.93: bytes=32 time=33ms TTL=126
Reply from 195.166.128.93: bytes=32 time=33ms TTL=126
Reply from 195.166.128.93: bytes=32 time=33ms TTL=126
Reply from 195.166.128.93: bytes=32 time=33ms TTL=126
Reply from 195.166.128.93: bytes=32 time=32ms TTL=126
Reply from 195.166.128.93: bytes=32 time=32ms TTL=126
Reply from 195.166.128.93: bytes=32 time=32ms TTL=126
Reply from 195.166.128.93: bytes=32 time=32ms TTL=126
Reply from 195.166.128.93: bytes=32 time=33ms TTL=126
Reply from 195.166.128.93: bytes=32 time=32ms TTL=126
Reply from 195.166.128.93: bytes=32 time=32ms TTL=126
Reply from 195.166.128.93: bytes=32 time=33ms TTL=126
Reply from 195.166.128.93: bytes=32 time=33ms TTL=126
Reply from 195.166.128.93: bytes=32 time=35ms TTL=126
Reply from 195.166.128.93: bytes=32 time=53ms TTL=126
Reply from 195.166.128.93: bytes=32 time=32ms TTL=126
Reply from 195.166.128.93: bytes=32 time=32ms TTL=126
Reply from 195.166.128.93: bytes=32 time=32ms TTL=126
Reply from 195.166.128.93: bytes=32 time=32ms TTL=126
Reply from 195.166.128.93: bytes=32 time=32ms TTL=126
Reply from 195.166.128.93: bytes=32 time=33ms TTL=126
Reply from 195.166.128.93: bytes=32 time=32ms TTL=126
Reply from 195.166.128.93: bytes=32 time=34ms TTL=126
Reply from 195.166.128.93: bytes=32 time=33ms TTL=126
Reply from 195.166.128.93: bytes=32 time=33ms TTL=126
Reply from 195.166.128.93: bytes=32 time=33ms TTL=126
Reply from 195.166.128.93: bytes=32 time=32ms TTL=126
Ping statistics for 195.166.128.93:
    Packets: Sent = 39, Received = 39, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 32ms, Maximum = 53ms, Average = 33ms

[#10]

Ah, of course, I forgot that it's intermittent 
Assuming it goes at some point tonight, try measuring the ping results with different size packets (specifically, try 8 bytes, 16 bytes, 64 bytes, 128 bytes, 256 bytes and 512 bytes). I'll do the same.

[#11]

Out of interest what routers/modems are you using for thse with problems?

[#12]

YAY! Another night of dial-up style broadband, I think what I'm going to do is just write letters to all the websites I normally visit asking if they can write back with all the news and information since it would be faster and more convienient for me.

[#13]

Quote from: badwolf

Out of interest what routers/modems are you using for thse with problems?

Mine's a beat-up old BT Voyager 2100. Convinced it's not the problem, though.
Interestingly my connection stayed fine all last night...

[#14]

Bojangles: Having same peak time probs as you. Mine start around 15.00, and only since upgrading to ADSL2+ a couple of weeks ago. Download speeds 90kbps! Non peak:6500+ kbps.
I'm in contact with PN about it.
Cheers

[#15]

Mine was strangely fine last night. Starting to think it might be something to do with outside interference, we've also had trouble with our central heating control system not being able to communicate with the boiler.
Primary router is a Draytek Vigor 2800V, have also used a Netgear DG834.