High packet loss since 06:45 3rd Dec

[#1]

Title and sig TBB plot says it all.
Poor browsing responsiveness if there are sizeable graphics in the content - editing a post is fast, but displaying the result (with my sig for example) is painfully slow.  Line stats are excellent as ever.
Looking here - http://community.plus.net/ping-graphs/ - user 'rammie' shows an identical profile.  Our TBB plots are either side of Chris Parr's.  Note my service is now unlimited.
I am on the Hartford exchange, is by any chance rammie on the same exchange?  Could this be BTOR exchange congestion?
Please avoid intrusive tests - I would prefer to avoid dropping my 170 day xDSL session if possible please.  Service has been fine until 06:45 this morning.
Sam Knows white box stats to follow.
Thanks,
Kevin

[#2]

I've seen a couple of complaints in p.s.customer-feedback too. I suspect an issue with pcl-ag07.
Edit: internal problem raised (ref: 83886).

[#3]

Bob,
Thank you for the quick response.  That gateway has been so good - 71 days with no issues!  Are you sure that it is the edge and not something inside it?  Trace route looks good to the gateway, but quite poor on the subsequent links...

Traceroute to plus.net (212.159.8.2), 64 hops max.
1 dsldevice.lan (192.168.1.254) time=66 ms
2 lo0-central10.pcl-ag07.plus.net (195.166.128.188) time=33 ms
3 link-a-central10.pcl-gw01.plus.net (212.159.2.184) time=235 ms
4 xe-9-0-0.pcl-cr01.plus.net (212.159.0.216) time=215 ms
5 ae1.ptw-cr01.plus.net (195.166.129.0) time=240 ms
6 te9-4.ptn-gw01.plus.net (195.166.129.33) time=251 ms
7 gi5-1.peh-cr02.plus.net (84.93.232.61) time=245 ms
8 po5.peh-cr01.plus.net (84.93.232.16) time=454 ms
9 vlan2657.peh-elb01.plus.net (84.93.232.44) time=247 ms
10 portal.plus.net (212.159.8.2) time=51 ms 
*** Traceroute at destination ***

Kevin

[#4]

It's probably one of the line cards, I'll let you know once our engineers have gotten to the bottom of it though.

[#5]

Some line cards have been reseated and I believe the problem is now resolved.

[#6]

Hi Bob,
Thank you - a service notice has been published reporting the issue resolved (see http://usertools.plus.net/status/archive/1417618871.htm).  Ping time also massively better... but the routing is markedly different...

Tracing route to plus.net [212.159.9.2]
over a maximum of 30 hops:
  1     1 ms     1 ms     1 ms  dsldevice.lan [192.168.1.254]
  2    47 ms    82 ms    35 ms  lo0-central10.pcl-ag07.plus.net [195.166.128.188]
  3    34 ms    33 ms    33 ms  link-b-central10.pcl-gw02.plus.net [212.159.2.186]
  4    36 ms    34 ms    34 ms  xe-9-0-0.pcl-cr02.plus.net [212.159.0.218]
  5    33 ms    33 ms    33 ms  ae2.pcl-cr01.plus.net [195.166.129.6]
  6    34 ms    33 ms    33 ms  po2.pcl-gw01.plus.net [195.166.129.41]
  7    41 ms    39 ms    40 ms  gi5-8.ptp-cr01.plus.net [84.93.224.48]
  8    45 ms    43 ms    40 ms  vlan2657.ptp-elb01.plus.net [84.93.224.36]
  9    41 ms    39 ms    40 ms  portal.plus.net [212.159.9.2]
Trace complete.

xDSL and PPP sessions not interrupted and TBB BQM plot is back to normal.  Thank you for the prompt and tidy resolution.
Kevin

[#7]

The routing is different because the first was to 212.159.8.2 and the second was to 212.159.9.2 - different routes for different IP addresses.

[#8]

Doh!  Did not expect (and therefore did not look) for a different DNS address resolution through the same gateway.

[#9]

There are plenty of hostnames that resolve to more than one IP address, the gateway has nothing to do with that.

[#10]

I suspect the routing can be gateway dependant though.