It takes a village to respond to and resolve incidents. But the teams involved in incident response often work in silos: SREs and devs are heads down fixing the problem, support is flooded with emails/tickets, and marketing/PR may be putting out fires on Twitter. Even if there’s some communication happening over chat or across desks, there’s typically room for improvement with getting these teams to work together when it matters most.

Automatic Twitter posts from Statuspage incident updates now link together into one Twitter thread. This update applies to Tweets that are posted automatically via the Statuspage Twitter integration.

Automatic Twitter posts from Statuspage incident updates now link together into one Twitter thread. This update applies to Tweets that are posted automatically via the Statuspage Twitter integration.

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.

If you’re hosting on AWS, you can expect some pretty excellent reliability and availability. If your service isn’t responding, it’s likely an issue with your own code. On the other hand, system outages do happen. They’re usually pretty minor. Sometimes they're not.

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.