Anything bad that can happen — will happen. This old adage applies 100% to the technology industry, where crashes and outages are far more common than the sales and marketing teams would want us to think. However, DevOps engineers that deal with infrastructure know how hard it is to ensure everything works as intended all of the time — and to configure monitoring that actually keeps track of a system’s health and helps prevent crashes and downtime.

COVID-19 has impacted every single aspect of our lives as we knew them. Almost overnight, businesses had to create an entirely new working environment, parents had to become teachers and essential workers become the real heroes. As time goes on, more and more businesses are transitioning to 100% remote workforces.

Check out the latest StatusHub updates and features, including bi-weekly schedule changes in widget, domains whitelist and more for the last two months. And We are happy to share with you that the new control panel is coming this autumn!

Often, outages are planned. In fact, in most organizations, outages are typically not caused by something going wrong, but because some kind of IT operation requires your team to take a system temporarily offline. Communicating scheduled maintenance is just as important, if not more important than alerting users to unplanned outages.

There’s nothing worse than turning on your computer to start the work day and discovering the internet is down. We all know the frustration of tediously trying to figure out what’s wrong before finally breaking down and calling our service provider and waiting on hold, only to discover that it’s a known issue and it’s being addressed. What if there was a better way?

A well-crafted status page is designed to save you time, energy, and resources when communicating service irregularities. Instead of fielding thousands of support requests when you experience an outage, a status page provides a self-service way for your customers to get up-to-the minute information about any current downtime. It also allows you to proactively communicate maintenance and other work in advance.

Communication is one of the hardest things to do well while responding to incidents. At FireHydrant, we’ve focused on helping people communicate well within their teams when responding to incidents, and also after the fact during post-incident reviews. But what about communicating with your customers? During an incident, your customers want to know that you’re aware of the problem and are working to mitigate or resolve it.