Usenet still up the spout after upgrades.

[#1]

I assume the news about the news server is that there is no news available?
My latest attempt shows - no news...

Quote

Sun Apr  6 10:41:01 2008 - Pan 0.129 started Sun Apr  6 10:41:12 2008 - Expired old score from /home/jeremy/.pan2/Score, line 76 Sun Apr  6 10:41:12 2008 - Expired old score from /home/jeremy/.pan2/Score, line 99 ... Sun Apr  6 10:41:12 2008 - Expired old score from /home/jeremy/.pan2/Score, line 108 Sun Apr  6 10:41:12 2008 - Expired old score from /home/jeremy/.pan2/Score, line 11972 Sun Apr  6 10:41:12 2008 - Read 1336 scoring rules in 9 sections from "/home/jeremy/.pan2/Score" Sun Apr  6 10:41:12 2008 - Loaded data backend in 0.2 seconds Sun Apr  6 10:41:23 2008 - Sending "AUTHINFO USER moiety" to news.plus.net returned an error: 502 Access Denied via @ auth server Sun Apr  6 10:41:23 2008 - Sending "AUTHINFO USER moiety" to news.plus.net returned an error: 502 Access Denied via @ auth server Sun Apr  6 10:41:23 2008 - Sending "AUTHINFO USER moiety" to news.plus.net returned an error: 502 Access Denied via @ auth server Sun Apr  6 10:41:24 2008 - Sending "AUTHINFO USER moiety" to news.plus.net returned an error: 502 Access Denied via @ auth server Sun Apr  6 10:41:29 2008 - Expired 2 old articles from "comp.text.tex" Sun Apr  6 10:41:29 2008 - Loaded 55 articles for "comp.text.tex" in 0.0 seconds (3537 per second) Sun Apr  6 10:43:33 2008 - Sending "AUTHINFO USER moiety" to news.plus.net returned an error: 502 Access Denied via @ auth server Sun Apr  6 10:43:38 2008 - Sending "AUTHINFO USER moiety" to news.plus.net returned an error: 502 Access Denied via @ auth server

(I realise there's my user name present in that log).

[#2]

Come on PlusNet please sort out the usenet problem, it's been here for almost a week and hardly ever gets updated on the service status page. It only affects users with IP's of 212.159.x.x, and I fall into one of those....
Ticket has been raised as per the service status - 24664590

[#3]

Can anyone still having problems accessing the USENET service PM me their IP address and I'll chase this up with our networks team.

[#4]

212.159.47.11  here will still not connect with '480' authentication error.
This is getting tedious now, it has been a week for something that was supposed to be a day.
Do I get a discount on my monthly fee now?
Alan.

[#5]

Chris, PM sent. Still unable to connect this afternoon. Thanks.

[#6]

Quote from: darkroom

212.159.x.x  here will still not connect with '480' authentication error... Alan.

Alan, you would be better PM'ing your IP rather than allowing all and sundry to see in the main forum (modify your post above).

[#7]

Pm'd my IP yesterday...
Still borked

[#8]

can you explain in plain English as its not in the large Oxford dictionary

Quote

Still borked

[#9]

Morning all,
Assuming you have raised a ticket about your issues then I should be able to have access restored for you all at some point this morning. Apologies for the continued inconvenience on this one. It's been a pain I know

[#10]

http://incontext.blogmosis.com/archives/015361.html

[#11]

Quote from: Bob

Assuming you have raised a ticket about your issues then I should be able to have access restored for you all at some point this morning.

It's a bad idea to specify a time 
Usenet is still down and it's 18 minutes into the afternoon...

[#12]

Quote from: Bob

Morning all, Assuming you have raised a ticket about your issues then I should be able to have access restored for you all at some point this morning. Apologies for the continued inconvenience on this one. It's been a pain I know

Are the performance issues also being addressed Bob?  Message body download is still very slow.
Maurice

[#13]

Well mines started working

[#14]

Everybody who raised a support ticket should now have access restored. Maurice, there shouldn't really be any performance issues TBH. I wonder if the traffic's being prioritised correctly?
I'll run a quick Wireshark capture.
Edit - seems like it's in the Gold traffic queues which is where it should be

[#15]

Quote from: Bob

Everybody who raised a support ticket should now have access restored.

Mine is certainly fixed now. Thanks!