There are as many ways to trigger an incident as there are new code deployments across the globe and, with the emergence of cloud-reliant businesses, uptime accountability has shifted from on-premise server teams to the service providers themselves. SLAs, SLOs, and websites dedicated to downtime have suddenly come to life in the internet age, and having a status page is now an industry standard. Just check out Dropbox, DigitalOcean, Apple, Reddit, and New Relic for a few examples of companies using status pages as a key part of their incident management process.
So, even if we agree that incident communication is important, what exactly is it about status pages that make them the go-to solution in today’s world?
It’s hard to build your own solution
A common problem with a homegrown status page is that when your website is down, so is your status page. We’ve been in the game for a while and spent a long time building our own status page on a completely separate…