just changed gateway from ptn-ag2 over to pcl-ag4 and things seem so fair, alot better !

Not sure why you've got that impression?

We are trying to collect examples, however it's not the easiest thing to replicate due to the intermittent nature. I also raised it in the daily operational meeting this morning to ensure that other areas of the business are aware of it.

The initial diagnosis was that this may have been caused by some recent updates at a number of exchanges, however your local exchange doesn't appear to have had this engineering work yet.

We're still investigating and I'll let you know any outcome.

I'm having trouble too.

Most websites fail to load unless I load them through a SOCKS5 proxy.

We've reloaded one of the traffic management switches as investigation showed it was having some problems. All the examples from the last couple of days were hitting that same switch as they were going through ptn-ag2.

Please let us know if you see the same issue again and include the tracerts, thanks.

I don't suppose I will attract much sympathy but I have had difficulty with this site today. At least it is not PN's router....

Tracing route to stocktradebroking.co.uk [195.11.221.105]

over a maximum of 30 hops:

1 27 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 36 ms 39 ms 35 ms lo0-plusnet.pcl-ag01.plus.net [195.166.128.27]
3 44 ms 37 ms 38 ms gi1-2-803.pcl-gw1.plus.net [84.92.5.57]
4 35 ms 41 ms 49 ms te2-2.pte-gw1.plus.net [212.159.0.186]
5 35 ms 35 ms 35 ms te2-4.pte-gw2.plus.net [212.159.1.102]
6 40 ms 34 ms 36 ms linx-1.router.demon.net [195.66.224.12]
7 37 ms 37 ms 38 ms anchor-core-1-g0-0-1.router.demon.net [194.70.98.5]
8 36 ms 35 ms 37 ms anchor-inside-1-g1-0-0.router.demon.net [194.70.98.10]
9 * * * Request timed out.

Seems to be a Demon.net problem tracert times out from Sky also.

Times out from work connection Nildram also..

In reply to a post by meldrew:

I don't suppose I will attract much sympathy but I have had difficulty with this site today. At least it is not PN's router....

Tracing route to stocktradebroking.co.uk [195.11.221.105]

over a maximum of 30 hops:

1 27 ms 99 ms 99 ms dsldevice.lan [192.168.1.254]
2 36 ms 39 ms 35 ms lo0-plusnet.pcl-ag01.plus.net [195.166.128.27]
3 44 ms 37 ms 38 ms gi1-2-803.pcl-gw1.plus.net [84.92.5.57]
4 35 ms 41 ms 49 ms te2-2.pte-gw1.plus.net [212.159.0.186]
5 35 ms 35 ms 35 ms te2-4.pte-gw2.plus.net [212.159.1.102]
6 40 ms 34 ms 36 ms linx-1.router.demon.net [195.66.224.12]
7 37 ms 37 ms 38 ms anchor-core-1-g0-0-1.router.demon.net [194.70.98.5]
8 36 ms 35 ms 37 ms anchor-inside-1-g1-0-0.router.demon.net [194.70.98.10]
9 * * * Request timed out.

That is a demon.net issue and not PN's .

Yesterday afternoon there were problems again with the route sticking at the PN router.

I am still waiting to know why! In its simplest form is this PN specific or will I still have the problem if I change to O2 LLU?

Meldrew

Personally my money is on the issues you regularly seem to have disappearing if you get shot of Plusnet from my experience.