Over the years here at Statuspage we’ve probably heard every version of the open source vs. paid status page argument. While we’re obviously fans of the SaaS model, we also know there are a lot of advantages to an open source status page for a lot of teams. We’ve even recommended that route to some potential customers we thought would have a better experience hosting their own open source page.

An incident postmortem is an excellent framework for learning from incidents and turning problems into progress. It also builds trust with customers, colleagues, and end users (basically the folks affected by the incident) and lets them know your team is working to minimize future incidents and impact.

Nothing puts a drag on IT service teams and customer support teams like answering the same question across multiple tickets. Outages and incidents have a way of sending these teams an avalanche of duplicate tickets. During a service interruption, tickets start flying in, the team can’t keep up, and end users have a bad experience made even worse.

We’ve talked about the increasingly-interconnected nature of cloud tools and the domino-goes-crashing-down effect thatcan happen when just one critical service has downtime. Web uptime is more important than ever, and it’s critical that these services we all rely on are up and running as often as possible.

The unfortunate reality about running a web service is that every now and again, you’re going to have downtime. Even the best web companies have the occasional blip in service. If downtime is inevitable, then it’s best to plan ahead so that you can be ready. After all, prior preparation prevents poor performance.