These days, I find it’s a requirement for vendors to provide operational status pages on their services. I say this because I know there are many companies who aren’t yet on-board. Status pages give your customers an immediate answer to the question, “What’s going on with X site?” or “Why does Y service seem slow today?”
A status page could be as simple as some of the third-party magic eight balls out there like Down For Everyone Or Just Me. But an effective status page will give more information than “yes” or “no”, and will communicate:
- Is the service or site down?
- How long has it been down?
- What is being done to fix it?
- When is the service expected to be back up?
Oh, and it probably warrants stating that you shouldn’t run these status pages on the same infrastructure that runs your site/service. If your servers, network, etc. go out of service, you want to be sure that your customers can still reach your status page.
Let’s get on to some examples:
Status page for Amazon’s Web Services which shows a separate status display for each of their infrastructure services. There are RSS feeds available for each service allowing you to subscribe to monitor service outages. One thing I like about this page is the “report an issue” link on the page, especially since it doesn’t require to to have your login credentials to quickly note an issue.
Similar in format to Amazon’s status page, this one also includes a running history of when the last issues occurred.
Status pages for Mosso and Dreamhost are fairly similar, they are both simple blogs. Support techs post issues when they arise and follow up with time-stamped messages when services are diagnosed and fixed.
This is by no means an exhaustive list but I think it highlights a few good examples. Why is this important? As much as I hate to use the phrase “controlling the message,” it is really important that your customers know that you’re on top of things… especially when they are paying you.
If you know of other good status pages, please feel free to add them to the comments below.