The_Traveller
Active member
As of 8pm GMT Realm Works server is unreachable. I've tried on 2 different computers. One will not start as it cannot register the computer with the server, the other will start but will not login, Login Unavailable.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Dev's are aware.
Would have been nice to have some sort of post
Would have been nice to have some sort of post
Why did you need to be the one posting a "the server is down. We know about it and are working on it" post? If there was a dev working on it that same dev could surely have spent 30 seconds making that post on the announcement board or here.My apologies for not posting an official company update.
Unfortunately, this occurred the one time all week I stepped away and had spotty cell signal. By the time I returned the issue had already been fixed and consumers were posting as much. I’m just grateful the devs worked to repair the issue on their days off.
Why did you need to be the one posting a "the server is down. We know about it and are working on it" post? If there was a dev working on it that same dev could surely have spent 30 seconds making that post on the announcement board or here.
Why did you need to be the one posting a "the server is down. We know about it and are working on it" post? If there was a dev working on it that same dev could surely have spent 30 seconds making that post on the announcement board or here.
Not on any team I've ever managed and I've been a project manager for 15 years. When something like this happens off hours and a dev or two is dealing with an outage and a short post or tweet needs to be made just to let the users know that the team is aware of the problem, a fix is underway and possibly an ETA of when service will be restored there is no need to get the social media rep involved. That just adds more delay before the users get information they should have ASAP. As the incident Sunday showed they may never get the information at all. The may only find out service is restored by trying to use the service or by some other user doing so and then posting somewhere that it is back up. Which erodes confidence in the company's customer service.Actually it makes sense that the dev would not be the one making the update notification. Communication of issues normally would be sent via manager/talking head/spokesmonkey to ensure the appropriate information is given in a consistent format. it also ensures that the feedback is going to one focus point.
Not on any team I've ever managed and I've been a project manager for 15 years. When something like this happens off hours and a dev or two is dealing with an outage and a short post or tweet needs to be made just to let the users know that the team is aware of the problem, a fix is underway and possibly an ETA of when service will be restored there is no need to get the social media rep involved. That just adds more delay before the users get information they should have ASAP. As the incident Sunday showed they may never get the information at all. The may only find out service is restored by trying to use the service or by some other user doing so and then posting somewhere that it is back up. Which erodes confidence in the company's customer service.
If you can't count on your devs to post "We're aware the log in server is down. We're working on a fix and hope to have the service back up soon." you need to reconsider your devs.