Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    40 ms    39 ms    39 ms  lo0-plusnet.pte-ag2.plus.net [195.166.128.72]
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *     2941 ms  212.58.238.149
  7    40 ms    39 ms    38 ms  virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

C:\Users\James>tracert 212.159.13.50

Tracing route to pth-cdns02.plus.net [212.159.13.50]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    51 ms    47 ms    44 ms  lo0-plusnet.pte-ag2.plus.net [195.166.128.72]
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13  1486 ms    43 ms    39 ms  pth-cdns02.plus.net [212.159.13.50]

Trace complete.

Seems to have improved but still not right
Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    43 ms    43 ms    42 ms  lo0-plusnet.pte-ag2.plus.net [195.166.128.72]
  3   220 ms   112 ms    52 ms  ge0-0-0-504.pte-gw2.plus.net [84.92.4.90]
  4    48 ms    46 ms    47 ms  vl23.thn-gw2.plus.net [212.159.4.20]
  5    43 ms    46 ms    43 ms  rt0.thdo.bbc.co.uk [212.58.239.25]
  6    39 ms    40 ms    41 ms  212.58.238.149
  7    39 ms    39 ms    40 ms  virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

[AOL] Me too [/AOL]

It's been bad all evening - since around 1900 anyway and I just about managed to get this tracert


before it ground to a complete halt about 1/2 hour ago.  I had no data transfer whatsoever to anywhere at all for around 10/15 mins followed by several minutes of sometimes it sort-of works sometimes it doesn't.  It's working again at the mo but   v...e...r...y.......s...l...o...w...l...y   so am posting this real quick in case it all goes totally t*tsup again real soon !!

PS: Same gateway as you it would appear so maybe a reboot is called for 

PPS: May or may not be related but eBay in particular has been virtually unusable every evening this week 1900-2300 (ish) as well but fine during the day and reasonably OK during the night. V.strange.

Just got this, when I couldn't send e-mails nor load Plusnet front page without three tries:

Tracing route to portal.plus.net [212.159.9.2]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  192.168.0.1
  2    26 ms    27 ms    25 ms  lo0.plusnet.thn-ag2.plus.net [195.166.128.93]
  3   126 ms    44 ms    34 ms  vl604.thn-gw1.plus.net [84.92.4.169]
  4   190 ms   208 ms   214 ms  te2-3.thn-gw2.plus.net [212.159.1.58]
  5   200 ms   141 ms    59 ms  vl23.pte-gw2.plus.net [212.159.4.28]
  6    32 ms    35 ms    32 ms  92.core.plus.net [212.159.1.92]
  7    59 ms    46 ms    31 ms  fhw-lb04.plus.net [212.159.1.146]
  8  1058 ms    30 ms    31 ms  portal.plus.net [212.159.9.2]

Trace complete.

Several odd times over the last couple of days it's been very sluggish, but not consistently enough for me to report it

This morning so far, my RSS Plusnet Service Status feed has failed to load as well.

Speeds seem to be back to normal again at present, though.

Erhm .... what exactly is going on in PN Towers at the mo ?  This week seems to be following on from where last week left off so far as strange and unexplained problems are concerned

Evening performance is pretty dire. DNS frequently taking a dogs age to respond, a number of several minute periods of no data transfer whatsoever, generally slow and unresponsive browsing for perhaps the majority of the time (although by no means all of the time),  intermittent problems accessing mail, ftp and PN home page, PN homepages apparently not reliably accessible from other networks either and now I find that webspace logfiles don't appear to have been generated overnight for yesterday as well 

Is this a BW or internal routing style problem or is something somewhere perhaps about to go completely t*tsup fairly soon ?

Absolutely no changes here: same connection, same gateway and same settings (incl DNS) as I've been using for several weeks if not months now.  No exchange, line or router problems either, everything is just fine at this end but the service is becoming next to useless at peak(ish) times.  I'm on pte-ag2 and using 212.159.13.49/50 as usual for DNS.

Everything is mostly fine right now, as it was yesterday daytime, but I expect that come tonight it will be more than a bit of a challenge to do anything remotely useful again.

Honestly not sure.

Look at the amount of capacity we've added in the last 6-8 weeks.  We've added 5 or 6 additional 155Mbps segments and I believe another one is going in next week.

I'll make sure that the DNS concerns are raised in the daily meeting today.

In my case there are no DNS problems because I have OpenDNS hard coded as a secondary to Plusnet

I am having the same sort of issues daytime is fine come night night browsing is so much slower , having to reload some pages due to not loading at all.  last night was quite bad just like mikeb, i was also having minutes where there was no data transfer .

i was trying to stream the following video early hours of this morning and it just kept buffering

http://www.thesun.co.uk/s...emergency-war-debate.html

Regards Mike

What I get is an almost instant DNS response (that much I can read from wireshark) and then its just treacle from there on in. Sometimes the target site starts "chatting" immediately, sometimes it can be silly times like 9 seconds before the target sends anything back (look at the capture I posted the other day).

I'm using a mix of PN DNS servers and OpenDNS servers through a local install of dnsmasq.

Have raised an internal problem so we can get some investigation underway (ref: 58439).

Not convinced it's a DNS issue especially in light of Steve's comments and some of the traceroute which seem to be timing out at the hop where the traffic management switches are. We did a quick health check on these yesterday and couldn't spot anything glaringly obvious but I guess we may have missed something.

There seems to be a few too many reports of problems here for something not to be wrong


Can you point me in the direction of that post Steve?

I had a similar issue last night with some sites, but downloading an update of Growl (5MB) took 12 minutes.
Facebook and ebay were particularly bad. P2P wasn't good.
VPN and IRC were fine.

EDIT: Only using OpenDNS

Sure, its :

http://community.plus.net...ex.php/topic,79517.0.html

I'm no wireshark expert so I might be missing something but...

FB was terrible but as a couple of friends in the US are having problems too that might not all be down to PN.

FB is frequently terrible for me. Thanks for the link Steve.

Bob,
If I see the problem again would a wireshark log help