usenet.plus.net

[#1]

Yep I am another 'more established' user who has noticed this and raised an issue.  Also another user who has a static IP.

For me it went down yesterday afternoon, and is still down.

[#2]

I've just tried to access usnet using Thunderbird. I'm now being asked for a username and password.
So ... it's not working

[#3]

---

@Jaggies wrote:

Don't think it is Geo-related, as I have a static IP address. More likely Plusnet haven't paid the bill...

---

We definitely have paid the bill.

Authentication is IP-based so you should never need to enter login credentials.

The allowed IP definitions look perfectly fine to me, so whatever the issue is - it is likely within Giganews' remit.

[#4]

---

@Jaggies wrote:

Just to add my name to the list of those also affected. Using news.plus.net here.

---

+1

Just chipping in to show there are quite a few of us usenetters still around.  😉

[#5]

Sorry, just being facetious...
I have a vague memory of something like this happening before, but can't recall the details. I mainly use news.individual.net, only using the Plusnet news server for the Plusnet groups, sparsely populated thoug they are these days.

[#6]

Looks like this has been fixed now.

[#7]

Started doing this to me yesterday (in Thunderbird, just like the OP), but it seems to have been fixed/fixed itself in the last couple of hours.

[#8]

Not here it hasn't - it is still asking for authentication.

[#9]

Yes working for me now.

[#10]

text.news.plus.net is working for me again now. Looks like it's fixed.

[#11]

usenet.plus.net now working again for me as of 6pm 11 Jan 2022.

[#12]

OK. My system was still requesting authentication until I did a reboot. Looks ok now - must have been something cached somewhere.

[#13]

👍🏽

[#14]

Here's the response to my ticket.

Dear Mr Ruck,

Thanks for getting in touch to let us know of the issues you are experiencing with Usenet currently.  Many of our customers use this forum (similar to the forums on the Plus.net website) so we have raised this as an incident.  It has been identified that the issue is with the vendor of the Usenet service (a company called Giganews).  They have been informed and this will be looked at, there is nothing we can currently do due to this being a third party company responsible for the fix, but we will continue to monitor the issue where we can.



Kind regards,  
 [CSA Removed]

Moderators Note: CSA name removed as per Forum rules

[#15]

Thanks all.

I'm not party to the specifics, but we also received word from Giganews last night confirming the issue has been rectified.

Shout if things go wobbly again.