Status.subeta.net
Filter
Show Official Posts OnlyReplies
It was nice to see warnings on both FB and Twitter last night, thank you for that!
Hopefully the status site will get more love as you guys get used to it :)
then you set the mask upon your face
my silhouette in the air you trace
and the dagger performs with a start
We're actually working on a bit of a hub on the back-end that will allow us to update "everything" (the actual "site is down" page, the technical status page, and our social media sites), in one fell swoop. This will help whoever is online at the time of trouble get the message out to as many mediums as possible.
Hmm. Another lengthy period when the site was inaccessible to lots of people, with not a blip on status.subeta.net. Can we agree that whatever functionality that site's supposed to provide is not informative to Subeta's end users?
I do not know what is worse: the fact that this status site doesn't really accomplish what it was created to do OR the fact that we seem to actually NEED this site rather regularly. :(
Staff didn't update anywhere else, either. Really not okay.
Even worse than staff not updating anywhere else, they actually did directly reply to one whole tweet directed at them about the situation on twitter, but didn't feel it was important enough to actually make a tweet about it themselves, I guess. Even though the problem persisted for hours after the promise of 'we'll be back up in a few minutes.'
So unless you happened to be looking at their replies on twitter, nobody would have even seen that staff was aware, much less know what was going on.
The lack of communication for this sort of thing is so frustrating. What are any of us supposed to think when the status site tells us nothing of value and staff can't- or won't -communicate with us in a meaningful way when something goes wrong?
So tonights status.subeta.net update was, again, my fault. The staff asked in our slack channel about the 404 pages and I responded saying "That's what happens when new servers spin up" (my same response as on tumblr) - then the problem ended up being something entirely different.
I tried to update the status site from my phone but unfortunately the dashboard wasn't really set up for mobile and couldn't submit. Instead I sent a status report and a fix to who resolved the problem and brought the 404 pages to an end by removing the faulty server from our loud balancer.
Some takeaways:
- Fix the status site for us updating from mobile, obviously.
- Change the algorithm for removing servers from the load balancer automatically. Right now it does that if it can't be reached by a server-to-server connection (SSH) or loaded at all in a browser. That doesn't account for 404/etc errors. I'm going to change that so if a 404 error happens, it removes it from the load balancer in the health check.
We're working on this, our goal is obviously complete communication and transparency. I realized I also don't have the Subeta twitter on my phone which I corrected tonight as well.
💖 ✨ 🤗
