Plusnet site take "forever" to load pages & email problem too!

shutter · ‎06-11-2007

For the past 18 hours (apart from when I was asleep last night) loading PlusNet pages from google or bookmarks is taking between 60 and 90 seconds, but any other sites or pages are loaded instantly.
I have disabled my ZoneAlarm firewall, and this makes no difference to the time it takes to get a plusnet page to appear.
Email.... I use Thunderbird and for the same period, I have not been able to get my email being given the following

Alert
An error occurred with the POP3 mail server. Mail server Plus.Net responded :
OK

Well, really? what does that mean? NO.... it is not "OK" I want to get my mail..... what is the point of this useless "alert".... does anyone know what it means, and what action should be taken when it appears.......... apart from clicking "OK" and accepting that you ain`t gonna get yer mail.... OK?
(Yes I may well be able to get my mail with squirrelmail on webmail at plusnet.... but I really don`t want to wait while it loads, ).... (see above)

csogilvie · ‎04-04-2007

Hi Shutter
What gateway are you on?
There was a message about Email access on one of the gateways earlier - http://usertools.plus.net/status/archive/1250582342.htm

Strat · ‎14-04-2007

You can check which gateway you are on here http://usertools.plus.net/@gateway/.

Windows 10 Firefox 109.0 (64-bit)
To argue with someone who has renounced the use of reason is like administering medicine to the dead - Thomas Paine

shutter · ‎06-11-2007

Thanks for the link Strat....
here is the answer
You are currently connected to the "City Lifeline, Juniper 11" gateway. This gateway is sometimes known as pcl-ag04
not that it means anything to me !

shutter · ‎06-11-2007

@cso I only have a problem with the thunderbird email.... not the webmail..... (apart from the slowness of loading )

MrC · ‎17-07-2008

@shutter: you aren't the only one. It's been terrible here with PN sites taking minutes to load and often timing out.
A bit of analysis shows that it started at 19:03ish yesterday and routing to all PN sites on 212.159.8.n and 212.159.3.14 (usertools) is failing from here. Their equivalents on 212.159.9.n seem to be OK.
My gateway is currently pcl-ag03 and all other routing external to PN is OK.
Is anyone from PN Towers listening and available to take this up, or should I start the dreaded PN ticket tennis?

shutter · ‎06-11-2007

Quote from: MrC
@shutter: you aren't the only one. It's been terrible here with PN sites taking minutes to load and often timing out.

Is anyone from PN Towers listening and available to take this up, or should I start the dreaded PN ticket tennis?

Seems to be an overload problem on the server then..... perhaps they need to get a couple of new hamsters to turn the wheels a bit faster to clear the backlog.

James · ‎04-04-2007

Hi MrC,
Is there any chance your can try to get onto a non City Lifeline gateway (PCL-AG01-04).
I'd be interested to see if you still experienced the problem then.
Of course it's not ideal and it's certainly not how things should be running, but that could possibly tie in with the mail issues we've been experiencing.

shutter · ‎06-11-2007

Just done another check on the email side..... still the same problem..... and same "alert" message...

MrC · ‎17-07-2008

Quote from: shutter
Seems to be an overload problem on the server then.....

No, it looks like a problem with routing or load-sharing within PN Towers. There's a few other messages around on the forums and on Usenet with people complaining of slowness and access to various internal sites (including someone's home pages).

MrC · ‎17-07-2008

Quote from: Jameseh
Is there any chance your can try to get onto a non City Lifeline gateway (PCL-AG01-04).

Sorry for the delay but I've now given up trying to post from my home account and am accessing the forums by rdp from another account, so apologies for dodgy formatting etc

I powered off the router for about 30 mins and reconnected, this time via pcl-ag01, but with the same problem. Here's a couple of traceroutes that demonstrate the problem. Note that the first (& working) traceroute to 212.159.9.110 ends up at 212.159.1.146


lucy tmp # host community.plus.net                                                          
community.plus.net has address 212.159.9.110                                                
community.plus.net has address 212.159.8.110                                                
lucy tmp # traceroute 212.159.9.110                                                         
traceroute to 212.159.9.110 (212.159.9.110), 30 hops max, 60 byte packets                   
 1  duncodin-rtr (80.229.212.249)  64.599 ms  64.031 ms  63.539 ms                          
 2  lo0-plusnet.pcl-ag01.plus.net (195.166.128.27)  42.748 ms  47.630 ms  49.625 ms         
 3  gi1-2-803.pcl-gw1.plus.net (84.92.5.57)  60.684 ms  62.801 ms 68.477 ms                
 4  te2-2.pte-gw1.plus.net (212.159.0.186)  73.076 ms  73.078 ms  70.481ms                 
 5  * * *                                                                                 
 6  * 92.core.plus.net (212.159.1.92)  44.709 ms  45.074 ms                                 
 7  fhw-lb04.plus.net (212.159.1.146)  47.000 ms  46.711 ms  47.848 ms                      
 8  fhw-lb04.plus.net (212.159.1.146)  45.064 ms  45.767 ms *                               
