This question was prompted by this answer by employee Mike Frank, from the SRE (Site Reliability Engineering) team.

In his answer Mike states:

We're looking at how we can better plan and notify for these type of events, as well as ways to increase resilience so no interruption in the process is necessary.

I think there already is a perfect way to notify users of these type of events, namely a post on the official "Stack Exchange Network Status" site https://StackStatus.net/. Combine this with a notification bar on the top of the screen that has the title of the status message and a link to the site. This can be limited to the affected pages when applicable, like in the case where Mike's answer was posted to.

Currently StackStatus is poorly maintained. Its Twitter account (@StackStatus) shows far more messages then the site itself does. Most notably the most recent scheduled maintenance wasn't even announced on stackstatus.net.

Can we please reinstate the usage of StackStatus.net and expand on its use, so that those of us that are unable to visit Twitter (e.g. in an environment where it's blocked) can be up to date as well?

  • 7
    This is something we've been discussing, making sure we use these communication tools more consistently. We'll come back and answer soon, once we have clarity across the team as to the specifics about posting these updates.
    – Mike Frank Staff
    Jun 22 at 20:58
  • 2
    Thanks for your reply @MikeFrank. I know that in most cases communication isn't the first thing that comes to mind when dealing with outages. You're busy looking for a fix. Users however are very eager to learn more, and to know when they can start using SE again. This is especially true for customers paying forna teams subscription of course. In that sense increased communication is highly desired. I don't think we'll need a status dashboard indicating health of all service though, that might be overdoing it.
    – Luuklag
    Jun 22 at 21:15

You must log in to answer this question.

Browse other questions tagged .