An outage with one, several or all of your servers is hectic enough, but add in a stream of emails and phone calls from concerned customers and you’ve got a full-on situation. When you start receiving these emails, phone calls or texts from clients who need access to their applications on these servers, you may have to individually answer each request in an emergency or during scheduled maintenance.

Have you ever seen a tweet like this and wondered what it was? It’s #HugOps! We’re sending you some giant #HugOps today (and every day), and hope that after reading this you feel inspired to pass on some #HugOps, too.

Each day, dozens (sometimes hundreds) of incidents and maintenances are created on the Status.io platform. We’ve analyzed and studied thousands of these events to help us learn how to improve the tools based on our users’ needs. Today we’re announcing a couple of updates that enhance and streamline the incident and maintenance processes. Let’s dive in!

Letting the right people know about incidents is an easier-said-than-done kind of task. Every incident is different and some notifications simply don’t need to land in everyone’s inbox. We’ve listened to a lot of customers who like the idea of posting an incident to their status page, but not having that incident sent as notifications to all their subscribers.

Want to share your latest monitoring status with your users? Want to notify your visitors about scheduled maintenace /downtime? You can do this very easily with AppBeat.