4 Important Tips for Using Status Pages



First and foremost…the woman in the picture looks stressssssed out!
Tip #1: Don’t be that person

Now you may be wondering why the woman in the picture (above) is in such dire straits (and no, we are not talking about the legendary band from the 80′s). It may be because someone told her to look frustrated in order to take some excellent stock photos…but for the sake of this blog post let’s imagine she’s you (yup, that’s right) right after you find out your site/app (or a section of it) has been down for the past hour and you have no way of telling  your customers. No one’s having fun in this scenario :(

But what could you have done to prevent this?

Well there’s a whole bunch of things…but we’re really only here to talk about "statushub's", so I’m going to focus on that.

Here’s a fact everyone already knows: Websites go down. There’s no point in arguing this fact, no matter how much infrastructure, failover, backup, etc at some point or another your site is going to experience downtime. But if your website is down, how do you alert your users to tell them what’s happening?

Tip #2: Get an offsite status page ( your very own "statushub")



Know what’s great about offsite status pages? They’re offsite! That means when your site goes down (let’s face the facts – it happens) you’re still able to communication with your customers. In the event there is a crisis, your  engineering team will be working around the clock to fix the problem. In these types of situations communication with your customers can fall through the gaps, and you definitely do not want that.

Another thing to keep in mind is that sometimes it’s not your entire site that will go down. Quite often an error will only effect a small percentage of your site. If that’s the case, your users will have no idea something is wrong until it’s too late – like when they’re trying to use your broken e-commerce checkout…

“Captain, prepare the site for a rage-quit!”

But it doesn’t have to be this way. By having a "statushub" in place you are able to let your users know that you know there is a problem and you’re working to fix it. They’re able to subscribe to receive notifications when you are experiencing issues. Instead of using "support@company.com" or shouting down the phone at you when things are wrong, they can keep an eye on things by using your "statushub". This will reduce the massive amount of inbound support tickets/ support calls you receive in the event of an issue.

*Cheers of joy from the support team*
Tip #3: Anyone can be a user

Were you thinking this whole time that statushub was only for your customers?

No! Your "statushub" can be configured to be used by anyone, maybe even your own team. By setting up a private "statushub" you can give access to your team, another department, a specific sub-set of customers, but most importantly – not the entire world.

Tip #4: Use statushub

StatusHub provides a beautiful solution for status pages and gives you complete control over communicating with your users in the event of a crisis. If you haven't spotted yet it also does everything mentioned above ;)



Now that you know how important a "statushub" is you no longer have to live in fear of customers rage-quitting when something on your site breaks. But to prove you really are as smart as we think you are, you should ensure you have a "statushub" set up in the event of any future issues.


With cool features like this it no wonder companies Telenor Digital, Citirix, University of Gloucestershire, and Michigan State University are proud owners of a "statushub".

If you don’t already have one you can always pop over to statushub.io and grab one for your site.

Still not convinced that statushub is the Bees Knees? Check out this awesome video and see if we can change your mind.