This post was written by Michael Knighten, Founder & COO of Sleuth There are some similarities between deploying continuously and driving in the fast lane. When driving, you need to be always on the alert, proactively looking down the road for potential hazards. When you see them, you need to be able to react immediately, hit the brakes, and change course nimbly.

If you’re wasting precious time and resources responding to customer emails and phone calls whenever an incident arises - now sounds like a good time to set up your very own status page! A Statuspal status page is a professional and effective way to communicate incidents and maintenance updates internally for your team or publicly to your customers. You would be right in thinking that there are many options available and one of the largest operators in the market is Status.io.

Subscribe to Work Life Get stories about tech and teams in your inbox Subscribe When one of your IT services is on fire there’s no time to waste. Especially if that fire is blocking your users from getting stuff done. Rapid resolution tends to eclipse all else during an incident, often causing your team to ignore or forget pieces of the incident response process – like keeping people in the loop.

Here are the latest StatusHub updates for the last 3 months and news on the progress of our new control panel.

Following our latest updates, which, from now on, we’d love to share with you regularly, we’re happy to announce last month’s news. There’s always space for improvements while doing necessary maintenance, so let’s take a look at it.

Yesterday April 8th 2021 at around 22:00 UTC, Facebook experienced a major outage where Facebook, Messenger, WhatsApp web and Instagram were down, lasting for as much as 3 hours. This was reported at Facebook’s status page, which was a good example of how to communicate and incident.

Yesterday April 8th 2021 at around 22:00 UTC, Facebook experienced a major outage where Facebook, Messenger, WhatsApp web and Instagram were all down and unavailable. The last update was reported 3 hours later resolving the incident, so even though the status page doesn’t state the duration of the incident, we can assume it was still affecting some users that long.