Usenet still up the spout after upgrades.

[#1]

Quote from: mbeenham

Since PN are unable to tell who can connect to Usenet and there is a fair bit of evidence from this forum that there is probably a fair cross-section unable to do so  it would be more honest to mark it as red for now, if only to highlight it within PN organisation and maybe galvanise somebody to sit on Giganews until it is fixed.

Status is now red.

Quote

A service update would be nice - just checked and still the same message from 17:59 yesterday

Have just posted an update (if you can call it that )

Quote

From Plusnet Newsreader on the portal which is failing also: List of Newsgroups Number of Postings     plusnet.announce  authentication   plusnet.chat  authentication   plusnet.games.general  authentication   plusnet.games.halflife  authentication   plusnet.games.quake  authentication   plusnet.games.unreal  authentication   plusnet.service.announce  authentication   plusnet.service.customer-feedback  authentication   plusnet.service.status  authentication   plusnet.social.chat  authentication   plusnet.social.forsale  authentication   plusnet.tech.dialup  authentication   plusnet.tech.e-commerce  authentication   plusnet.tech.general  authentication   plusnet.tech.hardware  authentication   plusnet.tech.linux  authentication   plusnet.tech.mysql  authentication   plusnet.tech.software  authentication   plusnet.tech.usenet  authentication   plusnet.technical-journal  authentication   plusnet.test  authentication   plusnet.test.customer-feedback  authentication   plusnet.www.announce  authentication   plusnet.www.cgi  authentication   plusnet.www.frontpage  authentication   plusnet.www.webdesign  authentication Presumably this does not relate to my ip address...

No it doesn't and yes it's the same for me.

[#2]

Quote

author=Bob link=topic=62838.msg508094#msg508094 date=1207044192] Status is now red. Have just posted an update (if you can call it that)

Thank you, and yes - I call that an update!
It demonstrates that PN have a grip on the problem scope (if not a solution yet ;)).
Good! Better late than never - leave you in peace now for a little while...

[#3]

Some more info here.

[#4]

This particular SNAFU is small beer compared with Terminal 5, but Giganews and BA/BAA seem to have adopted the same approach - "We won't bother with proper testing, just go ahead and do it. We can fix any problems later and to heck with the customers." An attitude all too prevalent in the business world today.
Jim

[#5]

Quote

It would seem that Giganews do not allow netblocks to be shared across reseller accounts.

Well Giganews/Supernews must have known all about the netblocks before they decided to embark on a half-assed migration. Seems a case of negligence pure and simple.
Does PN really want to be asociated with cowboys that will do their reputation no good at all?
Please feel free to pass my comments on (in fact I would be delighted if you did).
Hopefully PN is ensuring someone at Giganews will be working through the problem and not going home until its fixed. Sounds like an administration/commercial issue which should not be allowed to impact on PN users access to the service.

[#6]

Usenet has just leapt back into life here.
Thank you PlusNet.

[#7]

Can confirm the same thing here. Ah well.... nice to be working again and not exactly the end of the world that is wasn't, but will still be interesting to see what the actual problem was & resolution.

[#8]

Well not working here yet 
Hopefully Giganews are working their way through the netblocks they should have enabled 24 hours ago.

[#9]

Not working here either.

[#10]

Quote from: pittdj

Usenet has just leapt back into life here

Working here too, but BOY is the new server full of spam compared to the old one 

[#11]

Quote from: mbeenham

Well not working here yet  Hopefully Giganews are working their way through the netblocks they should have enabled 24 hours ago.

nor here yet
Don't like the sound of all that spam, I have few groups I use but its part of the daily routine and I have enjoyed them not being full of the rubbish others get.

[#12]

Hi
Not working for me yet, I suppose it will take a while.

[#13]

Quote from: vibes

Hi Not working for me yet, I suppose it will take a while.

And not here either.
So, let's recap on this problem.
We don't know exactly what the problem is; we can only surmise rather than accurately identify the problem.
We don't know how long it'll take to fix it.
We don't know the scope of the problem, or how many customers might be affected.
We didn't realise that web-based Usenet access (through our portal) was borked.
We don't know if we have an SLA in place with our service provider.
There doesn't appear to be any meaningful communication between the comms team and the back-end technicians who are supposed to be fixing this.
We don't know what the service provider is doing to fix the problem.
We don't appear to have tested this changed service before it went live.
We don't appear to have planned this changeover adequately and we had no change management contingency plan to account for problems during or immediately after the switchover.
Despite the service status (finally) showing red, we're not planning to issue more than one update in a full 24-hour period.
Is that a fair outline of where PlusNet is with this?


Latest from the ping...
ping news.plus.net
Pinging plusnet.vsrv-ams.supernews.net [138.199.67.64] with 32 bytes of data:
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Ping statistics for 138.199.67.64:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss).
ping sn-ip.vsrv-sjc.supernews.net
Pinging sn-ip.vsrv-sjc.supernews.net [216.168.3.44] with 32 bytes of data:
Reply from 216.168.3.44: bytes=32 time=94ms TTL=111
Reply from 216.168.3.44: bytes=32 time=144ms TTL=111
Reply from 216.168.3.44: bytes=32 time=87ms TTL=111
Reply from 216.168.3.44: bytes=32 time=136ms TTL=111
Ping statistics for 216.168.3.44:
Packets: Sent = 4, Received = 4, Lost = 4 (0% loss).
Approximate round trip times in milli-seconds:
Minimum = 87ms, Maximum = 144ms, Average = 115ms

[#14]

Interesting...
From my address 87.112.5.162
Pinging news.plus.net [138.199.67.64] with 32 bytes of data:
Reply from 138.199.67.64: bytes=32 time=30ms TTL=48
Reply from 138.199.67.64: bytes=32 time=28ms TTL=47
Reply from 138.199.67.64: bytes=32 time=28ms TTL=48
Reply from 138.199.67.64: bytes=32 time=29ms TTL=47
news.plus.net is still refusing service though, seems to think I'm not on PN network 
Could it be that PN wants me to go back to Demon? No chance - they don't get off that easy!
 
BTW, anybody know the email address for Ron Yokubaitis, CEO of Giganews? My email to him bounced so I guess I've got an old addy...
Cheers

[#15]

I am back. My static IP is 84.92.108.121. Giganews aint as bad as that although reports from the customer-feedback newgroup say that their porn filters are quite inadequate. I will have 2GB to download for my 60 newsgroups so I will do that in my Free time.