lucy tmp # traceroute 212.159.8.110
traceroute to 212.159.8.110 (212.159.8.110), 30 hops max, 60 byte packets
 1  duncodin-rtr (80.229.212.249)  26.119 ms  25.563 ms  25.038 ms
 2  lo0-plusnet.pcl-ag01.plus.net (195.166.128.27)  42.695 ms  45.472
ms  50.581 ms
 3  gi1-2-803.pcl-gw1.plus.net (84.92.5.57)  143.680 ms  146.059 ms 
147.891 ms
 4  84.93.224.48.broadband.plus.dyn.plus.net (84.93.224.48)  157.700 ms 
162.605 ms  164.890 ms
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Incidentally the traceroutes from the working account are a bit different:-

C:\Users\Mike.Civil>tracert 212.159.8.110
Tracing route to community.plus.net [212.159.8.110]
over a maximum of 30 hops:
  1     2 ms     1 ms     1 ms  wrws-rtr [192.168.100.1]
  2    20 ms    19 ms    19 ms  lo0.plusnet.thn-ag2.plus.net [195.166.128.93]
  3    23 ms    20 ms    18 ms  vl604.thn-gw1.plus.net [84.92.4.169]
  4    17 ms    19 ms    18 ms  vl22.pte-gw1.plus.net [212.159.4.11]
  5    20 ms    19 ms    19 ms  te2-2.pcl-gw01.plus.net [212.159.0.185]
  6    26 ms    30 ms    28 ms  84.93.224.48.broadband.plus.dyn.plus.net [84.93
224.48]
  7    28 ms    30 ms    27 ms  84.93.224.51.broadband.plus.dyn.plus.net [84.93
224.51]
  8    26 ms    26 ms    27 ms  if25.pih-lb04.plus.net [212.159.0.18]
  9    29 ms    26 ms    26 ms  community.plus.net [212.159.8.110]
Trace complete.
C:\Users\Mike.Civil>tracert 212.159.9.110
Tracing route to community.plus.net [212.159.9.110]
over a maximum of 30 hops:
  1     1 ms     1 ms     1 ms  wrws-rtr [192.168.100.1]
  2    19 ms    18 ms    18 ms  lo0.plusnet.thn-ag2.plus.net [195.166.128.93]
  3    21 ms    18 ms    18 ms  vl604.thn-gw1.plus.net [84.92.4.169]
  4    42 ms   207 ms   215 ms  te2-3.thn-gw2.plus.net [212.159.1.58]
  5    18 ms    17 ms    19 ms  vl23.pte-gw2.plus.net [212.159.4.28]
  6    24 ms    24 ms    24 ms  92.core.plus.net [212.159.1.92]
  7    94 ms    38 ms    25 ms  fhw-lb04.plus.net [212.159.1.146]
  8    26 ms    24 ms    24 ms  community.plus.net [212.159.9.110]
Trace complete.

Here's an attempt to connect directly to the webservers :-


lucy tmp # telnet 212.159.9.110 80
Trying 212.159.9.110...
Connected to 212.159.9.110.
Escape character is '^]'.
telnet> close
Connection closed.
lucy tmp # telnet 212.159.8.110 80
Trying 212.159.8.110...

If you need me to run any other form of diagnostics please shout (loudly...)

MrC · ‎17-07-2008

@jameseh: I'm not sure it's relevant but my non-working account (duncodin) has a /29 network; the working one (weystation) has a single static address.

shutter · ‎06-11-2007

Have been "out" (getting my car filled up with diesel) for about an hour, and just checked my email...... still the same problem..... still the same alert message

the pages on plusnet site seem to be back to normal though.!

James · ‎04-04-2007

Gerry - A reboot may solve your problems.
We believe this to just be affecting City Lifeline gateways (the ones that start PCL). So if you can get onto a different one, things should be ok.
Networks have been working on this solidly all day, and believe it to be related to load on a switch.
I've updated service status, but as per your post (and reports we're getting from the CSC), it doesn't seem to be fixed yet.

pierre_pierre · ‎30-07-2007

dont know what I was on, did have a good line up to 13:00 when the Cannabis Junkies caused a one hour power cut, then could not get lots of things, just rebooted and now on Telehouse North, Juniper 6" gateway. This gateway is sometimes known as thn-ag1. ,
Can at least get that

Plusnet site take "forever" to load pages & email problem too!

Plusnet site take "forever" to load pages & email problem too!

Re: Plusnet site take "forever" to load pages & email problem too!

Re: Plusnet site take "forever" to load pages & email problem too!

Re: Plusnet site take "forever" to load pages & email problem too!

Re: Plusnet site take "forever" to load pages & email problem too!

Re: Plusnet site take "forever" to load pages & email problem too!

Re: Plusnet site take "forever" to load pages & email problem too!

Re: Plusnet site take "forever" to load pages & email problem too!

Re: Plusnet site take "forever" to load pages & email problem too!

Re: Plusnet site take "forever" to load pages & email problem too!

Re: Plusnet site take "forever" to load pages & email problem too!

Re: Plusnet site take "forever" to load pages & email problem too!

Re: Plusnet site take "forever" to load pages & email problem too!

Re: Plusnet site take "forever" to load pages & email problem too!

Re: Plusnet site take "forever" to load pages & email problem too!