Phone Troubleshooter - is it working for you?

[PlusnetLiam]

Hi guys

I'm after some help, please :)

We're having some reports of customers not having the best experience when trying to diagnose an issue with their phone line, however, we're really struggling to pinpoint what the exact issue is.

If I could ask a few of you to login to https://www.plus.net/my-account/tools/phone-troubleshooter/ & go through the steps & let me know what you see - does it produce an error? Does it time out etc? If you can then message me with your username I can then check in the background what's happened & close off any unnecessary tasks.

Thanks in advance

Liam

[Adamtemp]

message sent

[Mustrum]

It seemed to be OK, but then it reported:

"Oops, something seems to have gone wrong"

[MauriceC]

Just tried a minute ago and got.

Service Unavailable

The service is temporarily unavailable. Please try again later.

[dvorak]

clicking the link gives:

Something's gone wrong...

We're sorry. There's been a problem, but don't worry, we're working hard to fix it. In the meantime, try refreshing your page.

If that doesn't work, contact us to report the problem.

[PlusnetLiam]

Thanks guys, seems we do have a problem then! We'll get straight on to it.

Thanks!

[Morgs]

I cannot see if you think this issue has been resolved ('We'll get straight on to it' 25 Jan 2017). However, when I used the phone line checker at the weekend (22/09/2018) I got the same message. As I thought the line had not been checked, I went through the process again and as a result there were two messages waiting for me on my plus net home paqge to tell me that a fault - T117 - had been detected on my line.

I suspect that on discovery of a fault by OpenReach that the handover from OpenReach back to Plus.Net is in somehow failing and as a result the plus.net webpage is left hanging, which then times out with the 'Whoops' message.

[Townman]

Hi @Morgs,

A warm welcome to the forums.

The process has been somewhat improved since this post was created (the problem was much more common), though there are still occasions where the UI repots an error, even though a ticket has been raised successfully.